Security & trust

How your data is isolated, and what we will and won't claim.

Orbnex Connect holds your circuit inventory, your costs, and your provider paperwork. This page describes the controls that are actually implemented today, in plain language, and is explicit about the assurances we are not in a position to make yet. If a control is not listed here, assume we do not have it.

Tenant isolation

Isolation is the control that matters most in a shared environment, so it is enforced in more than one place and tested on every change.

The workspace is derived server-side Your identity comes from the authenticated session token, and the active workspace is resolved from your own memberships on the server. A browser cannot select a workspace by supplying an ID in a request — the value is never trusted from the client. Implemented
PostgreSQL row-level security underneath Connect's tenant tables have row-level security enabled, so the database independently refuses rows outside your workspace even if an application-layer check were bypassed. Two layers, not one. Implemented
Cross-tenant tests and a static gate in CI A cross-tenant negative test suite and an isolation precheck run on every pull request. The precheck fails the build if any tenant-table query is not workspace-scoped, so an unscoped query cannot reach production by review oversight alone. Implemented
Role-gated writes and fail-closed entitlements Write access is checked on the server by workspace role — a viewer cannot write. Plan limits are enforced server-side and fall back to the most restrictive tier when a plan is missing or unrecognised, so no workspace gains paid capability by ambiguity. Implemented
Dedicated environments do not share An Enterprise dedicated deployment uses its own hostname, its own Cloudflare project, and its own database. It is configured to never silently fall back to the shared environment. Available on Enterprise

Application and platform controls

Authentication Accounts authenticate through Supabase Auth. Access to a workspace additionally requires active membership and an active or trialing subscription. Login, signup, password-reset, account-creation and data-write endpoints are rate limited. Implemented
Append-only audit trail Record changes, migrations, membership changes, billing events and integration events are written to a workspace-scoped audit log, each carrying an actor and a timestamp. Audit history is exportable to CSV. Implemented
Payments are Stripe-hosted Checkout and subscription management run on Stripe. Card data never reaches our servers and we do not store it. Stripe webhooks are signature-verified, and outbound integration webhooks are HMAC-signed and blocked from targeting private network addresses. Implemented
Transport security and browser hardening The site is served over HTTPS with HSTS, a Content-Security-Policy, X-Frame-Options: DENY, X-Content-Type-Options: nosniff, a referrer policy and a restrictive permissions policy, applied site-wide. Implemented
Secret handling and dependencies Service keys and webhook secrets live only in the hosting platform's secret store. A commit guard runs in CI to block committed secrets, dependency updates are automated weekly, and the Node runtime is pinned. Implemented
The public import sandbox is inert The sandbox on the marketing site parses your spreadsheet entirely in the browser. It makes no API or database call and persists nothing, so it cannot read or affect any customer workspace. Nothing you drop into it is uploaded. Implemented

Your data, and getting it back

Export whenever you want Every view exports to CSV from the portal, covering circuits, documents metadata, power records and audit history. Circuit views page at 500 records at a time; for a complete historical extract of a large estate, email us and we will run it for you. Implemented
Cancel without contacting us Billing is monthly and you can cancel from the Stripe billing portal yourself. There is no annual commitment on the self-serve plans. Implemented
Retention and deletion We retain workspace, document, audit and billing records while your subscription is active and as needed to run the service and meet legal, security and billing obligations. You can request deletion of your workspace data by emailing us, subject to records we are required to keep. The full description is in the privacy policy. On request

What we do not claim

Enterprise buyers are better served by an accurate list than an impressive one. As of the date below, Orbnex Connect does not have the following, and you should not treat them as in place:

No SOC 2, ISO 27001, PCI or HIPAA certification. We hold no third-party security certification or audit report, and we are not a HIPAA business associate. Stripe handles card data on certified infrastructure, but that is Stripe's compliance, not ours.
No contractual uptime SLA or formal support SLA on the self-serve plans. Support commitments for an Enterprise agreement are scoped in that agreement.
No published incident-response or business-continuity programme. We will notify affected customers of a security incident, but there is no documented, tested plan to point you at yet.
No independent attestation of encryption-at-rest or backup and recovery. These are properties of our hosting providers rather than controls we implement, so we describe them only in a security questionnaire where we can name the provider and its terms — not as a marketing claim here.
No single sign-on (SAML/OIDC) in the product today. SSO appears in Enterprise scoping conversations, but it is not implemented and should not be assumed. Ask us for the current status before it becomes a requirement.
No live CRM synchronisation. CRM integration stores configuration only; there is no two-way sync. Link records to your systems with the external-reference field instead.
No penetration-test report. We run automated cross-tenant and isolation testing in CI, which is not the same thing as an independent penetration test.

Security contact

We would rather answer a hard question early than lose your trust later. Security questionnaires, architecture reviews, and vulnerability reports all go to the same place, and we aim to acknowledge reports within three business days.

Contact: info@orbnexlabs.com
Company: ORBNEX LLC

Last reviewed 29 July 2026 · Orbnex Connect v1