Retention Policy
VibeCut is designed for temporary media processing, not long-term media storage. User content is deleted quickly; only limited records needed for security, abuse handling, account administration and legal obligations are kept longer.
Last updated: 16 October 2026
1. Media and generated outputs
| Data | Normal retention | Action |
|---|---|---|
| Source video, reference video and uploaded audio | Deleted as soon as the editing process no longer needs the file; in any event normally no later than approximately 30 minutes after the job completes or fails. | Automatic deletion from active processing storage. |
| Final rendered output | Normally available for approximately 30 minutes after completion. | Automatically deleted after the download window. |
| Blocked malware / explicit-content upload | Normally deleted immediately after blocking. | VibeCut does not intentionally retain the blocked media in normal public operation. |
| Low-resolution review copy | Not retained in normal public operation. | Public configuration keeps review-copy retention disabled. |
| Confirmed orphaned edit media | Normally removed about 30 minutes after it is confirmed to be unreferenced by a live job. | Aggressive crash/orphan cleanup. |
| Other crash/temp leftovers where a reliable live-job link is unavailable | Absolute fallback cleanup is normally within about 2 hours. | Prevents abandoned temporary media being left indefinitely without risking deletion of an active job. |
Important: VibeCut is not a backup or hosting service. Download any output you want to keep promptly.
2. Detailed worklogs and job records
| Record | Normal retention | Purpose |
|---|---|---|
| Detailed edit worklogs / engine logs | Up to approximately 24 hours after completion or failure. | Short-term troubleshooting and quality investigation. |
| Minimal completed-job metadata | Normally up to 30 days. | Short-term service/security troubleshooting after detailed logs have been removed. |
3. Security metadata
VibeCut keeps security records separate from the uploaded media. The security log is intentionally minimised and is designed to avoid retaining the original filename, raw media, local storage paths, full media-probe output, full classifier output, duplicate email/display-name fields or browser user-agent strings.
| Security record | Normal retention | Examples |
|---|---|---|
| Ordinary security/upload metadata | Up to 30 days. | Account/user ID, timestamp, IP address, content kind, file size, file hash where useful, scanner outcome and action taken. |
| Blocked, abusive, suspicious or other security-incident metadata | Up to 90 days. | Records needed to investigate repeat abuse, malware, blocked uploads, fraud or account/security incidents. |
4. Abuse reports
An open abuse report is kept while it is reasonably needed for triage or investigation. Once an ordinary case is closed or resolved, it is normally retained for up to 365 days from closure. A report closed as obvious spam or baseless may be removed sooner, normally after up to 30 days.
Where a specific legal hold, safeguarding need, law-enforcement request, court process or dispute requires preservation, only the records reasonably necessary for that matter should be held beyond the normal period. The hold should be lifted when that need ends.
5. Account/profile data
Core account/profile data is kept while the account exists. When an account is closed or deleted, VibeCut aims to delete or anonymise the core profile promptly and normally within 30 days. The current administrator deletion function removes the profile immediately. Limited security, abuse, dispute or legally required records may remain under their own retention periods.
6. Billing and tax records
If paid services are introduced, payment, invoice, tax and accounting records will be treated separately from uploaded media and account-profile data. They may be kept for the period required by applicable tax, accounting and company-law obligations. This does not extend the retention period for user videos.
7. Infrastructure backups
Where an infrastructure provider maintains system-level backups, deletion from the live service may not immediately remove every backup copy. Backup copies are not used as ordinary user storage and are removed or overwritten according to the provider's backup lifecycle.
8. Questions
For questions about data retention, deletion, privacy or security, contact:
Suspected misuse or prohibited content may also be reported through the Report Abuse page.