Contact & monitored channels

Waidrn is a small operation, and we would rather tell you exactly where to write than make you guess. The table below lists every monitored channel and what each one is for. The quickest route for content problems is always the Report button on the content itself — it goes straight to the moderation queue with the right context attached.

Version 1.5 — effective 2026-11-16.

Monitored channels

AddressUse it forWhat to include
security@waidrn.comSecurity vulnerabilities, abuse of the site, or anything that could harm usersSteps to reproduce, affected page or account, and what you expected. See /.well-known/security.txt for the canonical contact record.
copyright@waidrn.comCopyright and takedown notices, counter-notices, and rightsholder questionsThe formal fields listed on the copyright notice process page — a notice without them cannot be acted on.
support@waidrn.comAccount help: sign-in, email verification and resend problems, profile changes, data export or deletion, bug reports about your own accountYour username, the page or action, what you expected and what happened. Never send your password.
moderation@waidrn.comAppeals of moderation decisions (contract-aware decisions carry an id), and questions about how a decision was madeA link to the affected content, the decision you are appealing, and what you think was missed.

Formal copyright notices and counter-notices should follow the copyright process; the report form is not a substitute for a legal notice. Court orders, law-enforcement requests, regulator/DSA orders and foreign demands use the legal-notice intake and the same operator queue. A notice receipt is not a decision and not legal advice; delivery status for every address is listed above, honestly.

Honest delivery status

Waidrn runs its own mail service, and the addresses above are monitored inboxes. Public delivery from the wider internet depends on the operator finishing the MX/DNS mail configuration for waidrn.com. Until that is complete, a message from outside our network may be delayed or bounced; if an address bounces, use the in-app route and try the mailbox again later.

Some routes never depend on email:

No promised response times

We aim to read and triage messages within a few business days, and safety-critical content is escalated immediately through the report queue. We are a small team and we do not promise a fixed response time, resolution time or legal deadline through these channels. Formal legal notices take longer because they are reviewed carefully; the copyright process explains what we can and cannot do.

What not to send us

Where the rules live

Policy version 1.5

The monitored channels and delivery status above are unchanged. The current policy set (version 1.5, effective 2026-11-16) adds the account/profile model, adult-gating wording, realm contracts, the unified legal-notice workflow, provisional location availability and the privacy additions that go with them. The trust/legal review flag is still on: this policy set has not yet completed independent legal review, and nothing on these pages is a promise of a fixed response time or a legal outcome.