File contents
Nothing readableFiles are encrypted on your device before upload. We do not hold the keys and cannot produce plaintext for anyone, under any order.
Transparency report
Every request, and what we handed over.
Every government or law-enforcement request we have received, and what we were able to produce. Covering all activity to 1 September 2026.
Nothing to report yet. ShieldSync is pre-launch and does not yet operate a production service, so there has been nothing for an authority to request. The figures below are zero because they are genuinely zero, and this page will be updated the first time that changes.
Requests received
By jurisdiction.
| Jurisdiction | Requests received | Requests where data was produced |
|---|---|---|
| Denmark | 0 | 0 |
| Other EU / EEA | 0 | 0 |
| United States | 0 | 0 |
| Rest of world | 0 | 0 |
If we were asked
What we could produce.
More useful than a count, and true regardless of what any future order says: we can only ever hand over what we actually hold.
Filenames
Usually nothing readableWith filename protection on, names are encrypted client-side and we receive only opaque identifiers and file sizes.
Account details
Name and emailWhat you gave us at registration. This we could be compelled to produce.
Device and connection records
IP addresses, device namesSign-in records and device metadata, kept for 12 months. This we could be compelled to produce.
Our process
How we would handle a request.
- We require valid legal process. A request from outside Denmark must be domesticated through the Danish courts before we act on it.
- We produce the minimum the order actually compels, never more.
- We notify the affected user unless we are legally barred from doing so.
- We cannot produce file contents or encryption keys, because we do not have them. That is a property of the architecture, not a policy we could be ordered to change.