Report abuse
Anuron / report abuse
If something is wrong, give it a place to be understood.
Report suspected harmful, deceptive, or unauthorised activity connected to Anuron services, domains, email, or infrastructure.
Please remove passwords, API keys, payment details, private keys, and unrelated personal information before sending anything.
Incident note / first pass
01 / clearThe useful shape
What happened, where, and when?
Specific details create a useful starting point. You do not need to write a perfect report.
01 / Locate
Where it happened
02 / Explain
What you observed
03 / Protect
Remove private secrets
Do not send secretscontact@anuron.io
Trust & safety / 02Choose the route
Start in the place that matches the problem.
A simple distinction keeps urgent reports from getting buried in an ordinary support queue.
Get support
Is this an account, billing, setup, or ordinary technical question?
Open a support ticketNot sure
Do you need help identifying the right place to start?
Contact AnuronTrust & safety / 02What helps
Make the report easy to understand.
You do not need to write a perfect incident report. A few specific details give the team a useful place to begin.
Keep it safe
Never include passwords, API keys, payment details, private keys, or unrelated personal information.
Where
Point to the location.
Include the URL, domain, IP address, email address, or account reference connected to the report.
What
Describe the activity.
Explain what you observed in plain language and why it appears harmful, abusive, or unauthorised.
When
Add the time context.
Include the date, approximate time, and time zone when the activity occurred or was observed.
Evidence
Attach useful proof.
Screenshots, message headers, logs, or other relevant evidence can help explain the report. Remove secrets first.
Contact
Leave a way to follow up.
Include your name and a reply address if you are comfortable answering clarifying questions.
Trust & safety / 03Evidence hygiene
Show enough to explain it. Never enough to expose it.
Screenshots and logs can make a report clearer, but only when they have been checked for secrets and unrelated private information first.
Before you attach
Read the frame once more as if it belonged to someone else.
01
Keep the signal
Leave the useful context visible.
Keep the URL, domain, message header, timestamp, or log line that helps explain what happened.
02
Remove the secret
Redact what should never travel.
Hide passwords, API keys, tokens, private keys, payment details, and authentication codes before attaching anything.
03
Check the frame
Share only what belongs to the report.
Remove unrelated customer information, private conversations, and personal data that does not help explain the activity.
Trust & safety / 03Choose the right route
A report should reach the people who can understand it.
For suspected abuse, email the details directly to contact@anuron.io. For ordinary account or product support, use the support route instead.
Please do not use the abuse route for password resets, billing questions, or ordinary technical support.
Trust & safety / 04After you send
A report starts a clearer conversation.
The page cannot promise an outcome before the details are understood. It can make the first handoff more useful.
01 / Receive
The report reaches the right inbox.
Send the details to contact@anuron.io with a clear abuse-report subject so the message is easy to identify.
02 / Understand
The context gives the report shape.
A specific location, description, time, and supporting evidence make the situation easier to understand.
03 / Clarify
Questions can follow when needed.
If additional context is needed, a reply address gives Anuron a way to ask a focused follow-up question.
Trust & safety / 04Reference
The useful answers before you send.
A short reference for report scope, evidence, sensitive information, and the right contact route.
Open support insteadReports about suspected harmful, abusive, deceptive, or unauthorised activity connected to Anuron services, domains, email, or infrastructure belong on this page.
Include the relevant URL, domain, IP address, email address, account reference, a short description of the activity, and when you observed it. Screenshots, message headers, or logs can help if they do not contain secrets.
You can send the report with the information you are comfortable sharing. A reply address helps if Anuron needs to ask clarifying questions, but do not include unrelated personal information.
Do not send passwords, API keys, payment details, private keys, authentication codes, or unrelated personal information. Redact sensitive values from screenshots and logs before attaching them.
Use the support ticket route for account, billing, and ordinary product or technical questions. The abuse email is intended for suspected harmful or unauthorised activity.
Email the details to contact@anuron.io with a clear subject such as “Abuse report — Anuron”. The page’s Email a report button opens a pre-filled message subject.
Anuron on Discord
The next answer might be one message away.
Join the Anuron Discord to share what you are building, ask practical deployment questions, and compare notes with other people moving work from local to live.
Join the DiscordWhat to bring
A little context makes a better conversation.
01 / Context
Bring the real workload, not a perfect question.
02 / Conversation
Compare notes with people solving similar problems.
03 / Follow-through
Leave with a clearer next step.
The invite opens in a new tab.