Privacy Policy
NEUS Network, Inc. ("NEUS," "we," "us," or "our") enables cryptographic proof of facts without storing or processing personal data. This document outlines our data handling practices, privacy protections, and regulatory compliance approach.
What NEUS Is and Is Not
What NEUS Is
Technical Infrastructure: A protocol for creating cryptographic proofs of verifiable claims
Verification Framework: Tools for developers to integrate verification into applications
Zero-Knowledge System: Technology that proves facts without revealing underlying data
Decentralized Network: Protocol that operates across multiple blockchains
What NEUS Is NOT
Identity Provider: We do not verify, validate, or store personal identity information
KYC Service: We do not perform Know Your Customer verification or compliance services
Data Processor: We do not collect, store, or process personally identifiable information (PII)
Financial Service: We are not a Money Service Business (MSB) or regulated financial institution
Centralized Authority: We do not make authoritative claims about user identity or compliance
What We Collect
Technical Analytics (No Personal Data)
API Usage Metrics: Request counts, response times, error rates
Wallet Addresses: Public blockchain addresses (already public information)
Request Metadata: Timestamps, request types, success/failure status
Network Information: Chain IDs, transaction hashes (public blockchain data)
What We DO NOT Collect
Personal Information: Names, emails, phone numbers, addresses
Browsing History: Website navigation or tracking across sites
Private Keys: Wallet credentials or seed phrases
Content Data: Original content from verification requests (unless explicitly public)
Cross-Site Tracking: No tracking pixels or cross-domain cookies
Cookies
Essential Cookies Only
NEUS Network uses only essential cookies required for service functionality:
Session Management: Temporary session tokens for API requests
Security: Anti-CSRF tokens and rate limiting
Performance: Load balancing and service optimization
No Tracking Cookies
We do not use:
Advertising cookies
Social media tracking cookies
Third-party analytics cookies
Cross-site tracking technologies
Data Processing
Legal Basis
Legitimate Interest: Technical analytics to maintain and improve services
User Consent: Explicit consent via wallet signatures for verification requests
Legal Obligation: Compliance with applicable laws and regulations
Data Retention
API Logs: 30 days for technical debugging and security monitoring
Analytics Data: Aggregated, anonymized data retained indefinitely
Verification Proofs: Stored according to user privacy settings
Temporary Tokens: Deleted immediately after use
Third-Party Services
Analytics Providers
We may use privacy-focused analytics services that:
Do not collect personal information
Provide aggregated usage statistics only
Comply with privacy regulations
Allow opt-out mechanisms
Blockchain Networks
Public Data: All blockchain interactions are inherently public
No Control: We cannot control or delete on-chain data
User Choice: Users choose what data to put on-chain
Your Rights
Data Control
Minimal Collection: We collect only essential technical data
User Ownership: You control your verification data through wallet signatures
Opt-Out: Discontinue service use at any time
Transparency: All data practices are publicly documented
Privacy Settings
Private by Default: All verifications are private unless explicitly made public
Granular Control: Choose exactly what data to share
Wallet-Based: No accounts or profiles to manage
International Compliance
GDPR (European Union)
Minimal Data Processing: No personal data collected by design
Legal Basis: Legitimate interest for technical operations
User Rights: Data minimization principles applied throughout
CCPA (California)
No Personal Information: No data subject to CCPA collected
No Sale of Data: We do not sell or share personal information
Transparency: All data practices are publicly documented
Third-Party Integrations
OAuth Providers (Coinbase, GitHub, Discord, etc.)
Purpose: Verify user authentication with third-party services
Data Flow: Temporary tokens exchanged for user verification status only
Storage: No long-term storage of OAuth credentials or user data
Legal Basis: User consent for each verification request
Identity Verification Services
NEUS integrates with existing KYC providers (like Coinbase) but never receives or processes the underlying identity data
We only receive confirmation that verification occurred, not the personal details
All identity verification is performed by the third-party under their own regulatory framework
Zero-Knowledge Privacy Protection
Technical Implementation
ZK-STARK Proofs: Mathematical proofs that verify claims without revealing data
Circuit Privacy: Verification logic runs in isolated, zero-knowledge virtual machines
Input Privacy: Sensitive data never leaves the user's control
Output Minimization: Only essential verification results are disclosed
Privacy Guarantees
Personal data is never transmitted to NEUS servers
Verification occurs without data exposure
Proofs can be verified by anyone without accessing underlying information
Users maintain full control over their data at all times
Regulatory Compliance
GDPR Compliance (EU)
No Personal Data: NEUS processes no data subject to GDPR protections
Right to Erasure: Not applicable as no personal data is stored
Data Portability: Users control their verification proofs directly
Consent: Required for each verification action via wallet signatures
CCPA Compliance (California)
No Personal Information: No data subject to CCPA protections is collected
No Sale of Data: No personal information is sold or shared
Transparency: All data processing is publicly documented
International Compliance
Protocol designed to comply with major privacy regulations globally
No cross-border data transfers of personal information
Decentralized architecture reduces regulatory compliance burden
User Rights and Control
Data Control
User Sovereignty: Users maintain complete control over their data
Verification Choice: All verifications are initiated by explicit user action
Proof Ownership: Users own and control their verification proofs
Revocation: Users can choose not to use proofs at any time
Transparency
Open Source: Verification logic is publicly auditable
Protocol Documentation: All processes are publicly documented
Audit Trail: Verification events are recorded on public blockchains
Security Measures
Technical Security
Wallet-Based Authentication: No passwords or account credentials
Cryptographic Signatures: All actions verified via digital signatures
Rate Limiting: Protection against abuse and spam
Circuit Breakers: Automatic protection against service failures
Operational Security
Minimal Data Collection: Principle of data minimization applied throughout
Encrypted Communications: All data in transit is encrypted
Access Controls: Strict controls on system access
Regular Audits: Continuous security assessments
Children's Privacy
NEUS does not knowingly collect or process any information from individuals under 13 years of age. Our protocol requires wallet-based authentication which generally requires users to be of legal age in their jurisdiction.
Changes to This Policy
This privacy policy may be updated to reflect changes in our practices or legal requirements. Updates will be posted on our documentation site with revision dates. Continued use of the protocol constitutes acceptance of any changes.
Contact Information
For questions about this privacy policy or data handling practices:
Privacy Inquiries: [email protected]
Documentation: https://docs.neus.network
GitHub Issues: For technical questions about privacy implementation
General Support: [email protected]
Mailing Address: NEUS Network, Inc. 1111B S Governors Ave STE 39950 Dover, DE 19904, USA
Legal Disclaimer
This privacy policy is provided for informational purposes and does not constitute legal advice. Users should consult with qualified legal counsel regarding their specific compliance requirements and obligations.
Key Principle: NEUS is designed around the principle that the best way to protect user privacy is to never collect personal data in the first place. Our zero-knowledge architecture ensures that privacy protection is built into the technical foundation of the protocol.
Last updated
Was this helpful?