Privacy · Last updated October 6, 2026
ReadOrbit privacy
What stays on your device.
What optional AI sends.
Local documents and processing
ReadOrbit reads and renders PDFs on your computer. The current AI integrations send text and related classification information; they do not upload the PDF file itself or rendered page images to the developer or AI providers.
Tesseract OCR runs locally with bundled English/Japanese language data. Settings, extracted text and document caches, OCR text and coordinates, category icons, recent document locations, reading state, Dock preferences, and note drafts or indexes are stored on your computer. Markdown notes are saved in the folder you choose.
These local files are not all encrypted. Protect your device and backups. A cloud-synced folder or an external synchronization tool can copy them independently of ReadOrbit.
Adding a note does not call an AI provider. A note contains your selected quotation and your comment; review its contents before sharing.
Your AI choice
New installations begin with Local only. In this mode, external AI operations are disabled; local viewing, OCR, notes, cached results, and manual organization remain available.
Optional bring-your-own-key (BYOK) features use your configured TypeSafe Jev and OpenAI accounts. Requests go directly from the app to the corresponding provider, without a ReadOrbit-operated AI relay. Provider billing, terms, and data policies apply.
Adding or dropping a PDF for analysis in BYOK mode can start several provider requests automatically. Explicit analysis, reanalysis, selection assistance, icon generation, and provider connection checks may also make requests. A connection check sends a small test request rather than document content. Switching to Local only stops new AI requests and attempts to cancel active work; it cannot retract text already sent or undo provider charges.
ReadOrbit AI hosted account features are not configured for production. A hosted service would require a separately reviewed policy before release.
Text sent by optional AI features
| Feature | Provider | Information sent |
|---|---|---|
| Document information | OpenAI | A bounded excerpt from opening pages, including extracted or locally recognized text. |
| Field classification | TypeSafe Jev | Bounded document context, potentially including title, organization, abstract, claims, opening text, and category choices and descriptions. |
| Research topics | OpenAI | Field, title, summary, classification context, and existing topic names. A filename-derived title may be used if no document title is available. |
| Translate / Explain / Summarize | OpenAI | The passage you select, task instructions, and processing settings such as response language. |
| Category icons | OpenAI | The category label, category kind, and parent label. |
AI transmission is not limited to explicitly selected text. Local OCR text can leave your device if you choose AI analysis. Send material only when you have permission to share it with the provider.
The current OpenAI integration sets the API storage option to false. This does not guarantee zero provider retention or logging. ReadOrbit does not promise a retention period for either provider; consult the provider's current policies and account controls.
API keys and device storage
Provider keys entered in Settings are handled by the application's main process and stored using operating-system-protected encryption when available. The app refuses credential use or updates when protected storage is unavailable or saved credentials cannot be read, rather than silently replacing unreadable data. The interface reports key configuration status without returning saved key values.
This protection does not completely isolate keys from other processes running as the same Windows user. A key is sent as an authorization credential to its corresponding provider when making a request. Do not put keys in notes, reports, screenshots, or logs.
Production builds do not use environment-based API keys. Developer environment keys are restricted to explicitly opted-in, unpackaged development builds.
Usage records and diagnostics
The local API Usage ledger records provider, operation, model, timing, response status, token counts when available, and estimated cost. Its fields do not contain API keys, request bodies, selected passages, or full provider responses. Estimates are not a provider billing statement.
The current production implementation does not activate a ReadOrbit analytics exporter, automatic crash-report upload, or operator-hosted document service. This is not a claim that the operating system or external components never connect to a network.
Development or explicitly enabled debug logs can include document text or provider responses. Review and redact diagnostics before sharing.
Deletion and your choices
Use Local only when you do not want AI transmission. Configure only the keys you need and check permissions before enabling analysis. Closing a PDF tab does not delete the original PDF, saved notes, or caches; clearing recent history is not complete data erasure.
Contact information and the final privacy terms will be reviewed before public release. Contact information is not available yet.
This website
This static website is hosted on Cloudflare. It has no contact form, advertising, analytics scripts, third-party font downloads, or embedded services. If you change the appearance setting, that preference is stored in this browser.
Hosting is subject to the Cloudflare Privacy Policy. Links you choose to follow may take you to other services with their own policies.