HyperBridge Platformhyperbridge.digital β†—
QuantumOS
Book a demo
Security

Security is a platform capability, not an Enterprise tier

Row-level tenant isolation, encrypted secret and backup storage, and signed webhooks are built into the platform core rather than sold as add-ons. This page states each control and its limits, including what we do not hold: there is no SOC 2 report or ISO certificate.

No attestation
We hold no SOC 2 report or ISO certificate

No third-party attestation has been completed for QuantumOS X3, and we will not imply otherwise. If your procurement process requires an auditor's report rather than a controls walkthrough, we do not clear that bar today β€” better you learn it here than three weeks into a security review.

PCI Β· out of scope
Card data stays outside the platform

Payment fields are rendered by the payment processor, not by our storefront, and the storefront works with payment identifiers rather than card details. That is scope reduction: it shrinks what you have to evidence in your own PCI questionnaire. Which questionnaire applies to you is still your acquirer’s determination, and this is not a certification we hold.

Processors
Card compliance sits with your payment provider

Card processing runs through the payment provider you connect, such as Razorpay, Paytm or Stripe. Each provider publishes its own PCI compliance status, so check theirs. That is their certification, covering their infrastructure; we do not inherit it, and neither do you.

GDPR Β· CCPA Β· DPDP
Data protection obligations

GDPR and CCPA carry no certification body β€” compliance is a posture, not a badge, and no vendor can hand you one. Ours rests on the Data Processing Agreement published on this site for every tier, and on the controls listed below, which you are welcome to test rather than take on trust.

Platform controls

Security controls built into the platform core β€” not layered on top.

Tenant isolation β€” two layers, one of them opt-in

Row-Level Security policies are defined across the shared database, and dedicated-database tenants are isolated at the instance level. On shared infrastructure the restricted database role is a feature flag that is not on by default, so the enforcement doing the work today is the tenant predicate applied in the application layer, backed by a CI detector that fails the build on new unscoped queries. We would rather describe that accurately than call it impossible.

Encrypted secret storage

Infrastructure secrets β€” database URLs, object-storage keys, OAuth tokens β€” are stored encrypted with AES-256-GCM rather than as plaintext configuration, and are separated from customer-visible settings. Rotation is currently an operator procedure, not an automated one.

Data residency is arranged per deployment

Where a business's data is held can be set when its deployment is arranged, and Enterprise plans list it in the contract. It is not a self-service switch, so tell us about residency requirements before you sign.

Signed webhooks with a delivery log

Webhook deliveries are signed with HMAC-SHA256 so your server can verify them, and each attempt is logged with its status and response. A delivery is tried three times with a growing delay, and one that still fails goes to a dead-letter list that is retried after ten minutes. There is no one-click replay of old events and no secret-rotation overlap yet.

Encrypted tenant backups

Each business's backup is encrypted with its own key, so removing that key makes the backup unreadable, and point-in-time snapshots of a business's database can be restored from the admin. Audit logs follow a PII-redaction policy. This is a set of controls to discuss with your security reviewer, not a certification.

DSR handling β€” tracked, partly manual

Erasure, portability and restriction requests are recorded and worked through tooling in the admin console. Fulfilment is not yet fully automated: a person completes the export and closes the request. If you need a self-serve data-subject portal that cascades erasure without human involvement, we do not have one.

Append-only audit ledgers β€” where they are wired

Media production and legal-control events write to hash-chained, append-only ledgers enforced by database triggers, with tests that prove an UPDATE or DELETE fails. That guarantee covers those subsystems; it does not yet cover every admin action, and permission changes and API-key issuance are not among the events written today. We list what is chained rather than implying all of it is.

Sub-processors

There is no public sub-processor list yet. If your review needs one, ask through the security questionnaire request below and we will tell you which providers handle your data for the deployment you are considering. The published Data Processing Addendum sets out the terms.

Read the Data Processing Addendum β†’