Privacy policy

Last updated: 20 September 2026. This policy explains how SandboxPDF at sandboxpdf.com handles document processing, website requests, browser storage and contact messages. Use the contact form for privacy questions or requests.

Documents are processed on your device

Files selected in the PDF workspace are processed in your browser. The application does not send their contents, filenames, document passwords, certificate private keys, extracted text or document-chat questions to a remote processing API. Previewing a page and downloading a result are local operations. Selecting a file is not the same as uploading it to our host.

Open documents, intermediate results and conversation text are held in browser memory while the workspace is running. Closing or refreshing the tab releases the application’s references to that session. The website cannot delete your original files or downloaded results. Your operating system, extensions, device backups and browser may handle local data independently; local processing does not replace securing your device.

Downloads needed to run the tools

The browser requests application code, fonts and processing engines from the website. Optional OCR and AI features download language or model files. Model requests may go to Hugging Face and its delivery infrastructure; OCR language data may be requested from tessdata.projectnaptha.com. Those providers receive ordinary request information such as an IP address and browser headers. Document content is not included in model-download requests.

Office conversion downloads its processing engine from this site. Some model files are large and may be cached on your device for reuse. Being able to run an initialized model without a network connection does not mean every tool or a newly opened page is available offline. The interface describes any preparation required before offline use.

Website and hosting information

The hosting provider receives the requests needed to deliver pages and assets. These requests can include your IP address, browser information, requested path, time and referring page. Operational logs may be used for delivery, security and troubleshooting. They are separate from your locally processed PDFs. Do not put personal information in page URLs or share links containing confidential details.

The application does not create an account or a server-side document library for you. There is no password recovery service for encrypted PDFs and no remote document-chat history to retrieve. We do not sell the contents of your documents; the workspace does not receive those contents in the first place.

Browser preferences and storage

Theme preferences, guide preferences and saved workflow settings may be stored locally in your browser. Downloaded OCR and language-model assets may use browser caches. These settings and caches help avoid repeating setup; they are not a server-side archive of your files. Browser storage can be unavailable in restricted modes or removed when space is needed.

You can clear this site’s data in your browser settings. Doing so may reset preferences and require model files to download again. Deleting browser storage does not remove PDFs already saved to your Downloads folder. On a shared computer, also consider downloaded copies, recent-file lists and whether someone else has access to the operating-system account.

Contact messages

When you submit the contact form, the website receives your name, email address, subject and message for delivery to the support inbox. The form deliberately has no document attachment field. We use correspondence to respond, investigate reported issues and maintain necessary records of the request. Do not include sensitive document contents, passwords or private certificate material.

Contact delivery is an exception to the local-only document workflow: information you intentionally enter into the form is transmitted. Our host, email delivery service and inbox provider process that correspondence as needed to deliver and store it. The current support inbox uses Gmail. See Google’s privacy policy for information about Google services. We do not use contact messages to train a document model or automatically subscribe you to marketing.

Correspondence is retained only as needed to handle the request and related legitimate recordkeeping or legal obligations. You can ask about access, correction or deletion through the contact form. Applicable rights depend on your circumstances and the laws that apply. A request to delete server-side PDFs cannot be fulfilled because the workspace does not upload or retain such PDFs.

Advertising and cookies

If Google advertising is introduced, third-party advertising providers, including Google, may store or read cookies to select ads using visits to this website and other websites. Google and participating partners can use advertising cookies to personalise those ads. Personalised advertising choices are available in Google My Ad Center and through participating vendors at AboutAds choices.

Advertising consent and vendor information must be presented when relevant to an advertising deployment. Where a consent interface is offered, you can review or change choices there. Your browser also provides cookie controls, although blocking storage can affect preferences or model caching. A preference for non-personalised advertising does not necessarily mean no cookies or network requests are used for delivery, security or measurement.

Advertising choices are separate from document processing. Your document contents are not used to personalise advertising or sent to advertising providers. When advertising is available, the consent interface and this policy identify the applicable choices and providers.

Security, external links and changes

We use local document processing to reduce unnecessary transmission. No website or device can promise absolute security. Keep your browser current, use a trusted device, and inspect downloads before relying on them. External reference links take you to other websites with their own policies; following those links sends ordinary browser requests to their operators.

This policy may change when the service’s data practices change. The date above identifies this version. Material changes should be reflected here before the corresponding feature is enabled. If the way a feature handles data is unclear, ask through Contact before entering sensitive information into any communication field.