How Orbnex Connect handles information.

Orbnex Connect collects information needed to create secure customer access, operate connectivity and power-planning workspaces, process subscriptions, support CRM integrations, and protect the platform.

Information we collect

Account and contact details, such as name, company, work email, and phone number.
Workspace details, such as cross-connect records, circuit IDs, provider notes, facilities, cabinets, ports, renewal dates, and import files.
Power planning details, such as RPP, panel, breaker, feed, capacity, assignment, oversubscription, and approval notes.
CRM, webhook, import, and API metadata needed to map fields, test connections, sync records, and troubleshoot integrations.
Payment and subscription events processed through Stripe. Orbnex Connect does not store full card numbers.
Security, device, browser, request, and support logs used to protect accounts and diagnose issues.

How we use information

To create accounts, authenticate users, and enforce subscription access.
To operate dashboards for cross-connects, power planning, migrations, imports, exports, and CRM field mapping.
To run authorized CRM, ticketing, DCIM, API, CSV, and webhook workflows selected by the customer.
To provide customer support, audit visibility, security monitoring, product reliability, and platform improvement.

Service providers

Orbnex Connect may use trusted providers for hosting, authentication, database services, payments, analytics, email, security, and customer-selected CRM integrations. These providers only receive information needed to perform their services or complete authorized workflows.

Security notes

Customers should keep API tokens, webhook secrets, CRM credentials, and exported spreadsheets secure. Secrets should be stored only in the platform's configured secret storage or the customer's approved systems, not in shared spreadsheets or public notes.

Contact

For privacy questions, contact [email protected].