Skip to content
ReageOpen a PDF

PRIVACY

Reage privacy: local-first PDF editing

Choose where processing happens. Reage does not require an account, does not overwrite your original, and does not send your PDF to font or OCR asset providers.

Local mode

The local edition runs the Python PDF service on loopback. Documents live in bounded, expiring process memory and are removed when you close them or restart the service.

Hosted mode

The hosted editor sends the source PDF and the current edit state with each operation. The stateless service processes the request and returns the result; it does not provide a saved cloud document store.

Public assets

Optional open-font downloads and first-use OCR models use public repositories. Your PDF and rendered page data are not sent to those providers. Font uploads in hosted mode stay scoped to the current browser workspace.

Read the implementation

For exact limits and supported structures, read the capability matrix and implementation notes.

Frequently asked questions

Does Reage need an account?

No. Reage does not require sign-in or a saved project account.

Does Reage send my PDF to Google Fonts?

No. Public font providers receive only the requested font asset lookup. The PDF remains with the Reage processing path.

ABOUT THE PROJECT

Built in the open by Sameer and contributors.

Sameer is the creator and maintainer of Reage, an open-source PDF editor shaped around careful document handling and honest explanations of what a PDF can preserve.

Read the project story