Privacy Policy
Effective Date: September 11, 2026 • Version 1.2
1. Architectural Data Boundaries
Our core protocol is engineered under the principle of cryptographic data minimization. We distinguish strictly between two domains:
- Client-Side Private Witnesses (w): Private inputs (e.g., negotiation ceilings, auth credentials, prompt context) reside solely in client RAM. They are never transmitted over network protocols and are wiped (0x00) immediately post-SNARK synthesis.
- Public Protocol Receipts (x): The compact ~580-Byte cryptographic proof (π) and public state commitments relayed to Midnight Network Preprod (Contract:
6d2d6032...) contain zero private payload data.
2. Information We Process for Operations
When you subscribe to Developer, Pro Agent ($49/mo), or Scale tiers, we process minimal operational billing metadata:
- Payment Data: All financial transactions are processed directly by Stripe, Inc. Rohan Protocol never stores raw credit card numbers or banking credentials.
- API Key Telemetry: We record aggregate rate-limit counters (e.g., requests per 24 hours) tied to your pseudonymized API key to enforce tier quotas and prevent DDoS abuse.
- Infrastructure Logs: Transient edge web server logs (IP address, user agent) are retained for 72 hours solely for firewall routing and indirect prompt-injection neutralization.
3. Midnight Blockchain Ledger Immutability
Proof commitments anchored to the Midnight Blockchain become part of a decentralized, cryptographically shielded ledger. While state pointers are immutable, they reveal no identifiable human information, IP addresses, or readable agent intents.
4. Rights & Contact
Under GDPR, CCPA, and global privacy standards, you maintain rights regarding your billing metadata. For inquiries or data deletion requests, contact our Data Protection Officer at privacy@rohanprotocol.network.