Your data answers
your prompts. Nothing else.
Three promises sit underneath every conversation that runs on OurAI — written into the architecture, the contracts, and the routes between them.
Not by us, and not by the model providers we route to. Every frontier provider is connected through their enterprise API under zero-retention, no-training terms — not the consumer endpoint.
TLS 1.3 in transit, AES-256 at rest, per-tenant encryption keys. Tenant boundaries are enforced at every layer — storage, runtime, and the operational boundary around them.
Every data type has a stated retention period, honoured by default. Request deletion at the user, workspace, or tenant level — and it happens.
By contract, not by hope.
Training on customer data is the easiest promise to make and the hardest to verify. Here is exactly what stops your prompts from ending up in someone's next training run — at every point in the stack where that risk exists.
We do not train models on customer prompts, responses, files, or embeddings — not for general improvement, not for fine-tuning, not for evaluation. The DPA spells this out.
When a workspace uses a third-party frontier model, the call goes through the provider's enterprise API under their zero-retention, no-training terms — not the consumer endpoint.
Open-weight models are stateless by construction. The weights don't change between requests, there is no learning loop, and one tenant's prompts cannot influence another tenant's answers.
The no-training and zero-retention obligations are written into our standard Data Processing Agreement.
Read the DPAIn motion, at rest, between tenants.
When you use OurAI on our managed infrastructure, your data is encrypted at every step and isolated from every other tenant — including from our own engineers.
Every connection uses TLS 1.3 in transit. Data at rest is encrypted with AES-256. Backups and exports follow the same standard — no unencrypted copies, anywhere.
- —TLS 1.3 for every connection
- —AES-256 at rest
- —Backups and exports encrypted by default
Tenant boundaries are enforced at every layer — storage and runtime. No data from one tenant can ever reach another, and no engineer can read your prompts or responses.
- —Tenant isolation at storage and runtime
- —No cross-tenant data access
- —Backups are tenant-isolated and never co-mingled
On request. On schedule.
Your data is yours to delete — at any level, at any time. Submit a deletion request and we'll action it within a stated window. Nothing is retained beyond what you've agreed to.
Delete individual conversations on demand — the full transcript, every prompt and response, and the associated audit entry. Removed completely, not archived.
Delete all data within a workspace in one request — conversations, shared prompts, configurations, and the workspace audit log. Useful when a team winds down or a project closes.
Full account deletion — every conversation across every workspace, every audit entry, every configuration. Nothing is retained after the deletion window closes. The account cannot be recovered.
Promises kept, in writing.
Sign up & start in minutes, or book a demo to see if OurAI is the right fit.