Privacy

Nothing you open is uploaded. A PDF dropped into the pre-flight checker, a cover image, a font -- all of it is read inside your own browser and discarded when you close the tab. There is no endpoint here that accepts a file, so this is not a policy that could be changed by a setting.

The specifications you build -- title, trim size, paper, page count, keywords, description -- are stored by your browser, in localStorage, under the key kdp-book-spec. They stay on the machine that made them. Clearing your site data deletes them, which is why the library screen offers an export.

An account can carry that list to another machine you own. That is the only reason accounts exist here, and it is never required to use a tool.

Vercel Web Analytics, run by the company that hosts this site, counts visits to the public pages. It sets no cookie and is served from this site’s own address. For each page view it receives the page address without its query string, the page you came from, your browser, operating system, device type and an approximate location worked out from your IP address. It never counts the workspace, and if your browser sends Do Not Track it counts nothing at all. Vercel’s analytics privacy notes cover what it does with what it receives.

Umami, which counts visits to the public pages -- the calculators, the guides and pages like this one -- so we can see which of them people actually use. It is cookieless: it sets no cookie, keeps no identifier in your browser and does not follow you to other sites. For each page view it receives the page address without its query string, the page you came from, your browser, operating system, device type, screen size and language, and your IP address, from which it works out an approximate location.

It never counts the workspace. If you move from a public page into the workspace it stops sending anything, it sees no file you open and nothing you type, and if your browser sends Do Not Track it counts nothing at all. Umami’s own privacy policy covers what it does with what it receives.

There is nothing else: no advertising, no tag manager, no embedded fonts from another host, no social widgets, no session recording, no A/B testing. The Content-Security-Policy this site sends admits Umami’s two addresses besides this origin and nothing more, so a third-party script added by mistake would still be blocked by the browser.

One, and only while you are signed in: a session cookie set when you sign in and cleared when you sign out. It is httpOnly, so no script on the page can read it, and it holds your account id and address and nothing else.

There is no cookie banner because there is nothing to consent to. Signing in is the consent, and signing out is the withdrawal.

Three fields, on the server, and this is the complete list:

• the email address you signed up with;
• a hash of your password -- scrypt, salted, so the password itself is not stored and cannot be read back out;
• the date the account was created.

No name, no profile picture, no record of which tools you opened or when. Not as a courtesy -- there is no field for them.

At least 10 characters, and there is no way to reset it. This site sends no email, so it cannot send you a reset link. That is a real cost and it is stated here rather than discovered later: if you forget it, the account is gone and you make a new one. Your books are unaffected, because they were never in the account in the first place.

An account is kept until you delete it. Sign in and the option is at the bottom of the sign-in page; it removes the row immediately and there is nothing left behind, because the three fields above are all there ever was.

Deleting an account does not touch your books. They are in your browser and they stay there.

iLoveKDP is an independent tool and is not affiliated with, endorsed by or connected to Amazon or Kindle Direct Publishing. It does not connect to your KDP account, and it could not: there is no integration and no credential for one. Every number it gives you is computed locally from the published specifications.

This page describes the deployment you are reading it on. It is generated from the same configuration the application runs on, so it cannot fall behind the code in the way a hand-maintained policy does.