Flipbooks AI Privacy Policy
This policy explains what personal data Flipbooks AI (https://flipbooksai.com) collects, why, who processes it with us, how long we keep it and what rights you have. It covers the people who create flipbooks with an account and the people who read them.
Who Is Responsible for Your Data
The controller of your personal data, meaning the one responsible for it, is the person who runs Flipbooks AI. Their details are in the Who We Are section of our Terms and Conditions. For anything about your data, write to contact@flipbooksai.com.
Your account and your files are stored with Google Firebase, and signing in is handled by Firebase Authentication, with your email address and password or with your Google account. We do not sell your data or share it with anyone for their own use.
For the data that readers submit through a lead form, the controller is the owner of the flipbook, as explained below.
What We Collect
- Account. Your email address, your name and, if you sign in with Google, the name and photo of your Google profile. Your password is handled by Google Firebase Authentication and we never see it. We also keep when your account was created and when you last signed in.
- Your content. The PDF files, images, logos and audio you upload, the titles, descriptions and notes you write, the settings of each flipbook, and the reader names and passwords you set to protect a flipbook. Those passwords are stored only as secure hashes.
- Purchases. The plan, amount, currency, date and order number of each purchase, the country estimated from your connection, whether you bought from a mobile device and, if you arrived through an ad, the identifier of that ad click. For cryptocurrency payments we also keep the wallet address the payment came from and the details of the transaction. We never receive your card details.
- Readers of flipbooks. For each flipbook we count how many times it has been opened and when it was last opened, without recording who opened it. If a reader who is signed in saves bookmarks, we store them with their account. If a flipbook has a lead form, we store what the reader submits on behalf of the owner of the flipbook.
- Messages. What you write to us when you email us.
- Technical data. Our hosting provider processes your IP address and basic request data to deliver the site and protect it from attacks. Our server functions keep short technical logs that may include your account identifier.
Why We Use It and Our Legal Basis
- To provide the service you signed up for: your account, hosting and publishing your flipbooks, payments and support. The legal basis is the contract between us.
- To keep purchase records as tax and accounting law requires. The legal basis is a legal obligation.
- To protect the service, prevent fraud and abuse, count views, learn which ads lead to purchases and be notified internally of each sale. The legal basis is our legitimate interest in running a secure and sustainable service.
We do not send marketing emails, we do not sell your data and we do not make automated decisions that have legal or similarly significant effects on you. You need an email address to create an account; without it we cannot provide the service.
Who We Share It With
We share personal data only with the providers that help us run Flipbooks AI, and only as much as each one needs:
- Google, through Firebase, for sign in, the database, file storage and the emails that verify your address or reset your password.
- Cloudflare, for hosting the website, running our server functions and delivering images.
- Our payment providers, which process your payment on their own pages. We send them only the order number, your account identifier, the plan and the amount. For card payments we also send the email address of your account, so you do not have to type it and the receipt reaches you. Whatever you enter on their pages is handled under their own privacy policies.
- Slack, which we use to notify ourselves of each sale with the account identifier, plan, amount, country, device type and whether the sale came from an ad.
We may also disclose data when the law requires it, for example to answer a valid request from a court or an authority. We never sell personal data.
International Transfers
Google, Cloudflare and Slack may process data in the United States and in other countries outside the European Economic Area. These transfers are protected by the Data Privacy Framework between the European Union and the United States, or by the Standard Contractual Clauses approved by the European Commission.
How Long We Keep It
- Your account and content are kept while your account exists. Deleting a flipbook removes it and its lead submissions. Uploaded files are kept until you delete your account.
- Purchase records are kept for as long as Spanish tax and commercial law requires, generally up to six years, even after your account is deleted.
- Emails you send us are kept for as long as we need them to help you.
- Technical logs are kept for a short time set by our hosting provider.
You can delete a Free account yourself from your account page once it is at least 72 hours old. If you have ever bought a plan, email us from the address of your account and we will delete it within one month, keeping only the purchase records the law requires.
Your Rights
You can ask us to access, correct or delete your personal data, to restrict or object to how we use it, and to receive it in a portable format. Email contact@flipbooksai.com from the address of your account, or tell us how to check that the request comes from you. We answer within one month. If you are not satisfied with our answer, you can complain to the Spanish Data Protection Agency (www.aepd.es) or to the data protection authority of the country where you live.
Lead Forms and Flipbook Readers
When you fill in a lead form inside a flipbook, the owner of that flipbook decides what it asks and what happens with your answers, and is responsible for them. We store your answers on their behalf, show them only to that owner and delete them when the owner deletes the flipbook or their account. To use your rights over that data, contact the owner of the flipbook. If you cannot reach them, write to us and we will pass your request on.
Reading a flipbook does not require an account. If you read without signing in, your bookmarks and the last page you read are saved only in your browser.
Cookies and Browser Storage
Flipbooks AI does not set its own cookies and does not use analytics or advertising trackers. Your browser stores a small amount of information that the site needs for the features you use:
- keeping you signed in to your account;
- remembering layout and display preferences, such as the shape of your flipbooks and whether the sidebar is open;
- remembering the last page you read and your bookmarks when you are not signed in;
- remembering that you already filled in or skipped a lead form, or unlocked a protected flipbook during this visit;
- keeping the plan you chose while you sign in or retry a payment, and remembering that you closed a promotion bar.
Because this storage is needed for those features, we do not show a consent banner. You can delete it at any time by clearing your browser data. Other services can set their own cookies when you use them: Google when you sign in with Google, and the videos or web pages that a flipbook owner embeds, such as YouTube, which we load in its privacy enhanced mode, or Vimeo, which we load with Do Not Track.
Security
All traffic to Flipbooks AI is encrypted with HTTPS, and our providers encrypt the data they store. Account passwords are handled by Google, and flipbook passwords are kept only as salted hashes. Keep in mind that a published flipbook, and the files it is made of, can be opened by anyone who has its link. No system is completely secure; if a breach ever puts your data at risk, we will tell you and the authorities as the law requires.
Children
Flipbooks AI is not intended for people under 18, and we do not knowingly collect their data. If you believe a minor has given us personal data, write to us and we will delete it.
Changes to This Policy
We may update this policy when the service or the law changes. We publish every new version on this page with its date.
Last updated: October 3, 2026