Read-only Gmail scope
Sweep Tax requests exactly one Gmail scope: https://www.googleapis.com/auth/gmail.readonly. That scope can list and read messages and attachments. It cannot send mail, delete or trash messages, add or remove labels, change settings, or act as you in any other way. Sign-in with Google uses only the basic profile and email scopes.
How much of the mailbox a scan actually opens
A scan lists the messages in the financial year you pick, leaving out Sent, Drafts, spam and the bin and anything from your own address, and reads each one's headers and text, because that is what the next step needs. It then runs a rule-based prefilter over sender, subject, attachment types and amounts, and only messages that pass are sent to the AI model or kept. For the rest, all we record is an opaque message id, the mailbox it was in, the word "skipped" and the name of the rule that skipped it, so the next scan can pass over them; the rule's name is erased after 90 days. Typically the candidates are a small fraction of the mailbox.
Tokens and encryption
Refresh tokens are encrypted at rest, access tokens live only as long as a scan, and everything in transit is over TLS.
The cipher, the key, sign-in and disconnecting
- Refresh tokens are encrypted at rest with AES-256-GCM under a key kept in the application's environment and never in the database or the file store; the operator keeps a copy of it outside the service, so a backup can be restored. Access tokens are short-lived and kept in memory for the duration of a scan.
- All traffic is over TLS — between your browser and us, and between us and Google, Anthropic, Stripe and storage.
- Sign-in is by emailed magic link or Google sign-in. We do not store passwords. Sessions are HTTP-only, secure cookies.
- Disconnecting a mailbox deletes its refresh token immediately.
Tenant isolation
Every business is a separate tenant.
How that is enforced
Every database query is scoped to the business you are a member of, and every API request re-checks your session and membership before touching a row. Members of one business cannot see another business's mailboxes, records or files, even if the same person owns both — they switch explicitly. Plan caps are enforced per account, not per business, so they cannot be worked around by creating businesses.
File storage
Source documents — PDFs, images and rendered email bodies — are held in private storage with no public access, encrypted at rest, and backed up daily.
How a file reaches you
Files are served only through the app, to signed-in members of the owning business. Keys are namespaced by business so a file cannot be addressed from another tenant.
AI processing
Content that passes the prefilter is sent to Anthropic's Claude API for two narrow tasks: confirming a message is a receipt and extracting its fields. We send the message's subject, its sender as the mail header carries it, its date, the names of its attachments, a text excerpt and the attachment itself. Your account details and the address of the mailbox it arrived in are not sent, though a receipt may of course name you as the customer. Under Anthropic's commercial API terms this content is not used to train models.
How much of it runs at once
Concurrency is limited per tenant and globally so a single large mailbox cannot starve others.
Sub-processors
| Provider | Purpose | Location |
|---|---|---|
| Anthropic | Receipt classification and extraction (Claude API) | United States |
| Gmail API and Google sign-in | Global | |
| Stripe | Payments, subscriptions and invoices | United States / Australia |
| Resend | Sign-in and transactional email, and the one launch email to the early-access list | Japan (mail is sent from Tokyo) / United States |
| Microsoft | Microsoft Graph, for Outlook and Microsoft 365 mailboxes you connect | Microsoft's own regions |
| Fly.io | Application server, Postgres database, receipt files, daily volume snapshots | Per deployment — see below |
This deployment: the application, the Postgres database and the receipt files all run on Fly.io in Sydney, Australia, each on an encrypted disk attached to its own server. No separate object-storage provider is involved in serving them. Backups are Fly.io's daily snapshots of those disks, kept for 30 days.
We will update this list before adding a sub-processor that handles Gmail content, and email account owners about the change.
Google verification and CASA status
gmail.readonly is a Google "restricted" scope.
What Google requires of an app that asks for one
Apps that use it in production must pass Google's OAuth verification, including an annual independent security assessment (CASA Tier 2) and a review of how the app uses the data.
Status: Verification in progress — until it is complete Google shows an “unverified app” warning during sign-in. Everything else on this page applies regardless.
Data deletion
Deleting a business or an account removes its records and files for good, at once. Deleting a single record hides it from your lists and exports and keeps the row and the original file, so an export you have already sent still reconciles — clearing a whole business or the account is what removes those. Disconnecting a mailbox ends our access but leaves the records already extracted. Encrypted backups of the database and the files roll off within 30 days, the server log's security record of what was done with the account expires with our host's short-lived log buffer, and Stripe keeps invoices for as long as tax law requires. The one case this cannot cover is a disaster that makes us put the stored files back from a copy, on their own or with the database: anything deleted after that copy was taken could come back with it. If that ever happens, we delete again everything our records show was deleted since the copy, and email every account holder the date of the copy, so that anyone who deleted something after it can check and delete it again.
Where each of those lives in the app
- A record: open it and choose Remove. It leaves your lists and exports immediately; the row and its file are kept until the business or the account goes.
- A mailbox: Scan page → Mailboxes → Disconnect. The refresh token is deleted immediately, and with Google the grant is handed back in the same step; records already extracted stay until you delete them.
- A business: Settings → Businesses → Delete. All its mailboxes, records, files and memberships go immediately.
- Your account: Settings → Account → Delete account. Every business you own goes as above, with your user record and sessions, immediately. A mailbox you connected to a business someone else owns stays with that business. Stripe keeps invoices as required by tax law.
You can also revoke our access at myaccount.google.com/permissions at any time. Steps are on the Support page.
Responsible disclosure
If you believe you have found a security issue, please email security@sweeptax.com.au with enough detail to reproduce it. We will acknowledge within 2 business days, keep you informed, and credit you if you wish. Please do not access other customers' data or run automated scanners against the production service.