Privacy Policy

Flippy: AI PDF & EPUB Reader · Effective November 1, 2026

Overview

Flippy is a PDF and EPUB reader for Android, iPhone and iPad, and Mac, and a website at flippypdf.com, with optional read-aloud, AI, and cloud sync features. Your privacy matters to us. This policy explains what data Flippy accesses, how it is used, and your choices. In short: your books stay on your device, there are no ads, we do not sell your data, and the only things that ever leave your device are the specific pieces of text (or reading data) needed to run a feature you chose to use.

Data Stored on Your Device

Flippy stores your library and everything you create locally on your device. This data stays there unless you choose to sign in and turn on Cloud Sync (free and optional; see the next section), and even then only the reading data listed there is uploaded — never your files. The read-aloud and AI features described further down are the other exception: when you use one, the specific text involved is sent away to be processed, as explained in those sections.

• PDF and EPUB files you import into the app (an EPUB is converted into pages on your device when you import it)
• Bookmarks, highlights, notes, and annotations you create, and drawings made with the draw tool
• Reading progress and statistics (current page per book, pages read, time spent, streaks, the dates you read)
• App preferences (theme, language, reading settings, voice and reading style, collections and tags)
• Your AI conversations — the questions you ask and the answers you get back are saved on your device so you can come back to them later, kept separately for each book. They are never uploaded, and they are deliberately not included in Cloud Sync. You can erase a book's conversation at any time with the "Clear chat" button in the AI panel.
• Saved study sets and My Words — flashcards and quizzes you save, and the personal dictionary of words you look up, are kept on your device and are not synced
• Downloaded read-aloud audio — if you choose to download a chapter for offline listening, the generated audio is saved in the app's private storage on your device and can be deleted at any time
• A copy of your top-up balance — if you buy a top-up pack, the app keeps a local copy of your remaining minutes and AI uses; the master record lives on our backend (see In-App Purchases)
• Your answers to the first-launch questions — what you plan to read, what would help most, and the voice you picked. They are used on your device to order tips and the first screens, and are never uploaded. Our backend only counts, by event name, how many installs picked each answer (see the event counters below).

Flippy's interface is available in 18 languages. Your language choice is stored on your device and travels with AI requests so that answers come back in your language.

This local data is stored in your device's app storage and is not accessible to us or any third party.

Cloud Sync (optional, free)

Cloud Sync is optional and free for all users — no subscription is required to sign in or sync. Nothing is uploaded until you sign in. If you choose to sign in, the following applies:

• Authentication: You sign in with your Google account through Google Sign-In and Firebase Authentication. We receive your name, email address, profile photo, and a Firebase user ID, which are used to show who is signed in and to file your synced data under your account. We do not see or store your Google password.
• Data synced: For each book in your library: its name and page count (so a second device can recognize the same file; the file itself is matched by a fingerprint computed on your device), your bookmarks and their notes, your highlights (including the highlighted passage, its color, and any note), your reading position (and when you last turned to it, so another of your devices can offer to continue there), and which collection it belongs to. Plus your collections and your reading statistics (pages read, minutes, streaks, and the dates you read). This is stored in Google Firebase Firestore under your Firebase user ID and is written while you are signed in.
• Never synced: your PDF and EPUB files, your AI conversations, saved study sets, My Words, downloaded audio, and top-up balances. Only your reading data is synced.
• Your plan on all your devices: while you are signed in, the app sends your Firebase sign-in token to our backend, which links that device (its install ID) to your Google account's user ID. A subscription bought on one of your signed-in devices, or on the website, then also works on your other signed-in devices. We keep the link — your user ID and the devices linked to it (at most 10; a new device is turned away while all 10 are in use, unless one of them has not been used for 30 days) — until you sign out on that device, use Delete Account & Data on it, or reinstall the app. To remove the links of all your devices at once, email us.
• Signing out stops syncing and leaves your cloud data in place for the next time you sign in. Delete Account & Data in Settings → Cloud Sync deletes the reading data we hold for you in Firestore and signs you out; your local data is untouched. See Data Deletion below.

The Flippy Website (flippypdf.com)

You can also read in any web browser at flippypdf.com.

