Documentation

What Data We Store and Where

A practical map of account data, task content, and operational records.

Account data

Account identity is handled through Clerk. Unexposed stores the account records needed for access tokens, balance, billing, and deletion controls.

Task content

Prompts and source images are sealed before they reach the Task Manager. Generation infrastructure may temporarily access decrypted task content only to run the selected model.

Operational data

  • Access token metadata.
  • Selected model, request time, task status, and usage counts.
  • Billing records and account balance changes.
  • Security, abuse-prevention, and reliability logs.

Retention

The product goal is zero retention for prompts, source images, and generated output after delivery. Operational records may be kept for billing, security, legal, accounting, and reliability needs.

Model infrastructure

Prompts, source images, generated outputs, and keys stay inside infrastructure controlled by Unexposed. Model selection does not send task content to third-party image providers.