Antimatter

Privacy policy

Privacy, and what the API keeps

This page is read from the code that writes the data. Every retention window and every list here is this deployment's own setting, read when you opened it.

Last updated 29 October 2026.

A request to the API (chat completions, messages, responses, embeddings, images, audio) writes no prompt and no answer to Antimatter's database unless you ask it to. What is kept is the bill: model, token counts, cost and timings.
The response cache (10 minutes), resumable streams (10 minutes) and flight recorder capture (24 hours by default) hold content. You switch each one on, per request or per key, and each is swept when its window ends.
The /chat playground saves your threads, batch jobs keep their lines and answers, and the Telegram bot keeps a short history. Each is listed below with how long it is kept and how to remove it.

Where your content can be stored

Everything in Antimatter that can hold the text of a prompt or an answer. Nothing else does. No log line prints a prompt, and the site has no analytics script.

Response cache

A hash of the request and the answer it got. Not the prompt.

when
A request sends x-antimatter-cache: on. Non streaming requests only, never on your own provider key.
kept
10 minutes, then swept. The prefix index beside it holds hashes only, 30 minutes.
remove
Do not send the header. Entries expire on their own, and erasure deletes yours. An entry written before 2 October 2026 names no account, so erasure cannot find it. It ages out on its window instead.

Semantic cache

An embedding of the prompt and the answer.

when
Off on this deployment, because no embedding model is configured.
kept
30 minutes, then swept.
remove
Leave it off on the key. Erasure deletes your rows.

Resumable streams

The streamed answer, so a dropped connection can pick up where it left off. Not the prompt.

when
A keyed streaming request sends x-antimatter-resumable: 1.
kept
10 minutes after the last write, then swept.
remove
Do not send the header. Erasure deletes them.

Flight recorder capture

The full request body and the full answer, for replay and debugging, up to 128 KiB each.

when
You turn capture on for a key on the dashboard. It is off for every key until then, and never applies to anonymous or keyless traffic.
kept
24 hours by default, set per key from 1 hour to 30 days. A change to the window, shorter or longer, applies to what is already stored.
remove
Delete a capture, or erase the account. Turning capture off stops new captures. The ones already taken stay until their window ends.

Shadow tests

For each replay of a captured request to a candidate model: whether the answers agreed, what it cost, how long it took and any error. Never a copy of the prompt or of either answer.

when
You start a shadow test for a key on the dashboard or through the API. It replays only requests the key already captures, while their capture lasts.
kept
Results 90 days after the replay. A stopped test goes 90 days after it stopped, unless a switch from it still stands.
remove
Stop the test, or erase the account. A switch stays on the key until you revert it.

Playground threads

Your messages in /chat and the reply to each, and, signed in, the pictures you make there with the words that made them.

when
Always, while you use /chat. The page saves the thread so it is there when you come back.
kept
Signed in: until you delete the thread. Anonymous: 30 days after the last message.
remove
Delete the thread in /chat, or erase the account. The API never writes here.

Batch jobs

The uploaded JSONL file, each line's request and each line's answer.

when
You create a batch through /v1/files and /v1/batches.
kept
No window yet. Kept until the account is erased.
remove
Deleting the input file removes the upload, but each line's copy of its request and its answer stay with the batch until erasure. A batch made with an organization's key stays with the organization.

Saved prompts

The prompts you keep: every version's messages, its model and note, and the labels that point at a version.

when
You save a prompt on the dashboard's Keys tab.
kept
Until you delete the prompt or erase the account. A version is never changed once written.
remove
Delete the prompt on the dashboard, or erase the account. A usage row keeps only the prompt's id and version number.

Vector stores

The files you upload for file search, the text they are cut into, its embeddings, and the attributes you set on them.

when
You upload a file with purpose assistants and attach it to a vector store through /v1/vector_stores.
kept
Until you delete the store or the file. A store with expires_after loses its files that many days after it was last used.
remove
Deleting a store removes its text and embeddings. The uploaded file stays in /v1/files until you delete it. Erasing the account deletes every store it made.

Memory spaces

The facts your keys ask to be remembered, or that a model read from a conversation they sent, each with its embedding, and the history of every change to them with the words before and after.

