security · offload
security.
last updated · july 13, 2026
the shape of the system
Your iMessage and Apple Notes are read locally, from your Mac’s own databases. Gmail and Google Calendar connect through Google’s own sign-in, so they stay current even when your Mac is closed. To do the work, the context donna needs is processed on our servers and sent to our AI providers to reason over, under the retention and training controls described below.
ai providers keep nothing
donna’s reasoning runs on language models served by a small, fixed set of US inference providers, under the same two controls on every request: zero data retention and the training opt-out. Your content is sent to a model only to generate the response, held in memory for the duration of the request, and not retained afterward. It is never used to train models.
We enforce this at the routing layer: retention-free endpoints are the only place a request can go, and fallback to anything else is disabled. If a zero-retention route is unavailable, the request fails rather than falling back.
nothing is sent without your approval
Every outbound action, whether a reply, a post, a purchase, or a text on your behalf, is presented as a draft with a button. Until you approve it, nothing moves. This is enforced in code, in a gate the model cannot reason its way around, rather than by instructions alone.
how donna connects to google
Gmail and Google Calendar connect through Composio, a managed connection provider that has passed Google’s security review for this class of access, which is why the Google consent screen names Composio. You approve the access on Google’s own page, and neither Offload nor Composio ever sees your Google password. The connection is encrypted in transit, and you can revoke it at any time, from your Google account or from inside Offload.
how your data is stored
The context donna keeps for you is stored in our database and object storage, hosted in the United States. Data is encrypted in transit, and our infrastructure providers encrypt the underlying storage at the platform level. Access is isolated per account: every database query is scoped to your user with Postgres row-level security, enforced at the database itself, so your data is never visible inside another account’s session. Connection secrets and OAuth tokens are stored encrypted.
signing in
You sign in with a one-time code sent to your phone, and you can register a device passkey, secured by Touch ID and Apple’s Secure Enclave, so there is no password to phish or steal. You can sign out and revoke sessions at any time.
prompt injection
Any assistant that reads the open web and your inbox will encounter content that tries to give it instructions. We design for that assumption rather than against it: untrusted content is walled off from donna’s instructions, and the approval gate bounds the impact of anything that gets through, because no message, purchase, or change can leave without your explicit approval. As with any AI product, we recommend reviewing donna’s drafts carefully when she is working with untrusted content.
what we never do
We never sell your data, never use it for advertising, and never use it to train generalized AI models. Our use of Google data follows the Google API Services User Data Policy, including the Limited Use requirements, spelled out in our privacy policy.
your data is yours to revoke
You can disconnect Google or any other integration at any time inside the app, which revokes our access and deletes the stored tokens for that source. To delete your account and data, email support@offload.so. The privacy policy has the full rundown of your rights.
reporting a vulnerability
If you believe you have found a security issue in Offload, email support@offload.so with the details. We read every report and will respond promptly.