Atso

Privacy Policy

Last updated: 30 October 2026

Atso connects the business tools you already use — such as Xero, Shopify, Infusion and Unleashed — to an AI assistant such as Claude, so you can ask questions about your own business data. This policy explains what we collect, why we hold it, where it lives and how to get it removed.

In this policy, “Atso”, “we” and “us” mean the operator of the Atso service at app.atso.ai. “You” means the person or business using it.

1. What we collect

Support messages

When you contact support in the app, we email your message, sign-in email, name if set, and organisation name to hello@atso.ai so we can respond. Do not include passwords or access tokens.

Account information

When an organisation Admin invites someone, we store the invited email address, assigned role, a one-way hash of the invitation token, and its expiry and acceptance or cancellation status. Invitations expire after seven days.

Your email address, the name of your organisation inside Atso, your timezone if set, your full name if you add it in Settings, your organisation role and access status, and the dates you signed up and signed in. There is no password: you sign in with a one-time link sent to your email address.

Sign-in information

When you request a sign-in link we store your email address, a one-way hash of the link's token, and the time the link expires. The link is valid for 15 minutes and can be used once. After you sign in, your browser holds one signed session cookie. It is essential to the service and cannot be turned off while you are signed in.

Credentials for the platforms you connect

When you connect a platform, we store what is needed to call it on your behalf: an OAuth access and refresh token (Xero, Shopify) or an API key (Infusion, Unleashed), plus non-secret details such as the organisation or store name, its currency and its identifier on that platform. Every credential is encrypted before it is written down, using AES-GCM with a key held only as a server secret. Nobody can read a credential out of our database, and the Atso interface never shows one back to you.

MyFitnessPal

Your MyFitnessPal connection is private to you. Other organisation members, admins and staff support sessions cannot see or use it. Your password is used for the sign-in exchange and discarded; access and refresh tokens are encrypted at rest. You separately choose whether your agent may make food-related changes.

Food and recipe content is returned to your chosen agent when requested. It is not cached, captured in tool traces, or automatically added to your Brain. To prevent duplicate writes, Atso keeps a keyed request digest, opaque result identifiers and an outcome for a 24-hour retry window, with daily cleanup. No meal body or password is stored in those receipts. Disconnect removes tokens and receipts; removed accounts are denied immediately and their token storage is cleared by a daily check.

Your business data

Atso does not copy your accounting, sales or inventory records into a database of its own. When your AI assistant asks a question, we call the connected platform at that moment, with the access you granted, and pass the answer back. Atso reads from those platforms by default and changes nothing in them. An administrator of your organisation can turn writing on for one connected platform at a time, and only then can your assistant create or change records there. Every attempt is recorded — who, which platform, which tool, which record and the outcome — and that record never holds what was written.

Webflow has no way to undo a change through its interface for other programs, so when Atso changes a Webflow CMS field it first reads what was there and keeps the previous value for ninety days, so the change can be put back by hand. This is the one place Atso stores content from a connected platform. It is kept for your organisation only, it covers only the fields that were changed, and it is deleted after ninety days or when the organisation is deleted.

If you connect your Gmail mailbox, your assistant can search it and read email threads. Atso reads it live, only when your assistant asks, and only reads: it cannot send, draft, label, archive or delete email. Your mailbox is private to you: other people in your organisation cannot read it through Atso, and an administrator can only see that it is connected (the address, status and date) and disconnect it. Email content is not automatically cached, traced or ingested; content is delivered only to the connected assistant. You can still ask your assistant to save something to your Brain. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

If you connect your Google Calendar, your assistant can list your calendars and read your events. The same rules apply as for Gmail: Atso reads it live, only when your assistant asks, and only reads, so it cannot create, change, answer or delete an event. Your calendar is private to you, an administrator can only see that it is connected and disconnect it, and calendar content is not automatically cached, traced or ingested.

If you connect your Google Drive, your assistant can search it, see a file's details, and read the text of Google Docs, Sheets, Slides and text files. The same rules apply as for Gmail: Atso reads it live, only when your assistant asks, and only reads: it cannot create, change, share, move or delete files. Your Drive is private to you, an administrator can only see that it is connected and disconnect it, and file content is not automatically cached, traced or ingested.

Your Brain, described below, is the one place business facts are kept. Only what you or your assistant chose to save goes into it, and only for you.

The one exception is a short-lived cache used to avoid asking the same platform the same question twice in a row. Cached answers expire automatically within five minutes and are stored under a key that is specific to your organisation.

