Contact

This platform is self-hosted, so the people who can act on almost anything are the ones running this particular deployment.

Last updated 24 August 2026

1. Reaching the operator

The operator installed and runs this copy of the platform. They hold the database, they make moderation decisions, and for data-protection purposes they are the controller.

This deployment has not published a contact address yet.

If you are trying to reach the operator, use whatever channel you already have with them — the organisation whose site brought you here is very often the same organisation.

If you are the operator: set PLATFORM_CONTACT_EMAIL and restart the web service. This page, the abuse page and the privacy notice all start pointing at it.

2. Things you can do faster than writing to anyone

Forgotten password: Use password reset. A link arrives by email; it can be used once and it expires.
Signed in somewhere you should not be: Account settings lists every session with when it was last used, and ends any of them — or all of them at once, which also changes nothing else about your account.
Verification email did not arrive: You can ask for another from the verification screen. Check the spam folder first; these are plain-text messages from a server you have never received mail from before, which is exactly what a spam filter is suspicious of.
Something you published looks wrong: Every save left a revision behind it. Open the post’s history and restore the version you wanted — restoring adds a new revision rather than deleting anything, so it is always reversible.

3. What to include, depending on why you are writing

Reporting content: The abuse page lists exactly what makes a report actionable. The short version: the URL, the category, and two sentences.
A data-protection request: Say which account you mean and what you are asking for — access, correction, deletion, a copy. The privacy notice sets out what is stored and, just as importantly, what deletion does and does not currently do.
A security vulnerability: Privately, with enough detail to reproduce it, and before publishing it anywhere.
A custom domain that will not verify: Include the hostname and the DNS record you created. Verification is re-run periodically, so a record added minutes ago may simply not have propagated yet.
A moderation decision you think is wrong: Say which publication or post, and what you think the reviewer missed. A person reads it; there is no automated appeal queue.

4. What the operator cannot help with

A publication’s own content. Publications here are independent. If you have a question about an article — a step that does not work, a fact that looks out of date — the publication itself is who to ask, and most list a way to reach them in their own navigation. The operator can act on content that breaks the terms, and not on content that is merely wrong.

Another deployment. This software is run by many different people. An operator can only see their own installation.

5. What to expect back

Unless the operator has published a response time, there is not one. Reports of active harm — malware, phishing, material involving minors — should be looked at first and usually are. If something is urgent, say why in the first line rather than at the end.