Privacy for pdfpix in ChatGPT

The tools on pdfpix.com run in your browser. The pdfpix app inside ChatGPT cannot: ChatGPT hands us your file, and our server runs the tool. We process the file in memory, serve the result for 15 minutes through an unguessable link, and keep no copy of the file you gave us. This page lists everything the app keeps and for how long.

What the app keeps, and for how long
What Kept?
The file you give ChatGPT Kept?In memory while the tool runs, then dropped
The file the tool produces, and its file name Kept?Up to 15 minutes behind its link; deleted within a day
The reply ChatGPT receives Kept?Reused for 10 minutes, so a repeated call gets the same answer; deleted within a day
The text inside your file Kept?Never in logs or the counter; only inside a reply that quotes it
File names and download links in our logs Kept?Never stored
Which tool ran, how long it took, file count and total size Kept?One usage-counter row, with no identifier
Your ChatGPT user id Kept?Used as a rate-limit key for 60 seconds, never stored

How your file reaches us

When you ask ChatGPT to use a pdfpix tool, ChatGPT sends our server a short-lived download link for the file you attached. Our server fetches the file from OpenAI's file host, runs the tool on it in memory inside a Cloudflare Container, and verifies the result the same way the browser tools do. The source file is not written to disk and is not kept after the run.

The result and its link

A tool that produces a file stores it in a Cloudflare R2 bucket that no route lists, under a random, unguessable link. The link works for 15 minutes and then returns an expiry message. A lifecycle rule on the bucket deletes anything older than a day. Anyone who has the link can download the file while it works, so do not share it.

ChatGPT sometimes repeats a tool call. To give the same answer instead of running the tool twice, we keep the reply ChatGPT received, with its summary, verification results and link, in the same bucket. We reuse it for 10 minutes and never read it after that; the same lifecycle rule deletes it within a day. A few tools quote your document in that reply: Compare PDFs names the words that changed. That quote lives and dies with the reply.

Logs

Each request writes one log line with counts and fixed codes: the tool name, whether it succeeded, how long it took and the output size. To tell repeated calls apart, the line also carries short one-way hashes of the chat session and the file ids. Logs never hold a file name, a download link, file bytes or the text of your document.

Our usage counter

Every tool run in ChatGPT writes one row to the same usage counter the website uses: which tool, whether it finished or failed with a fixed error code, how long it took, how many files went in, their total size and the size of the result. The row also holds the coarse location of the request, which for this app is OpenAI's server, not you. A repeated call that we answer from the kept reply writes no row. The row stores no IP address, no file name, no document data and no identifier.

Rate limit

Each ChatGPT user can run 20 tool calls a minute. To count them, we key the limit on the opaque user id ChatGPT sends with each call. The count lives for 60 seconds and is not written anywhere else.

No account, no analytics

The ChatGPT app needs no pdfpix account and no sign-in. It loads no analytics script and sends nothing to PostHog. We do not see your conversation, only the tool call ChatGPT makes and the file it links.

Third parties

Two companies handle data for this app. OpenAI runs ChatGPT, holds your conversation and the files you attach under its own terms, and sends us the tool call. Cloudflare runs our server, the container and the storage bucket. Nothing is sold or shared with anyone else.

Questions and removal

Wraxle LLC runs pdfpix and this app, and is responsible for the data this page describes. Results delete themselves, so there is usually nothing to remove. To ask about this policy, write to us through support. The policy for the website itself is on the privacy page.

Where to go next