Operational resilience without invented guarantees.

1. Resilience objective

Civerent is designed to preserve access to organization-scoped governance records and restore essential service functions after a disruption. Response priorities are protecting people and information, containing impact, restoring safe service, communicating material effects, and recording follow-up actions.

Resilience depends on Civerent controls, operating capacity, customer configuration, and the availability and recovery capabilities of core service providers.

2. Continuity and recovery process

• Identify the affected service, provider, customer scope, data-integrity risk, and security implications.
• Contain unsafe activity and restrict affected functions when needed to protect customers or evidence integrity.
• Prioritize authentication, organization access, governed records, evidence, billing administration, and support communications according to impact.
• Validate service and data behavior before declaring recovery.
• Document material findings, corrective actions, and required customer or public communication.

3. Core dependencies

Civerent relies on Netlify for application delivery and execution, Supabase for database and authentication services, Stripe for hosted billing functions, and Resend for business communications. A provider interruption can affect the Civerent capabilities that depend on it.

Civerent does not represent provider availability as Civerent-controlled uptime. Provider-specific commitments remain governed by that provider's terms and the Civerent agreement applicable to the customer.

4. Backups and data recovery

Managed infrastructure may provide backup, replication, and recovery capabilities, but this public page does not promise a specific backup frequency, retention period, point-in-time recovery window, restoration method, or customer recovery outcome.

Customers should retain exports or independent records needed for their own continuity obligations. Contract-specific backup, recovery, residency, and retention requirements must be reviewed before a regulated or mission-critical deployment.

5. Recovery objectives and testing

Civerent does not currently publish contractual recovery-time objectives, recovery-point objectives, historical restoration-test results, or guaranteed uptime. Publishing unverified targets would not create reliable resilience.

Recovery objectives, test evidence, notification deadlines, and remedies may be defined in a signed enterprise agreement after the architecture, service scope, and operating capacity have been evaluated.

6. Incident communications

Civerent may use the public Service Status page, direct customer email, in-product communication, or designated enterprise contacts for confirmed material disruptions. The channel and timing depend on severity, affected customers, legal obligations, and signed agreements.