Last updated 15 November 2026

Security

How IdeaToBook protects your account and your books, built so your manuscript is seen only by you and the AI that writes it.

Passwordless sign-in

You sign in with a six-digit code we email you. Each code lasts 10 minutes, allows five attempts and is stored hashed, never as the code itself. There are no passwords to steal or reuse. Sessions last 30 days and are renewed while you use IdeaToBook; sign out to end one sooner.

Encrypted everywhere

TLS for every connection, and encryption at rest for everything stored, on Cloudflare's network.

Your books are yours alone

Every read and write of a book, its interview answers, chapters and editor notes is tied to the signed-in author's account and checked on the server. Ask for a book that isn't yours and IdeaToBook answers as if it doesn't exist. Billing pages and checkout also act only on the signed-in account.

AI that doesn't keep your manuscript

Every AI request goes through OpenRouter with its data collection setting set to deny, so only model providers that don't store prompts or use them for training write your book. A request carries the idea, book type, interview answers, outline and chapters it needs, never your email address or billing details. Our own logs of AI requests record the model, token counts and cost, not your text. We don't use your books to train models. Which providers are used, and where, is on our Subprocessors page.

Signed billing events

Payment events from Stripe reach IdeaToBook through Sansa Group's billing relay. Each one is signed with HMAC-SHA256 using a key only IdeaToBook and the relay hold, must carry a timestamp within five minutes of the time we receive it, and is checked in constant time. Unsigned events, forged events and events meant for another product are rejected, and each event is applied only once.

Card details never reach us

Checkout and the billing portal are pages run by Stripe. Your card details go straight to Stripe and never touch our servers. We keep only Stripe's references (customer, subscription and payment ids), your subscription status and the amount of each purchase.

Data in the EU

The database is held in the EU (Cloudflare D1 with EU jurisdiction). Requests are handled at the Cloudflare location nearest to you, and AI requests go to providers that may be outside the EU; our Subprocessors page lists each one and what it receives.

Protection against abuse

Sign-in codes expire after 10 minutes and five wrong attempts. Each connection can ask for three codes and try five codes a minute, and each email address can receive at most five codes an hour, so nobody can guess codes or flood an inbox. These counters are shared across our whole network, not kept per server. Checkout and the billing portal refuse requests sent from other websites. Plan limits, such as books per month and rewrites per chapter, are enforced on the server, and rewrites are counted atomically so two at once can't slip past the limit. IdeaToBook runs on Cloudflare's network, with its DDoS protection.

What we don't claim yet

IdeaToBook is new. We haven't yet completed an external penetration test or a certification such as SOC 2 or ISO 27001, and IdeaToBook isn't offered for use that requires a HIPAA business associate agreement. We'll update this page when that changes.

Privacy by design

No ads, no selling data, no training AI on your books. We ask for an email address and nothing else to get started. Visit counting on our public pages stays off until you allow it. Delete a book and it's removed, with its chapters and notes, from the live database at once; backups roll off within 30 days.

Reporting a vulnerability

Email security@ideatobook.my with “Security report” in the subject. Include steps to reproduce and the impact. We acknowledge reports within two business days and keep you updated until it's fixed. Please don't access other people's data, degrade the service or publicly disclose before we've had a chance to fix the issue.