Data Retention

Public preview

New registrations, uploads and purchases are closed. The public example is an intentionally published asset, separate from private test media. It remains available while used to explain the product, unless withdrawn after a rights complaint or editorial review.

Test inputs and outputs

Inputs uploaded for authorized tests are processed by Yir and the selected model provider. Yir reports file expiry; an application upload authorization can expire sooner than the provider deletes the underlying file. We do not describe a one-hour authorization as a one-hour deletion promise.

Generated test videos saved in private Cloudflare R2 storage remain until no longer needed for the test/account or a verified removal request is processed. Automatic age-based deletion and self-service deletion are not enabled. This is not a permanent backup service; retain your own copy. Upstream providers have separate retention rules, and we do not claim that deletion from our storage erases their records immediately.

Account, support and billing records

Existing account and task records are retained while needed for account operation, support, security or legal obligations. Support correspondence is kept while needed to resolve the request and related disputes. Payment records, if payments open, may need longer retention under applicable accounting or legal rules. We use purpose and necessity to determine retention rather than promise an unimplemented automatic schedule.

Request access or deletion

Email parenth166@gmail.com with the account email and the relevant task or file identifiers. Do not attach private media unless specifically requested through an agreed channel. We verify ownership, review relevant storage and provider copies, and explain the action taken or any lawful retention exception. Deletion requests are handled manually under applicable deadlines; archived or provider-managed copies may not disappear at the same time as the active copy.

Before public uploads open, we will publish the applicable user-facing retention schedule and verify the corresponding deletion process. See privacy and contact.