Security

Cephron is an authenticated operational platform. Public legal and compliance pages are separate from the authenticated console used by organizations and their authorized users.

This page summarizes the active security posture of the live Cephron platform in restrained terms intended for external review. It focuses on the controls that are actually represented in the current runtime.

Access to system data is restricted through authenticated sessions, role-based application logic, and database-level enforcement mechanisms.

• Authenticated users access the console through Supabase-backed sessions.
• Application routing, landing pages, and page access are role-based.
• Sessions are linked to store context, and active session state also carries organization context where available.
• Operational SMS consent pages are public only for the intended tokenized workflow and do not expose authenticated console data.
• Organizations are responsible for provisioning and removing their own authorized users.

All application data is logically isolated by store and organization boundaries using row-level security policies enforced at the database layer.

• Operational records are associated with stores, and stores can be associated with organizations.
• The active security boundary for most operational data remains store scope.
• Public SMS consent records and delivery logs are tied back to store-scoped contact records.
• Public legal pages are intentionally separate from authenticated workflow records.

• Cephron uses row-level security in Supabase/Postgres for exposed operational tables.
• Store scope is part of the database access model for operational records.
• Authenticated clients use publishable browser credentials, while privileged database operations remain server-side.
• Privileged SMS and administrative actions are not performed directly from the public browser client.

SMS delivery is performed through secure third-party infrastructure providers. Cephron does not expose messaging infrastructure directly to end users.

Consent is required prior to any SMS being sent. Contacts begin in a pending state and are not eligible to receive messages until explicit opt-in is completed.

• Transport encryption is used for communication between browsers, servers, and infrastructure providers.
• Twilio handles SMS transport and delivery-status callbacks for operational messages.
• Public opt-in and opt-out pages are tokenized and limited to a specific consent action.
• Messaging records are written back to Cephron for auditability and operational troubleshooting.

Mobile phone numbers and SMS consent data are used solely for delivering operational messages.

Cephron does not sell, rent, or share mobile numbers or SMS consent with third parties or affiliates for marketing or promotional purposes.

• Privileged secrets such as service-role and SMS provider credentials are kept in server-side environment configuration.
• Administrative access is limited to support, maintenance, incident response, and controlled operational tasks.
• Cephron does not rely on client-side storage of privileged credentials.
• Administrative review is intended to support service operation, incident response, and compliance review rather than unrelated monitoring.

• Workflow activity is recorded through operational event history.
• SMS consent changes and message delivery events are logged for auditability.
• Application error telemetry can be routed to Sentry when the active environment is configured for it.
• Infrastructure providers support storage protections at rest.
• These records support troubleshooting, incident review, and reviewer verification of the consent workflow.

Cephron relies on secure third-party infrastructure and service providers to operate the platform, including database/authentication services, application hosting, SMS delivery, and error monitoring.

Current service-provider disclosures are limited to the providers materially involved in operating the live platform and are listed on a dedicated public page.

Current provider disclosures are listed on the subprocessors page.

• Investigate, contain, and resolve security or operational incidents.
• Review relevant workflow, consent, message, and system telemetry as part of incident handling.
• Notify affected organizations when Cephron determines notice is appropriate under the circumstances.

contact@cephron.com

Cephron LLC