SECURITY

Your memory is yours. Here is how we keep it that way.

Every customer separated

Each team's memory lives in its own store, with its own data key kept outside the data and the backups. One team can never read another's.

No outside AI sees your data

Prism, our own model, finds and packs the context inside Remiq. Your data never goes to an outside AI service, and your model and keys stay with you.

Delete means gone

A delete removes the record from every index, cache and derived fact. Deleting a team destroys its key, so its backups become unreadable too.

Secrets never shown

Keys and passwords in memories are hidden in every answer. Personal data is hidden by your rules.

Memory is data, not orders

Every context arrives fenced as quoted data, with rules that tell your model never to obey it. Keeper, which holds such text back for review, is being switched on before launch.

Keys you control

Keys are 192 random bits, stored only as a fingerprint. They can expire, be limited to some spaces, and show when they were last used. Many wrong keys from one address are slowed down.

Checked from the outside

Independent security audit: planned before launch. Results will be summarised here.

Found a problem? Write to security@[your-domain]. We reply within 2 working days. Rules for researchers: /.well-known/security.txt

STATUS · STATUS.[YOUR-DOMAIN]

Status

Memory APImeasured from launch
Consolemeasured from launch
MCP (Claude, ChatGPT)measured from launch
Connectionsmeasured from launch
Sign-in emailsmeasured from launch

Uptime is published from the first day of service, never estimated.