Legal
Privacy
Plain language, no lawyer fog. If something here is unclear, it is a bug in this page.
What we store
| Data | Where | Why | How long |
|---|---|---|---|
| Email or wallet address | Account database | To link a plan and an API key to you | Until you ask us to delete the account |
| API key, plan, monthly usage count, expiry | Account database | To enforce plan limits | Same |
| Per-IP daily counters (chat, image, video, builder, keys) | Rate-limit store | Abuse ceilings | 24 hours, then they expire |
| Payment record (transaction hash, plan, amount) | Account database | To prevent a transaction being reused | Indefinitely (on-chain payments are public anyway) |
| Fact-check scores (numbers only) | Rate-limit store | To calibrate the trust score | Rolling window of the last 10,000 checks |
| Synced history (optional) | Account database | So your chats follow you across devices | Until you overwrite or delete it |
What we do not store
- Your conversations are not logged by us. Chat requests are processed and the reply is returned; nothing is written to a database unless you turn on synced history.
- Fact-check logs contain scores and counts, not the text, unless a short calibration window is explicitly enabled on the server (it is off by default).
- No advertising identifiers, no third-party analytics scripts, no tracking pixels.
What "encrypted" means here, precisely
Synced history is encrypted on your device. Your sync secret never leaves your browser. The server only ever sees a one-way hash of it and an opaque ciphertext blob. We cannot read your synced history, and we cannot recover it if you lose the secret.
The live conversation is not end-to-end encrypted. A model has to read your message to answer it. Messages travel over TLS to our servers and on to the inference provider that runs the model, and are processed in memory. We do not claim otherwise.
Third parties that process requests
Inference, web search, image, video and voice generation run on infrastructure operated by upstream providers under their own privacy terms. We send them the minimum needed for the request and we strip identifying headers from what comes back. We do not disclose which providers, and requests are not sent with your email or wallet attached.
Cookies and storage
One HttpOnly session cookie remembers the email or wallet you signed in with, for 30 days. Local storage on your device keeps your conversations, your settings and (if you generated one) your API key and sync secret. Clearing site data removes all of it.
Payments
Payments happen on the Base network from your own wallet. Blockchain transactions are public by nature. We record the transaction hash to prevent reuse and nothing else about your wallet activity.
Your rights
You can export your history from the app at any time, delete synced history by disabling sync, and ask for your account row to be deleted. Contact details are on the terms page.
Last updated: September 2026.