• Your files stay in your browser. PDFs you open on the website are stored in that browser's own storage on that computer. They are never uploaded to us or anyone else. Clearing the site's data in your browser removes them.
• Sign-in and sync work as in the apps (see Cloud Sync above): the same Google Sign-In and Firebase Authentication, and your bookmarks, notes, highlights, reading positions and collections sync the same way. Delete Account & Data works on the website too.
• Read-aloud, AI, and purchases on the website work when you are signed in. The website then sends your requests (page text to read aloud, your AI questions with the relevant page text, a word to define) to our backend together with your Firebase sign-in token, which tells our backend your Google account's user ID. Our backend routes them to DeepInfra, OpenAI or Anthropic exactly as it does for the apps (see below). The website itself sends no analytics or event counts. Our backend keeps daily totals only: how many times website pages started (signed in or not), how many signed-in readers visited that day (counted through a one-way code of the account ID that is deleted after two days), and how often prices were shown. No IP address or visitor ID is stored.
• Read-aloud without a plan uses your browser's own built-in voice. Depending on your browser and the voice it picks, the browser maker may process that text online under its own terms (for example, some voices in Chrome are provided by Google).
• Import URL on the website: browsers may only download files from sites that allow it, so when you paste a link the website's own server fetches that PDF for you and passes it straight to your browser. It sees the link and your IP address (to limit how many links can be fetched a minute), logs only the site's name and the file's size (or why it was refused), and does not keep the file.
• To show the prices for your country, our backend uses the country of your IP address as reported by Cloudflare. The country is not stored with your account.
• The website is hosted on Cloudflare, which sees your IP address as any website host does. So that sign-in works in browsers that block third-party storage, flippypdf.com passes Google sign-in pages through to Firebase (flippy-pdf.firebaseapp.com). Like the apps, it loads open-source libraries from cdnjs.

Free Week, Free Sample, and Paid Allowances

The read-aloud and AI features below are available with a Premium or Pro subscription, during the free week that starts when you first install the app, from a small free monthly sample, or from a purchased top-up pack. The data handling described in each section is the same in every case. When a free user's sample minutes run out, read-aloud continues in your phone's own built-in voice, which runs entirely on your device and sends nothing anywhere.

AI Read-Aloud

Flippy's natural voices are generated by Kokoro, an open-source voice model, which DeepInfra runs for us, with Together AI running the same model as a second host when DeepInfra is slow or unavailable. Pages in a language Kokoro does not speak yet are read by OpenAI's Text-to-Speech API, which is also the last backup if neither Kokoro host can generate a page.

• When you use this feature, the text of the page being read is sent via our backend to DeepInfra (or, as described above, to Together AI or OpenAI) to generate audio. So that playback does not pause between pages, the text of the next page or two may be sent slightly ahead of when you reach it. If you ask Flippy to read an AI answer out loud, that answer text is sent as well. Downloading a chapter for offline listening generates its audio the same way, once, at download time.
• No PDF or EPUB files are uploaded. Only extracted text is transmitted.
• Choosing the voice service: our backend looks at the text of each page to tell which language it is in, and sends it to a Kokoro host if Kokoro speaks that language, or to OpenAI if it does not. So that a book does not switch voices on a page with very little text (such as a chapter title or a reference list), our backend remembers the language of the last page you listened to — only the language, for example “Spanish” — under your install token for one day. Before the text is sent, our backend may rewrite parts of it so they are read aloud correctly (for example numbers, abbreviations, Roman numerals and web addresses); this happens in memory and nothing is kept.
• DeepInfra processes the text and returns audio. Per DeepInfra's Data Privacy terms, the text is held only in memory while the audio is generated and is never written to disk, the audio is deleted once it has been returned, the content of requests is not logged, and the data is not used to train models or shared with anyone else.
• Together AI processes the text and returns audio when it is used as the second host. On our Together AI account, storage of requests and responses is turned off, sending requests on to third-party providers is turned off, and use of our data for training is turned off. Together AI's handling of data is governed by its Privacy Policy.
• OpenAI processes the text it receives and returns audio. OpenAI's use of this data is governed by OpenAI's API Data Usage Policies. Per their policy, data sent via the API is not used to train their models.
• Audio cache: so that re-reading a chapter does not generate the same audio twice, our backend keeps a copy of generated audio in Cloudflare's edge cache for up to 30 days. Each copy is filed under a one-way hash of the text together with the voice, speed, and reading style — not under your install token — so it is not linked to you. It does mean that audio of a page you listened to can exist on our infrastructure for up to 30 days, and that anyone who requests exactly the same text with the same settings would receive the same cached audio. Beside some of that audio we keep the time each word starts, as numbers only, so the follow-along orb can stay under the word being read.
• The short voice-preview sentences in Settings, on the first-launch screens, and on the subscription screen are fixed sample lines, not text from your books. The app sends its display language with them so that the right voice speaks them.

