Retention and deletion
Know what happens when payment, capacity, or ownership changes.
Unpaid application timeline
| Time after payment failure | Behavior |
|---|---|
| First 7 days | Normal access during the payment grace window |
| After day 7 | New uploads blocked; retained-file delivery remains available |
| After day 30 | Normal downloads suspended |
| Day 60 | Unpaid retained files purged after warning notices |
Over-capacity cancellation or downgrade
The paid subscription ends or the lower plan begins at the scheduled boundary. Data that does not fit receives a 30-day authenticated export and cleanup window before purge. This window does not create a new paid subscription or recurring consent.
Making a payment can resume a recoverable account after the server verifies the payment and lifecycle state. It cannot restore files that have already been permanently purged.
Deliberate permanent deletion
Permanent deletion is different from a billing grace period. It revokes new requests within the targeted 60-second window and purges owned copies within the targeted 24-hour window. There is no user-facing trash or undo.
Deletion jobs remain visible while pending and must retry failures. Recovery copies and versions are included in permanent-purge work. Operational recovery objectives need deployment validation and are not a guarantee that deliberately deleted data can be restored.
Uploadfile is an independently operated service. The framework SDK is forked from the MIT-licensed UploadThing SDK; UploadThing’s hosted backend is not included in that source.