Privacy policy
Last updated 2 November 2026
This policy is a draft written by the team, not by a lawyer, and it will be reviewed before Aux0 takes a paying customer. It describes what the product actually does today, which is the part we can be accurate about.
Who we are
Aux0 is a product of Exa Labs LLC. For privacy questions, write to hello@aux0.com.
Two kinds of data
Your data as our customer — the name, email and company of the people on your team, your plan and your invoices.
Your end users' data — the accounts your users link and the mail, calendar events and contacts that flow through them. For this, you are the controller and Aux0 is the processor: we hold it to provide the service you asked for, and we do not use it for anything else.
How we use Google user data
When one of your end users connects a Google account, they grant access through Google's own consent screen and see every permission before they accept. Aux0 requests the narrowest scopes that cover the endpoints you have enabled, and each project chooses its own subset — a read-only product asks for read-only access.
| Scope | Why we request it |
|---|---|
gmail.modify | Reading threads and messages, sending and replying, saving drafts, and applying labels, archiving or trashing on the user's instruction. Narrower read and send scopes cannot archive or label. Google's consent screen words the send permission as "from any of your Gmail addresses": this scope can send from an alias the user already has, though Aux0 cannot create one. |
gmail.settings.basic | Reading and writing mail settings — filters, the signature on the user's primary address, vacation replies and labels — where the product you are using offers those settings. Google's consent screen also discloses that this scope can see a mailbox's forwarding settings and who else has access to it; Aux0 reads neither, and cannot change either. Google also warns that filters under this scope can move or delete mail; Aux0's filters can only add and remove labels, with no delete action to express. We do not create or change send-as addresses, which Google places behind a scope we do not request. |
calendar.calendarlist.readonly, calendar.events, calendar.freebusy | Listing calendars, reading availability, and creating, updating or deleting events with attendees. |
contacts.readonly, contacts.other.readonly | Resolving a message's sender or recipient to a known person, and completing an address as it is typed. |
We do not request https://mail.google.com/, gmail.settings.sharing or domain-wide delegation, and Google accounts are never connected over IMAP.
Limited Use
Aux0's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- We use Google user data only to provide and improve the user-facing features of the product the user connected their account to.
- We transfer it only as necessary to provide those features to that product, to comply with applicable law, or as part of a merger or acquisition after obtaining explicit consent.
- We do not use it for advertising, and we do not sell it.
- We do not allow humans to read it, except with the user's explicit consent for specific messages, where necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data is aggregated and anonymised for internal operations.
- We do not use Google user data to develop, improve or train generalised artificial intelligence or machine learning models.
The same commitments apply to data from every other provider Aux0 connects, including Microsoft and Apple accounts.
What we hold, and for how long
- Account credentials. Tokens and app passwords are encrypted at rest with a per-credential key, used only to reach that account, never shown to you, never written to a log, and never sent to a third party.
- Mail, calendar and contact content. 30 days by default, so history reads and backfill work. You can set a project's retention to zero, after which Aux0 keeps only ids, timestamps and the account each belongs to.
- Webhook payloads. 7 days, so a failed delivery can be replayed.
- The audit log. 90 days on Growth, one year on Scale. It records who did what, not the content of what they did.
- Operational logs. 30 days, with message bodies excluded.
Where it is held
Account and message metadata is held in Google Cloud Platform in the United States. Message bodies and attachments are held in Cloudflare R2. Enterprise plans can be deployed single-tenant in a region you choose.
Sub-processors
| Provider | What for |
|---|---|
| Google Cloud Platform | Application hosting and the database |
| Cloudflare | DNS, the website, and object storage for message bodies |
| Infisical | Secret management |
We tell customers before a sub-processor is added or changed. None of them is given access to message content except as storage.
What we never do
- Sell or share your data, or your end users', with anyone.
- Train a model on message content.
- Read your end users' messages, except on the narrow grounds set out under Limited Use above.
- Send marketing to your end users.
Your end users' rights
An end user can disconnect an account at any time, from your product or by revoking access with the provider directly — for a Google account, at myaccount.google.com/permissions. When an account is disconnected or deleted, Aux0 deletes its credentials immediately and its content within 30 days. If one of your users asks you to export or erase their data, the API gives you what you need to answer them; tell us if it does not.
Cookies
This website uses no advertising or tracking cookies. Page views are counted with Plausible, which stores nothing on your device and identifies nobody. The dashboard uses one cookie to keep you signed in.
Changes
If this policy changes in a way that affects you, we will tell you by email before it takes effect, not by quietly editing this page. See also our terms of service and our security practices.