when
A key writes to /v1/memories, a chat request sends x-antimatter-memory-write, or an agent run uses its memory tool. A conversation queued for reading is kept only until it is read.
kept
Until you delete the memory or its space. Its history is kept 365 days, and until the space is deleted.
remove
Forget a memory or delete a space on /memory or through the API. Erasing the account deletes every space it made, with its memories, vectors and history.

Tools market calls

For each call of a market tool: which tool, whether it succeeded, what it cost and how long it took. The arguments you send go to the provider's server and its answer comes back to you; Antimatter keeps neither.

when
You call a tool through /mcp/tools, /v1/tools or a hosted agent run.
kept
90 days after the call, then swept.
remove
Erasing the account detaches its calls, which stay only as anonymous measurements until they are swept.

Agent passports

For each agent you gave a passport: its name and description, the endpoints you listed, its public address, where its registration stands on chain (the token, its owner and the transactions), the signed records of what was measured for it, and the feedback other clients gave it on the registry. A record holds counts and sums by day and the hashes of sealed receipts, never a prompt or an answer.

when
You open a passport for an agent on the dashboard. From then on it is public at its own address.
kept
Until you delete the passport, or until the account is erased.
remove
Delete the passport on the dashboard, or erase the account. A registration on a chain cannot be erased. The token stays on the registry, and its owner can transfer it.

Test suites

Your test cases and their checks, and every run's results: each model's answer to each case, whether it passed, its cost and its latency.

when
You create a suite on the Suites page or through /v1/evals.
kept
Until you delete the suite, or until the account is erased.
remove
Deleting a suite removes its cases, runs and results. Routing on it stops at once.

Telegram

The recent conversation with the bot: your messages and its replies. A photo you send goes to the model and is not stored. The history notes only that there was one. Also the chat's settings: the image model you picked, whether the cost line shows, and the model and billed cost of the last reply.

when
You link a Telegram chat to your account.
kept
The last 12 messages, each for at most 24 hours after it was sent, and each cut at 8,000 characters. The settings until you unlink.
remove
/new or /unlink in the chat, or erase the account.

Notification devices

For each device you turn notifications on for: the address its browser's push service gave it, the keys that encrypt what is sent to it, and a label such as "Safari on iPhone".

when
You turn notifications on from Billing, in a browser or the installed app.
kept
Until you turn them off or remove the device, the push service says it is gone, or 8 deliveries in a row fail.
remove
Turn notifications off, remove the device on Billing, or erase the account.

Shares, saved prompts, presets

What you chose to save or share.

when
You save or share it.
kept
Until you delete or revoke it.
remove
Delete or revoke it, or erase the account.

Hosted agent runs

A run's conversation: its input, the model's answers, what its tools returned and any picture it made, and your agent's definition. A remote MCP server's headers are kept only encrypted.

when
You start a run of one of your agents.
kept
30 days after the run ends, then swept.
remove
Erasure deletes the runs and the definitions.

What is kept about requests

