Ream

Privacy Policy

Last updated: June 2026

The short version

Ream processes your files entirely on your device. Your files are never uploaded, transmitted, or shared with anyone — including us.

What data we collect

None. Ream collects no personal data whatsoever.

  • — No analytics or telemetry
  • — No crash reporting
  • — No usage tracking
  • — No advertising identifiers

How your files are handled

All PDF and image processing happens locally in your browser using WebAssembly. Your files are read from your disk, processed in memory, and the output is saved back to your disk. At no point does any file content leave your device.

You can verify this yourself: open Chrome DevTools (F12), go to the Network tab, and run any Ream operation. You will see zero outbound requests carrying file data.

Permissions

Ream requests only one browser permission:

  • storage — used solely to cache the OCR engine (WASM binary + language data) so it does not need to reload on every use. No file content is stored.

Ream has one host permission for extensionpay.com — used only to verify your one-time Pro license. No file data is sent to this service.

Pro license (ExtensionPay)

If you purchase Ream Pro, payment is processed by ExtensionPay (via Stripe). ExtensionPay receives your email and payment information to manage your license. Ream itself only checks whether your license is active — it never sees payment details.

Local storage

Ream uses Chrome's storage API to cache the Tesseract OCR WASM binary and English language model so they load quickly on subsequent uses. This data is stored locally on your device and never transmitted anywhere.

Third-party code

Ream bundles open-source libraries (pdf-lib, pdf.js, Tesseract.js). These libraries run entirely locally — they make no independent network connections.

Changes to this policy

If we ever change this policy, we will update the date above and post the new version here.

Contact

Questions? Email neek.by@gmail.com.