Security Overview

1. Access and Authentication

• Dashboard access is authenticated via Clerk-backed identity.
• Project-scoped endpoints require authenticated ownership checks.
• SDK ingestion requires project API keys and validates per-project usage limits.

2. Transport Security

Service endpoints are served over HTTPS to protect data in transit between SDKs, browsers, and backend services.

3. Abuse and Reliability Controls

• Rate limiting is applied on ingest and dashboard routes.
• Billing and entitlement checks are enforced on event ingestion.
• Operational events are audited for key security and billing actions.

4. Data Handling

Olvex processes telemetry payloads (sessions, custom events, crash diagnostics) and account metadata needed to operate the service. Customers control what telemetry fields are sent from the SDK.

5. Incident Communication

Security reports can be sent to security@olvex.dev. For customer-impacting incidents, status and follow-up communication are provided through support and customer channels.