ProductModelsPrivacyPricingCLIGet Early Access

Your Data

Last updated: June 26, 2026

This page explains the data lifecycle in plain language.

What You Send

When you use @unexposed/image-gen, you may send:

  • an access token;
  • a model identifier;
  • a text prompt;
  • an optional source image;
  • basic request metadata needed to route and bill the task.

The package seals the prompt and source image before submitting the task payload.

What The Task Manager Sees

The Task Manager receives:

  • your account access token;
  • the selected model name;
  • encrypted task payload;
  • operational metadata such as request time and task status.

The Task Manager does not receive the client-side generation private key or plaintext prompt/source content from the package.

What Workers Need

Generation workers may need temporary access to task content to run the model and produce the output. The product goal is to keep that access short-lived, isolated, and limited to the task being processed.

What We Try Not To Keep

Unexposed is designed around zero retention for generation content:

  • no hosted prompt history by default;
  • no public image gallery;
  • no prompt or source image in normal application logs;
  • generated output should be removed after delivery.

What May Be Kept

Some data may be retained for practical operation:

  • account records;
  • billing records;
  • access token metadata;
  • model and usage counts;
  • task status and error metadata;
  • security and abuse-prevention logs.

Third-Party Model Paths

If you choose a model that runs through a third-party provider, that provider may receive the prompt and source image needed to run the task. Their own terms and privacy policy may apply.

Requests

You can request access, correction, deletion, or export of account data where applicable law gives you that right. We may need to keep limited records where required for security, fraud prevention, legal compliance, or accounting.

Token Hygiene

Treat access tokens like passwords:

  • do not commit them to source control;
  • rotate them if exposed;
  • use environment variables instead of hardcoding them;
  • remove tokens from old machines and CI jobs when they are no longer needed.