Data use

As a condition of use, Flovia collects how you use its data lookups and uses it as data, and Nansen lookups are also shared with Nansen. You agree to this once, when you register, by accepting the Terms of Service and Privacy Policy. This page summarizes what Flovia does under them today. Ask your agent “What does Flovia share?” at any time for the full data-use notice. The Privacy Policy (opens in new tab) covers all personal information Flovia handles.

Agreeing to the notice

Accepting the Terms of Service and Privacy Policy when you register is your yes, so neither Console nor chat asks again unless the law or the Privacy Policy requires a new answer.
If you signed in through the earlier waitlist sign-in instead, Console shows the full notice before your first key, and agreeing there is your yes.
A key created outside Console, or one whose only answer is to a version Flovia no longer accepts, is shown the full notice once, at its first lookup, and asked y or n. It is never asked twice, and your agent cannot answer for you.
With n, lookups, text generation and your referral code stop. Nothing else is deleted, and you can change to y at any time.

What Flovia keeps

For each data lookup: what you asked, what you want to decide with it (one sentence your agent writes from the conversation), the lookups, and how your agent called Flovia.
Lookup and text-generation records include the app family, such as Claude Code or Codex, when it can be recognized. This field does not keep the app version or the full User-Agent.
For refused tool calls, Flovia records the tool name, refusal code, app family and time, without the request or answer text. These records are deleted after 30 days.
To keep keys from being shared and regional limits from being bypassed, Flovia records for each hour the country and network (ASN and its name) that Cloudflare reports for your requests, without your IP address. These records are deleted after 90 days.
Feedback. If a Flovia answer looks wrong, your agent may send Flovia a short excerpt of your request and the answer as feedback on its own, and it tells you when it does.
Flovia may copy shortened, partly masked excerpts of feedback into an external team chat service for its operators to read. These copies are scheduled for deletion after 7 days, or sooner if you stop sharing or the original feedback is deleted. If you stop sharing, they are deleted within 30 days at the latest.
Counts and costs.
Flovia uses these records to learn how people look things up with agents and improve Flovia, and to help data providers improve their data for agents.

What each data source receives

Nansen: your request text, what you want to decide with it, the names of other tools your agent used for the same request (names only), the Nansen endpoint and conditions your agent chose, and Nansen’s answer are shared with Flovia and Nansen. Each time Flovia fetches from Nansen, Nansen receives the endpoint and conditions, and Flovia may give Nansen the rest. The same applies when you pay from your purchased balance.
CoinGecko and Quicknode: only the lookup itself (a coin, an address, a method, search terms and conditions), never your request text or purpose. Flovia keeps the request text, what you want to decide and the conditions (for Quicknode, also chains, addresses and transaction hashes).
Exa: only your search terms for public information, never your request text or purpose. Exa may use them to improve its service, including model training. Do not put private or personal information in a search.
Firecrawl sharing and retention: only the allowed public HTML URL, the scrape settings and an anonymous reference ID go to Firecrawl, never your request text or purpose. Flovia keeps the page text for you alone for about 15 minutes, and the request text, purpose, URL and settings for 2 years (30 days after you stop sharing). Firecrawl keeps pages in its normal index and cache without zero data retention (ZDR). Firecrawl fetches and caches pages in the US under its own Terms (https://www.firecrawl.dev/terms-of-service (opens in new tab)) and Privacy Policy (https://www.firecrawl.dev/privacy-policy (opens in new tab)). Those documents set no deletion period for these pages and make no commitment about model training. A cache setting of up to 2 days is not a deletion guarantee.
Zerion sharing and retention: only the public wallet address and conditions (chain, period and so on) go to Zerion, never your request text or purpose. Flovia keeps the address with the lookup’s record for 2 years (30 days after you stop sharing) and never shares Zerion’s answers with anyone else.
OpenAI text generation: the text you send and an account-derived identifier (not your name, email or key) go to OpenAI for safety checks and generation. OpenAI does not use them for training but may keep them for up to 30 days to monitor abuse.
Flovia gives Nansen none of the records from the other sources.

Answers

Flovia may reuse a Nansen answer for about 10 minutes for anyone who asks the same lookup.
Public CoinGecko and Quicknode answers (prices, markets, block data) may be reused for someone else who makes the same lookup, for about a minute at most. Answers about wallets or transactions are never reused.
Apart from Nansen’s answers and the reports you choose to save below, Flovia keeps answer text only for short-term delivery and reuse. If a reply does not reach you, you can usually retrieve that answer yourself for about 15 minutes. Only you can, and after that Flovia cannot return it.

Reports you choose to save

A report is optional and needs your explicit opt-in for that one report. Your agent can send its final or partial answer, the Flovia lookups it used and whether the work finished or stopped. Your request as you wrote it is included only if you agree to include it. Flovia does not read your conversation by itself, and your agent must not send the rest of the conversation, raw answers from other services, instructions, reasoning or secrets.
Reports are used only to check Flovia’s own work, never shared with Nansen or other data providers and never used to train AI. Their text is deleted after 90 days, or 30 days after you stop sharing, and you can ask your agent to delete a report at any time. Only that a report was saved, when and its status labels remain. Saving a report costs nothing and does not change your credits or free use. Saying no saves nothing.

How long Flovia keeps records

Data-lookup request texts, purposes, stored Nansen answers, wallet addresses and feedback are kept for 2 years for analysis during the alpha, then deleted. Records made before you agreed to the current notice keep 90 days.
If you stop sharing, they are deleted 30 days later.
Counts and costs are kept.
In OpenAI generation records, Flovia does not store your input text. It keeps a keyed fingerprint to detect resends for 90 days, the answer for you alone for about 15 minutes, and counts and costs. Reports you choose to save follow the separate limits above. A safety refusal generates and charges nothing, and Flovia records only the event and time. Too many refusals stop that person’s new generations until an operator reviews them. This record is kept for 30 days or until the stop is lifted, and a safety stop remains even after you stop sharing.
When you confirm an email address, Flovia keeps an irreversible value derived from it for 2 years so that free credit is granted only once per address. This value remains even if you delete the address or stop sharing; its link to you is removed.
These are Flovia’s retention periods, not deletion promises for the data sources.

For a request you don’t want shared, say “Don’t share this.” Flovia is not used for that request.
To stop, tell your agent “Stop sharing with Flovia.” Lookups stop from then on, and your request texts, answers and feedback are deleted after 30 days.
To use Flovia again, tell your agent you want to use Flovia again and answer y to the confirmation question. This works even after 30 days; only what was deleted cannot be restored.
Your purchased balance stays yours either way. Any unused purchased balance can be refunded on request. If Flovia suspends or terminates your account for a Terms violation, the unused purchased balance is not refunded unless the law requires it (Terms §3 (opens in new tab)).
To remove the connection, run claude mcp remove flovia --scope user or codex mcp remove flovia.

Never send secrets

Do not put keys, recovery phrases (seed phrases) or passwords in a request. Flovia refuses them and does not store them. If you included a real one, replace it right away.