Short, because it has to be readable. These conditions apply to every transfer created through the API or the dashboard.
429 and Retry-AfterBecause objects are encrypted client-side, we cannot inspect content and do not attempt to. Enforcement is therefore reactive: we act on reports that identify a specific link, and on traffic patterns that damage the service for others.
| Situation | What we do |
|---|---|
| Report about a specific link | The link is disabled pending review. The account holder is notified with the report. |
| Sustained abuse of rate limits | Writes are shaped, then refused at the edge. The account holder is notified before refusal. |
| Repeated substantiated reports | Keys are revoked and the account is closed. Objects expire on the normal schedule. |
| Legal order | We comply with orders valid in our jurisdiction and notify the account holder unless prohibited. |
Send reports to abuse@fileexchange.site with the full link and the
age header from the response. Reports without a specific link cannot be acted on:
we have no way to search content we cannot read.