Some of that data may include personal information belonging to other people — for example the name on an invoice, or a store customer's details. We only request it when the access you granted allows it, we pass it to the AI assistant that asked for it, and we do not keep it beyond the short cache described above.

Your Brain

Each person using Atso has a private Brain. Your AI assistant writes a page to it when you ask it to — a summary of a decision, a customer, a month, a note or a way you like something done. Each page holds what was written down, when it was true, how confident it is, and pointers back to the records it came from. It does not hold a copy of those records: the pointer is followed at the moment you ask, so the number you are given is the live one.

If you save a model API key or subscription token (below), a writer runs with that credential and can add pages of its own. Pages it writes are marked as written by the writer, and are never marked as directly observed. It can only change pages it wrote itself; a page you or your assistant wrote is never edited or retired by it.

Each of those runs reads recent records from every system you connected — the last 30 days, and at most 50 records from each — and sends short summaries of them to the AI provider whose key you saved, in one request. That includes the text of Notion pages it reads. Pumble is the exception: the writer reads a Pumble conversation only if you selected it for your Brain, and until you do it reads none. From GitHub it reads only the repositories an organisation Admin enabled, only what changed since its last run, and it removes text that looks like a password or key before sending anything. It never reads your Gmail mailbox, your Google Calendar or your Google Drive. We do not keep a copy of those records: the summaries exist only for the length of that one request, and what stays afterwards is the pages the writer chose to write, in your own private Brain. The run's own log records which systems were read and how many records came back, never what they said.

Your Brain is private to your account and is not shared with other people in your organisation. Atso staff admins can access it while helping you in a timed support session. Staff can manage your account in that session, and their changes are recorded against the acting admin. Every earlier version of each page is kept as its history, so you can compare versions, restore one or undo a Brain run. Ask your assistant to remove a page and it leaves your Brain straight away; its history stays, so it can be restored. All of it goes when your account does.

Tool call trace

This is recorded only while your saved model key or token is marked active, because the only thing that reads it is your own nightly Brain writer. If you have no active credential, nothing here is recorded at all. Removing your key or token stops the recording from your next question onwards.

While it is on, we keep a short record of each question your assistant asks Atso: the tool it used, the values it sent, and the first part of the answer it received. Access credentials are removed before it is written down. We keep at most the last 500 of these per person, and delete anything older than 14 days. It is visible only to you, and only ever read by your own writer. Gmail, Google Calendar and Google Drive questions are never recorded here.

Model API keys and subscription tokens

If you want the nightly Brain writer, you give Atso your own Anthropic or OpenAI API key, Claude setup token, or ChatGPT access token on the Brain page. We check it with the provider before saving, then encrypt it the same way as every other credential described above. It is never shown back to you — the page shows the last four characters — and it is used for nothing but writing your own Brain, once a night. Remove it in Settings at any time and it is deleted immediately, along with the recording described above. This feature does not store ChatGPT refresh tokens or browser cookies. What the provider does with your writer's input is covered by the privacy policy and account terms that apply to the API or subscription credential you chose.

If you connect through Claude’s native sign-in, Claude Code runs in a private Cloudflare workspace for your connection. Claude Code manages its own credentials in private persistent storage; Atso stores an encrypted reference to that workspace. The one-time sign-in code is passed to the waiting native process and is not retained. Disconnecting Claude removes that workspace’s stored files and stops your Brain writer and tool-call recording.

Technical information

Our hosting provider processes your IP address and standard request information to deliver the service and to protect it from abuse. We use your IP address to limit how many sign-in links can be requested in an hour.

We use two vendor tools and both are configured to keep your information out of them. Error reports (Sentry) are sent with personal identifiers turned off; cookies, authorisation headers, request bodies and query strings are removed before an error leaves the service. Product analytics (PostHog) record which pages are used and which features are clicked, identified by an internal member identifier rather than your email address, with page text masked and session recording switched off. When you sign up we also record how you arrived: the campaign parameters in the link you followed and the address of the page that referred you, without its query string, so we can tell which of our own pages and campaigns bring people to Atso.

2. What we do not do

  • We do not sell your information, and we do not share it for advertising.
  • We do not use your business data to train AI models, our own or anyone else's.
  • We do not send you marketing email because you signed up. Email is used for sign-in links, organisation invitations and service notices.

3. AI assistants you connect

