Privacy Policy
This page explains what personal data ocrepublic handles when you turn a PDF into an EPUB, why, who else sees it, and how long we keep it. The short version: we keep your files for hours, not days, we do not track you, and we do not sell anything about you. Last updated 11 November 2026.
1. Who is responsible
ocrepublic (ocrepublic.ai, "we", "us") is responsible for the personal data described here. For anything about your data, write to support@ocrepublic.ai.
2. What we handle, and why
Your files
The PDF you upload and the EPUB we make from it. A book can contain personal data, yours or other people's; we treat the contents as yours and look at them only to convert them. We use the file to analyse it, quote its price, convert it and let you download the result, because you asked us to (performing our contract with you, Art. 6(1)(b) GDPR).
Your account
When you sign in: your email address, the ID our sign-in provider gives your account, how you last signed in (email code, Google or Microsoft) and when. We need these to keep your credits, conversions and history together (Art. 6(1)(b) GDPR). We do not get or keep a password.
Credits and purchases
Each purchase, conversion and refund of credits is a line in your credit records, with its date and the file name it was for. For a purchase we also keep the Stripe reference and the pack you bought. Card details go to Stripe and never reach us. We keep these records to run your balance (Art. 6(1)(b) GDPR) and because tax and accounting law requires purchase records (Art. 6(1)(c) GDPR).
Your history
For each conversion: the file name, its pages, the credits it cost, when it ran and whether you downloaded it. It is your list; you can remove entries from it.
Free previews and abuse limits
To limit free previews and stop automated abuse, we count requests per network (IP) address and, when you are signed out, per browser. We store only a one-way hash of the address and of a random browser ID, never the address itself, and delete the address hash after 7 days. Short-lived counters of uploads and sign-ins per address live only in memory for an hour. This is our legitimate interest in keeping the free preview fair and the service available (Art. 6(1)(f) GDPR).
Server logs
Our server logs each request with its path, result and timing, and each conversion with its pages and cost, to keep the service running and find faults (Art. 6(1)(f) GDPR). The logs do not contain IP addresses or the text of your books.
Emails with us
If you write to us, we use your message and address to answer you. We do not send newsletters. Your sign-in codes come from our sign-in provider and your receipts from Stripe.
3. Who else processes your data
We use these providers to run ocrepublic. Each gets only what its part needs.
- Z.ai (text recognition): receives the images and text layer of the pages being converted, nothing about your account. Z.ai's servers are outside the European Union, so the pages of your book leave the EU for the few seconds it takes to read them.
- Fly.io (hosting): runs the app and stores files and the database on servers in Frankfurt, Germany.
- Tigris (backups, through Fly.io): holds a continuous copy of the database (accounts, credit records, history), not your files.
- WorkOS (sign-in): handles signing in by email code, Google or Microsoft, and holds your email address and sign-in details for that.
- Stripe (payments): handles checkout, card details, fraud checks, receipts and tax. Stripe is also responsible for its own processing as a payment provider.
- Cloudflare (domain): answers DNS lookups for ocrepublic.ai and forwards email sent to our support address. Your visits to the site do not pass through Cloudflare.
Where a provider is outside the EU or the European Economic Area, the transfer relies on an adequacy decision, such as the EU-US Data Privacy Framework for providers certified under it, or on the European Commission's standard contractual clauses.
4. How long we keep it
- Uploaded PDF: deleted when its conversion finishes; a PDF that was only quoted, or whose conversion failed or was cancelled, within an hour.
- EPUB: deleted one hour after your first download, or 24 hours after the conversion if you never download it.
- Preview pages: deleted together with the preview's EPUB, on the same schedule.
- Network address hashes: 7 days.
- Account, history and credit records: until you delete your account. Then your account, files and history are deleted, here and at WorkOS. The credit records are kept without any link to you, as accounting law requires for purchases.
- Backups: the database copy keeps 7 days of changes, so deleted data leaves the backups within 7 days.
- Server logs: kept briefly by our host for operating the service.
5. Cookies
We use only cookies the service needs to work, so we do not ask for consent and there is no banner. No analytics, no advertising, no tracking across sites.
ocr_session: keeps you signed in, for up to 30 days.ocr_auth_stateandocr_auth_next: protect the sign-in and bring you back to the right page; 10 minutes.ocr_visitor: a random ID that counts free previews when you are signed out; one year. We store only its hash.
Stripe's checkout page and our sign-in provider's page set their own cookies under their own policies.
6. Your rights
You can ask us for a copy of your data, to correct it, to delete it, to restrict or object to its processing, and to receive it in a portable format. Two of these are built in: Account → Download my data gives you everything we hold about you as a file, and Account → Delete account deletes it. For anything else, write to support@ocrepublic.ai; we answer within a month.
You also have the right to complain to a data protection supervisory authority, in particular in the EU country where you live or work.
7. Other points
- You do not have to give us any data to quote or preview a file. To convert whole books and buy credits you need an account, and so an email address.
- We make no automated decisions about you that have legal or similarly significant effects.
- ocrepublic is not meant for children under 16.
- We protect data with encrypted connections (HTTPS), encrypted storage at our host, and access limited to what running the service needs.
- If we change this policy, we update the date at the top; for important changes we also tell signed-in readers.