Skip to content

30% off your first paymentends Nov 30Plans

Privacy Policy. What we collect, and what we do with it.

Last updated October 25, 2026SuperEbook is run by its co-founders, Shri and Sarath.

1. The short version

We try to be honest by design, and that includes how we handle your data. In plain terms:

  • we collect what we need to run the Service and your account;
  • the material you upload to ground a book is kept private to your account, and is never used to train any AI model — ours or anyone else's;
  • we don't sell your personal information;
  • we run analytics, and (where enabled) advertising measurement — §6 names every tracker we load, and none of them ever sees your book or your material;
  • you can delete your material, your books and your whole account yourself, at any time.

The sections below spell out the details.

2. Who this applies to

This Privacy Policy explains how SuperEbook ("SuperEbook," "we," "us," or "our") handles personal data when you use superebook.ai and the SuperEbook app (the "Service"). It should be read together with our Terms of Service.

The operator of the Service is the data controller for the personal data described here. SuperEbook is run by its co-founders, Shri and Sarath. Payments are a partial exception: Dodo Payments is the merchant of record and acts as the controller of your payment and tax data (see §7).

3. Information we collect

We collect the following, mostly so we can operate your account and write your books:

  • Account information — your name, email address and, if you sign in with Google, your profile picture. You sign in with Google, or where it is offered, with a one-time code sent to your email. We do not store account passwords.
  • Your books and settings — the ideas, plans, chapters, covers and files you create, your preferences, and your progress through the app's getting-started steps.
  • Usage and credits — your credit balance and transactions, and basic product and log data such as device and browser type, approximate location derived from your IP address, and timestamps, used to run, secure, and improve the Service.
  • Connected apps — if you connect Claude or another app to your account: for each API key, the name you give it and the app it is used from, as that app reports it; for each connected app, its name; for each key and app, when it was created or connected, when it was last used and how many calls it made; and for your account, the calls made with each tool, the books started and the credits charged through connected apps. A book started from a connected app also records which app started it, such as Claude or ChatGPT, and your library shows it with the book; it is deleted with the book. API keys and sign-in tokens are stored only as a one-way hash.
  • Product analytics — pages viewed, the marketing page or ad that brought you here, a small set of named product events (for example: signup completed, book created, generation started, book ready, pricing viewed, checkout started), together with the technical details listed above, and session replays: recordings of how pages change as you use them (see §6). Once you sign in, these records are linked to your account ID, and your analytics profile holds your account's email address. They carry identifiers and page URLs — never the contents of your material or your book, and never the ideas you type.
  • Payment information — handled by Dodo Payments as our merchant of record. We receive confirmation of a purchase and limited billing metadata (such as plan, country, and card brand or last four digits), but we do not receive or store your full card number. DataBull, our self-hosted analytics tool, also imports a record of each payment from Dodo, including the buyer's name and email address (see §6).
  • Lifecycle contact data — when contact sync is enabled, AutoSend receives your verified email address, name, account ID, account creation date, plan and credit balance, language preference, subscription status and renewal date, app email opt-out status, latest book ID, type, status, dates and link, how many books you have and how many are ready, when your first book was ready, the date of your latest activity (a visit to the app, planning a book or spending credits), and whether you have ever paid us, plus lifecycle events for account verification, a book's plan being ready, your first and every later completed book, a failed book, your credits falling below the price of the cheapest book, seeing upgrade options (at most once a day), starting a checkout and leaving it unpaid for an hour, purchases, subscription changes, and 7, 14 or 30 days without activity. Book events carry the book's ID, type and app link; checkout events carry the product, any discount code, and for a single-book purchase the book's ID and link. These contact and event records do not include your book contents or sign-in codes.
  • Communications — the contents of messages you send us, including feedback, support correspondence and related internal notes. After your first completed book, we may ask for an optional rating and feedback linked to that book. We remember your choice to dismiss or postpone the prompt and whether you submitted feedback; administrators may review it and award creation credits regardless of whether the feedback is positive or negative. Authorized administrators may send support replies or credit-reward notices. Product news and offers sent through the admin console require your optional email preference in Settings; you can turn it off or use the unsubscribe link. Provider delivery restrictions still apply.
  • Customer stories — only if you choose to send us one (see Share your results): what you email us about a book you made with us and sold, such as your name, what you do, a photo and a link, the book, its sales or royalties figure and the period it covers, your words, a screenshot of the store's report that backs the figure, and your written permission. With that permission we publish on our website only what you approved, never the screenshot; we keep the screenshot and your permission privately, as the record behind the story. You can withdraw your permission at any time by emailing us, and we will take the story down. Deleting your account does not take it down on its own.

