Legal

Privacy Policy

Last updated: 27 May 2026

Short version

Zoza is designed to be server-blind. We can't read your messages, your AI prompts, your browsing history, your wallet contents, or your trading positions. Most of the time we know nothing about you except that an opaque Ed25519 public key has paid for some credits. Razorpay knows your email and payment details — we don't.

1. What we collect

From the website (zoza.world)

• Standard Cloudflare access logs (IP, user agent, requested URL, timestamp). Retained for at most 7 days for abuse mitigation, then deleted.
• No analytics scripts. No Google Analytics. No Meta pixel. No third-party tracking.
• No cookies set by us.

From the buy flow

• When you buy a redemption code, Razorpay collects your email and payment details (card / UPI / bank). Razorpay holds this — we don't. See Razorpay's privacy policy.
• We store the Razorpay payment_id + order_id, the amount in INR paise, the product SKU, the SHA-256 hash of the redemption code, and the issuance + expiry timestamps. We do NOT store the raw code (only its hash) and we do NOT store your email.
• When you redeem a code inside Zoza, we record which Ed25519 pubkey redeemed it. This pubkey is opaque to us — it isn't linked to your email, your name, your IP, or your payment method.

From the browser / app

• Your Ed25519 identity key is generated locally and never leaves your device.
• Wallet keys, message keys, browsing history, bookmarks, and form data stay on your device. We see ciphertext at most (for the optional encrypted sync).
• When you use the paid AI proxy, the API request transits our edge worker on the way to Anthropic. We record (a) the input + output token counts, (b) the cost in USD, (c) the model name, (d) the timestamp, (e) your identity pubkey for billing. We do not store the prompt content or the model's response.
• When the trading agent runs, the cycle outcome (regime label, candidate count, stage-1 survivor count) is logged for operator debugging. The LLM prompts themselves are not stored.

From the push notifications surface

• If you opt into trade-proposal push notifications, we store your FCM token (Android) or APNs token (iOS) tied to your identity pubkey. We use these tokens solely to deliver the proposal push.
• You can unregister at any time from the in-app settings; the token is purged from our database.

2. What we share

• Razorpay — payment processing. They receive payment details directly from your browser; we forward order metadata only.
• Anthropic — for paid AI requests, the prompt content transits our edge to Anthropic's API. We do not retain it; Anthropic's retention policy applies.
• FCM / APNs — for push notification delivery to Android / iOS devices.
• Cloudflare — our hosting provider for zoza.world and api.zoza.world.
• We do not sell, rent, or trade your data. We do not run an ad network.

3. Brokerage credentials

If you link a broker (e.g. Binance) to Zoza for automated trade dispatch, your broker API key + secret are encrypted using the operator KMS before they enter our database. The unsealed credentials exist only briefly in the cloud agent's memory at dispatch time. We refuse to accept broker credentials with withdraw scope; only trade-execution scope is supported. Revoking a broker connection wipes the encrypted credential from our database.

4. Your rights

• Access — email [email protected] citing your Razorpay payment ID; we can confirm what we've recorded against your purchase.
• Deletion — uninstalling the browser deletes everything on-device. Your purchase ledger entry (pubkey + amount + timestamp) is retained for audit / refund purposes; the pubkey itself is meaningless without your device.
• Refund — see Refund Policy.

5. Security

Sensitive data is encrypted in transit (TLS) and at rest (D1's underlying SQLite encryption + KMS-sealed broker credentials). Vulnerability disclosures: security.txt or email [email protected].

6. Children

Zoza is not directed at users under 18 (or the age of majority in your jurisdiction). We do not knowingly collect data from children.

7. Changes

Material changes to this Policy will be posted here with an updated "Last updated" date.

8. Contact

Privacy questions: [email protected]. General support: [email protected].