Privacy
The editor runs entirely in your browser. When you drop a PDF and fill the blanks yourself, the file is read, analysed, edited, and saved again on your own device. It is never uploaded.
While you work, Blanq keeps the current document, the PDF and what you have typed, in your browser's own storage, so a reload doesn't lose it. It stays on your device. It clears when you start over, load a different file, or seven days after your last edit.
Blanq AI
Blanq AI, at /ai, is the separate tool that fills a form for you, and it works differently. It sends a picture of each page you chose to an outside service (currently Google's Gemini and OpenAI's GPT-5) to read the page and return what to write. Those pages are used only to answer that one request, under the providers' API terms, and are not kept on my server or used to train a model. The full detail, including what each company sees and what gets recorded, is on the security page. If you'd rather nothing left your device, use the editor and skip Blanq AI.
Reporting a detection problem
The editor has a "Report detection" option in the ⋯ menu. If you use it, your PDF is sent to my server so I can see why blank detection missed a field and fix it. It is stored privately and never shared. It is entirely optional: skip it and nothing is sent.
Release updates
If you enter your email to get release updates, it is saved to a file on the same server that runs this site, and used only to email you when something ships. No one else receives it, and you can ask me to remove it whenever you want.
Feedback
If you post feedback, your message and an optional name are stored on my server. By default a post shows publicly on the home page; uncheck the box and it comes only to me. Ask me and I will remove any post.
Rate limiting
To keep the service from being abused, I keep a hashed fingerprint of your IP and browser, never the raw values, and use it for nothing else. Blanq AI also counts requests per network against its daily limit; that count lives in memory for the day and is not written to disk.
Helping the editor find blanks
When the editor guesses a blank in the wrong place and you move or resize it, that correction can be sent to me as four numbers: where the box was and where you put it. It is how detection gets better at the shapes it currently gets wrong. No text is included, and there is no path in the code for your answers, your filename or anything from the page to travel with it.
This is on by default. Turn it off here and nothing further is sent from this browser.
What Blanq AI records about a fill
When you use Blanq AI, one line is written for the request. It holds the country your request came from, which Cloudflare tells my server so that I never handle your IP address to get it; the label on the link you arrived through, if you came from one, which describes the link and not you; how many pages and how many blanks were on them; whether the answers came from a web lookup, straight from the model, or not at all; and how long it took.
That line is counting, not watching. It has no identifier in it, so there is no way to join two of them together or to work back to a person. Nothing from inside your document is in it: no text, no filename, no question you were asked and no answer you were given. I read it to see whether the thing works, in which countries people are trying to use it, and how often it fails, because until now I had no way of telling.
What I don't do
No third-party analytics, no ad pixels, no trackers, no cookies, and no account. Nothing you type and nothing your document says is ever recorded. The only things kept in your browser are the document you're working on and a couple of local settings.
To remove your email, a feedback post, or anything else about you, use the contact form or email [email protected], and I will delete the record.