01 / YOUR INSTANCE
A boundary for your work.
Free and Pro use dedicated Akasha instances. Workspace access, individual agent permissions, and the services running inside that instance still need their own configuration.
Minds / Trust center
Trust comes
from the details.
Your AI’s memory deserves a careful review. Here is the architecture, the paperwork, and the operating context to make one.
A dedicated Mind.
A clear responsibility.
Isolation matters. So do the systems around it. Review the full path from a person or agent to stored knowledge and any connected provider.
02 / YOUR CONTEXT
Know where it travels.
Helm, tools, models, and platform operations can involve systems outside your instance. Map those processing paths before sending information with special restrictions.
03 / YOUR AGREEMENT
Put requirements in writing.
Region, retention, recovery, provider restrictions, and service-level commitments belong in the agreement for your deployment. A product illustration is not a signed commitment.
The review folio.
A focused collection for your security, privacy, procurement, and engineering teams.
01
Security architecture
How transport, agent permissions, and storage protection fit together—and what to verify in your deployment.
02Privacy notice
Account information, customer content, Helm context, analytics, retention, and your privacy choices.
03Data processing
Scope the responsibilities, controls, providers, and transfer terms for a signed agreement.
04Service providers
Understand delivery infrastructure, platform services, and the models or tools you connect.
05Terms of service
The agreement covering use, customer data, payment, responsibilities, and service commitments.
06Current service checks
Public availability observations with individual timestamps, endpoint details, and explicit scope.
Independent assurance
Evidence before
assumptions.
Minds has not published a SOC 2 report, ISO 27001 certificate, HIPAA attestation, or independent penetration-test summary. We do not represent an engine feature or a vendor’s certification as certification of Minds.
If your organization requires a particular report, agreement, or control, request it before choosing a deployment. Contact legal@minds.sh for a review or security@minds.sh for a security question.
A direct line.
Minds, Inc.
2701 North Central Expy.
Richardson, TX
Privacy
Rights requests, personal information, and processing questions.
privacy@minds.sh ↗Security
Private vulnerability reports and security concerns. Do not include credentials.
security@minds.sh ↗Agreements
Data processing, procurement requirements, and contractual notices.
legal@minds.sh ↗