Privacy Protocols

1. The Privacy Covenant

At the Jandu Heritage Registry, privacy is not a feature; it is an institutional mandate. As a private registry for the diaspora, our business model is based on stewardship, not surveillance. We do not scan your correspondence, we do not harvest your metadata, and we never monetise your identity. You pay for the service so that your privacy remains the priority, not the product.

2. Data Stewardship (What We Oversee)

To maintain the integrity of your digital estate, we collect only the essential information required for authentication:

- Stewardship Credentials: Your name, existing contact email, and requested @jandu.net handle.

- Financial Records: All transactions are processed via Stripe. The Registry does not see, store, or have access to your full credit card details.

- Technical Logs: Basic technical data (IP addresses) is utilised by our infrastructure partner (Zoho) solely for security auditing and the prevention of unauthorised access.

3. Purpose of Processing

Your data is used exclusively for the maintenance of your digital estate:

 - To provision your private mailbox on the Jandu.net domain.

 - To facilitate secure billing and annual renewals.

 - To provide direct, human-to-human support from the Office of the Steward.

4. Institutional Infrastructure

We utilise world-class, enterprise-grade partners to secure your legacy. These entities are bound by strict data protection standards (including UK GDPR):

- Zoho Corporation: Our primary infrastructure for email hosting and data storage.

- Stripe, Inc: Our secure gateway for financial stewardship.

- Registry Systems: We use localised secure database tools to manage the Founding 180 ledger and reservation waitlists.

5. Retention & Continuity

- Active Stewardship: We retain your data for the duration of your membership.

- Right to Erasure: Upon the formal closure of a digital estate, all mailbox data is purged from Zoho’s primary servers within 60 days.

- The Registry Ledger: To maintain the historical integrity of the domain, we retain a record of "Allocated" vs. "Available" handles to prevent identity duplication.