AI Q&A, Summaries, Explain, Study Tools, and Define

Flippy uses Anthropic's Claude API to answer questions about your books, generate summaries, explain highlighted passages, create study materials (flashcards and quizzes) from chapters you choose, and define words.

• When you use these features, the text content of your book (the most relevant pages for your question, or the chapter you selected) is sent to Anthropic's Claude API along with your question.
• When you ask the AI a question, images of the pages involved may be sent with the text so the AI can read charts, tables, figures and pictures: the page you are reading, the page that best matches your question, and, when your question mentions something like a chart, graph, table or picture, a few more matching pages. When you use Explain on a page that contains figures, diagrams, tables or comic panels, an image of that page is sent. Images are not stored beyond the request.
• To work out which pages are the most relevant, Flippy may first send your document's table of contents together with a short one-line extract from each page. This step covers more of your document than the answer step, but it is used only to pick the right pages to read closely.
• If you ask about another book in your library while reading, the same table-of-contents-and-extracts step, and then the relevant pages, may be sent for that other book too.
• When you ask a follow-up question, the earlier turns of that conversation are sent along with it so the AI has context. Conversations are otherwise only stored on your device.
• Define: the selected word and your app language are sent via our backend to dictionaryapi.dev; when the dictionary has no entry, or the app is set to a non-English language, the definition is generated with Anthropic's Claude API instead. Definitions are cached on our backend by word alone for up to 90 days, never linked to your install.
• Search the web: when no definition is found and you tap Search the web, your web browser opens a DuckDuckGo search for the word. That search happens in your browser, under DuckDuckGo's privacy policy.
• This data is processed to generate a response and is not stored by Flippy.
• Anthropic's use of this data is governed by Anthropic's Commercial Terms. Per their policy, data sent via the API is not used to train their models.

Help & FAQ Question Box

Settings → Help & FAQ includes a box where you can type or speak a question about the Flippy app itself. It first searches the built-in FAQ on your device. If you choose "Ask Flippy AI", your question is sent via our backend to Anthropic's Claude API together with a fixed description of the app, so it can answer. None of your books, reading data, or conversation history is sent — the box has no access to them. This is free for everyone and does not count against any allowance; to prevent abuse it is limited to 20 questions per day per install. Spoken questions are transcribed the same way as Ask Aloud (next section). Answers are generated automatically and may be wrong; the written FAQ and our support email are the authoritative sources.

Ask Aloud / Speak-to-PDF Voice Questions

Flippy lets you ask questions out loud — about your book, as a spoken follow-up in Explain or Study, or in the Help & FAQ box. This feature uses your device's microphone.

• The microphone is only active while you are recording a question (after you press the microphone button). Flippy never listens in the background.
• On iPhone, iPad, and Mac, your speech is transcribed entirely on your device, using Apple's built-in speech recognition. Your voice recording never leaves your device — only the resulting text is used, and the recording is deleted straight afterwards. If your device cannot transcribe (for example, Dictation has never been enabled), Flippy tells you what to enable; nothing is uploaded.
• On Android, Flippy transcribes your speech on your device first, using Android's built-in speech recognition — on most modern devices this is what happens, and the recording never leaves your device. Only if on-device recognition produces no result is the voice recording sent via our backend to OpenAI's transcription API (Whisper). In that case the recording is used only to produce the transcript and is not stored by Flippy or our backend beyond the lifetime of that request.
• The transcribed question is then handled exactly like a typed question (see the sections above), and the spoken answer is generated with OpenAI's Text-to-Speech.
• OpenAI's handling of this audio is governed by OpenAI's API Data Usage Policies. Per their policy, data sent via the API is not used to train their models.

AI Explain Pictures

When you highlight a word or phrase and tap "Explain," Flippy generates a short, even-handed explanation of that term from the surrounding text (see the AI section above) and, where it helps, shows a picture.

• To find pictures, the highlighted term (or a short related search phrase the AI suggests based on it) is sent directly from the app to Wikipedia and Wikimedia Commons to look up public images and their descriptions, which are shown as captions. For a person or place, Wikimedia Commons may be searched for several photos of that subject.
• These are standard public search requests, made directly from your device; no account, login, or personal data is involved, but Wikimedia's servers see your IP address the way any website you visit does.

In-App Purchases

