Account Profile
- Examples
- Name, email, preferences
- Where stored
- Primary database
- Purpose
- Authentication and personalization
- Retention
- Active account + limited retention window
This map summarizes how data is used for product operations. Retention can vary by legal or operational requirements.
| Category | Examples | Where Stored | Purpose | Retention |
|---|---|---|---|---|
| Account Profile | Name, email, preferences | Primary database | Authentication and personalization | Active account + limited retention window |
| Session Tokens | App session tokens | Encrypted secure store | Session continuity | Short-lived or until revoked |
| Conversation Context | Recent messages, tone signals | Ephemeral memory | Reply quality and context | Minutes to hours |
| Usage Analytics | Page views, feature usage | Analytics provider | Product improvement | Aggregate or anonymized |
| Billing Records | Invoices, subscription status | Payment processor | Billing and compliance | Per legal requirements |
We collect the minimum required to operate and improve the product.
You can request a summary of your stored data at any time.
Retention windows are designed to be short and proportional to purpose.
We are happy to walk through your specific concerns or compliance needs.
Contact Security