We also collect the material you choose to upload to ground a book — that gets its own section below, because it matters most.

4. Your grounding material

When you paste text or upload notes, files, or transcripts to ground a book, we extract the text, split it into passages, and build a private search index tied to your account. While a book is being written, we retrieve the most relevant passages for each chapter so the draft is built from your substance rather than generic filler. An uploaded file itself is deleted as soon as its text has been indexed; the passages stay until you remove that source, delete the book, or delete your account.

Your material — and the books you generate from it — are private to your account. We do not use them to train, fine-tune, or improve any AI model, ours or anyone else's. We do not sell them and we do not use them for advertising. When your material is sent to an AI provider — to index it, or to write your book — it is processed only to produce that output for you, under provider terms that prohibit training on your data (see §7). This is a core promise of the product, not a footnote.

5. How we use information

We use the information above to:

  • provide and operate the Service — planning and writing your books, retrieving passages from your material, generating covers, and producing your files;
  • manage your account, credits, plans, and billing;
  • provide support and respond to your messages;
  • publish a customer story you sent us, only as you approved it in writing (see §3);
  • keep the Service secure and prevent fraud, abuse, and violations of our Terms;
  • understand and improve the product using aggregated or non-content usage data — not the contents of your material or your books;
  • see which sources bring visitors and which visits lead to purchases (see §6);
  • comply with legal obligations.

Where data-protection law (such as the GDPR) applies, our legal bases are performance of our contract with you, our legitimate interests in operating and securing the Service, your consent where we ask for it, and compliance with legal obligations.

6. Cookies, analytics, and advertising

We use cookies and similar local storage that are essential to the Service — keeping you signed in, remembering your light/dark theme and reading preferences, carrying an idea you typed through sign-up, and protecting against abuse. Those are always on; without them the Service does not work.

For internal operations we keep limited account, generation and fulfilled-purchase counters. When attribution collection is enabled, we record your first reported public landing path, referrer origin and campaign labels, plus, when you are signed in, an approximate country supplied by our hosting provider and the device type (desktop, mobile or tablet), browser family and operating-system family of your latest recorded visit. This feature does not store your IP address, precise location, full browser identification string or version numbers, and respects Do Not Track and Global Privacy Control. A first-visit record in local storage expires after 30 days if it has not been attached to your account. Historic or unavailable origins remain unknown. Admin console pages are excluded from browser analytics and advertising pixels.

Account deletion removes stored origin and email-permission records, private support notes and personalized admin message data. Personalized admin message content and recipient details are also removed 90 days after a campaign and its delivery activity finish; inactive unsent drafts expire after 180 days. Minimal accounting and security audit records, and aggregate operational counts, may remain as described below.

For product analytics and session replay we use PostHog. It sets its own cookie/local storage to recognise a returning browser and records page views and the named product events listed in §3, along with technical details such as browser, device and referrer. PostHog receives your IP address, keeps it with these records and uses it to estimate your approximate location, such as your city and country. When you sign in, PostHog links this browser to your account ID and keeps your account's email address on your analytics profile; we do not create analytics profiles for anonymous visitors. Session replay records how pages change while you use them — scrolling, clicks, mouse movement and the pages you move between — so we can see where the Service is confusing or broken. Everything you type is masked in your browser before it is sent, on every page. Our public pages, such as the home page, pricing and the guides, are otherwise recorded as they appear. On every other page, including the whole signed-in app, all text is masked and images, video and canvases are left out, so a replay never shows your book, your covers, your material or your ideas. Labels and links that could name a book or open one of your files are removed from every recording, and the admin console is never recorded. Ideas you type are removed from every address before it is sent. PostHog browser analytics, including session replay, honours Do Not Track and Global Privacy Control. Automatic click/text capture, console and network recording and automatic error capture are disabled; URLs exclude private query values and document identifiers. Separately, our servers report operational account, generation, download-link and payment outcomes using account identifiers and limited metadata, and the report of a new account also gives your analytics profile your email address. These server events are not controlled by browser tracking settings. When you delete your account, we remove your email address from your analytics profile; events and replays already recorded stay with PostHog until its retention period ends.

