Privacy

Most ebook converters want you to upload your book to a server you know nothing about. This one can't, because there's no server to upload it to. Everything below follows from that.

What happens to your file

Drop an EPUB on the page and your browser hands it to JavaScript that's already running in the tab. That code unpacks it, typesets it and offers a PDF back as a download. No network request carries your book at any point, because the site has no endpoint that would accept one. It's a static site. HTML, CSS and JavaScript on a CDN, nothing more.

The conversion runs in a background thread of the same tab, so the page stays responsive. That thread has no more access to the network than the page does, and both are held to the same content security policy.

Check it yourself

Please do, actually. It takes about a minute.

1. Open your browser's developer tools and go to the Network tab.
2. Convert a book. Watch what gets requested: the page's own scripts, and that's it.
3. Or better: load this page, turn off your wifi, and convert a file anyway. It works. Software that needs no network can't be sending your book over one.

This is also asserted mechanically. A test in the build drives the real site in a real browser and fails if any request during a conversion goes anywhere but this origin, or carries a payload bigger than two kilobytes. If someone ever adds an upload, the build breaks.

What we collect

Your EPUB

Never sent anywhere. Read off your disk by the browser, held in the tab, gone when you leave.

The PDF we make

Built in memory and handed to your browser as a download. We never see it.

Its title, author or contents

Never sent, never logged, never counted.

The settings you chose

Not even those. Page size and type size stay in the tab with everything else.

Your email or an account

There's no sign-up. We don't ask and couldn't store one.

Cookies

None. Nothing in local storage either.

Analytics

We use Plausible. It sets no cookies and builds no profile of you. It records that a page was viewed, and that a conversion finished or failed. It's never told the book's name, size, length or contents, since none of that leaves the tab in the first place.

Advertising

There's a paid placement for Dracotel on the site, a travel eSIM. Worth spelling out what that involves, because "we run ads" normally means something a lot worse than what's happening here.

It's not an ad network. No AdSense tag, no auction, no remote script, no tracking pixel, no image pulled off someone else's server. The advert is ordinary HTML baked into the page when the site gets built, the same as any other paragraph on it. It can't see you, profile you or follow you anywhere, because there's no code in it to do any of that.

Click it and you land on Dracotel's site with a tag saying you came from here, so they know the placement earns its keep. That's the whole mechanism. Don't click it and they learn nothing about you at all, including that you saw it.

Hosting

Cloudflare Pages serves the site. Like any web host, they handle the requests for the page itself and may keep short-lived logs with IP addresses in them. Those requests are for our own files. Your book isn't among them.

If this changes

If some feature ever genuinely needed a server, this page would say so at the top, in plain words, before that feature shipped. A privacy policy that quietly widens is worse than not having one.