Privacy policy
Last updated 4 October 2026
This policy explains what personal data Folivore processes, why, where it is kept, who helps run the service, and the rights you have. Folivore keeps your documents in folios and answers questions about them with your own key from Anthropic, OpenAI, xAI or OpenRouter.
Who is responsible
Folivore is run by Václav Novotný, a private individual in the Czech Republic, who is the controller of your personal data. Write to support@folivore.app about anything in this policy. A postal address will be published here once Folivore operates as a registered business.
What Folivore processes
- Your account: the identifier of your sign-in account, your email address, your name and your theme setting. You sign in with Google or with your email address, to which Clerk sends a one-time link or code. With Google, your name, email address and profile photo come from Google through Clerk.
- What you put in: the files you upload; the text Folivore extracts or transcribes from them, including email headers such as sender, recipients, date and subject; file names, sizes and checksums; the names, descriptions and instructions of your folios; your questions, the answers, their citations, and the model and token counts of each answer, and the model you chose for each folio.
- Your AI provider keys, one for each provider you connect, encrypted. Only the last four characters of each are ever shown.
- Technical data: logs and telemetry with internal identifiers, the addresses of the pages and API calls you request (which contain folio and file identifiers), timings, error codes and your browser's user agent. Folivore's telemetry does not store your IP address. Clerk records the IP address and browser of each sign-in session to protect your account, and the services that deliver the app, your files and the API see your IP address when they answer.
- The Folivore AI waitlist, if you join it: your email address, as described under "Folivore AI waitlist" below.
Your uploads may contain personal data about other people, for example in contracts or emails. Folivore processes it only to provide the service to you.
Why, and on what legal basis
- To provide the service you signed up for: storing your files, reading their text, answering your questions and showing what each question costs (GDPR Art. 6(1)(b), performance of a contract).
- To keep the service secure and working: preventing abuse, limiting request rates and diagnosing errors (Art. 6(1)(f), the legitimate interest in a secure and reliable service).
- To send the one email the Folivore AI waitlist asks for: your consent (Art. 6(1)(a)).
- To meet legal obligations (Art. 6(1)(c)).
Folivore does no advertising or profiling, sends no marketing beyond that one waitlist email, and makes no automated decisions with legal or similarly significant effects. Your account data is needed to use Folivore: without it you cannot sign in.
Your AI provider keys
Your API keys are stored encrypted with a key held in Azure Key Vault. Folivore's server can decrypt them in order to call your AI providers on your behalf. A key is never shown back to you, except its last four characters, and never written to logs.
Your AI providers
Folivore calls Anthropic, OpenAI and xAI with your own key, under your own agreement with each of them; Folivore is not their customer for these requests. For each question it sends the full text of every ready document in the folio, each document's name and type (and the sender and date of an email), the folio's instructions, the conversation so far, your question and the chosen model. To read an image or a scanned page it sends the image, or the scanned pages of the PDF, to the provider and model you chose for the folio. Each provider's terms with you govern what it does with that data. The requests come from Microsoft's data centre in West Europe (the Netherlands), and each provider may process them in the United States and other countries.
- Folivore asks OpenAI and xAI not to store the requests (
store: false), but both keep API requests for up to 30 days to monitor for abuse, unless longer retention is required by law or needed to protect their services or others from harm, or your account with them has zero data retention. - OpenRouter is called with your own OpenRouter key and forwards each request to an upstream provider of the model you chose. Folivore asks OpenRouter to use only upstream providers that do not keep your prompts (
data_collection: "deny"). The upstream provider's own terms govern what it does with them.
Folivore AI waitlist
The home page lets you join a waitlist for Folivore AI, a planned option in which Folivore provides the AI. If you join it:
- What is kept: your email address, when you joined, which version of this policy you were shown, and a hash of a random token that lets your browser correct the address later. Folivore never stores your IP address with it.
- Why: One email when Folivore AI launches. Nothing else.
- Legal basis: Your consent (GDPR Art. 6(1)(a)). You can withdraw it at any time: write to support@folivore.app, and your address is deleted. Withdrawing does not affect what was done before.
- Where: Folivore's database at Neon, in Frankfurt, Germany.
- How long: Until the launch email is sent, then deleted, or earlier if you ask.
- Against abuse: while it handles a join, the server counts joins per IP address and per email address in its memory only, for at most a day, to limit repeated attempts. Neither is written to the database or to logs.
- On this device: your browser remembers that you joined, under
folivore_waitlistin its local storage (the address, when, and the token), so the page can show it. Clearing the site's data removes it. - Not shared: the list is not shared or sold. If an email service is used to send the launch email, it will be named here before that email goes out.
Who helps run Folivore, and where
- Microsoft Azure runs the application, holds the encryption key in Key Vault and keeps logs and telemetry, in West Europe (the Netherlands).
- Neon hosts the database in Frankfurt, Germany, on Amazon Web Services.
- Cloudflare stores your files in its EU jurisdiction, serves the web app from its global network, provides DNS, and forwards email sent to support@folivore.app.
- Clerk handles sign-in and sessions and sends the one-time sign-in links and codes, in the United States. Its sign-up form checks for bots with Cloudflare Turnstile, which reads signals from your browser.
- Google, if you sign in with it, is a separate controller of your Google account; it shares your name, email address and photo with Folivore through Clerk. Email sent to support@folivore.app is delivered to the operator's mailbox at Google.
Where one of them processes data outside the European Economic Area, the transfer relies on the EU–US Data Privacy Framework or the European Commission's standard contractual clauses. A copy of the safeguards is available on request.
Folivore's public status page (https://folivore.betteruptime.com) is hosted by Better Stack, which checks that folivore.app responds and shows Anthropic's service status; it receives no personal data about you from Folivore.
How long data is kept
- Your account and everything in it: until you delete your account, in Settings → Account. Your email address, your name, your theme setting and any waitlist entry for that address go at once; your folios, files, extracted text, chats, stored keys and AI settings, and your sign-in account at Clerk, within a few minutes. If you can no longer sign in, write to support@folivore.app from the address you sign in with: the operator deletes the account for you and confirms by email, within a month at the latest. You can delete files, chats, folios and your API keys yourself at any time.
- What stays of a deleted account is a record that it was deleted: its internal identifier, the identifier of your deleted sign-in account, and when. It stops a session that is still open from bringing the account back, and it is deleted 30 days after your sign-in account at Clerk.
- Database backups: up to 7 days.
- Application telemetry (requests, timings, errors and the application's logs): 90 days.
- The server's console logs: 30 days.
- Internal job and event records hold random identifiers only, never content. Finished jobs are deleted after 7 days, and event records 30 days after they were handled.
- Cloudflare may keep technical request logs of the web app for a few days.
- Emails to support@folivore.app: as long as needed to answer them.
- The Folivore AI waitlist: until the launch email is sent, or earlier if you ask.
Your rights
You can ask for access to your data, its correction or erasure, a restriction of its processing, and a copy in a portable form; your files can be downloaded at any time, and the rest is sent on request. You can object to processing based on legitimate interests, and withdraw a consent you gave at any time. Write to support@folivore.app. You can also complain to a supervisory authority: in the Czech Republic the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, uoou.gov.cz), or the authority of the EU country where you live or work.
Cookies and browser storage
Clerk sets the cookies that keep you signed in; they are strictly necessary. Folivore keeps your light or dark choice in your browser's storage (folivore-theme); if you joined the Folivore AI waitlist on this device, that you joined (folivore_waitlist); and, once you close the notice of a change to this policy, which change that was (folivore-policy-seen). There are no analytics, advertising or tracking cookies, and so no cookie banner.
Age
Folivore and its waitlist are for people aged 16 and over.
Changes to this policy
Changes are posted here with a new date. A material change is announced on this page and in the app before it takes effect: a notice at the top of every page, until you close it.