Data Handling

Data Categories

• Account data: identity and authentication-related profile data.
• Service usage data: interaction and feature usage needed to operate and improve services.
• Operational telemetry: logs and monitoring data for reliability and security operations.

Data is stored using a Hybrid Entity Pattern, combining high-performance rigid columns for identity with flexible, schema-validated JSONB metadata for service attributes.

For legal policy terms and regional rights language, see the Privacy Policy.

Storage and Protection

• Data is stored in managed infrastructure with environment-scoped controls.
• Secrets are handled through encrypted secret management workflows.
• Automated Differential Auditing provides a granular, space-efficient history of all data changes without compromising system performance.
• Production and test email paths are separated; test mail tooling is not intended for public exposure.

Retention and Deletion

• Data is retained for service operation, legal obligations, and operational safety requirements.
• Customers can request account and personal data deletion through our privacy channel.
• Operational logs are retained according to internal retention controls and policy requirements.

To submit deletion or access requests, contact [email protected].

Data Processing Boundaries

• Access to customer data is limited to authorized operational and support contexts.
• Customer data is processed for service delivery, support, and security operations.
• Virtual Flattening via non-materialized views allows for secure, role-based reporting and analytics without exposing raw sensitive blobs.
• We do not publish sensitive implementation details in public documentation.