Abuse
Something's wrong out there.
This is the abuse reporting policy for PageWeave. If a site we host is phishing, spreading malware, spamming, scamming, or serving illegal content, report it — we read every report, and a human investigates.
01 — Scope
What this policy covers.
In scope: any site served on pageweave.site or any domain pointing at PageWeave that you believe breaks our terms — phishing, malware, spam, scams and fraud, illegal content, and copyright or trademark concerns.
Not here: security vulnerabilities in the platform itself — that's /security. And raw automated scanner output with no actual issue behind it doesn't get action.
02 — Report
Two ways, always read.
Report below — anonymous reports welcome, leave the contact field blank. Or write to abuse@pageweave.dev.
What helps us act fast
- The URL of the offending site or page.
- The category — phishing, malware, spam, scams, illegal content.
- What you saw, and when.
- Screenshots or a link to evidence, if you have them.
Screenshots land in our submission inbox with private download links; include only what's needed to show the problem.
03 — Response
What happens next.
We acknowledge every report within two business days and investigate it against our terms. If we confirm abuse, we act — suspending the site or removing the content, often permanently.
Automated abuse scoring runs continuously across hosted sites. Your report helps us catch what it misses — and see the context a machine can't.
If the site is still live and the harm is ongoing, say so in your report. Ongoing harm gets priority.
04 — Your report
Used to investigate.
We use reports to investigate abuse, and nothing else. If you leave a contact, we use it to ask follow-up questions and to tell you the outcome where we can. Anonymous reports are read the same as named ones.
The terms spell out what gets a site suspended. The privacy policy covers how we handle what you send.
Looking for the vulnerability policy instead? Security issues in the platform go to /security — machine-readable at /.well-known/security.txt (RFC 9116).
Policy reviewed 2026-11 · abuse@pageweave.dev