Trust

Trust and security at Mensara

Mensara checks each person's access before any model sees a file, holds changes to governed areas for an approver, keeps a signed, tamper-evident receipt for each read and change, and keeps your records as ordinary files in a Git repository that you can back up to your own GitHub. Its public pages list no SOC 2 report or HIPAA compliance claim, and if Mensara operates the server that holds your Mind, the separation between your Mind and Mensara's account system is not a promise that the operator cannot access it.

Facts checked 18 November 2026 against the pages listed under Sources.

The short answer

QuestionAnswer
Who can read a record?Each person signs in with their own account. Their agents work within that person's access, checked by software before any model sees a file.
Who approves changes?Changes to governed areas, such as decisions, wait for the owner or another approver. Deleting or renaming a file always waits.
What is recorded?A signed, tamper-evident receipt for each read and change, including refusals. It stores fingerprints, not the file path or the text.
Where does our content live?On your Mind's own server, not in Mensara's account system. Who runs that server depends on the hosting arrangement you choose.
Where do keys and credentials live?On your Mind's server, not in the mensara.ai account system. The owner keeps a Recovery Kit separately. If Mensara operates the server, that separation is not a promise that the operator cannot access it.
Can we take our data?Yes. Saved records and their version history are ordinary files in a Git repository, and you can keep a private copy in your own GitHub.
Which AI providers see our content?The providers behind the agents you connect, and only what those agents read within each person's access. An app or automation you install uses the AI provider set up for it, limited to that app's access.
Certifications?Mensara's public pages list no SOC 2 report or HIPAA compliance claim.

How changes are approved

People and their agents propose updates where the work happens. Out of the box, a change saves without a person only when an automatic check passes and both the proposer's trust level and the area's own limit allow it. Read the outcome: an applied proposal has changed the saved record; a held one is waiting and has not; a rejected or refused one has not saved.

  • In governed areas (decisions, charter, principles, skills and practice), a member's change is held for the owner or another approver. You can require approval in other areas too.
  • Deleting or renaming a record is always held.
  • An area can give someone permission to suggest edits without giving them authority to approve.
  • Automatic approval is a separate setting a person can turn on for review cards they are already allowed to approve. It gives no extra authority, and it never covers renames, deletions, policy and app code, or requests that explicitly require a human decision.

Sources: Review changes and check what was saved, Understand your Mind's settings.

Signed, tamper-evident receipts

The Mind keeps a signed, tamper-evident receipt for each read and change, including refusals.

  • What a receipt holds: who asked, the kind of action, which areas it touched and the outcome (allowed, refused or held), plus fingerprints of the request and response.
  • What it does not hold: the file path or the text.
  • Where to read them: the owner reads the receipts in the Mind's policy area, 25-policy/audit.jsonl, with older sealed segments in 25-policy/audit-segments/.
  • Where to see the wording that changed: each saved record keeps its earlier versions, and that version history shows the actual wording.

A receipt shows what the Mind did. It does not prove that the original email, meeting note or decision was true.

Source: Review changes and check what was saved.

Access is checked for each person before any model sees a file

  • Every teammate signs in with their own account, and their connected agent works using that person's access. A well-written prompt cannot give it permission to open an excluded area.
  • The Mind checks the caller's permissions before serving a read or allowing a change. Search results leave out areas the caller cannot read, and a direct request for an excluded record is refused.
  • Reading, suggesting and approving are separate permissions. Being able to read a policy does not by itself let someone replace or approve it.
  • An installed app has its own identity and granted access. Approving an automation does not give it all of the owner's access.
  • A new Mind starts on the Open team preset, which lets every member read, suggest, subscribe and work on tasks in eleven shared areas. The owner can switch to Locked down, which removes that broad default. Check each person's actual access as well as the preset.

Sources: How zones and permissions work, Understand your Mind's settings, Automate a routine task.

Where content, keys and credentials live

  • Your Mind's content lives on its own server, which runs the content workspace and its Portal, not in Mensara's account system. Who runs that server depends on the hosting arrangement you choose.
  • Mensara's account service manages accounts, billing, Mind identity, selected catalogs and coarse service health. It is designed not to hold customer records, chat history or provider keys as account data.
  • Keys and credentials live on your Mind's server, not in the mensara.ai account system. If Mensara operates the server, that separation is not a promise that the operator cannot access it.
  • Card details go to Stripe, Mensara's payment processor. Mensara never sees or stores card numbers.
  • Portal chat conversations and sign-in sessions are kept in the Portal's own database, outside the Mind's Git repository.