Flippy offers optional Premium and Pro subscriptions and one-time top-up packs of extra natural-voice minutes and AI uses. All purchases are processed by Apple (App Store) or Google (Google Play). We never see or store your payment details; billing, receipts, and refunds are handled entirely by the respective store.

• Subscriptions: to confirm a subscription is active, the app sends your App Store or Google Play purchase receipt to our backend, which checks it with Apple or Google. The receipt contains no name, email, or payment details; the verification result is cached for up to 72 hours.
• Renewal and refund notices: Apple and Google also send our backend a notice when a subscription starts, renews, is cancelled or refunded, or a store free trial ends. We use these only to count how subscriptions are doing. For each subscription we keep its first-seen date, whether it began as a trial, and how many times it has renewed, filed under a one-way hash of the store’s subscription ID; we also keep daily counts of each kind of notice and a list of the last 100 notices (the kind, the product, its price and currency, and the date). These are kept for up to 400 days. They contain no install token, name, email, Apple or Google account details, or payment details.
• One subscription, several devices: a subscription can be used on up to 5 devices, and its monthly read-aloud minutes and AI uses are shared by all of them. To do this, our backend keeps a record for each subscription, filed under a one-way hash of the store's purchase ID: the anonymous install tokens of the devices using it (up to 5), the dates each one first and last used it, and the subscription product. A device that hasn't been used for 30 days gives up its place to a new one. This record is kept without a time limit (see Data Deletion). The backend also counts the minutes and AI uses the subscription draws each month, under the same hash; these counts are kept for about 40 days. None of this contains a name, email, or payment details.
• Top-up packs: when you buy a pack, the app sends the store's purchase token (Google Play) or signed transaction (App Store) to our backend, which verifies it with Google or Apple and then credits your balance. Our backend keeps a purchase ledger keyed to your install token: the pack bought, the store's order or transaction ID, the platform, the quantity, the date it was credited, whether it was a test purchase, and running counts of the minutes and AI uses you have drawn from it. It contains no name, email, or payment details. Because packs never expire, the ledger is kept without a time limit (see Data Deletion). The balance is tied to the device install it was bought on: the hashed device identifier described below lets it survive a reinstall on the same device, and "Restore" simply re-reads the ledger. It cannot be moved to another device, account, or person.
• If a top-up purchase is refunded or reversed by the store, we may remove the corresponding credit.

Purchases on the Website (Stripe)

Plans and packs bought on flippypdf.com are sold and processed by Stripe as merchant of record, through Stripe's Managed Payments service (receipts may say “Sold through Link”). Stripe collects your payment details, name, email address, and billing address to process the payment, calculate tax, prevent fraud, and send receipts, under the Stripe Privacy Policy and the Link Privacy Policy. We never see your full card details.

• When you start a purchase, our backend creates a Stripe customer record for you with your Google account's email address and user ID, so the purchase can be matched to your account.
• From Stripe we receive and keep, filed under your Google account's user ID: your Stripe customer and subscription IDs, the plan, its status, whether it is set to cancel, and the date it is paid until. We use them to turn your website plan on and off and to open Stripe's page when you choose Manage subscription.
• Your website plan's monthly read-aloud minutes and AI uses are counted under your user ID (kept for about 40 days), and website packs are kept in a purchase ledger under your user ID, in the same way as described for the apps above.
• These records contain no card details. They are kept while you have a website plan or pack balance, and until you ask us to delete them (see Data Deletion). Stripe keeps its own payment records as the law requires.

Our Backend, Analytics, and Advertising

There are no ads inside Flippy. We do not display ads, sell your data, or include any third-party advertising or analytics SDKs (no Meta/Facebook SDK, no Google Analytics, no crash reporting SDKs).

Flippy uses a small backend service we operate (a Cloudflare Worker) to route read-aloud, AI, transcription, dictionary, and purchase-verification requests to their providers. This proxy lets us keep our API keys server-side so they aren't extractable from the app, and lets us apply usage limits. The backend receives:

