Abuse policy
Version: 14 October 2026.
This page says what may not be stored or served through Dynjandi, how to report it, and what we do about a report. It is part of the terms, and it is a separate page so that it can be linked on its own.
1. What is prohibited
- Child sexual abuse material, and any sexualised depiction of a minor, in any form.
- Content that is illegal where it is stored, served or viewed.
- Content that infringes someone else's copyright, trade mark, privacy or other rights, including intimate images shared without the consent of the person shown.
- Sexually explicit content, whether or not it is lawful.
- Content that promotes terrorism or incites violence or hatred against people.
- Content used to harass, threaten, defraud, impersonate or deceive people, including images made for phishing pages, or to distribute malware.
- Use of the service to disrupt it, to get around plan limits or rate limits, or to store or distribute files that are not images.
2. How to report
Send a report to abuse@dynjandi.dev. So that we can act on it, a report should contain:
- the full URL of each image on
cdn.dynjandi.dev(the file identifier is the first path segment); - why you consider the content illegal or in breach of this policy, and, for an infringement of rights, which right is infringed and that you hold it or act for the person who does;
- your name and an email address where we can reach you, which you may leave out when reporting child sexual abuse material; and
- a statement that the report is accurate and made in good faith.
Please do not send the content itself. If someone is in immediate danger, contact the police first.
3. What we do
We do not review content before it is stored, and we do not monitor content generally.
When a report or an order from a court or an authority gives us knowledge of illegal content, we remove it or disable access to it without delay. For other breaches of this policy we decide what to do in proportion to the breach. We can:
- Remove the file. This removes the stored copies (the original and every stored variant) and asks Cloudflare to purge the cached variants. If the purge does not complete, we repeat it until it does. Copies already held by browsers or other caches are outside our control and can remain for up to a year.
- Disable the users of the workspace that owns the file, which ends their sessions and blocks sign-in. A file records its workspace and project, not the user who uploaded it, and uploads are authorised by the project's key, so this does not revoke that key.
- Switch the workspace off, which refuses new uploads and new variants. This alone does not stop originals, or variants that are already rendered, from being served, so it is used together with a removal.
We may also suspend a customer or end their contract under the terms, and we do so on a third breach of this policy, or on a first serious one.
For child sexual abuse material we remove the content immediately, report it to the police, and do not notify the customer where that could harm an investigation.
In other cases we tell the customer what we did and why, unless the law or an authority prevents it, and the customer can ask us to reconsider by replying to that message. We aim to acknowledge a report within two working days and to decide it within seven days, and we tell the person who made the report what we decided. We keep a record of reports and decisions for two years. We may disregard reports that are plainly unfounded or made in bad faith.