Sources: Decide where your information may go, Privacy, About, Back up, recover and export your Mind.

Recovery Kit

The Recovery Kit holds the separate key material needed to verify and recover your Mind.

  • The owner downloads the current kit from Settings → Recovery kit in the Portal.
  • Store it in an owner-controlled place away from the Mind and its file backup. Do not paste it into a chat, a shared record or a support message.
  • A successful download shows the kit was generated. It does not show that its storage is safe or that a restore works.
  • To rehearse recovery, an authorised operator restores the tracked files on a separate replacement environment, using the Recovery Kit supplied through a secure owner route, then verifies the signed activity history and reconnects outside services.

Source: Back up, recover and export your Mind.

Git files and GitHub backup

  • Your saved records and their version history are ordinary files in a Git repository. Your team can read those files without Mensara.
  • In Settings → Backup, the owner connects a private GitHub repository they control, granting access only to that repository.
  • The Git backup excludes private key material and external connection credentials. It is not a snapshot of every running service: Portal chat conversations and sign-in sessions are not in it.
  • Check the backup's last successful push, not only its connected label. Declining a backup records that choice; it does not protect against losing the server.

Sources: Back up, recover and export your Mind, Connect a backup and inspect recovery readiness.

What Mensara can and cannot access

  • What Mensara's account system keeps: your name and email, sign-in records, billing status, and coarse operational records about your Mind's server: plan, version and health.
  • What it never holds: your Mind's content. Knowledge, chat history, files, keys and credentials live on your Mind's server, not on mensara.ai.
  • Problem reports you email are kept to fix the problem and reply, are not used to train AI models, and are deleted from working files after 12 months; copies in backups and version history can last longer.
  • Sharing: Mensara shares data only with the providers needed to run the service, such as hosting, payments, email delivery and Google Analytics for public pages.
  • Operator access: the separation between your Mind and the account service does not make vendor access technically impossible when the vendor operates the computer hosting the Mind. If Mensara operates your Mind's server, that separation is not a promise that the operator cannot access it. Ask how operator access, incidents and recovery are handled for your hosting arrangement before you place information with special requirements there.

Sources: Privacy, Decide where your information may go.

Which AI providers see what

  • Your people's AI tools: a person's connected tool, such as Claude, ChatGPT, Codex or Cursor, can receive the information that person's account may read and send relevant content to its AI provider. How that provider handles it depends on the provider and the arrangement you use.
  • Installed apps: an app uses its own granted access and the services configured for it. If its job uses a model, authorised content can be sent there. The owner's App model access setting controls which model routes and models apps may use; connecting a personal chat provider does not authorise apps to use it.
  • Your backup: the backup target receives the records and history included in the backup.

Sources: Decide where your information may go, Manage models and service connections, About.

Certifications

Mensara's public pages list no SOC 2 report or HIPAA compliance claim. If your review requires one, ask before you sign up: write to hello@mensara.ai.

Questions

Can a connected agent read records its person cannot?

No. A connected agent works using its person's access, and the Mind checks that access before serving a read. Excluded areas are left out of search and a direct request is refused. A prompt cannot widen it.

Can an agent change an important record without a person?

In governed areas, such as decisions, a member's change is held for the owner or another approver, unless an approver has turned on Automatic approval for that area; it acts only within their own authority and never covers renames, deletions or requests that require a human decision. Deleting or renaming a record always waits. Elsewhere, a permitted change can save after an automatic check, and the owner can require approval there too.

Can Mensara read our Mind?

Your Mind's content lives on its own server, not in Mensara's account system. But if Mensara operates that server, the separation is not a promise that the operator cannot access it. Ask how operator access is handled for your hosting arrangement.

Does the backup include our keys?

No. The Git backup excludes private key material and external connection credentials. The owner keeps the Recovery Kit separately, away from the Mind and its file backup.

Do receipts contain our content?

No. A receipt records who asked, the kind of action, the areas touched and the outcome, with fingerprints of the request and response. It does not store the file path or the text.