• An anonymous install token — a random ID created the first time the app contacts our backend. It is stored on your device, and our backend keeps a record of it alongside the date it was created, your platform, the app version, and the IP address it was created from. It is used to apply the free sample and rate limits per install so a single device can't run up unexpected charges, to hold your top-up balance, and to count unique installs in the anonymous event counters described below. It is not linked to your name, email, or any account.
• A hashed device identifier — a one-way SHA-256 hash of a device identifier (on Android, the app-scoped Android ID; on iOS, a random ID the app keeps in the device Keychain; on Mac, the Mac’s hardware ID, which the app hashes before sending). The raw identifier never leaves your device. The backend stores only the hash, next to the install token it was first seen with, and uses it solely to recognize a device that has already used Flippy, so that uninstalling and reinstalling the app does not reset the free week or free sample — and so that a purchased top-up balance is not lost on reinstall. It is not linked to your name, email, account, or advertising identifier, and it is never shared with anyone.
• The text of your AI question (or highlighted term) and the book content you're asking about (only for AI Q&A, summary, Explain, Define, and study-tool requests; only for as long as it takes to forward the request).
• The page text you've asked Flippy to read aloud (only for read-aloud requests; the generated audio may be cached as described above).
• The text of a question you ask in the Help & FAQ box (only for as long as it takes to forward it).
• On Android only: your voice recording when you ask a question by voice and it could not be transcribed on your device (only to forward it for transcription; see the voice section above). On iPhone, iPad, and Mac, voice recordings are never sent to the backend.
• Your App Store or Google Play purchase receipt or transaction when the app verifies a subscription or credits a top-up pack (see In-App Purchases).
• Remote settings and test groups: a few seconds after the app starts, it asks our backend for its current settings (for example, the length of the free week or how often tips may appear), sending its install token. When we are comparing two versions of a screen, the backend puts each install in group A or B, chosen from the install token, and keeps a record of which group it gave that install (the test's name and the letter, filed under the install token) for 90 days, so the anonymous event counters can be split by group. Nothing else is stored, and no record is made while no test is running.
• App screen updates (Android, iPhone and iPad): the app checks our backend for an updated version of its screens and downloads the files if there is one. The check sends only the platform and the app's build number — no install token, device identifier or reading data. Each update is signed by us and checked on your device before it is used.
• Your IP address, as is standard with any HTTPS request. It is recorded once alongside your install token when that token is first created, and it appears in our backend's short-term request logs. Cloudflare may also retain it in standard request logs (typically days, not months).

The backend does not store the contents of your questions or book pages beyond the lifetime of each request. Per install, it keeps only small operational records: how much of the free monthly sample has been used (kept for about 40 days), how many natural-voice minutes the free week has used (kept for 30 days), a marker that the install recently had an active subscription (kept for 7 days), daily request counts used for rate limiting (kept for one day), the top-up ledger and the subscription records described above, and one small preference — the Reading style you choose for read-aloud (Auto, Natural, Narrator, Lively, or Calm), kept for up to 400 days after you last set it so the voice can follow it — the language of the last page you listened to (kept for one day; see AI Read-Aloud), the test group record described above (kept for 90 days), and the activity markers described in the next paragraph (kept for 90 days). It does not receive bookmarks, highlights, notes, reading history, or any data that identifies you.

The backend also keeps small, anonymous daily counters of certain in-app events so we can understand how Flippy is used, improve the app, and detect abuse of free features. Examples: the app being opened (counted at most once per day per install, so we can see how many devices actively use Flippy), the local hour and weekday when the app is opened (counted, never linked to an install), a book being imported, the upgrade screen being viewed, a purchase or top-up completing, a trial reminder being shown, or a monthly usage limit being reached. Only the name of the event is counted — never the content of your documents, questions, notes, or anything that identifies you — and the counters roll off after 90 days. To count each install only once, the backend keeps small activity markers filed under the install token: one for each event an install sent on a given day (the event name and the date), and one for each day and each month the install was active. They hold nothing else and are deleted after 90 days.

Sharing a Page, Quote, or PDF

When you share a quote card, a page picture, or a PDF from Flippy, the share includes a short line with a link to flippypdf.com/get. The link says only what kind of share it was (for example, a quote card); it contains nothing about you or the book. Whoever taps it is sent to Google Play, the App Store, or the Flippy website, depending on their device. The flippypdf.com/get page sets no cookies and keeps no log or count of who taps it. On Android the Google Play link carries the kind of share as a campaign tag, which Google Play may report to us only as totals.

Notifications

Reading reminders, streak reminders (sent in the evening when your reading streak is about to end), the reminders sent the day before and the day after your free week ends, and — only if you turn on “Remind me before my free week ends” — a reminder three days before it ends, are generated and scheduled entirely on your device using the operating system's local notifications; no push service or server is involved. The name of your last-read book and its page, your reading streak, your monthly listening totals, and the date your free week ends are stored locally to personalize them and never leave your device. To avoid sending reminders you don't need, the app also works out once a day, on your device, how likely you are to come back on your own, from your recent reading and listening activity and your first-launch answers; the result is used only to choose which reminder (if any) to show. Our backend only receives the name of an event for the result (high, medium, or low), counted like the other events above. The playback controls shown in your notification bar while listening are local too. You can turn reminders off anytime in Settings or in your device's notification settings.

Third-Party Services

Flippy integrates with the following third-party services. Except where noted, each is contacted only when you explicitly use the corresponding feature:

• Google Sign-In and Firebase Authentication — for signing in to Cloud Sync (free and optional)
• Google Firebase / Firestore — for storing your synced reading data
• DeepInfra — runs the Kokoro voice model for AI Read-Aloud and for speaking AI answers out loud (routed via our backend; see AI Read-Aloud)
• Together AI — runs the same Kokoro voice model as a second host when DeepInfra is slow or unavailable (routed via our backend; see AI Read-Aloud)
• OpenAI Text-to-Speech and Whisper transcription APIs — for AI Read-Aloud and spoken AI answers in languages Kokoro does not speak yet and as a last backup when neither Kokoro host can generate a page, and (Android only) for transcribing voice questions that your device could not transcribe locally (routed via our backend; see the backend section above)
• Anthropic Claude API — for AI Q&A, summaries, AI Explain, study tools, some definitions, and the Help & FAQ question box (routed via our backend)
• dictionaryapi.dev — for in-app word definitions (routed via our backend; cached by word alone, never linked to your install)
• Wikipedia / Wikimedia Commons — for the images and captions shown in AI Explain (contacted directly from the app; only the highlighted term or a related search phrase is sent; no account or API key involved)
• "What's coming" — the list of features we are working on is fetched from our backend when you open it; only your app language is sent with the request, to get the list in that language.
• Apple App Store and Google Play — our backend contacts Apple's and Google's servers to verify subscription receipts and top-up purchases, and Apple and Google send our backend notices of subscription renewals, cancellations, and refunds (see In-App Purchases)
• Stripe — sells and processes purchases made on the website, as merchant of record, and sends their receipts
• Cloudflare Workers and Cloudflare's cache — our own backend proxy that holds our API credentials, applies usage limits, and caches generated read-aloud audio for up to 30 days
• cdnjs (a public Cloudflare CDN) — Flippy loads the open-source library it uses to draw PDF pages from this public CDN. This happens every time the app starts, not only when you use a particular feature. Only the ordinary information carried by any web request is involved, such as your IP address; none of your documents, questions, or reading data is sent.

Each service is subject to its own privacy policy. Apart from the CDN noted above, no data is shared with these services unless you actively use the corresponding feature.

Children's Privacy

Flippy is not directed at children under the age of 13. We do not knowingly collect personal information from children.

Data Deletion

You can delete all your data at any time:

• Local data: Uninstall the app or clear app data from your device settings. (Because of the hashed device identifier, reinstalling later will not restart the free week or free sample, and any top-up balance will still be there.)
• AI conversations: Use "Clear chat" in the AI panel to erase the conversation for a single book, or uninstall the app to remove all of them. They are only ever stored on your device.
• Cloud data: Use "Delete Account & Data" under Settings → Cloud Sync. This deletes the reading data we hold for you in Firestore and signs you out. The sign-in record itself (your Google account's name, email, and photo as held by Firebase Authentication) may remain with our authentication provider — email us at the address below and we will remove it for you.
• Backend records: the install-token record, the hashed device identifier, usage counters, the test group record, the activity markers, the subscription device record, and the top-up ledger are not linked to your name or email, so we cannot find them from your email address alone. (One exception: while you are signed in, a device’s install record also holds your Google account’s user ID — see “Your plan on all your devices” above.) Email us from the app (Settings → Help & FAQ → Contact support) and we will work with you to identify and delete them. Note that deleting the top-up ledger forfeits any unused top-up balance.
• Website purchase records: the records we keep under your Google account's user ID (see Purchases on the Website) can be deleted by emailing flippypdf@gmail.com from that Google account. Deleting them ends website plan access and forfeits unused website packs, but does not cancel billing: cancel first under Settings → Premium → Manage subscription on the website. Deleting your Flippy account does not cancel a Stripe subscription either.

Changes to This Policy

We may update this privacy policy from time to time. Changes will be posted on this page with an updated effective date.

Contact Us

If you have questions about this privacy policy or your data, contact us at:

flippypdf@gmail.com