Nothing to report yet
Share links are not enabled. There have been no shares, no reports and no legal requests, so every figure below is zero — and is published as zero rather than omitted, so that the first non-zero number is visible as a change rather than as a new page.
Reporting period
This report will be updated at least twice a year once sharing is enabled, and will cover the period since the previous one.
Abuse reports
| Category | Received |
|---|---|
| Child sexual abuse material | 0 |
| Malware | 0 |
| Phishing or fraud | 0 |
| Copyright | 0 |
| Personal data published without consent | 0 |
| Other | 0 |
Action taken
| Action | Count |
|---|---|
| Links removed following a report | 0 |
| Links removed automatically pending review | 0 |
| Reports found not to warrant removal | 0 |
| Networks rate-limited or blocked | 0 |
Legal requests
| Request type | Received / complied |
|---|---|
| Requests for stored file contents | 0 / 0 |
| Requests for user identity | 0 / 0 |
| Preservation orders | 0 / 0 |
| Takedown orders | 0 / 0 |
What we are able to provide
This matters more than the counts, and does not change with the reporting period. In response to a valid legal request about a share link that has not yet expired, we can provide the encrypted blob, its size, its timestamps, and the network address that created it.
We cannot provide the contents, because we cannot decrypt them. The key exists only in the part of the link after the # symbol, which never reaches us. This is a property of how the feature is built, not a policy we could change under pressure — and it is why the 24-hour expiry cap matters: after that, there is nothing left to ask about.
We have never received a request of any kind. If that ever ceases to be true, this sentence will be removed rather than quietly left in place.