Is Mensara SOC 2 or HIPAA compliant?

Mensara's public pages list no SOC 2 report or HIPAA compliance claim.

Can we leave?

Yes. Your saved records and their version history are ordinary files in a Git repository. Copy them and keep them.

Sources

All Mensara pages, checked 18 November 2026:

Related

Practical guides for people and agents

Start with one useful job

Sign up

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is open to people and agents acting with their explicit authorization. Sign up at https://www.mensara.ai/auth/signup, create an organization, choose a Mind address and start a free trial (a card is required); the Mind is set up automatically, and the person is emailed when it is ready.
- Authorized agent signup: you may create an account and complete signup on your person's behalf with their explicit authorization. Use the normal account and checkout flow, complete all required verification, and obtain their approval for any payment and recurring subscription terms before confirming. Hand off any step that requires the person; do not bypass it. Use only payment methods offered at checkout.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and complete authorized signup or share the sign-up link.
- Agent sign-up hand-off: https://www.mensara.ai/agent-signup.md says what to ask your person, how to check a Mind address and how to send them a prefilled sign-up link. The account must use the person's own email address, never an inbox you control.
- Agent references: https://www.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Trust and security at Mensara

Content updated 18 November 2026.

Mensara checks each person's access before any model sees a file, holds changes to governed areas for an approver, keeps a signed, tamper-evident receipt for each read and change, and keeps your records as ordinary files in a Git repository that you can back up to your own GitHub. Its public pages list no SOC 2 report or HIPAA compliance claim, and if Mensara operates the server that holds your Mind, the separation between your Mind and Mensara's account system is not a promise that the operator cannot access it.

Facts checked 18 November 2026 against the pages listed under Sources.

