Local-only vault
Markdown and derived local intelligence stay in browser-managed storage on this device. Sync and connected processing remain off until you choose them.
Privacy-first product
Local-first does not mean local-only.
You decide what stays on-device, what syncs, and what connected intelligence may process. Creating an account does not upload local-only note content or change a vault's storage mode.
Where your data can live
Provider-backed vault
Phasoric keeps a local working cache and syncs the mapped vault to your chosen Google Drive, Dropbox, or GitHub connection where supported.
Phasoric Hosted vault
Markdown and attachments mapped to Phasoric Hosted are stored for your account, collaboration, recovery, API, or automation features you enable.
Connected provider context
A bounded set of authorized source excerpts can be retrieved or processed for the request; connecting a provider does not remap every local vault.
Selective, inspectable boundaries
Your deviceLocal knowledge and private derived indexes
Optional sync
Your chosen storageLocal, provider-backed, or Phasoric Hosted
Bounded context
Connected intelligenceOnly under the selected provider and scope
What leaves the device, and when
The answer depends on the vault, storage mapping, processing route, and feature you choose. This matrix describes product behavior; the legal policy remains authoritative for personal information.
| Activity | Leaves the device? | Boundary |
|---|---|---|
| Local notes and search | No | Local-only editing and lexical search run on the device. |
| Local embeddings, OCR, transcription | No, when local processing is selected | Models and derived indexes remain rebuildable local state. |
| Provider sync | Yes, by choice | Mapped content goes to the provider selected for that vault. |
| Phasoric Hosted sync | Yes, by choice | Only vaults and inputs explicitly mapped to hosted storage use it. |
| Connected AI requests | Yes, by choice | Only bounded, authorized context needed for the request is sent. |
| Connections retrieval | Yes, on request | The selected connection is queried under its grant and context scope. |
| Traffic and measurement | Basic counts; optional deeper measurement | Aggregate visits and limited consent-mode signals continue with either privacy choice. Optional cookies and deeper attribution require consent. Measurement excludes private workspace content. |
| Collaboration | Yes, when enabled | Shared hosted workspace state is available to authorized collaborators. |
| MCP and API | Yes, for explicit hosted mappings | Hosted interfaces cannot remotely read an unmapped local-only browser vault. |
AI processing you can choose
- Use supported local models so source context stays on-device.
- Connect your own provider under its credentials and policies.
- Use metered Phasoric Hosted intelligence with bounded authorized context.
- Inspect and govern Personal AI Memory; inferred items require confirmation.
- Source content is treated as evidence data, not as a system instruction.
Controls stay with you
- Export portable Markdown and attachments.
- Choose or change a vault storage mode explicitly.
- Disconnect providers and remove their grants.
- Inspect AI memory and source provenance.
- Review consequential Forge mutations before execution.
- Export hosted data and request account deletion; local and external-provider vaults remain separately controlled.