← Back to Candar

Security & Compliance

Candar is built for government and enterprise clients. We take data security seriously and maintain rigorous compliance standards.

🔒

SOC 2 Type II

In Progress

🛡

HSTS Preload

Active

🔐

TLS 1.3

Active

💾

AES-256

Active

Data Protection

No PII Collection

Candar does not collect, store, or process personally identifiable information. License plate numbers, driver names, and other PII are stripped at the point of data ingestion. Only public-record citation data is retained.

Encryption at Rest

All data is encrypted at rest using AES-256 encryption via our infrastructure provider (Supabase/AWS). Database backups are encrypted using the same standard.

Encryption in Transit

All data in transit is protected by TLS 1.3. HSTS is enabled with preload, ensuring browsers always connect via HTTPS. Certificate transparency logging is active.

Data Isolation

Multi-tenant data is isolated using PostgreSQL Row-Level Security (RLS). Each organization can only access data for their assigned cities. RLS policies are enforced at the database level, not application level.

Authentication & Access Control

SAML SSO

Enterprise clients can configure SAML 2.0 Single Sign-On with their identity provider (Azure AD, Okta, Google Workspace, OneLogin). Users are auto-provisioned on first login.

Multi-Factor Authentication

TOTP-based multi-factor authentication is available for all users. Organizations can enforce MFA as a policy requirement for all members.

Role-Based Access Control

Three roles (Owner, Admin, Viewer) with granular permissions. API access and data export are controlled by organizational role and plan tier.

Session Management

Sessions expire after 30 minutes of inactivity. All sessions are logged with IP address and user agent for audit purposes.

Audit & Compliance

Comprehensive Audit Logging

All user actions, data access, API calls, and administrative changes are logged with timestamp, user identity, IP address, and action details. Audit logs are retained for 2 years.

Audit Log Export

Organization administrators can export audit logs in CSV or JSON format for compliance review, incident investigation, or regulatory requirements.

FOIA-Ready Data Export

Self-service data export allows authorized users to extract citation data in CSV or JSON format for public records requests. Exports contain only public-record fields and are audit-logged.

Data Retention

Citation data is retained for the duration of the contract plus 1 year. Audit logs are retained for 2 years. AI conversation logs are retained for 90 days. All retention periods are configurable per-client to meet local records retention requirements.

Infrastructure

US Data Residency

All data is processed and stored within the United States. Our primary database is hosted in AWS US regions. Serverless functions are restricted to US data centers.

Uptime SLA

We target 99.9% uptime with defined severity-level response times. Severity 1 (system down): 1-hour response. Severity 2: 4-hour response. Severity 3: 1 business day. Scheduled maintenance is communicated 72 hours in advance.

Backup & Recovery

Automated daily database backups with 7-day retention. Point-in-time recovery available. Recovery Point Objective (RPO): 24 hours. Recovery Time Objective (RTO): 4 hours.

Sub-Processors

ProviderPurposeLocationCertification
SupabaseDatabase & AuthUSSOC 2 Type II
VercelApplication HostingUSSOC 2 Type II
AnthropicAI Analysis (Claude)USSOC 2 Type II
UpstashRedis CacheUSSOC 2 Type II
ResendEmail DeliveryUSSOC 2 Type II

Legal Documents

Security Questions?

For security inquiries, vulnerability reports, or compliance documentation requests, contact us at security@candar.city. We respond to all security inquiries within 1 business day.