Skip to content
RR
RaiderRep

Privacy Policy

What we collect and how we use it.

← Home

1. Who We Are

RaiderRep ("we", "us") operates the RaiderRep website and services. This policy describes how we collect, use, and protect your information.

2. Data We Collect

Account data: Auth provider identifier, email (if provided), display name, and claimed Embark ID. User-generated content: Reports, watchlist entries, private notes, dispute reasons, AI queries. Usage data: Google Analytics aggregate metrics. We may log requests for security. Security data: IP address and browser user agent, recorded for rate limiting, abuse prevention and error reports. Local storage: Session state, preferences, and guest AI usage tracking.

3. How We Use It

To operate the reputation database, AI feature, watchlist, marketplace, and other tools; to enforce rate limits and prevent abuse; to improve the service and comply with law.

4. Third Parties

We rely on: Supabase (auth/db); Google (OAuth/Analytics); Umami (privacy-friendly analytics); Cloudflare Turnstile (anti-spam check); Vercel (hosting); Buy Me a Coffee (donations); OpenAI / Tavily (AI); MetaForge / RaidTheory (game data). We do not sell your personal data.

5. Public Record

Reports, Embark IDs in reports, and trust scores are public. By submitting a report you acknowledge the data will be indexed and searchable.

6. Right to Erasure (Opt-Out)

Use the Opt-Out tool (footer or dedicated page) to permanently blocklist your Embark ID. This is irreversible from our side.

7. No Payments

RaiderRep is free and has no paid plans, so we never collect payment information. Optional donations are handled entirely by Buy Me a Coffee; we never see or store card details.

8. Data Retention

Reports and scores are retained indefinitely unless you opt out. Account data is kept while your account exists. Security, error and usage logs that contain IP addresses are deleted after 90 days.

9. International & Your Rights

Data may be processed in the United States. EEA/UK users may have rights to access, rectify, or erase data. We do not knowingly collect data from children under 13.

10. Security

We use HTTPS, Supabase Auth, Row Level Security, rate limiting, and input sanitization. No system is 100% secure.

11. Changes

We may update this policy. Continued use after changes means you accept the updated policy.

Last updated: October 2026 (v2.9.9). Questions: use the Suggestion Box or contact us via the footer.