Cloud memory and AI processing
Natural-language notes and recall use Memoato’s cloud memory. Original notes are stored on the server. Note text and relevant context can be sent to configured AI providers to extract details or answer a recall question.
This flow is not end-to-end encrypted. When you connect an AI client through MCP, that client and its provider can also see the data you ask them to handle.
What the storage modes cover
- Cloud sync — categories, entries, and cloud memory are stored on the server for use across devices.
- Encrypted cloud — category titles and per-entry notes are encrypted on your device before saving. This protects those fields, not every field or the separate cloud memory and MCP flow. You need your passphrase on each device; Memoato cannot recover it.
- Local-only — category-based logging stays in this device’s browser. Cloud memory and MCP are not local-only features. Clearing browser storage or losing the device can lose this local history.
Review these options under Profile → Privacy. Switching to local-only deletes your account’s server data. Export anything you need to keep before switching.
Give a client only the access it needs
API keys are scoped and revocable. Choose logging, recall, both, or Context packets for a configured pilot. A key does not require sharing your account password. You can set an expiry and revoke it from Profile; the full key is shown only when created.
For project context, the current pilot reads from GitHub and Linear without writing back to them. Claims need human acceptance; access grants and freshness are checked before a context packet is built. The pilot is one owner and one workspace, rather than open multi-user team access.
Read the exact behavior and service providers in the privacy policy.