Verification & Privacy

How we prove "one human โ‰  a farm of sockpuppets" without harvesting your life

Version 0.1 โ€ข Draft Status

Our Approach

Privacy-first human verification without biometric surveillance

๐Ÿ”’

Privacy-First Design

This page states plainly what data we collect now, what we refuse to collect, and how we'll prove "one human โ‰  a farm of sockpuppets" without harvesting your life.

1. Principles

Our core commitments to user privacy

๐Ÿ“‰

Minimize

Collect the least data required to operate the MVP

๐Ÿ‘๏ธ

Legible

Explain choices in normal language; no dark patterns

โœ…

Verifiable

Where possible, make the checks auditable or locally verifiable

๐Ÿšช

Revocable

You can leave; we delete what we can and anonymize what we must retain

2. MVP Verification (No Biometrics Yet)

Layered friction instead of privacy-invasive biometrics

โŒ

Why no biometrics now?

They're a privacy minefield, require specialized storage/consent, and create breach risk. For MVP we use layered friction instead:

๐ŸŽซ

Invite Codes

One-time codes tied to an introducer account

๐Ÿ“ฑ

Phone Verification

Optional, region-limited: one number โ†” one account; VOIP blocked. Stored as salted hash, not plain number

๐Ÿ”

Device Fingerprint

Coarse, ephemeral, salted; used for rate limiting only; not shared

๐Ÿ“Š

Behavioral Limits

Caps on claims/day and concurrent stakes for new accounts

๐Ÿ”ฎ

Future Direction

Future: As we scale, we'll consider privacy-preserving proofs (see Roadmap) before touching biometrics.

3. Data We Collect (MVP)

Minimal data collection for platform operation

๐Ÿ‘ค

Account

  • Username
  • Email (optional for notifications)
  • Hashed phone (if used)
  • Invite referrer
๐Ÿ“ˆ

Activity

  • Claims, votes, stakes, timestamps
  • Rationales (public)
  • IP (rotated logs, 14 days) for abuse mitigation
๐Ÿ“Š

Telemetry (Minimal)

  • Anonymized events for performance
  • Page load, API errors
  • No cross-site tracking, no ad pixels
๐Ÿšซ

We do NOT collect

โŒ

Legal names

โŒ

Government IDs

โŒ

Face/voice prints

โŒ

Exact location

โŒ

Contact list

โŒ

Background data

4. Storage & Retention

How we secure and manage your data

๐Ÿ’พ

Primary DB

Encrypted at rest. Access scoped by role.

๐Ÿ“Ž

Backups

Encrypted; 30-day rolling window.

๐Ÿ“…

Log Retention

14 days for IPs/user agents; longer for aggregated counters (no IPs).

๐Ÿšฎ

User Deletion

Hard-delete account profile + email; claims/votes remain as public records with your handle replaced by an anonymized tag (because the integrity of past resolutions matters).

5. Public Transparency

Verifiable processes and public accountability

๐Ÿงพ

Receipts

Each resolved claim emits a machine-verifiable receipt (seed, witness set, votes, settlement)

โš“

Daily Anchors (Optional MVP)

A Merkle root of the day's receipts anchored on a public chain; anyone can audit consistency

6. Roadmap: Stronger "One Human" Without Biometrics

Future privacy-preserving verification methods

1

Web-of-Trust Staking

Introducers post a small stake; fraud slashes introducer and introduced

2

Periodic Proof-of-Personhood Sessions

Privacy-preserving: commit-reveal rendezvous with liveness checks where only a zero-knowledge proof is published, not raw images

3

ZK Phone Assertions

Carrier-signed statements that a number exists and is unique per account, without revealing the number (research stage)

๐Ÿ”’

Biometrics Commitment

Any move toward biometrics will require:

  • Explicit consent
  • Local-device-only templates
  • No central storage of raw images
  • Third-party audits

7. Your Controls

Full control over your data and privacy

๐Ÿ“Ž

Download Your Data

JSON export of all your account data

๐Ÿšฎ

Delete Account

See retention policy above for details

๐Ÿ””

Toggle Notifications

Control email notifications

๐Ÿ“Š

Opt-out Analytics

Functional cookies only

8. Policy & Compliance (MVP)

Legal framework and platform rules

๐Ÿ“„

Privacy Policy

Plain-English + full legalese version; link in footer

๐Ÿ“œ

Terms

Code of conduct, staking rules, dispute process, jurisdiction

๐ŸŽ‚

Age

18+ only at MVP

๐Ÿ›ก๏ธ

Security

Report vulnerabilities to security@agora.fail; rewards for valid reports

9. Blunt Risks You Should Know

Honest assessment of platform limitations

โš ๏ธ

Brigading Risk

You can still get brigaded; rate limits blunt, they don't erase mobs

โš ๏ธ

Centralization

Coordinators are trust anchors in MVP; not fully decentralized yet

โš ๏ธ

Account Security

If your account is compromised, your stakes can be lostโ€”use 2FA

10. Contact

Get in touch with questions or concerns

๐Ÿ“ง

Privacy Questions

privacy@agora.fail

๐Ÿ›ก๏ธ

Security Reports

security@agora.fail

๐Ÿ’ฌ

Community Forum

#transparency forum (upcoming)

Related Documentation

Learn more about our platform

๐Ÿ’ป

MVP Documentation

Technical specification for our minimum viable product

๐Ÿ’ฐ

Token & Governance

Economic model and governance structure

๐Ÿ”’

Privacy Policy

Complete privacy policy and data handling practices