Privacy model
Workspace-first
Documents and application settings are designed to remain in your browser's local storage/IndexedDB rather than being uploaded to a Parallel Notes backend.
Local AI option
When a local WebLLM model is used, model inference runs in the browser on supported hardware.
Cloud AI is optional
If you configure Gemini, OpenAI, OpenRouter or another compatible provider, text required for the task is sent to that provider from your browser.
No account system
The static application does not require a Parallel Notes account for its normal workspace workflow.
Workspace and settings
Parallel Notes stores workspace documents in the browser using IndexedDB. Application settings are also stored locally. This includes document content, generated results and configuration needed to restore your workspace.
Because this is browser-local storage, it is tied to the browser profile and site origin. Clearing site data, private browsing sessions or destructive reset actions can remove local information.
PDF and DOCX processing
Imported PDF and DOCX files are processed in the browser/application workflow and the resulting editor content is saved through normal workspace persistence. The application does not intentionally keep the original uploaded file as a workspace document.
For any import mode that uses an AI provider for structure assistance, the relevant extracted content is processed by the selected provider. Review the provider's own privacy and data-use terms before using sensitive material.
When text leaves your browser
Parallel Notes supports both local and cloud AI workflows. The distinction is important:
- Local WebLLM: generation is performed in the browser when the selected model can run on your device.
- Gemini: requests are sent to Google's configured API endpoint using the API key you provide.
- OpenAI: requests are sent to the configured OpenAI API endpoint.
- OpenRouter: requests are sent to OpenRouter and then handled according to the selected model/provider's policies.
- Custom OpenAI-compatible APIs: requests go to the endpoint you configure; that endpoint's privacy policy applies.
Parallel Notes does not control how an external provider stores, logs, retains or uses content after the request reaches that provider. Consult the provider's current documentation before sending confidential information.
API key handling
If you choose to remember an API key, Parallel Notes stores it locally in the browser for convenience. This is not a secure secrets vault. Anyone with access to the relevant browser profile and local site data may potentially access locally stored credentials.
You can avoid persistent storage by leaving the remember option disabled where supported, and you can remove/reset stored configuration from the application's settings.
Website analytics
The hosted application currently loads a Counter.dev analytics script. This is separate from the application's workspace storage and AI generation pipeline.
For details about Counter.dev's own handling of analytics information, consult Counter.dev's privacy information.
Offline assets
The application uses a service worker to cache application assets for faster repeat visits and offline-friendly shell behaviour. Cached assets are scoped to the Parallel Notes application's own origin/cache namespace.
Deleting your local data
- Use Data & Reset in Settings to delete workspace documents or clear local model caches.
- Browser/site-data controls can also remove locally stored application data.
- Deleting local data does not undo data already sent to an external AI provider; provider-side retention is governed by that provider.
Keep this policy current
This page describes the current static application's architecture and should not be treated as a guarantee about third-party services. Provider terms, analytics services and browser capabilities can change independently of Parallel Notes.