Skip to content
O ONCORR

Colour theme

Text size

Contrast

Request a quote

Trust centre

Security, privacy and reliability at ONCORR

How we protect event and attendee data, who helps us run the service, where data is stored, and how to reach our security team. We only state what is true today.

Service status

All systems operational

Live state of every part of the service, planned maintenance and incident history.

Status page Service levels

Certifications

  • SOC 2 Type II: in progress — readiness assessment done, audit not yet performed. No report is available yet.
  • 21 CFR Part 11 / EU Annex 11: ONCORR provides the technical controls (electronic signatures with re-authentication, tamper-evident audit trail, access reviews) and a validation pack. Compliance is reached together with each client's own validation and procedures — it is not a certificate.
  • Independent penetration test: planned before go-live; not performed yet.
  • Accessibility: an accessibility conformance report (WCAG 2.2) is available on request.

How we protect data

Encryption

HTTPS for every page. Secrets such as provider keys and two-step secrets are encrypted in the database.

Accounts and sign-in

Hashed passwords, lockout after repeated failures, two-step verification for every portal, single sign-on for enterprise clients.

Least privilege

Organizers, agencies and participants see only their own events and registrations. Staff rights have three levels. Access is reviewed every quarter.

Audit trail

Every change is recorded with who, when and what changed. The journal is append-only and hash-chained, so changes to it are detectable.

Card data

Card numbers never touch ONCORR: payments use the provider's hosted fields. Only the card type and last four digits are kept.

Privacy

Data requests (access, erasure), consent records, retention policies and versioned privacy notices.

Sub-processors

Outside services that may process data for ONCORR. Each one is used only when it is switched on for this installation; most are optional and chosen per client.

Sub-processors
PurposeProvider(s)On this installation
Hosting and database To be confirmed by the owner before go-live —
E-mail delivery SMTP provider chosen by the owner (e.g. Postmark, Amazon SES, SendGrid, Microsoft 365) In use
Text messages Twilio, Vonage Not in use
WhatsApp Meta (WhatsApp Cloud API), Twilio Not in use
Card payments Stripe, Authorize.net Not in use
AI writing and assistant Google (Gemini), Anthropic (Claude) Not in use
Flight status FlightAware, Cirium, OAG Not in use
Wallet passes and push Apple, Google Not in use
Video meetings Zoom, Microsoft Teams Not in use
Entry requirements Sherpa Not in use
Client-enabled connectors Salesforce, HubSpot, Veeva Vault, SAP Concur, Zapier, Make Not in use

Where data is stored

United States

Running today. All client data is stored here.

European Union

Prepared as a separate installation for clients who require it; not running yet.

Each region is a separate installation with its own database. Personal data is not copied between regions.

Report a security issue

If you believe you found a vulnerability, please tell us at security@oncorr.com. Give us reasonable time to fix it before you share it; do not access or change data that is not yours, and do not run denial-of-service tests. We will reply within five business days. Machine-readable contact: security.txt.