Privacy should be explicit, especially when agents can act.

Who we are

tamag0 is published by Scalizy SAS. For privacy questions or requests, contact [email protected].

Website and waitlist data

When you join the waitlist from this website, we collect the information you submit: email address, optional first name, optional segment, 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.

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 a website waitlist submission, 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 waitlist entry. See Agent access for how this works.

Product data

If you use tamag0, the product may process account and workspace information, conversations, activity threads, companion 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).

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

• Provide access to the waitlist and early-access program.
• Operate companion memory, collaboration, scheduling, integrations, and permissions.
• Secure the service and prevent abuse.
• Communicate about access, support, product updates, and important changes.

Retention

We keep waitlist data while early access is active or until you ask us to delete it. 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.