Trust & security

Straight answers, before you have to ask twice.

A security or procurement team should be able to ask “how does this work, and how is our data protected?” and get a plain written answer—not a sales deck. That is the standard this page holds itself to.

Isolation

Your data stays yours—and stays separate.

Each customer’s data is isolated from every other customer’s. Nothing about how one portfolio’s policies, numbers, or conversations are structured, stored, or served ever touches another portfolio’s. Isolation isn’t a setting someone can switch off—it is how the system is built.

Ownership

Full export, standard formats. Stay or go.

Everything you put into Opsurant—your policies, your procedures, your portfolio’s own history in the product—is yours. If you ever decide to leave, you leave with a complete export in standard, usable formats: no proprietary lock-in, no file only we can open.

This is concrete from day one, not a promise deferred to some future off-boarding process. The Knowledge Foundation engagement builds a structured operations library with you early on, and that library is yours to keep regardless of what you decide about the subscription afterward.

What we don’t do

Three lines we don’t cross.

TRAINING

We don’t train public models on your data

Your policies, your numbers, and your conversations don’t become training data for a general-purpose AI model that any other account could benefit from. What you put in stays scoped to you.

SELLING

We don’t sell your data

Not to advertisers, not to data brokers, not to anyone. Your information isn’t a product we monetize separately from the service you’re paying for.

ACCESS

We don’t go looking around

Access to customer data is limited to what running and supporting the service actually requires—not open browsing. If we ever need to look at something specific to help you, it’s for a real support reason, not curiosity.

Honest AI

It cites its sources—and admits what it doesn’t know.

Every answer Opsurant gives from your knowledge library points back to the document and section it came from, so you can verify it yourself in seconds. It doesn’t summarize from memory or blend sources into something unattributable.

And when the assistant doesn’t have the data to answer a question—a feed that isn’t connected yet, information nobody has given it—it says so plainly instead of guessing. That isn’t a feature bullet; it is the whole trust model.

Certifications

No certifications yet—we won’t pretend otherwise.

We’re an early-stage company. We don’t hold formal security certifications today, and we won’t tell you we do. What we will do is put a straight written answer to your specific questions in front of your security team—how data is isolated, how access is controlled, how backups and incident response work—so you can make an informed call instead of taking a badge on faith.

Procurement

Bring your questionnaire.

If your process runs on a standard security questionnaire, send it—we’ll answer it directly, in writing. Start that conversation →

Early access

Kick the tires. Then bring us your portfolio.

We’re onboarding early-access partners now—PMCs who want a real say in what gets built next. Bring your unit count and your worst operational headache.