Privacy Policy

Last Updated: [Insert Date]

Tythe is committed to preserving user privacy while enabling verifiable trust. We operate as a ZK-native Credibility Operating System — which means we do not collect or store raw identity data. This policy outlines how we handle data related to TRIS identities, DISC Scores, TCT and TYT interactions, and organizational onboarding — all while respecting the principles of decentralization, zero-knowledge security, and user sovereignty.

1. What Data We Process

Tythe processes only the minimum information necessary to compute and enforce credibility. All sensitive data is either ZK-proofed, anonymized, or handled through user-controlled disclosures.

For All Users

Data Type
Description

TRIS Metadata

Public identity handle and associated score-linked metadata.

Wallet Addresses

Used to link actions, Trovebook entries, and token logic to a TRIS.

ZK Proofs (ZKPs)

Used to verify identity uniqueness, credentials, and contributions without exposing raw data.

Interaction Logs

Immutable, on-chain records of DISC Score changes, TCT usage, and Credonations.

API Integration Logs

Non-identifiable metadata for tracking platform-submitted Decision Relays.

2. Identity Verification

Tythe supports zero-knowledge-based identity verification for both individuals and organizations.

ZK-KYH (Know Your Human)

Method
Provider
Privacy Scope

Decentralized Biometrics

Humanity Protocol

ZK-verified only

Biometric Uniqueness

World ID

ZK-verified only

  • KYH is optional but required to unlock DISC Score computation.

  • Only ZK-nullifier hashes are stored. No raw identity, biometric, or credential data is seen or held by Tythe.

ZK-KYB (Know Your Business)

Used for onboarding onchain organizations only.

Data Collected
Purpose

Project metadata (site, DAO, etc)

Validates onchain presence

Governance & funding history

Assessed via public records or partner tools

ZK founder verification

Performed via Privado ID (ZK-only, no raw data stored)

Smart contract activity

Confirmed through explorer and signature checks

Social Account Ownership

zkTLS powered by Reclaim Protocol

All KYB validations are stored as ZK hashes in the org’s Trovebook and mapped to their TRIS.

3. How We Use Data

Use Case
Description

DISC Scoring

Inputs from platforms and users are converted into credibility scores.

Trovebook Verification

Users can verify credentials and claims via their ZK-hashed ledger.

Credonation + Staking

Enables peer validation and protocol-weighted access decisions.

Governance Eligibility

TRIS metadata determines participation thresholds.

Integration Access

Organizations are scored and gated via KYB-linked TRIS identities.

Tythe does not use data for marketing, profiling, or analytics.

4. Storage & Security

Mechanism
Description

Zero-Knowledge Proofs

All sensitive data is verified without disclosure.

Decentralized Storage

Metadata stored on IPFS or Arweave where applicable.

On-Chain Anchoring

TRIS, TCT, and DISC Score data is recorded onchain.

No Centralized Databases

No raw identity, biometric, or credential files are ever held.

User data remains sovereign, non-custodial, and non-extractable.

5. Your Rights

Tythe complies with global data privacy laws including GDPR, CCPA, and others.

Right
Description

Transparency

Users can view how TRIS, DISC Score, and KYB/KYH attestations are used.

Portability

ZK-KYH / KYB attestations can be reused across integrated platforms.

Correction

Organizations may request metadata correction during KYB onboarding.

Deletion (Orgs)

Organizations may request offboarding and data erasure (subject to constraints).

Platform Opt-Out

Users may choose not to interact with platforms requiring KYC or scoring logic.

Users control what to share and when — with no surveillance or behavioral profiling.

6. Third-Party Sharing

Data Type
Sharing Policy

KYB Verifications

Not shared unless explicitly made public by the verified organization.

KYC Attestations

Shared only in ZK format with requesting third-party platforms.

DISC Score Metadata

Public and queryable by platforms or developers.

Trovebook Entries

Never shared unless the user intentionally reveals or proves a submission.

Tythe is a pass-through validator, not a data processor or controller.

7. Cookies & Analytics

Tythe avoids traditional surveillance-based analytics. We use:

Mechanism
Purpose

Session Cookies

Used for login integrity and anti-spam protections.

On-Chain Analytics

Aggregated analysis of DISC Score distributions, not linked to personal data.

API Metadata Logs

Only request-level metadata is stored to prevent abuse, not user tracking.

No advertising cookies, fingerprinting, or metadata resale occurs.

8. Policy Updates

Material changes to this policy will be announced:

  • Via the tythe.tech homepage

  • Onchain announcements via TRIS-linked messaging

  • Optional email notice (if user subscribes)

Continued use of Tythe after changes implies acceptance.

9. Contact Us

For inquiries related to privacy, compliance, or data protection:


“For the Lord sees not as man sees: man looks on the outward appearance, but the Lord looks on the heart.”

— 1 Samuel 16:7

Last updated