Privacy notice

Last updated 2026-05-25 · sandbox version

SybilShield is an open-source Sybil detection sandbox. This notice describes the limited personal data we process to run it. We're a small project pre-incorporation — when we incorporate and accept production customers, this notice will be replaced with a DPO-reviewed version.

1. Data we collect

· email — when you register an account, only to deliver your API key and audit-log notifications. Never sold or shared with third parties.
· api_key_prefix — first 12 characters of your API key, stored alongside the bcrypt hash to identify your account on requests.
· request metadata — endpoint, timestamp, status code, customer ID. Used for rate-limiting and usage counters. No request bodies are logged.
· on-chain addresses you submit — stored against your analysis ID for evidence reproducibility. Public information by nature.

2. Data we do NOT collect

· Cookies (we use one functional cookie for session, no analytics/ads)
· Browser fingerprints, IP geolocation logs, device IDs
· Payment data of any kind — SybilShield is a free public good with no billing
· Third-party tracking pixels, Google Analytics, Hotjar, FB pixel — none

3. Where data lives

Postgres + Redis on a single Hetzner VPS in Germany (DE). Daily local pg_dump backup retained 7 days. Off-site backup planned, not active yet. TLS via Let's Encrypt.

4. Retention

· Analyses + scores: kept for the life of your account
· Audit-log entries: kept indefinitely (append-only by design)
· Account email: until you delete your account (see §6)
· Request logs: 30 days

5. Sub-processors

See /sub-processors for the canonical list (Hetzner, Vercel, Alchemy).

6. Your rights (GDPR / CCPA)

Email support@sybilshield.org for access, correction, deletion, or export of your data. We respond within 30 days. You can also use the public /appeal flow to dispute a score about an address you control.

7. Contact

SybilShield (pre-incorporation, sole maintainer).
Email: support@sybilshield.org

⚠ This notice reflects the public sandbox. Production-customer terms will be governed by a separate DPA on contract signing.