Privacy should be explicit, especially when agents can act.
Here’s what tamag0 collects on the website and in the product, why, and where it’s stored.
Who we are
tamag0 is published by Scalizy SAS. For privacy questions or requests, contact [email protected].
Website and access-request data
When you request access from this website, we collect the information you submit: email address, optional first name, optional last name, optional company name, and the language you are browsing in. We also use Cloudflare Turnstile to reduce spam and a lang cookie to remember whether you chose English or French.
Demo requests
When you request a demo from this website, we collect the information you submit: email address, first and last name, company name, the kind of organisation (a company, or an agency or IT services firm), what you want to move forward first if you tell us, the page of this website you came from, and the language you are browsing in. We also use Cloudflare Turnstile to reduce spam. This information is sent to us by email so that we can reply and set up the demo with you.
Agent-submitted requests
An AI agent can request access on its human's behalf through our public MCP server, after that human explicitly consents. We record the same information as a website submission — email address, optional first name, and preferred language — plus the agent framework it identified itself as (for example, "claude-code") and the fact that consent was attested at the time of the request. That attestation records the caller's declaration; it is not proof that the human controls the mailbox. We use this data for the same purpose as an access request made on the website, keep it for the same retention period (see Retention below), and you can ask [email protected] to access, correct, or delete it exactly as for any other access request. See Agent access for how this works.
Product data
If you use tamag0, the product may process account and workspace information, conversations, activity threads, agent memory, rules, preferences, tool outputs, scheduled tasks, and integration events needed to operate the service you enabled.
- Secrets: API keys and OAuth tokens are stored through the operating system’s secure storage where supported.
- Workspaces: thread workspaces run on your machine in isolated local folders.
- Integrations: connected services such as Slack, Gmail, Calendar, Jira, GitHub, or Sentry process data according to the permissions you grant.
- Hosting: data synced server-side — company memory and threads — is hosted at Hetzner, in a data center located in the European Union (Falkenstein, Germany).
Google user data (Gmail, Calendar, Drive)
From the desktop app, you can connect your Google account so your agent can work with Gmail, Google Calendar and Google Drive. You open the connection yourself, from the app, through Google’s own sign-in page, and tamag0 requests only the scopes those tools need: reading and searching your mail (gmail.readonly), sending mail and replies (gmail.send), saving drafts to your Drafts without sending them (gmail.compose), listing and editing calendar events (calendar.events), reading and searching the files of your Drive and of the shared drives you are a member of, and working on them as far as your own access allows — creating folders, uploading files, updating files in place, renaming and moving files and folders, and copying files, never deleting or sharing anything (drive), plus your account identity and email address to label the connection. tamag0’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.
- Use: Google data is used only to carry out the request you or your agent make in the app: search or read a message, send a reply, save a draft, list, create, update or cancel an event, find or read a file, create a folder, upload, update or copy a file, rename or move a file or a folder. Sending mail, saving drafts, changing events and writing to Drive go through the permission you set for the agent, with a confirmation prompt unless you configured it otherwise.
- Where it goes: the Google connection runs on your machine. Credentials are kept in the operating system’s secure storage on your computer and are never sent to our servers. Content returned by these tools becomes part of the conversation that asked for it and follows the Product data rules above; the model provider you chose receives it to answer that request, under that provider’s terms.
- What we do not do: we do not sell Google data, do not use it for advertising, do not use it to train or improve any machine learning or artificial intelligence model, and do not let people at Scalizy read it, except with your explicit agreement, for a security investigation, or where the law requires it.
- Disconnect: disconnecting Google in the app deletes that work context’s credential from your computer; a connection made in another work context is listed in Settings and is disconnected separately. It does not revoke the grant on Google’s side: you can do that at any time from your Google account permissions.
- Deletion: content derived from Google data stays with the conversation or agent memory it was kept in, under the Product data and Retention rules of this policy. Deleting a conversation in the app removes it from your view and archives it on our servers; deleting an agent memory removes it. To have Google-derived content erased from our servers, write to [email protected].
Model providers and locality
tamag0 lets you choose Claude, Codex, Ollama, or OpenAI-compatible providers. If you use a cloud provider, the prompts and context required for the task are sent to that provider. If you use Ollama or a self-hosted compatible endpoint, model inference can stay inside your infrastructure.
Why we use data
- Review access requests and give access to the product.
- Answer your demo requests.
- Operate agent memory, collaboration, scheduling, integrations, and permissions.
- Secure the service and prevent abuse.
- Communicate about access, support, product updates, and important changes.
Retention
We keep access-request data until we have reviewed and answered your request and, if you get access, while your account is active, or until you ask us to delete it. We keep demo requests for as long as we follow up on them, or until you ask us to delete them. Product data is kept while your workspace or company account is active.
Your rights
Depending on where you live, you may request access, correction, export, restriction, objection, or deletion of your personal data. Email [email protected] and we will respond as required by applicable law.
Security
tamag0 is designed with per-company isolation, local workspaces, OS-level secret storage, permission gating for sensitive actions, and auditability.
Changes
We may update this policy as tamag0 evolves. The date above shows the latest version.