zkbounty
Legal

Privacy Policy

Privacy isn't a setting here - it's the architecture. This policy explains what data zkbounty does and does not handle.

Last updated · June 11, 2026

The short version

zkbounty is a privacy-preserving protocol. Proofs of physical action are generated on your device; personal identifiers are stripped before anything leaves it. What reaches the network is a zero-knowledge proof that the bounty criteria were met - never your identity, your raw media, or your device fingerprint.

What the protocol never sees

  • Faces or other biometric content - redacted on-device.
  • Raw photos, video, or sensor recordings.
  • Device identifiers, IMEI, or hardware fingerprints.
  • Your real-world identity.

The on-chain verifier program receives only public proof inputs (booleans such as coordinate-in-geofence and slot-in-window) and a payout address.

What we do process

  • Wallet address. Used to attribute submissions and release rewards. It is public on-chain by nature.
  • Account contact (optional). If you connect with email or a social login via our authentication provider, that identifier is held by the provider, not by us.
  • Basic usage telemetry. Aggregated, non-identifying analytics to keep the service reliable.

On-chain data is permanent

Anything settled on Solana - proof commitments, payout transactions, slot bindings - is public and immutable. It cannot be edited or deleted by us or anyone else. By design, it contains no personal data.

Cookies & local storage

We use local storage to keep your session and preferences on your device. We do not sell personal data, and we do not run cross-site advertising trackers.

Third parties

Wallet connection and authentication are handled by our wallet/auth provider, and settlement occurs on the Solana network. Each operates under its own terms and privacy practices.

Your choices

You can disconnect your wallet at any time, which clears your local session. For questions about data handling, reach us at privacy@zk-bounty.com.

Changes

We may update this policy as the protocol evolves. Material changes will be reflected by the “last updated” date above.