Community Guidelines

Last updated: 30 June 2026

flagwise gets better when people share what they actually experienced. To keep the community useful, trustworthy, and lawful, please follow these rules when you contribute or confirm a report.

Do

• Share first-hand experience or public information. Tell us what you actually encountered, or point to publicly available, official information.
• Be specific and factual. Country, topic, what happened, and roughly when.
• Keep it current. Note when your experience took place; rules change quickly.

Don’t

• No personal data. Do not include names, contact details, account numbers, ID numbers, or anything that could identify you or another person — neither yours nor anyone else’s. Describe the institution and the process, not individuals.
• No copyrighted text. Do not paste verbatim text from banks, law firms, or other sources. Summarise in your own words and link to the public source instead.
• No confidential or privileged information.
• No false, manipulative, or promotional content. No fake reports, no astroturfing, no attempts to game reputation or rankings, no advertising.
• Nothing unlawful, hateful, or infringing.

How we handle contributions

• Contributions are shown as community-reported (“not verified”) and kept clearly separate from verified data. A high number of similar reports does not make them official.
• If you are signed in, your display name and contributor reputation may be shown with your contribution. Recognition is non-monetary.
• We may review, edit, refuse, or remove any contribution, and may suspend accounts that break these rules.

Reporting & takedown

If you see content that contains personal data, is unlawful, infringes your rights, or is otherwise inappropriate, email hello@flagwise.me with a link and a short description. We aim to review reports promptly and will remove content that violates these guidelines or the law. If you submitted a contribution and want it removed, contact the same address.

By contributing, you agree to our Terms of Service (including the content licence) and confirm your contribution follows these guidelines.