[Page as Markdown](https://www.mensara.ai/trust.md)

## The short answer

| Question | Answer |
| --- | --- |
| Who can read a record? | Each person signs in with their own account. Their agents work within that person's access, checked by software before any model sees a file. |
| Who approves changes? | Changes to governed areas, such as decisions, wait for the owner or another approver. Deleting or renaming a file always waits. |
| What is recorded? | A signed, tamper-evident receipt for each read and change, including refusals. It stores fingerprints, not the file path or the text. |
| Where does our content live? | On your Mind's own server, not in Mensara's account system. Who runs that server depends on the hosting arrangement you choose. |
| Where do keys and credentials live? | On your Mind's server, not in the mensara.ai account system. The owner keeps a Recovery Kit separately. If Mensara operates the server, that separation is not a promise that the operator cannot access it. |
| Can we take our data? | Yes. Saved records and their version history are ordinary files in a Git repository, and you can keep a private copy in your own GitHub. |
| Which AI providers see our content? | The providers behind the agents you connect, and only what those agents read within each person's access. An app or automation you install uses the AI provider set up for it, limited to that app's access. |
| Certifications? | Mensara's public pages list no SOC 2 report or HIPAA compliance claim. |

## How changes are approved

People and their agents propose updates where the work happens. Out of the box, a change saves without a person only when an automatic check passes and both the proposer's trust level and the area's own limit allow it. Read the outcome: an applied proposal has changed the saved record; a held one is waiting and has not; a rejected or refused one has not saved.

- In governed areas (decisions, charter, principles, skills and practice), a member's change is held for the owner or another approver. You can require approval in other areas too.
- Deleting or renaming a record is always held.
- An area can give someone permission to suggest edits without giving them authority to approve.
- Automatic approval is a separate setting a person can turn on for review cards they are already allowed to approve. It gives no extra authority, and it never covers renames, deletions, policy and app code, or requests that explicitly require a human decision.

Sources: [Review changes and check what was saved](https://www.mensara.ai/how-it-works/changes-approvals-receipts), [Understand your Mind's settings](https://www.mensara.ai/how-it-works/mind-settings).

## Signed, tamper-evident receipts

The Mind keeps a signed, tamper-evident receipt for each read and change, including refusals.

- **What a receipt holds:** who asked, the kind of action, which areas it touched and the outcome (allowed, refused or held), plus fingerprints of the request and response.
- **What it does not hold:** the file path or the text.
- **Where to read them:** the owner reads the receipts in the Mind's policy area, `25-policy/audit.jsonl`, with older sealed segments in `25-policy/audit-segments/`.
- **Where to see the wording that changed:** each saved record keeps its earlier versions, and that version history shows the actual wording.

A receipt shows what the Mind did. It does not prove that the original email, meeting note or decision was true.

Source: [Review changes and check what was saved](https://www.mensara.ai/how-it-works/changes-approvals-receipts#understand-the-record-of-a-change).

## Access is checked for each person before any model sees a file

- Every teammate signs in with their own account, and their connected agent works using that person's access. A well-written prompt cannot give it permission to open an excluded area.
- The Mind checks the caller's permissions before serving a read or allowing a change. Search results leave out areas the caller cannot read, and a direct request for an excluded record is refused.
- Reading, suggesting and approving are separate permissions. Being able to read a policy does not by itself let someone replace or approve it.
- An installed app has its own identity and granted access. Approving an automation does not give it all of the owner's access.
- A new Mind starts on the Open team preset, which lets every member read, suggest, subscribe and work on tasks in eleven shared areas. The owner can switch to Locked down, which removes that broad default. Check each person's actual access as well as the preset.

Sources: [How zones and permissions work](https://www.mensara.ai/how-it-works/zones-and-permissions), [Understand your Mind's settings](https://www.mensara.ai/how-it-works/mind-settings#team-access-presets), [Automate a routine task](https://www.mensara.ai/how-it-works/automate-a-task).

## Where content, keys and credentials live

- **Your Mind's content** lives on its own server, which runs the content workspace and its Portal, not in Mensara's account system. Who runs that server depends on the hosting arrangement you choose.
- **Mensara's account service** manages accounts, billing, Mind identity, selected catalogs and coarse service health. It is designed not to hold customer records, chat history or provider keys as account data.
- **Keys and credentials** live on your Mind's server, not in the mensara.ai account system. If Mensara operates the server, that separation is not a promise that the operator cannot access it.
- **Card details** go to Stripe, Mensara's payment processor. Mensara never sees or stores card numbers.
- **Portal chat conversations and sign-in sessions** are kept in the Portal's own database, outside the Mind's Git repository.

Sources: [Decide where your information may go](https://www.mensara.ai/how-it-works/ownership-data-flow), [Privacy](https://www.mensara.ai/privacy), [About](https://www.mensara.ai/about), [Back up, recover and export your Mind](https://www.mensara.ai/how-it-works/backup-restore-ownership).

## Recovery Kit

The Recovery Kit holds the separate key material needed to verify and recover your Mind.

- The owner downloads the current kit from **Settings → Recovery kit** in the Portal.
- Store it in an owner-controlled place away from the Mind and its file backup. Do not paste it into a chat, a shared record or a support message.
- A successful download shows the kit was generated. It does not show that its storage is safe or that a restore works.
- To rehearse recovery, an authorised operator restores the tracked files on a separate replacement environment, using the Recovery Kit supplied through a secure owner route, then verifies the signed activity history and reconnects outside services.

Source: [Back up, recover and export your Mind](https://www.mensara.ai/how-it-works/backup-restore-ownership#keep-the-recovery-kit-separately).

## Git files and GitHub backup

- Your saved records and their version history are ordinary files in a Git repository. Your team can read those files without Mensara.
- In **Settings → Backup**, the owner connects a private GitHub repository they control, granting access only to that repository.
- The Git backup excludes private key material and external connection credentials. It is not a snapshot of every running service: Portal chat conversations and sign-in sessions are not in it.
- Check the backup's last successful push, not only its connected label. Declining a backup records that choice; it does not protect against losing the server.

Sources: [Back up, recover and export your Mind](https://www.mensara.ai/how-it-works/backup-restore-ownership), [Connect a backup and inspect recovery readiness](https://www.mensara.ai/how-it-works/backup-procedure).

## What Mensara can and cannot access

- **What Mensara's account system keeps:** your name and email, sign-in records, billing status, and coarse operational records about your Mind's server: plan, version and health.
- **What it never holds:** your Mind's content. Knowledge, chat history, files, keys and credentials live on your Mind's server, not on mensara.ai.
- **Problem reports** you email are kept to fix the problem and reply, are not used to train AI models, and are deleted from working files after 12 months; copies in backups and version history can last longer.
- **Sharing:** Mensara shares data only with the providers needed to run the service, such as hosting, payments, email delivery and Google Analytics for public pages.
- **Operator access:** the separation between your Mind and the account service does not make vendor access technically impossible when the vendor operates the computer hosting the Mind. If Mensara operates your Mind's server, that separation is not a promise that the operator cannot access it. Ask how operator access, incidents and recovery are handled for your hosting arrangement before you place information with special requirements there.

Sources: [Privacy](https://www.mensara.ai/privacy), [Decide where your information may go](https://www.mensara.ai/how-it-works/ownership-data-flow#distinguish-the-content-and-account-services).

## Which AI providers see what

- **Your people's AI tools:** a person's connected tool, such as Claude, ChatGPT, Codex or Cursor, can receive the information that person's account may read and send relevant content to its AI provider. How that provider handles it depends on the provider and the arrangement you use.
- **Installed apps:** an app uses its own granted access and the services configured for it. If its job uses a model, authorised content can be sent there. The owner's **App model access** setting controls which model routes and models apps may use; connecting a personal chat provider does not authorise apps to use it.
- **Your backup:** the backup target receives the records and history included in the backup.

Sources: [Decide where your information may go](https://www.mensara.ai/how-it-works/ownership-data-flow), [Manage models and service connections](https://www.mensara.ai/how-it-works/model-connections), [About](https://www.mensara.ai/about).

## Certifications

Mensara's public pages list no SOC 2 report or HIPAA compliance claim. If your review requires one, ask before you sign up: write to [hello@mensara.ai](mailto:hello@mensara.ai).

## Questions

### Can a connected agent read records its person cannot?

No. A connected agent works using its person's access, and the Mind checks that access before serving a read. Excluded areas are left out of search and a direct request is refused. A prompt cannot widen it.

### Can an agent change an important record without a person?

In governed areas, such as decisions, a member's change is held for the owner or another approver, unless an approver has turned on Automatic approval for that area; it acts only within their own authority and never covers renames, deletions or requests that require a human decision. Deleting or renaming a record always waits. Elsewhere, a permitted change can save after an automatic check, and the owner can require approval there too.

### Can Mensara read our Mind?

Your Mind's content lives on its own server, not in Mensara's account system. But if Mensara operates that server, the separation is not a promise that the operator cannot access it. Ask how operator access is handled for your hosting arrangement.

### Does the backup include our keys?

No. The Git backup excludes private key material and external connection credentials. The owner keeps the Recovery Kit separately, away from the Mind and its file backup.

### Do receipts contain our content?

No. A receipt records who asked, the kind of action, the areas touched and the outcome, with fingerprints of the request and response. It does not store the file path or the text.

### Is Mensara SOC 2 or HIPAA compliant?

Mensara's public pages list no SOC 2 report or HIPAA compliance claim.

### Can we leave?

Yes. Your saved records and their version history are ordinary files in a Git repository. Copy them and keep them.

## Sources

All Mensara pages, checked 18 November 2026:

- [Review changes and check what was saved](https://www.mensara.ai/how-it-works/changes-approvals-receipts): approvals, outcomes and signed receipts
- [Understand your Mind's settings](https://www.mensara.ai/how-it-works/mind-settings): governed areas, Automatic approval, team access presets, models
- [How zones and permissions work](https://www.mensara.ai/how-it-works/zones-and-permissions): per-person access, refusals, read, suggest and approve
- [Decide where your information may go](https://www.mensara.ai/how-it-works/ownership-data-flow): content and account services, AI providers, operator access
- [Back up, recover and export your Mind](https://www.mensara.ai/how-it-works/backup-restore-ownership): Git files, GitHub backup, Recovery Kit
- [Manage models and service connections](https://www.mensara.ai/how-it-works/model-connections): personal and app model routes
- [Privacy](https://www.mensara.ai/privacy): what Mensara keeps and never holds
- [About](https://www.mensara.ai/about): what's live today

## Related

- [Mensara for solo founders](https://www.mensara.ai/for/solo-founders)
- [Mensara vs Mem0](https://www.mensara.ai/compare/mensara-vs-mem0)
- [About](https://www.mensara.ai/about)
- [How Mensara works](https://www.mensara.ai/how-it-works)

[Sign up](https://www.mensara.ai/auth/signup)