No text is kept, but enough to bill, apply rate limits and answer for the service. A window of zero means the record is not swept.

  • Usage records: per request, the model, token counts, cost, status, timings, the key, the provider's error message when there was one (cut to 200 characters) and, if you send one, your x-antimatter-session label. No prompt, no answer, no IP address. Kept 400 days.
  • Traces: the same metadata as spans, for the flight recorder and OpenTelemetry export, with any error message cut to 500 characters. Kept 7 days. This deployment pushes them to no collector.
  • Autopilot decisions: which model was chosen and why, for signed in accounts. Kept 30 days.
  • Sign in: your wallet address is your account. Sessions last 30 days. The IP address of a sign in is kept only as a keyed digest, for the abuse rules, and pruned 30 days after it was last seen. Sign in with email, Google, X or a wallet app goes through Privy, which holds your email or social account and your embedded wallet's key shares. Antimatter keeps nothing from it but the wallet address. Buying USDC with a card is between you and Stripe or MoonPay.
  • Devices: each session keeps the family of browser and system it was made on (for example Chrome on macOS, never the whole browser string) and, at most once an hour, when it was last used, so the dashboard can list your devices and sign any of them out. They go with the session.
  • Abuse signals: beside the digest of a sign in address, a digest of its network range is kept the same way. When a chat turn is sent, the page also says whether the browser reports that software drives it, whether it calls itself headless, and whether nothing was clicked, tapped or typed before the send. For a signed in account those signs are counted, never the words of the turn, and pruned 30 days after they were last seen. Like every abuse rule, they only write a flag the operator reads.
  • Rate limits: an anonymous request is counted against its IP address. Where the operator shares the limiter between instances, that address is written to the database as the counter's key for the length of its window, about a minute.
  • Audit log: notable acts on an account (a key created, a deposit claimed, a member invited) with the IP address that made them. The address is kept in plain text for 30 days, for security review, and then replaced with a keyed digest that shows whether two acts came from one address without saying which. Not swept on this deployment. It is the account's own record, and it is in the export.
  • The ledger: deposits, charges and credits. Kept for good, because money has to add up. Erasure detaches it from you.
  • Webhook deliveries: each attempt to send one of your webhooks, with its event, its payload, the status, how long it took and the first bytes of the answer, so you can see what happened and send it again. Kept 30 days, and gone sooner when you delete the endpoint or erase the account.
  • Billing details and invoices: the name, address and tax id you enter for invoices, and each invoice issued with a copy of them as they stood. Kept until you change them or erase the account. A team's go when the team ends.
  • Spend forecast warnings: when the forecast of your month's spend passes your monthly cap or a key's monthly budget, the figures it warned on (the month so far, the daily mean, the projection and the cap) and when, once a month per cap. Kept thirteen months, and gone when you erase the account.
  • Error reports: when a page or the server fails, what failed (the error's message and stack trace, the page's path and the release), so it can be fixed. Scrubbed before it is stored, in your browser and again on the server, of query strings, keys, tokens, wallet addresses and email addresses. No account, no IP address. Kept 14 days after the error was last seen.

What is collected, and why

  • Your wallet address: it is your account. It signs you in, it is how a deposit you send is credited to you, and it is the one thing that ties the records above to you. Kept while the account exists. If you sign in through Privy, the wallet address is still all Antimatter receives. Your email or social account stays with Privy. If you link more wallets to the account, each linked address is kept the same way, until you remove it or erase the account.
  • Records of your requests: to bill you, to apply your limits, budgets and caps, and to show you your usage.
  • Deposits: the transaction, network, token, amount and the sending wallet, and for $ANTI the credit price it was credited at, to credit you exactly once and to keep the books.
  • IP addresses: briefly for rate limits, as a keyed digest for the abuse rules, and in the audit log, as described above.
  • What you choose to save: threads, prompts, presets, shares, key names, webhooks, alert rules, and a public handle if you publish one.
  • Stars and lab alerts: the models you star, and the labs whose new models you asked to hear about by email. Kept until you take them away or erase the account.
  • Error reports: to find and fix what broke.

Nothing here is sold or used for advertising, and the site runs no analytics that follow you from page to page or site to site.

Who else handles your data

The services this deployment hands any of your data to, read from its configuration now. An optional one is listed only while it is switched on.

Vercel

does
hosts the site and the API and runs the scheduled jobs
receives
every request as it passes through, including its IP address, and the platform's own request logs
when
always

Turso

does
hosts the database
receives
everything this page says is stored
when
always

OpenAI

does
serves OpenAI's own models directly
receives
the prompt, the answer and the request's parameters; no wallet address and no account
when
for OpenAI's models

OpenRouter

does
routes a request to the model's lab and serves the answer
receives
the prompt, the answer and the request's parameters; no wallet address and no account
when
for every model it serves, which is every model not served directly

Privy

does
sign in with email, Google or X, the wallet it makes for you, and wallet apps
receives
your email address or social account, and your embedded wallet's key shares; Antimatter receives only the wallet address
when
only if you sign in through it

Blockchain RPC providers

does
read a deposit's transaction to check and credit it
receives
the transaction you claim, which names your wallet address
when
when you claim a deposit (Robinhood Chain)

Robinhood Chain's RPC

does
reads how much $ANTI the signed in wallet holds, for holder tiers
receives
your wallet address
when
while you are signed in

Vercel Speed Insights

does
measures how fast pages load for real visitors
receives
page load timings, the page's path and the kind of device and browser; it sets no cookie
when
on every page view

Your wallet, and any webhook endpoint or OpenTelemetry collector you configure yourself, are yours. What you send there is under your control, not ours.

Public blockchains

A deposit is a transfer on a public blockchain. It, your wallet address and the amount are public there for good, whatever happens to your account here. Erasure cannot reach them, and neither can anyone else.

