Legal
Privacy Policy
On this page
The short version
We keep your account, the books you write and a record of what you have paid for. We don’t sell any of it for money. Outside the UK and Europe, the Meta Pixel helps us see which ads work, and your name, email address and books are never sent to Meta by us. We do measure how the site is used, with everything you type hidden.
To write a book, the brief you type is sent to a third-party AI provider, under terms where it is not used to train their models. Payments are handled by Polar, who take the card details; we never see them.
This box is a summary and nothing more. Where it and the sections below disagree, the sections below are what applies.
1.Who we are
BookArc is operated by Istiaq Ahmed (sole trader), based in Bangladesh. We decide what happens to the personal data described here, which in data-protection language makes us the controller of it.
For anything in this policy — including a request to see, correct or delete your data — write to support@bookarc.ai. A person reads that inbox; there is no ticket system to get lost in.
2.What we collect
Four things, and nothing beyond them.
- Your account. Your email address, and — only if you chose “Continue with Google” — the name and profile picture Google hands over. Passwords are never stored by us in any readable form: sign-in is handled by a specialist provider, and what we hold is a reference to your account with them, not a password.
- What you write. The idea you type into the box, the settings you pick for a book, the plan it produces, every chapter written, and the cover images drawn for it.
- What you have bought. Your plan, your credit balance, and a line for every credit spent or granted. Card numbers are not on that list — see section 4.
- How the service ran. For each generation: which model answered, how many tokens it used, what it cost us and whether it failed. A few moments in the app, tied to your account: the days you used it, when you opened the plans, set off to pay or downloaded a file. Plus ordinary server logs — IP address, browser, page requested — which is how the site is kept up and abuse is spotted.
We measure how the site is used with PostHog, so we can tell which pages help people and which get in the way. It records the pages you visit, the link or search that sent you, your browser and rough location from your IP address, and — once you have an account — your account id and email address, so that we can see how a signed-in person got on. Events reach PostHog through this site’s own domain.
PostHog also records how pages were used, so we can watch back where people get stuck. Everything you type is hidden from those recordings — your book idea, your chapters, your email address, your password. We see where you clicked and scrolled, not what you wrote.
PostHog is a processor: the data is ours, held on our account. See the cookie policy for what this stores in your browser and how to refuse it.
We advertise on Facebook and Instagram, and like many websites, we use the Meta Pixel to see which ads work. Outside the UK and Europe, it tells Meta when someone visits a public page, creates an account or makes a purchase, including the amount. As with any web request, Meta also receives the page address, IP address and browser details, along with its own cookies. Your name, email address and books are never sent to Meta by us.
Meta decides how it uses this information, including to choose which ads people see, under its own privacy policy. The cookie policy explains how to opt out.
Separately, our host, Vercel, counts page views for us with Vercel Web Analytics. It sets no cookie and stores nothing in your browser. It records the page, the link that sent you, your country, and your browser and type of device. It tells visits apart using a code made from your request that resets every day, so it cannot recognise you from one day to the next and never knows who you are.
3.What we send to the AI providers
What goes to them, on each request:
- The idea you typed, and the title, genre, audience, format and length settings for the book.
- A short summary of the chapters already written, so the next chapter follows on from them rather than repeating them.
- For a cover: the title, subtitle and genre, the art direction we derive from them, any style hint you add, and your author name if you choose to put it on the cover.
- For Edit with AI: the chapter’s current text and the change you asked for.
- For a coloring book: the theme, who it is for, the style and page size, and the idea for each page — and, when you edit a page with AI, that page’s picture and the change you asked for.
What does not go to them: your email address, your account id, your payment details, or anything about what you have bought — and your name only when you ask for it to be printed on a cover. The model is sent a brief, not a person.
The work is done by a small number of established AI companies, on their paid developer APIs, under terms in which the provider states that content sent through the API is not used to train their models. We do not grant anybody the right to train on what you write, and we do not sell it, publish it or share it with anyone else.
Which provider answers depends on the kind of request, and it changes as models improve. We do not publish the list, for the same reason we do not publish the rest of what the service runs on — but if you are evaluating BookArc for something sensitive and need to know before you commit, ask at support@bookarc.ai and we will tell you.
Those providers process the request on servers outside Bangladesh, including in the United States. If we change provider, this section is updated before the change goes live.
4.Payments
Payments are taken by Polar, who act as the merchant of record. That means Polar — not us — takes the card, handles the tax and issues the invoice. Your card details go to Polar and their payment processor. They are never sent to us and we could not store them if we wanted to.
What we keep is enough to tie a payment to your account — a customer reference, your plan, and the date your period ends. That is how a payment becomes credits in your balance.
5.Why we are allowed to hold it
For readers in the EU and the UK, the lawful bases are these, in the language that framework uses:
- Performing our contract with you — your account, your books, your credits, your payments. Without these there is no service to provide.
- Our legitimate interests — server logs, generation records and those few app moments, used to keep the service running, work out what it costs us, see which parts of the app help people, and stop abuse.
- Legal obligation — records of what was sold, kept for as long as tax rules require.
6.Who else touches it
Running BookArc means a handful of other companies handle some of this on our behalf. These are the kinds of company involved, and there are no others:
- Infrastructure and hosting. Runs the servers, the database your books are stored in, and the sign-in system. They hold what you write because it has to live somewhere; they do not read it.
- Payments. Polar, our merchant of record, who take the payment, handle the tax and issue the invoice. Card details go to them and their processor and are never sent to us.
- AI providers. The specialist companies whose models write and edit the chapters, draw the covers and draw coloring-book pages. What they are sent, and what they are not, is section 3.
- Sign-in with Google. Only if you use that button instead of an email and password, in which case Google tells us your name, email address and profile picture.
- Advertising. Meta, to see which of our Facebook and Instagram ads work. What it is sent, and what it is not, is section 2.
Apart from Meta, each is bound to use what it is given only to provide the service to us. We name the payment provider because it is who charges you and who appears on your statement, and Meta because it uses what it receives for its own purposes; we do not publish the rest of the list, because a public map of the systems a business runs on is worth more to somebody attacking it than to anybody reading this page.
We don’t sell your personal data for money. The Meta Pixel in section 2 is the only thing we share for advertising. Some US state laws call this kind of sharing a “sale” or “sharing”; our cookie policy explains how to opt out. If the business is ever sold or merged, whoever takes it on inherits this policy — and you would be told before anything about it changed.
7.How long we keep it
- Your account and your books: until you delete them, or until you ask us to close your account.
- A book you delete: removed from the database, and its cover, any pictures added in the chapter editor and any coloring-book pages removed from storage, at the time you delete it.
- Billing records: kept for as long as tax and accounting rules require, which is longer than your account may live. This is the one category we cannot delete on request.
- Server logs: a short rolling window, then overwritten.
8.Your rights
You can ask us for a copy of what we hold about you, to correct it, to delete it, or to stop a particular use of it. Ask from the email address on the account and we will do it within 30 days — in practice, within a few days.
Deleting your account deletes your profile, your books, your chapters, your cover images and the pictures in your books. You can do it yourself under Profile → Delete my account, or email support@bookarc.ai and we will do it. If a paid plan is still set to renew, cancel it first so you are not charged again.
These rights are set out in the EU and UK GDPR. We offer them to everyone who uses BookArc, wherever you are, because running two standards of privacy for two sets of customers is not a thing worth building.
9.Security
Every table holding your work is protected by row-level security in the database itself, so a query for somebody else’s books is refused by the database rather than by a check in the application that somebody could forget to write. Traffic is encrypted in transit, and API keys for the AI providers live only on the server.
Apart from you, the only people who can see your books are the BookArc team. We may look at a book to help you when you ask, to fix a problem, or to check the quality of what BookArc writes. We never publish or share your books.
No system is perfect. If there is ever a breach that affects you, you will be told about it, and told what to do about it.
10.Children
BookArc is not for under-18s, and accounts are not knowingly created for them. If you believe a child has an account here, write to support@bookarc.ai and it will be removed.
11.Changes to this policy
When this changes, the date at the top changes with it. If a change matters — a new processor, a new use of what you write — you will get an email about it before it takes effect, not a silently edited page.