Data use

Agreeing to the notice

• Agreeing to the full notice in Console is your yes, so chat does not ask.
• 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.
• 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.
• 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 if you buy credits.
• 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) and processes them in the US; its deletion deadline and no-training guarantee are unconfirmed. 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, Flovia stores no answers. 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.

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.
• For OpenAI text generation, 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. A safety refusal generates and charges nothing, and Flovia records only the event and time. Three refusals in 24 hours 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.

Stop sharing

• 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.
• Bought credits stay yours either way, and unused credits are refunded on request.
• To remove the connection, run claude mcp remove flovia 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.