Local-first by default
Tramya indexes what your agents (Claude Code, Codex, Cursor…) already write to disk. The index, memories and decisions live on your device and need no server to work.
Security & privacy / Local-first
Your data stays with you.
The Cloud is optional and encrypted.
Tramya is local-first memory for your AI coding agents. By default, your history, index and decisions stay on your machine. The Cloud is only an end-to-end encrypted bridge you enable if you want it — never a data warehouse.
Architecture
What stays local, what may travel.
Optional encrypted Cloud
If you enable Cloud backup, every item is encrypted on your machine before it leaves. The server only stores ciphertext (AES-256-GCM): it cannot read your content.
Keys derived locally
The encryption key is derived from a passphrase via scrypt, and cross-device key exchange uses ECDH X25519. Private keys never leave your machine.
Recovery key
When you enable the vault, you get a recovery key to keep offline. It restores your index on a new machine. Without it and the passphrase, no one — not even Tramya — can decrypt your data.
MCP, no exfiltration
Tramya hands context from one agent to the next over MCP (Model Context Protocol), locally. The protocol is a bridge between your tools, not a channel to a third party.
Zero product telemetry
The companion ships no analytics tracking. We don't collect your coding activity, prompts or files. What Google Analytics measures is limited to the marketing site, with consent.
Data boundary
What never leaves your machine.
- Your agent API tokens (Claude, Codex, Gemini…). Tramya doesn't read them and doesn't transmit them.
- Your code files and raw conversation content, as long as you don't explicitly enable an encrypted backup.
- Your local secrets (environment variables, config, vaults). They stay out of reach of the Cloud.
- Your private encryption keys. They are generated and kept locally.
The optional Cloud only receives what you deliberately share, and only as ciphertext. See also the local-first model and our privacy policy.
Threat model
What Tramya protects you against.
- Server-side leak. Because the Cloud only holds ciphertext, a server compromise does not expose your content in the clear.
- Malicious device linking. Connecting a device to an account requires explicit confirmation and only accepts Tramya's official Cloud servers.
- Silent tracking. No product telemetry: nothing is sent from the companion behind your back.
- Assumed limits. Tramya can't protect against malware that already has full access to your session, nor against losing both your passphrase and your recovery key.
Frequently asked questions about Tramya security
Does my data get sent to a server?
Not by default. Tramya is local-first: the index and memories stay on your machine. Only if you enable Cloud backup is encrypted data sent, and the server can never read it in the clear.
What encryption does the optional Cloud use?
Content is end-to-end encrypted with AES-256-GCM. The key is derived from a passphrase via scrypt, and cross-device key exchange uses ECDH X25519. Encryption happens on your machine before anything leaves.
What happens if I lose my passphrase?
Your recovery key, issued when you enable the vault, lets you restore the index on a new device. If you lose both the passphrase and the recovery key, the encrypted data is unrecoverable — that's the trade-off of encryption where we don't hold the key.
Does Tramya collect telemetry?
The companion ships no product tracking. We collect neither your prompts, nor your files, nor your coding activity. Only the marketing site uses audience measurement, subject to your consent.
Can Tramya see my agent API keys?
No. Your agents' API tokens (Claude, Codex, Gemini…) stay managed by those tools. Tramya doesn't read them and never transmits them.