Marginalia

Privacy Policy

Last updated June 2026. This policy covers Marginalia, the private manuscript-submission tracker used by literary agents to follow their own submissions through their own email.

The short version

Marginalia reads your submission correspondence so it can keep a ledger of which manuscripts are with which editors. Your mail is used for that and nothing else. We do not sell it, we do not advertise against it, we do not use it to train AI models, and no member of staff reads it except in the narrow cases described below. Each agency's data is isolated in its own workspace: other agencies using Marginalia cannot see yours.

What we access in your Google Account

When you connect Gmail, Google asks you to grant these scopes. We request no others:

gmail.readonly
Read-only access to your Gmail messages. We use it to find your submission correspondence — messages matching the subject-line patterns you configure (for example Your Agency/) — and the replies in those threads. We never modify, delete or label anything in your mailbox.
gmail.send
Permission to send mail as you. Used only when you explicitly click to email a submission report to one of your authors, so that it arrives from your own address and their reply comes back to you. Nothing is ever sent without you pressing the button.
userinfo.email · userinfo.profile · openid
Your email address, name and profile picture, used to sign you in and to show who made a change in a shared agency workspace.

What we store, exactly

For each message that matches your submission patterns, we store in our database:

  • subject, sender, recipient, date, and whether it was sent or received
  • the message body text, so the ledger can show you the correspondence and detect replies, passes and offers
  • Google's message and thread identifiers, so we recognise a message we have already seen and can link you back to the thread in Gmail
  • a short AI-written summary of the message (see below)
  • the names of any attachments, but not their contents

Alongside that we hold the submission ledger you build from it (manuscript titles, authors, editors, publishers, statuses, dates, your own notes), your editor directory, and your settings.

What we do not store: messages that do not match your submission patterns are never written down — they are filtered out during the sync and discarded. Attachment file contents are fetched from Gmail only at the moment you ask to view or save one, and are only kept if you deliberately save one to an editor's record. We never store your Google password.

To keep your mailbox connected, we store Google's access and refresh tokens for your account. They are held in our database and used solely to call the Gmail API on your behalf.

AI processing

To turn an email into a ledger entry — who the editor is, which manuscript it concerns, whether a reply is a pass or an offer — we send the message text to Anthropic's Claude model through our AI gateway provider. Up to roughly the first 6,000 characters of a message body may be included.

That processing is automated and transient: the model returns structured fields and a summary, which we store. Our AI provider does not use this content to train their models. No advertising profile is built from it, and it is not shared with any other third party.

Who else is involved

  • Other people in your agency workspace. If your agency has more than one member, they see the agency's shared editor directory and submissions. Nobody outside your workspace does.
  • Our hosting and database providers, who store the data on our behalf under contract.
  • Our AI gateway and Anthropic, as described above.
  • Our email provider, if you switch on the weekly digest — it delivers that summary to the address you choose.

We do not sell personal data, and we do not transfer it to advertisers, data brokers or model-training datasets.

Limited Use commitment

Marginalia's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically, Google user data is used only to provide and improve the submission-tracking features you can see in the app; it is not transferred to others except as necessary to provide those features, to comply with applicable law, or as part of a merger or acquisition with notice; it is not used for advertising; and no humans read it except with your explicit permission for a specific support issue you raise, to comply with applicable law, or where required for security.

Keeping control, and deletion

  • Disconnect Gmail at any time in Settings. We discard the stored tokens and stop syncing immediately.
  • Reset imported data in Settings → Danger Zone erases the submissions and email records we imported from your mailbox.
  • Revoke access at Google from your Google Account permissions page, which cuts our access off at the source.
  • Delete everything — including your account and workspace — by emailing abigail@redfoxliterary.com. We action deletion requests within 30 days.

We keep your data for as long as your workspace is active, because the ledger is the product. We do not retain copies after deletion beyond short-lived encrypted backups.

Security

Access requires a signed-in Google account, and every request is scoped to your workspace. Data is stored on managed database infrastructure with encryption at rest and in transit. Gmail is accessed over HTTPS using OAuth tokens rather than passwords, so your Google credentials never reach us.

Contact and changes

Questions, requests, or anything that looks wrong: abigail@redfoxliterary.com. If this policy changes in a way that affects how your mail is handled, we will update the date at the top and note the change in the app.