Legal
Privacy Policy
Last updated November 7, 2026
InboxToll filters email from people you don't know and asks them to pay before their message reaches your inbox. To do that, we need limited access to your mailbox. This policy explains exactly what we access, why, who we share it with, and how to delete it. InboxToll is operated by The National Correspondent LLC ("InboxToll", "we", "us").
The short version
- We read email headers (sender, recipients, subject, date, and authentication results). We never download, store, or read the body of your email.
- We use your contacts and the people you've emailed only to make sure they're never charged.
- We don't sell your data, show you ads, or use your Gmail or Outlook data to train AI models.
- You can disconnect your mailbox at any time; we then delete our access tokens.
Information we access from your Google account
When you connect Gmail, you grant InboxToll these Google permissions:
- Gmail (read, compose, send, and manage labels; no permanent deletion), to: read the headers of new messages to decide whether a sender is someone you know; move messages from unknown senders into an "InboxToll/Pending" label and back to your inbox; send one automated payment request from your address, in the same thread, to an unknown sender; and read the recipients of messages you send, so those people are never charged.
- Contacts (read-only), to: add the email addresses of your Google contacts to your whitelist so they're never charged.
We do not request access to message bodies or attachments, and our software never fetches them. We store the subject line only for messages we hold, so you and the sender can identify them, and we store sender and recipient email addresses as needed to run your whitelist and block list.
Information we access from your Microsoft account
When you connect Outlook (Outlook.com, Hotmail, Live, or Microsoft 365), you grant InboxToll these Microsoft permissions, used the same way as the Google permissions above:
- Mail.ReadWrite and Mail.Send, to: read the headers of new messages; move messages from unknown senders into an "InboxToll Pending" folder and back to your inbox (marking paid ones with an "InboxToll Paid" category); send one automated payment request from your address to an unknown sender; and read the recipients of messages you send, so those people are never charged. We never permanently delete mail.
- Contacts.Read, to: add your Outlook contacts' email addresses to your whitelist.
- User.Read, openid, email, and offline_access, to: learn which mailbox you connected and keep filtering while you're away.
As with Gmail, we never request message bodies or attachments, and we handle data received from Microsoft under the same commitments listed below: no advertising, no sale, no AI training, and no human reading except as described.
Google API Services User Data Policy (Limited Use)
InboxToll's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, information we receive from Google APIs:
- is used only to provide and improve InboxToll's user-facing filtering and payment features described above;
- is not transferred to others except as necessary to provide those features, to comply with law, or as part of a merger or acquisition with notice to you;
- is not used for advertising, and is not sold;
- is not used to train generalized or non-personalized AI or machine-learning models; and
- is not read by humans, except with your explicit consent for specific messages, for security purposes such as investigating abuse, to comply with law, or when the data has been aggregated and anonymized.
Other information we collect
- Account information: your email address, a hashed password (if you don't sign in with Google), your display name, handle, and settings.
- Payout information: handled by Stripe. We receive your Stripe account ID and whether payouts are enabled. We never see your bank or card numbers. If you choose wallet payouts, we store the public wallet address you provide.
- Payments from senders: amount, status, and the Stripe payment identifiers for messages paid to reach you. Sender card details go directly to Stripe.
- Activity log: a record of what InboxToll did with each message (held, payment requested, paid, released), so you can audit it.
- Technical data: standard server logs (IP address, browser, timestamps) kept for security and debugging. We don't log email content.
Senders who receive a payment request
If you email an InboxToll user who doesn't know you, we process your email address, display name, the subject of your message, and the authentication results added by the recipient's mail provider, to decide whether to send you a single payment request and to deliver your message if you pay. We do not read your message body. Payments are processed by Stripe under Stripe's privacy policy.
How we protect your data
- Google and Microsoft access tokens are encrypted at rest with AES-256-GCM using per-record keys, and are readable only by our backend services.
- All traffic is encrypted in transit (TLS).
- Database access is restricted by row-level security, so each user can read only their own records.
Service providers we share data with
We share data only with providers that help us run InboxToll, under contracts that limit their use of it:
- Google: Gmail and Contacts APIs, at your direction.
- Microsoft: Microsoft Graph (Outlook mail and contacts), at your direction.
- Stripe: payments, payouts, and identity verification for payouts.
- Supabase: database and authentication hosting.
- Vercel: application hosting.
- Inngest: background job processing (message identifiers and job metadata, not email content).
- Email delivery provider: account emails such as sign-up confirmation.
We may disclose information if required by law, or to protect the rights, safety, and security of our users and the service.
Retention and deletion
- Disconnecting Gmail (dashboard → Disconnect) releases held messages back to your inbox, revokes our Google access, and deletes our stored tokens immediately.
- You can also revoke access anytime at myaccount.google.com/permissions.
- Disconnecting Outlook releases held messages back to your inbox, stops notifications, and deletes our stored tokens immediately. You can also remove InboxToll at account.live.com/consent/Manage (personal accounts) or myapps.microsoft.com (work accounts).
- Deleting your account: email support@inboxtoll.com and we will delete your account and associated data within 30 days, except records we must keep by law (such as payment records).
- Message metadata and activity logs are kept while your account is active so you can review them.
Your choices and rights
You can view and change your settings, whitelist, and block list at any time. Depending on where you live, you may have rights to access, correct, delete, or export your personal information, or to object to its processing. Contact us to exercise them; we won't discriminate against you for doing so.
Children
InboxToll is not intended for anyone under 18, and we don't knowingly collect information from children.
Changes
If we make material changes, we'll update this page and notify you by email or in the app before they take effect.
Contact
The National Correspondent LLC, Missouri. Questions or requests: support@inboxtoll.com.