A practical retention guide
Your videos, ready to download for seven days.
Biyra stores finished videos for seven days from when they are ready. Download your copy from the video library before expiry. Eligible files are then automatically removed from private storage, subject to the holds and backup limitations below.
Data retention
Loading the retention schedule…
What happens to your files
From upload to deletion.
- Accept. A signed-in workspace uploads authorized source media through secure upload.
- Work. Source files, brand assets, and released outputs can remain linked to the account and project in private storage.
- Request. An authorized organization member can start a project deletion request after confirming the account.
- Track. The request shows whether deletion is waiting, in progress, complete, or needs attention.
- Finished videos
- 7 days from release
- Automatic erasure
- Scheduled after expiry
- Deletion
- Also available by request
- Active holds
- May pause deletion
01 / Account and project media
Download your finished videos before expiry.
Finished videos and companion delivery files are available for 168 hours from release. The library shows each file’s expiry date. Download and viewer links stop at expiry; physical deletion follows on the next eligible cleanup sweep. Uploaded photos keep their separate retention schedule, and account records are not deleted with a video.
02 / Working files
Different files serve different stages.
A project may create temporary or working files in addition to your photos and final videos. Different file types may follow different schedules. A recorded cleanup result—not simply the passage of time—is the evidence that deletion finished.
03 / Deletion requests
A request has a state you can follow.
Project deletion begins from signed-in project controls or support and may require an account check. The request shows its current state. A request that is waiting or in progress is not the same as completed deletion; contact support if it needs attention.
You may be able to cancel a request before deletion starts. When the product reports completion, the service has finished its deletion workflow. Some records may remain when needed for security, support, or legal reasons.
04 / Holds and limited records
A documented hold can block cleanup.
A documented hold may pause deletion. Some support, security, incident, audit, or request records may be kept longer when needed to understand what happened. We do not promise a deadline for review or completion.
05 / Connected services
Connected services have their own rules.
AI generation and quality checks send photos, instructions, and generated material to AI providers. Those providers may retain information under their service terms and account configurations. Backup cycles can also delay complete erasure. Listing imports may send a public property URL and limited page content to a retrieval service. Photos copied into your private project follow the same retention process as uploaded photos.
06 / Account-level requests
Account access and project cleanup are distinct.
Deleting a project does not automatically delete your account or every support or security record. Use the Contact page for an account-level request, even if you cannot sign in. We can verify the request and explain what was removed.
Need the status of a request?
Use the Contact page and include the project reference when available. Do not send private media or passwords through a public channel.