Account identifiers
Email addresses, user IDs, and Lamba account references used to authenticate and support users.
Privacy controls for identity operations.
Lamba processes the data needed to provide authentication, policy enforcement, operational reliability, support, and billing.
Privacy model
Account, Workspace, Project, and operational records stay tied to clear service purposes.
Identity data
Account identifiers and membership context.
Operational evidence
Auth events, audit trails, and reliability signals.
Request handling
Deletion, access, and correction requests receive a request ID.
- Data minimization
- Scoped access
- Request IDs
- Retention windows
Data categories
What Lamba processes.
Categories stay limited to identity operations, service reliability, security controls, billing, and support.
Workspace and Project metadata
Names, roles, memberships, and setup context used to keep access scoped correctly.
Auth events and security signals
Session, login, audit, and operational signals used for reliability and abuse prevention.
Billing and plan metadata
Subscription, invoice, and plan state needed for commercial operations.
Support communications
Messages and attachments submitted through contact, support, or privacy request paths.
Retention
Retention windows are purpose based.
We retain operational data for defined windows and keep specific records longer only when legal, billing, security, or abuse-prevention obligations require it.
| Category | Retention | Notes |
|---|---|---|
| Operational logs | Defined windows based on plan and operational need | Used for security investigations and reliability analysis. |
| Security and fraud records | May be retained longer when required | Extended retention can apply for abuse prevention and legal compliance. |
| Billing records | Retained per financial and legal obligations | Retention follows invoicing, tax, and contractual obligations. |
Requests
Subprocessors and privacy requests stay reviewable.
Infrastructure and messaging providers are reviewed for security, reliability, and contractual controls before onboarding.
Subprocessor approach
Providers are approved for service purposes and reviewed for contractual and operational controls.
Need a privacy action or review path?
Use the privacy request flow for account data requests, or review Trust for the operational controls behind Lamba.
- Privacy requests
- Scoped data
- Security signals
- Support context