Cookies & Browser Storage
A practical explanation of theme storage, public engine caches and private document handling in InBrowserPDF.
Last updated: 4 November 2026
- Zero advertising, retargeting, or third-party analytics cookies.
- Only your light/dark theme choice is saved in localStorage (inbrowserpdf-theme).
- CacheStorage holds public WebAssembly engine binaries, never your private PDFs.
Current storage behavior
The application does not set advertising or analytics cookies and does not load tracking scripts. A preference named inbrowserpdf-theme is stored in localStorage so your selected light or dark theme survives future visits.
The browser may retain public JavaScript, WebAssembly, OCR data and AI model assets in its HTTP cache. The Office converter uses CacheStorage for public compressed engine parts. These caches contain processing software, not private document contents.
Workspace data and downloads
The app keeps selected files and results in its active workspace rather than storing them in an application document database. Downloaded files are separate: your browser or operating system saves them at the location you choose. Clearing site data does not delete those downloads.
There is no blanket offline guarantee. Previously cached public assets may be available, but first use, a cache miss, eviction or a new version can require a connection to this site.
Managing storage
Use your browser’s site-data controls to clear localStorage, CacheStorage and cached assets for inbrowserpdf.app. This may reset your theme and require processing engines to download again. Contact support@inbrowserpdf.app about storage behavior.
Production hosting may add infrastructure cookies or storage behavior outside the current application code. The operator must review and disclose any such additions before introducing them.