Documentation menu
Security
Data handling
The CLI
- Runs locally or in your CI. It has no telemetry and makes no network requests other than to the adapter target you configure and, only when you run
authorupload, the Memtru server you name. - An optional SDK factory can call its configured embedding/model services. The Mem0 loader disables Mem0 telemetry before factory import, and raw insertion disables extraction inference, but a real embedder still sends synthetic fixture/query text to its model service. The local integration test uses deterministic model substitutes and makes no model calls. Review factories and supply provider credentials only for an authorized sandbox.
- Creates synthetic fixtures only. Principals, tenants and markers are generated per run.
- Writes reports to
report.output_dir. By default reports contain fingerprints, labels and outcomes, not fixture text. - Stores an API token only when you run
memtru auth login, in~/.memtru/credentials.json.
The web application
Stored per organization:
| Data | Purpose | Retention |
|---|---|---|
| Account: name, email, scrypt password hash | Sign-in | Until the account is removed by an operator |
| Sessions: SHA-256 of the cookie value, expiry | Sign-in | 14 days, pruned on new sign-in |
| Organizations, memberships, projects, settings | Access control | Until deleted |
| API tokens: SHA-256 hash, prefix, scopes, expiry, last use | CLI authentication | Until the project is deleted |
| Runs, results, findings (sanitized) | The product | Project retention setting, 7–365 days (default 90) |
| Upload records: run id, size, outcome, time | Idempotency and audit | With the project |
| Audit events: action, actor id, target id, time | Security review | Not pruned in this release |
Not stored: plaintext tokens, plaintext passwords, raw memory content (uploads that declare it are rejected), request bodies in logs.
Deletion
- Owners can delete a run, or a whole project (runs, findings and tokens cascade).
- Retention removes runs older than the project's window when the next report arrives.
- Local mode stores data in SQLite; the selected hosted topology stores it in the private Supabase PostgreSQL schema. Operators who back it up must apply their own retention to backups; Memtru cannot delete data from copies it does not control.
Analytics
The web application has no third-party analytics or tracking scripts. Product metrics, if added later, must follow the same rules: explicit policy, no prompts or memory content, opt-out where required.