Data use
Customer content is not used to train shared models. The selected model runs locally and is stateless between requests.
Security
A privacy boundary your team can inspect.
OwnMind is designed so inference and configured application storage run in the designated deployment. The evaluation pilot is transparent about the services used to reach that deployment.
Evaluation data path
- 01
Identity-gated access
Named users sign in through Cloudflare Access. The application independently validates the signed identity assertion and a local invite list.
- 02
Encrypted remote connection
Cloudflare Tunnel creates an outbound connection from the evaluation host. No application, database, model, or SSH port is opened publicly.
- 03
Local inference and storage
The model and approved knowledge index run on the designated OwnMind-managed pilot host. Temporary conversations are processed there without saving chat history.
Cloudflare terminates browser TLS for the remote pilot and is therefore a disclosed network and identity provider. The pilot is encrypted in transit, but it is not described as zero-knowledge or browser-to-host end-to-end encryption.
Controls in V1
Approved company knowledge
Optional Company Mind uploads require an administrator and explicit confirmation. These documents are persistent and shared within the workspace. Personal long-term memory is not available in this pilot.
Retention
Temporary chats and request-scoped attachments are not persisted. Approved company documents remain until removed by an administrator or operator. Backup retention and pilot close-out must be agreed and verified with the operator; automated backups are not yet validated on the current evaluation host.
Application limits
V1 supports bounded temporary attachments and optional administrator Company Mind uploads. It has no web browsing, email, code execution, shell access, external tools, or autonomous actions.
Operational access
Authorized OwnMind operators can administer the pilot host. The pilot is not a zero-knowledge service, and no claim of “no human access” is made.
Production deployment
Confidential production use begins only after a customer-controlled deployment, customer-approved backup policy, legal terms, and security review.
Security contact
Questions deserve a direct answer.
Request the current pilot data-flow, retention, and threat-model documentation before enrolling.
Ask through the request form