Managed-service boundary
European hosting, documented isolation, encryption in transit and at rest, scoped connector identities, backups and deployment-specific recovery commitments.
TRUST CENTER
Security and control around the action—not only the login.
Customer systems remain authoritative. SupraOS operates within approved sources, scoped credentials, customer-set authority and independent destination verification.
Security architecture
Certified infrastructure
SupraOS uses HYLMAN’s ISO/IEC 27001:2022-certified information-security infrastructure and management system for the managed-service boundary.
Read-only first
Discovery can begin without write authority. Source, object and field scope is approved before access begins.
Data handling and isolation
Customer systems stay authoritative
CRM, product, support, contract, finance, identity and work systems remain the sources of record.
Scoped retained state
SupraOS retains only the approved operating state, evidence references, authority events, execution metadata and proof required for the deployment.
Retention and deletion
Retention, export, deletion and portability follow customer instructions and the contractual deployment boundary.
Model and provider use
Approved providers only
Enabled model providers and deployment-specific processors are disclosed before customer data is sent.
No shared customer-data training
Customer data is not used to train a model shared across customers.
Models do not create authority
Models can reason and propose. Customer rules, eligible roles and named approval determine what may run.
Action authority and verification
Intent Lock
The move is bound to current state, actor, payload, destination, limits, expiry and required readback. Material drift requires a rebuilt decision.
Independent readback
A connected-system change is verified only after SupraOS rereads the designated destination separately from the executor.
Recoverable execution
Safe retries, duplicate prevention, held states, repair and compensation keep partial execution from disappearing into a workflow status.
Diligence documents
Security review
Architecture, data flows, isolation, connector scope, execution controls, incident process and deployment commitments.
Contractual controls
DPA, security schedule, processor disclosures, retention, deletion and customer-specific authority boundaries.
Direct contact
security@supraos.co for security and disclosure; legal@supraos.co for legal review.
COMMERCIAL PROOF
How does SupraOS prove the commercial result?
SupraOS rereads the designated destination separately from the executor, then keeps customer, Finance or other agreed confirmation conditions open until the designated source closes them. The retained Transition Receipt links the decision, authority, action, observed state and confirmation.