HidePDF Content

Privacy

Last updated: 28 October 2026

HidePDF Content processes PDFs you send to hidepdfcontent.com so it can list sensitive fields and, if you ask, return a file with those fields burned out. This page is the plain description of that handling, plus cookies and advertising. You can reach the operator from the contact page. There is no customer account.

Files you upload

A playground or API request sends the PDF to the server for that request. The bytes are read into memory, up to the 25 MB limit. The server looks for emails, phones, cards, IBANs, country IDs, labeled names and addresses, and amounts. It then either returns a review list or builds a new PDF.

The upload is not written into a document library, a user folder, or a database. It is not kept after the response is sent. The contact form on this site does not upload a file at all. It opens your email app.

Inspect responses show a masked preview (a single letter of an email, the last digits of a number) so you can recognise a field without the JSON repeating the full secret. The raw value is used on the server to place the block, then dropped with the request.

OCR and temporary files

Pages that already contain a normal text layer are read from that text. A page with very little text, under about 40 characters, is treated as a scan. The server renders that page to a PNG, writes the PNG to the operating system's temporary directory under a name that starts with hidepdf-ocr-, runs Tesseract on it, and deletes the PNG when that step finishes, including when OCR fails or returns nothing. The PDF itself is not written beside that image.

If the process is killed in the middle of OCR, a temp image can remain until the host clears its temp directory. That file is not indexed, not attached to an account, and not reused for a later request. See the scanned PDF guide for what OCR is good at and where it misreads.

How long anything is retained

  • The PDF: in memory for the request, then gone. No retention period, because it is not stored.
  • The OCR PNG: deleted at the end of the OCR step for that page.
  • The download: sent to your browser or API client. We do not keep a copy of the burned PDF.
  • Request logs: the server logs the usual request line (time, method, path, status, duration). Those logs are for running the service. They do not include the PDF bytes or the field list. The host (Railway) may keep platform logs under its own retention.
  • Email you send us: kept in the hello@ inbox like any other mail, until it is deleted.

API keys

The playground in your browser talks to the same host, so it does not need a key. Direct API calls, RapidAPI, and Zapier do. A key is a secret we issue. It is not a user profile. We do not sell upload contents. Do not put a live secret in a support email when you ask for a key.

Cookies

HidePDF Content does not set a login cookie, a session cookie, or an analytics cookie of its own. You cannot sign in, so there is nothing to remember.

The pages load fonts from Google Fonts. When you preview a PDF in the playground, the browser loads PDF.js from jsDelivr. Those are requests your browser makes to those hosts. They are not the same as storing your PDF.

Advertising and Google AdSense

This site uses Google AdSense to show ads, under publisher ID ca-pub-1210860150241703. The AdSense script (adsbygoogle.js) is included on the pages, and /ads.txt authorises that publisher. Ads help pay for the hosting. They are not related to the contents of a PDF you upload. The PDF is not sent to Google as an ad signal, and ad code does not read the file you drop on the playground.

Google, and other vendors it works with, may use cookies, mobile advertising IDs, or similar identifiers to serve and measure ads, and to show personalised ads if your Google settings allow them. That includes cookies set from Google domains when an ad or the AdSense script loads. How Google uses information from sites that use its services is described in Google's privacy policy and in Google's advertising policies and technologies page.

You can opt out of personalised ads, or tune the categories Google uses, without creating an account on this site:

Browser controls that block third-party cookies will also limit what an ad can store. Where Google asks for a consent choice before personalised ads in your region, that choice is part of Google's ad flow. This site does not run a separate account system for it.

What we do not do

We do not sell the contents of uploads. We do not build a marketing profile from the fields inside your PDF. We do not ask for a name or email before you use the playground. Country ID patterns exist so the tool can find those numbers on a page. Finding one does not mean we store it.

Contact

Privacy questions, and requests about mail you have already sent, go through the contact page.