Tenant scope
Customer records, workflows, evidence, connections, and product access remain tenant-bound.
Trust Center
Evidence and boundaries before procurement claims.
OpenOS publishes the current security, privacy, responsible AI, data, provider, and shared-responsibility position for evaluation.
Policies are not presented as certifications. Provider and deployment readiness remain subject to scope, configuration, contract, and acceptance.
Product controls
Trust is expressed in operating state.
The buyer should be able to inspect who has access, what was released, which connection is healthy, what evidence supports an action, and where responsibility remains external.
Role access
Product surfaces and operational actions are bounded by authorized user roles and entitlements.
Release state
Draft, validation, publication, binding, and execution are separate workflow states.
Secret references
Provider and tool credentials are not embedded as plaintext workflow content.
Open document
Security overview
Architecture, access, tenant boundaries, and shared responsibility
Review →Open documentPrivacy policy
Personal information collection, use, protection, and retention
Review →Open documentResponsible AI policy
Human responsibility, evidence, boundaries, and AI use
Review →Open documentData retention and deletion
Lifecycle, retention, deletion, and customer responsibilities
Review →Open documentData processing addendum
Data-processing roles and contractual terms
Review →Open documentSubprocessors
Service providers involved in OpenOS delivery
Review →Open documentVulnerability disclosure
How to report a potential security issue
Review →Open documentTerms of service
Terms governing use of OpenOS services
Review →Shared responsibility
Connection trust is deployment-specific.
OpenOS can supply the intelligence and governance layer only when customer and provider responsibilities are explicit.
- 01Customer
Owns provider contracts, credentials, consent, policy, users, source-system permissions, and acceptance.
- 02Provider
Owns the service it delivers, including channel-specific availability, media, retries, and platform obligations.
- 03OpenOS
Owns the configured evidence, governance, exception, and Decision Card behavior inside its documented boundary.
- 04Joint review
Defines data scope, health, failure behavior, retention, approval, and production acceptance.
Tailored walkthrough
Bring security and architecture into the first walkthrough.
We will explain tenant scope, provider ownership, credentials, evidence, and the acceptance boundary for the workflow under evaluation.
- 01Your current loopChannels, systems, volume, and the operational gap.
- 02The product proofResolve, escalate, audit, and decide in one scenario.
- 03A scoped first deploymentOne workflow with explicit evidence and success measures.
Prefer email? sales@openost.com