Atso is useful because you point an AI assistant at it. When you connect one — for example Claude — you approve a specific connection, and from then on that assistant can ask Atso for data from the platforms you connected. Anything it asks for is sent to that assistant's provider and is then handled under that provider's own privacy policy and terms, not ours. You can see every connected assistant on the Agents page in Atso, and revoke any of them at any time. Revoking takes effect immediately.

4. Who processes your information

We use a small number of service providers to run Atso:

  • Cloudflare — hosting, the database, the cache and the network in front of them.
  • Resend — delivery of sign-in emails, organisation invitations and support messages.
  • Sentry — error reporting, scrubbed as described above (United States).
  • PostHog — product analytics, as described above (United States).
  • Chatwoot — the support chat in the signed-in app. Its widget receives browser and page information, and any messages, attachments or contact details you choose to send. We provide your signed-in email address, your name and a verified user identifier so you do not need to enter your email again. We do not send your connected platform data. See Chatwoot's privacy policy.
  • Anthropic or OpenAI — only if you saved your own API key or subscription token for the nightly Brain writer, and only for that. Your agreement is with them (United States).
  • The platforms you connect — Xero, Shopify, Infusion, Unleashed and any we add later. Your data on those platforms stays governed by your agreement with them.

These providers operate internationally, so your information may be stored or processed outside New Zealand. We only use providers who are required to protect it to a standard comparable to the New Zealand Privacy Act 2020.

5. How long we keep it

  • Sign-in links — valid for 15 minutes, single use.
  • Cached platform answers — deleted automatically within five minutes.
  • Platform credentials — disconnecting a Shopify store, an Infusion company or an Unleashed company in Atso deletes the stored credential at once. Uninstalling Atso in your Shopify admin removes our access at Shopify's end as well, and we delete our copy as soon as Shopify tells us. You can disconnect a Xero organisation on the Connectors page. Once Xero confirms removal, we remove its local connection record. The encrypted Xero login credential is retained, including after the final organisation is removed, because one login can serve several organisations. It cannot read an organisation disconnected at Xero. To cancel the entire Xero login grant and delete its stored credential, contact support@atso.ai. You can also remove Atso from the connected apps list in Xero.
  • Your Brain — pages and every earlier version of them, kept until your account closes.
  • Tool call trace — recorded only while your model key or token is marked active; the last 500 entries per person, and nothing older than 14 days.
  • Previous values of changed Webflow fields — kept for ninety days so a change can be put back by hand, then deleted, and deleted with the organisation.
  • Model API key or subscription token — kept until you remove it on the Brain page or your account closes.
  • Account information — kept while your account is open, and deleted within 30 days of your request to close it.
  • Error reports and analytics — kept for the retention period of the provider, currently up to 12 months.

6. Shopify stores

If you connect a Shopify store, Atso answers Shopify's required privacy webhooks. When Shopify tells us the store has uninstalled Atso, or that the store must be erased, we close that store's connection and delete the credential we hold for it. A request about a store customer's data, or to erase a store customer's data, is recorded and answered: Atso keeps no copy of your store's orders, products or customer details, so there is nothing on our side to hand over or erase. To make a request about a specific store, contact us at the address below or ask Shopify to pass the request on.

7. Your rights

Under the New Zealand Privacy Act 2020 you can ask for a copy of the personal information we hold about you, and ask us to correct it. If you are in the European Union or the United Kingdom, you also have rights to erasure, restriction, objection and portability. Write to support@atso.ai and we will answer within 20 working days.

To delete your account and everything attached to it, email the same address from the address you sign in with. We do this within 30 days.

8. Cookies

Atso sets one essential cookie, which keeps you signed in. Product analytics set their own cookies to count returning visits; that cookie is shared with our marketing site at atso.ai, which is how a sign-up is linked to the visit that led to it. The Chatwoot support widget uses a conversation cookie to keep your chat available as you move between pages or return later. There are no advertising cookies.

9. Security

Credentials are encrypted before storage. Traffic is served over HTTPS only. Every request for your data is checked against the organisation on your session, so one organisation can never read another's. If a breach affects you, we will tell you and the Office of the Privacy Commissioner as the Privacy Act requires.

10. Children

Atso is a business tool. It is not intended for anyone under 16, and we do not knowingly collect information about children.

11. Changes

If we change this policy we will update the date at the top. If a change materially affects how we handle your information, we will email account holders before it takes effect.

12. Contact

Privacy questions, access requests and deletion requests: support@atso.ai. If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner at privacy.org.nz.