📜 Community Guidelines
Short version: be kind, be honest, respect privacy — including each other's.
We built GhostStat to measure the web without treating people like products, and
this community runs on the same values. If you keep the spirit of that in mind,
you'll never need the rest of this page. But here's the rest of this page.
The spirit
- Assume good faith. We're all figuring the web out. Ask before you accuse,
and give people the benefit of the doubt.
- Be generous with help. The person asking a "basic" question today is the
one answering it next month. Nobody starts an expert.
- Disagree well. Argue the idea, not the person. Strong opinions, loosely
held, kindly expressed.
Posting well
- Search first. There's a good chance your question or idea already has a
thread — add to it rather than starting a duplicate.
- Use the right category and tags. One primary tag per thread; add secondary
tags to help people find it. It genuinely helps everyone (and earns goodwill).
- One topic per thread. Separate ideas get separate threads so voting and
discussion stay clean.
- Write a clear title. "Funnel step won't save on Safari" beats "help
please". Include your GhostStat version and the exact error when something's
broken.
- Format code in fenced blocks, and redact private data in screenshots —
your own numbers included. This is a privacy community; act like it.
Self-promotion (yes, within reason)
- Built a plugin, theme, or wrote a guide? Great — share it in Showcases,
Plugin Ideas, Tutorials, or the Developer Zone, whichever fits.
- What's not okay: drive-by links, affiliate spam, dark-pattern "growth"
tactics, or DMing members with pitches. If the post is for the community,
it's welcome. If it's at the community, it isn't.
Respect other members
- No harassment, hate, or personal attacks — zero tolerance, regardless of
how good the underlying point was.
- Don't scrape, profile, or dox other members. Being an analytics community
is not a licence to analyse each other.
- No impersonation of the team, other members, or brands.
Security issues are different
If you find a vulnerability, do not post it here. Report it privately — see
the Security & Responsible Disclosure thread — the Security thread, or email
security@ghoststat.me. Public bug-hunting that exposes other users is treated as
a serious breach of these guidelines.
Moderation
- We moderate lightly and in the open where we can. Expect a friendly nudge
before anything heavier.
- Escalation looks like: edit/move → gentle warning → formal warning →
temporary suspension → ban, scaled to the situation. Spam, harassment, and
security-endangering behaviour can skip straight to the end.
- Made a mistake? Own it, edit it, move on — we all have. Think we got a
call wrong? Message the mods; we'd rather hear it than have you stew.
The good news: we reward the people who make this place good
Helping others, ideas that ship, translations, plugins, and solid bug reports
earn GhostPoints, ranks, and badges — and consistent contributors earn a
free GhostStat Pro account, for life. It's earned, not given. The system is
tuned to reward quality and consistency, not volume — so please don't try to
game it. Being genuinely helpful is, by design, easier than gaming it anyway.
Full details → The Ghost Guild.
Visitor → Signal → Tracker → Analyst → Architect → Ghost Council
That's it. Thanks for helping make this the most useful — and most humane —
analytics community on the web.
— The GhostStat Team