Plain answers about your data.

Scope of this notice

This notice describes the Fee private beta and the interest form on flatfee.one. The final commercial notice, including the public controller identity, legal bases and category-specific retention periods, will be published before public commercial onboarding.

Who is responsible

The responsible operator is identified in the invitation or agreement under which you received private-beta access. Flatfee's full public controller identity and registered address have not yet been published on this website. Commercial onboarding remains closed until those details and the final retention schedule are approved and published.

Data we use

• Account and beta access: email address, account identifiers and the information you submit when registering interest.
• Work requests: prompts and the project context you choose to send for a task.
• Task evidence: provider and model route, usage, cost, timing, approvals, file or result hashes and task reports.
• Operations and security: allowlisted events needed to run the service, investigate errors and prevent abuse.

Why we use it

We use this information to assess beta requests, provide Fee, route model work, account for capacity and cost, support users, investigate failures, protect the service and meet applicable legal obligations. We do not use the beta-interest form for newsletters.

Providers and processing regions

Selected prompt and project context may be sent through the Flatfee proxy to the model provider chosen for a task. The provider and processing region depend on that route. Fee does not currently offer an EU-only model-processing option. Do not use the beta for information that requires a fixed processing region.

Task reports record the provider and model when that information is available.

Retention and erasure

We keep each data category only for as long as it is needed for the private beta, account administration, billing evidence, security, support and applicable legal obligations. The usage system has an owner-configured retention window and scheduled purge; the approved production period is not published on this website yet.

A verified account-erasure request uses the audited erasure workflow to pseudonymize account linkage in usage records and freeze new usage recording for that account. Some evidence may need to be retained where law, security, fraud prevention or legal claims require it.

Your rights

Depending on the circumstances, you may have rights to information, access, correction, erasure, restriction, portability and objection. These rights are not absolute, and we may need to verify your identity before acting on a request. You may also complain to the competent data protection authority.