On our production website we also use Vercel Web Analytics to measure visits and page views, with technical information such as browser, device, country and referrer. It does not use cookies. We remove private query values and document identifiers from the page URLs we send, and honour Do Not Track and Global Privacy Control. This analytics integration is disabled on preview deployments and in local development.

We also use DataBull, an analytics tool we host ourselves on our own Cloudflare account, to measure which sources bring visitors and which visits lead to purchases. It sets its own first-party cookies on superebook.ai: a random visitor ID that lasts 365 days, a session ID that lasts 30 minutes, and three more that record when this browser was first seen, how many visits it has made and where the current visit came from. It also keeps the last page it counted, and when, in your browser's session storage, so that a reload isn't counted twice. It records page views, a periodic signal while a page stays open, how far down each page you scroll and how long you actively read it, a few named steps (submitting an idea, signing up, creating a book, seeing the plans, starting a checkout, downloading a book and using a free tool) with plain details such as the plan or format but never an ID, the idea, a title or any book text, and, when you return from checkout, the payment's reference, together with your browser, device, screen size, language, time zone and referrer. Every event passes through our own server first, which removes private query values and document identifiers from every page address it carries, reduces the referrer to its origin and drops ad-click identifiers. Our server forwards your IP address to DataBull only so it can limit the rate of requests; DataBull does not store it. DataBull receives your approximate continent, country, region and city from our hosting provider, not your precise location. It honours Do Not Track and Global Privacy Control, the admin console is excluded, and it is off on preview deployments and in local development.

DataBull is also connected to our Dodo Payments account, and imports from Dodo a record of each payment made on superebook.ai: the product, amount, currency, tax and date, the buyer's name, email address and Dodo customer ID, the subscription ID for a subscription, and the payment's metadata, which carries your account ID, the product and its catalog version, a checkout reference and, for a single-book purchase, the book's ID. We use it to tie each sale to the visit and the source it came from. The import runs between DataBull and Dodo, so it does not depend on your browser, and Do Not Track and Global Privacy Control do not stop it. It never includes your material or the contents of your books.

We do not currently run advertising pixels or cross-site ad trackers on this deployment. If we turn them on, they will be named here — and where consent is required, asked for first.

The footer's "Featured on" row shows small badge images that the listing directories host themselves: aidreamhub.com, doforai.tools, tooldisk.com, wayfindio.com, bigkr.com, deeplaunch.io, dofollow.tools, gets.tools, shinylaunch.com, neeed.directory, fazier.com, tooldirs.com, aitoolslist.tools, themicrosaasdir.com, indielineup.com, saaslineup.com, theaitoolsdir.com, thesaasdir.com, artificin.com, getbannerbid.com, agentwork.tools, aitrustlist.com, www.popwebtools.com and hokai.io. Your browser loads each badge from that directory's server, which receives your IP address and browser details, as any site does for an image it serves. No referrer is sent with those requests.

Whatever is enabled, the rule does not change: no analytics or advertising tool ever receives the contents of your material or the books you generate.

7. Service providers and sub-processors

We share data with a small set of providers who process it on our behalf, under agreements and only on our instructions:

  • Vercel — hosts the website and app, and runs the AI Gateway through which our requests reach the AI model providers below. It also provides the website analytics described in §6.
  • Convex — our database and backend: your account, credits, books, and the private index of your material.
  • Cloudflare — R2 file storage (uploads until they are indexed, covers, and your exported files) and Browser Rendering, which turns your book into a PDF. It also runs DataBull, the analytics tool we host on our own Cloudflare account, which holds the visit and payment records described in §6.
  • AI model providers, through Vercel’s AI Gateway — Anthropic (writing chapters and AI rewrites), Google (planning, format suggestions, and cover prompts), and OpenAI (indexing your material and, through fal.ai, cover images). If you turn on paid web research, the research model receives your book's topic and the research you asked for. Each receives only what it needs to produce your output, under terms that prohibit training on your data.
  • TinyFish — our web-search provider, used only when you turn on paid web research for a book or tick Research this on a rewrite. It receives the search queries the research model writes about your book's topic or the passage you are checking (the model is told to search for the public facts and not to copy your text into a query) and, for book research, the addresses of public web pages to read. It never receives your uploaded material, your files, or your account details. Unlike the providers above, TinyFish's terms allow it to use the requests it receives to improve its own services and AI models.
  • fal.ai — generates cover artwork from a short art prompt derived from your book's title and topic; it never receives your material.
  • AutoSend and Resend — deliver one-time email sign-in codes, depending on which provider is configured. When contact sync is enabled, AutoSend also receives the verified account contact details and lifecycle properties and events listed in §3. AutoSend also sends the lifecycle emails we switch on there: notices about your own books and purchases, such as a book being ready, and tips and offers, which follow the app's email preference. Each one has an unsubscribe link. The app itself sends no book-ready or free-tool-results emails.
  • Dodo Payments — the merchant of record, which sells and processes payments and handles applicable tax. Your card details go to Dodo, not to us; for that transaction Dodo is its own controller, under its own privacy policy.
  • Google — if you choose "Continue with Google," Google authenticates you and shares your name, email address, and profile picture with us.
  • PostHog — product analytics and session replay, which receives the page views, product events, session replays and account email address described in §6.