Cookies and browser storage

Every cookie and storage key the site writes, and nothing else. None is for advertising or for following you across sites, and browser storage never leaves your browser.

antimatter_session

cookie

keeps you signed in: a signed token naming your account, unreadable to the page (HttpOnly)

Lasts: 30 days, or until you sign out

antimatter-anon

localStorage

a random id for /chat threads you start before signing in, so they are there when you come back

Lasts: until you clear site data

antimatter-chat-settings:<id>

localStorage

each /chat thread's system prompt and temperature, by thread, in this browser only

Lasts: until you clear site data

antimatter-chat-canvas:<id>

localStorage

what you opened on each /chat thread's side canvas and its versions, by thread, in this browser only

Lasts: until you clear site data or delete the thread

antimatter-chat-next-step

localStorage

that you dismissed the next step tip in /chat

Lasts: until you clear site data

antimatter:chat-guide

localStorage

that you finished or skipped the three step guide in /chat

Lasts: until you clear site data

antimatter:pricing-density

localStorage

whether the price table on /pricing is comfortable or compact

Lasts: until you clear site data

antimatter:pending-claims

localStorage

deposit claims still confirming on chain (the transaction and your wallet address), so a reload keeps waiting for them

Lasts: until each is credited or refused, a day at most

antimatter:privy

localStorage

that this browser signed in through Privy, so Privy is loaded again only then

Lasts: until you sign out

antimatter:arrived

localStorage

when the arrival animation last played, so it plays at most once a day

Lasts: until you clear site data

antimatter:sound

localStorage

whether you turned the site's sounds on

Lasts: until you clear site data

antimatter:quality

localStorage

the graphics quality you chose

Lasts: until you clear site data

antimatter:lite

localStorage

whether you turned the lighter pages on or off, which draw still pictures in place of moving scenes

Lasts: until you clear site data

antimatter:quality-demoted

sessionStorage

that graphics were lowered because this device was struggling

Lasts: until the tab closes

antimatter:charted

localStorage

the models you visited on the map

Lasts: until you clear site data

antimatter:explore-hint

localStorage

that you have seen the map's one line hint on a touch screen

Lasts: until you clear site data

antimatter:ach-seen

localStorage

the achievements already shown to you

Lasts: until you clear site data

antimatter:atlas-opened

localStorage

the day the front page last played its opening, so it plays at most once a day in this browser

Lasts: until you clear site data

antimatter:atlas-dragged

localStorage

that you have turned a family's drawing on the front page, so the hint to drag one is not shown again

Lasts: until you clear site data

antimatter:atlas-last

sessionStorage

the last family you opened on the front page, so it is marked when you come back to all of them

Lasts: until this tab closes

antimatter:home-chat-draft:v1

sessionStorage

your unsent homepage message, model choice and the text of any documents you attached, carried into chat in this tab

Lasts: until opened in chat or this tab closes. Drafts older than 30 minutes are ignored

antimatter:home-film-draft:v1

sessionStorage

the first shot you described on the homepage, carried into Nova Studio in this tab

Lasts: until opened in Nova Studio or this tab closes. Drafts older than 30 minutes are ignored

antimatter:presence-token

sessionStorage

a random token for this tab's light on the shared map, so two tabs are two lights

Lasts: until the tab closes

antimatter:ref-banner-dismissed

sessionStorage

that you closed the referral banner

Lasts: until the tab closes

antimatter:error-reports

localStorage

how many error reports this browser sent in the current hour, so it never sends more than a few

Lasts: replaced every hour

webllm/model

Cache Storage

the weights, tokenizer and index of each model you chose to run on this device, so it starts again without a download

Lasts: until you delete the download on /local or clear site data

webllm/config

Cache Storage

the settings file of each model you downloaded to run here

Lasts: until you delete the download on /local or clear site data

webllm/wasm

Cache Storage

the program each downloaded model runs on your GPU

Lasts: until you delete the download on /local or clear site data

antimatter-studio

IndexedDB

Nova Studio's projects and the clips in them, kept only in this browser so the editor at /studio/edit can open them again

Lasts: until you delete the project in the editor or clear site data

antimatter-studio:pending

localStorage

the film being edited in Nova Studio, mirrored the moment an edit is made so nothing typed just before the page closes is lost. It is read back into the projects above and removed on the next open

Lasts: until the studio next opens, or clearing site data

