This page answers what a security review usually asks about Retain7. It describes what the service does today, including what it does not do yet. The legal detail is in the privacy policy and the terms.
What we store
The titles, bodies, types, tags and file paths of the memories and handoffs your team and its agents save, with their edit history, plus account, team and usage records. Usage records hold no memory text. Card numbers never reach us: Dodo Payments handles payment.
Your content is not used to train models
Memories are turned into search vectors by an embedding model that runs on our own infrastructure. Retain7 does not send memory text to third-party AI providers, and does not use your content to train AI models. The AI tools you connect receive the memories they ask for, under their own terms.
Isolation between teams
Every project belongs to one team, and every lookup is limited to projects the signed-in user can reach. Isolation between teams is covered by automated tests that run on every change.
Roles
Each member is an Owner, Admin, Member or Viewer. Viewers and their agents can search and read memories but cannot save. Only owners see billing. Agents act with the permissions of the person who connected them.
Sign-in and agent access
Agents connect over MCP with OAuth 2.1 and PKCE, so most people never handle a token. Personal access tokens exist for headless machines and can be revoked. Accounts can sign in with a password or with Google. Every request to the MCP endpoint is rate limited.
Secrets are blocked before they are stored
A save that contains an API key, token, private key, password or a connection string with credentials is refused before anything is written.
Shared memory and prompt injection
Memory that every teammate's agent reads is also a place bad instructions could be planted. Retain7 reduces that risk but cannot remove it. Memories saved by agents land in a review inbox, and an automated check rejects progress logs and noise. Anyone with access can mark a memory outdated, every edit is kept in the history, and each memory shows which tool saved it. Treat memory as notes, not as commands, and review what your agents save.
Retention and deletion
- Deleted memories can be restored for 30 days, then they are removed for good.
- Deleting a project, team or account removes its memories and history within a day. Backups expire on the normal backup schedule.
- Usage records are kept for 30 days. Edit history is kept for up to 12 months.
- You can export any project as JSON or Markdown from the dashboard at any time.
Sub-processors
The providers that handle data for us are listed in the privacy policy, under "Who receives it". We will update that list and tell account owners before we add one that handles your content.
Data processing agreement
Your team is the controller of the content it saves and we process it on your instructions. Email [email protected] to get a data processing agreement signed.
What we do not have yet
- No SOC 2 or ISO 27001 report. We do not claim one.
- No single sign-on (SAML or OIDC) for teams.
- No self-hosted edition.
- The audit trail covers edits to memories, not every action in a workspace.
If one of these blocks your team from using Retain7, tell us at [email protected]. What blocks real teams decides what we build next.
Report a vulnerability
Email [email protected] with the details. We will confirm receipt, fix real issues quickly, and credit you if you want.