The current independent build does not have provisioned cloud storage, hosted delivery, account authentication, or billing. It therefore does not currently retain cloud-uploaded MediaToURL assets or active account records. This policy explains the retention principles that will apply if those features are enabled.
Future retention periods will depend on the enabled feature, user settings, legal requirements, and provider configuration. A legal hold, safety investigation, rights dispute, incident response, or recovery process may require limited preservation once the service is operating.
1. Active, Expired, and Deleted Assets
No cloud files or hosted-link records are stored by the current build. If file hosting is enabled later, a file and its operational metadata may be retained while needed to provide the feature and according to the published account, expiry, and deletion settings.
Expiry, a reached view or download limit, manual deletion, account action, plan enforcement, or safety enforcement can make a link unavailable before background cleanup removes the related storage objects. Deletion of an active asset revokes normal access through the MediaToURL delivery routes; a copy already downloaded or republished elsewhere cannot be recalled.
Expiry-based cleanup and abuse enforcement are separate. A file restricted because it was reported is not permanently deleted solely because it reached a report threshold. It remains unavailable while it is reviewed and may be permanently purged after a confirmed violation or an authorized administrator action.
2. Abuse Restrictions and Operator Review
When a file is temporarily restricted for abuse review, public delivery may be blocked across its direct URL, share page, variants, transformations, downloads, and verified custom delivery domains. The restriction is intended to stop continued access while avoiding automatic permanent deletion based only on an unverified report.
Assets with repeated open reports may be presented to authorized operators for review and bulk action. After confirming a violation, an operator may remove the asset, versions, variants, thumbnails, and related storage objects. Report and audit records may be retained separately so that the action, reason, and investigation history remain accountable.
Urgent safety, malware, phishing, legal, or law-enforcement matters may require faster restriction, preservation, or removal. MediaToURL may limit disclosure of investigation details when disclosure would create risk or conflict with privacy or legal obligations.
3. Account, Security, and Abuse Records
We retain account, workspace, API, authentication, billing, request, rate-limit, upload, delivery, abuse, moderation, and audit records for as long as reasonably needed to operate the service, prevent fraud and evasion, investigate incidents, resolve disputes, meet legal duties, and protect users. Retention periods depend on the record type and risk.
Subscription and transaction records may be retained after an account is closed when they are still needed for accounting, tax records, payment disputes, fraud prevention, legal obligations, or reconciliation with a Merchant of Record. This does not mean that complete payment card credentials are stored by MediaToURL.
Security-derived identifiers, such as IP-derived rate-limit values and request metadata, may be retained in a limited form for abuse prevention and investigation. We do not promise that every log is retained for a fixed period or that every record can be removed immediately after a request.
When the business purpose ends, records are deleted, anonymized, or isolated where reasonably practicable, subject to legal holds, backups, security needs, billing requirements, and other lawful exceptions.
4. Backups, Recovery, and Legal Holds
Infrastructure backups and recovery copies support service continuity. They are not a customer-facing archive, do not guarantee selective restoration of one file, and may retain deleted records until the applicable backup cycle expires or the copy is safely overwritten.
A legal hold or preservation request may pause ordinary deletion for an asset, workspace, account, report, or related record. Holds may arise from a subpoena, court order, law-enforcement request, DMCA dispute, safety investigation, fraud review, or security incident. Preserved information is accessed only for the reason requiring preservation and is deleted when the hold and other retention needs end.
MediaToURL may retain limited records after an account or file is deleted when needed to prevent repeat abuse, establish what happened, respond to a legal request, enforce an agreement, or protect another person's rights.
5. Deletion Requests and Contact
Account holders can delete eligible files, links, folders, or accounts through the available product controls or by contacting [email protected]. We may verify the requester and may ask for the exact asset or account information needed to avoid deleting the wrong material.
Deletion of a MediaToURL record does not remove copies held by recipients, search engines, third-party caches, custom-domain consumers, or other websites. We can stop the normal delivery paths we control and may provide additional instructions where a separate third party controls the copy.
For privacy, retention, abuse, copyright, or legal questions, contact [email protected]. Do not include passwords, access tokens, live malware, or unnecessary sensitive files in a request.