antimatter-studio:kept

localStorage

whether this browser keeps a film in Nova Studio (the value 1, nothing of the film), read before the studio first draws so a kept film is never shown as an empty one first

Lasts: while this browser keeps a film, or until clearing site data

antimatter-studio:likes

localStorage

the shared takes you started a shot from with Make one like this, kept until a take of that shot lands, so it counts toward the shared take's remixes

Lasts: until that take lands, 30 days at most, or clearing site data

antimatter-studio:open

localStorage

the id of the film open last in Nova Studio (nothing of the film itself), so the next visit opens on the film you were working on rather than the newest

Lasts: until another film is opened, or clearing site data

nova-design:workspace:v1

localStorage

Nova Studio's shots and their direction as an earlier version of the studio kept them, read once into the projects above

Lasts: removed as soon as it has been read

antimatter:signed-in

localStorage

the time a sign in last completed in this browser (a time, nothing else), so a film made here while nobody was signed in is offered to your account rather than kept on it by itself

Lasts: until the next sign in, or clearing site data

antimatter:visit

sessionStorage

the time this tab's visit began (a time, nothing else), so signing in moves into your account only the chats this visit wrote signed out

Lasts: until this tab closes

If you sign in through Privy, Privy's own code keeps its session in this browser's storage and cookies under its own names, under Privy's policy.

What the provider sees

A prompt has to reach a model to be answered. It goes to the provider that serves the model you chose: OpenRouter and the model's lab behind it, or the lab's own API (OpenAI, Anthropic, Google or DeepSeek) where the operator connected it. Their retention and training policies apply to what they receive, under the operator's account with them, or under yours when you bring your own provider key.

On requests Antimatter sends to OpenRouter on its own account (chat, embeddings, speech and transcription), it asks OpenRouter to use only providers that do not collect or train on prompts. This is not zero retention. A provider may still keep a prompt for a while, for example to watch for abuse. A model with no such provider is refused, never sent somewhere looser.

Image generation (OpenRouter's image endpoint takes no such preference), requests sent straight to a lab's own API (OpenAI, Anthropic, Google or DeepSeek) or to the providers that make video, music and 3D, and requests on your own provider key are outside this preference. There the provider's own terms, or your account's settings, decide. Antimatter removes routing fields such as provider from your requests before they leave, so a request cannot change the policy. Read each lab's policy before sending what you would not want kept.

Export and erasure

The dashboard exports everything held about your account as one file. Erasing the account deletes your threads, keys, captures, traces, autopilot decisions, personal batches, resumable streams, Telegram link and history, shares, prompts, presets, settings and the digests of your sign in addresses. Keys of an organization are revoked, and its batches stay with it. A thread written in /chat before you signed in was never tied to the account. It goes 30 days after its last message.

What stays, and why: ledger rows and usage records stay with your identity cut from them, because the books and the operator's margin have to add up. Audit rows of your own acts lose your identity and their address, while a row of an admin acting on the account keeps the account's number. Transaction references stay so a deposit cannot be claimed twice. The free allowance already spent, an open abuse flag or a freeze, and a referral stay under a keyed digest of the wallet address, so erasing refills nothing. The key is held outside the database, so the digest cannot be matched to an address without it. Records an account left before 2 October 2026 carry an older digest that is not keyed until that wallet signs in again, when the hourly sweep rewrites them. Your response cache entries are deleted. One written before 2 October 2026 names no account and ages out within 10 minutes, plus the hour the sweep may take. A funded account is told what it forfeits before it can be erased.

Where the books are sealed by day for verifiable receipts, the sealed days stay too: per request and per ledger entry they hold the model, the token counts and the amounts, with the account only as a keyed digest, never an address or an account number. Erasure leaves them as they are, for good, so a sealed root can always be checked and the proofs you were given still verify.

Checking your session.

Depending on where you live you may have other rights over your data, such as to correct it, to object to a use of it, or to complain to a data protection authority.

How retention windows work

An hourly sweep deletes what has passed its window, so a row can outlive it by up to an hour. The operator sets these windows, and the numbers here are the ones in force now. For what each request costs, see pricing. For the headers named here, see the docs.

Changes to this policy

  • When what this policy promises changes, the date at the top changes with it.
  • The windows and lists on this page follow the operator's settings, and the page always shows the ones in force when you open it.