Apps you connect are a different case: you choose to share with them. If you connect Claude or another app to your account, it receives what it asks our server for on your behalf: the plan you're on and your credit balance, our prices, your books' titles, the idea each book started from, their plans and progress, and links to download the books your plan or a purchase covers. It never receives your name or email address from us. Material an app sends us for a book is handled like material you add yourself (§4). The app and its provider (for Claude, Anthropic) handle what they receive under their own terms and privacy policy, not ours. You can disconnect an app or revoke a key in Settings at any time, and its access stops at once.

We do not sell your personal information, and we do not share it with third parties for their own marketing.

8. Data retention and deleting your account

We keep your data while your account is open, so you can keep working with your books. When you remove a source or delete a book, it is deleted from our active systems — the book's chapters, covers, and files, and the source's indexed passages.

You can delete your whole account in Settings. Deleting it cancels any active subscription immediately, then deletes:

  • every book, including any still being written — manuscripts, covers, and exported files;
  • the material you uploaded or pasted, and its index;
  • your name, email address, and profile picture, which are removed from the account record;
  • your sign-in on every device, and your credit balance;
  • your API keys and the apps you connected, with their usage records;
  • the email address on your analytics profile (see §6);
  • your email address from our log of the emails we sent you.

We keep, under the anonymized account:

  • records of your payments, subscriptions, and credit transactions — what was bought, when, and for how much — which accounting, tax, and dispute rules require us to keep, and which let a refund still be processed after deletion;
  • any feedback you sent us, no longer linked to you;
  • a one-way hash of your email address, so that a new account with the same address doesn't receive the free starting credits again.

Copies held in our providers' backups, if any, are removed as those backups expire. Payment and tax records held by Dodo Payments as merchant of record are kept under Dodo's own policy. Analytics events and session replays PostHog has already recorded stay there until its retention period ends. Deleting your account does not remove the payment records DataBull has imported from Dodo, or the visits it has recorded.

9. Your rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal data, to object to or restrict certain processing, and to withdraw consent. You can delete your material, your books, and your account yourself, in the app. For anything else, email privacy@superebook.ai and we will help.

We do not sell personal information. If you are in a region with a supervisory or data-protection authority, you also have the right to lodge a complaint with it.

10. Children

The Service is not directed to, and is not intended for, children under 16 (or, where lower, the minimum age required by your local law, and in no case under 13). We do not knowingly collect personal data from children. If you believe a child has provided us data, contact us and we will delete it.

11. International data transfers

We and our providers may process and store data in countries other than the one you live in, including the United States. Where such transfers are subject to data-protection law, we rely on appropriate safeguards, such as the Standard Contractual Clauses in our providers' data-processing terms.

12. Security

We use reasonable technical and organizational measures to protect your data — including encryption in transit, access controls, and indexing your material privately per account. No method of transmission or storage is completely secure, so we cannot guarantee absolute security, but we work to protect your information and to respond promptly if something goes wrong.

13. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date above and, where appropriate, give you additional notice. Your continued use of the Service after an update means you accept the revised policy.

14. Contact

Questions about your privacy or this policy? Email privacy@superebook.ai. SuperEbook is run by its co-founders, Shri and Sarath.

See also Terms of Service, Refunds & cancellation and Pricing.

Start with 50 free credits. No card needed.

Plan a book for free, write it with the free credits, and read every word before you pay for anything.