Draft privacy policy

Privacy should be plain to read.

This working draft describes the public Zenzo site and early-access request flow. It should be reviewed by qualified counsel and finalized with a designated privacy contact before general product availability.

Privacy Policy

Working draft — review before production useThis page is a transparent policy draft for Zenzo Beta, not a substitute for legal advice. It must be reviewed and finalized for the jurisdictions and actual product data practices that apply before general availability.

1. Scope

This Privacy Policy describes how Zenzo Beta handles information connected with the public Zenzo website, its documentation and policy pages, and the early-access request flow. It does not describe a future production application beyond the practices expressly stated here.

2. Information that may be processed

Zenzo may process information that a visitor chooses to submit through the early-access request flow, such as contact and application details. The public site may also cause service providers that deliver the page or an external form to receive technical information needed to operate their services, such as browser and network information.

CategoryExamplesWhy it may be used
Early-access informationDetails a visitor voluntarily provides in the linked request form.To evaluate access requests, communicate about the beta, and understand feedback.
Public-site delivery dataTechnical information normally generated when a browser loads a static site or third-party resource.To deliver the page, protect the service, and diagnose operational issues.
Feedback and correspondenceFeedback a visitor sends through an approved channel.To respond, improve the product direction, and maintain a record of the exchange.

3. How information may be used

Zenzo may use the information described above to administer the early-access program, communicate about product participation, maintain the security and integrity of the public site, understand product feedback, and meet applicable legal obligations. Zenzo’s policy is not to sell personal information or use public-site information for behavioral advertising.

4. External services and links

The public site uses external services to deliver resources and routes visitors to external destinations such as a request form and the public GitHub repository. Those destinations are governed by their own terms and privacy practices. When you leave the public Zenzo site, review the destination’s policies before submitting information.

5. Cookies and similar technologies

The static public Zenzo page does not intentionally set first-party advertising cookies. External services may use cookies or similar technologies under their own policies. You can control many browser-level preferences through your browser settings.

6. Sharing and disclosure

Zenzo may share information with service providers that support the public site or early-access workflow, where necessary to operate those services, comply with law, protect rights and safety, or respond to a valid legal process. Zenzo does not authorize providers to use personal information for unrelated purposes.

7. Retention and security

Zenzo aims to retain early-access and feedback information only for as long as reasonably necessary for the purposes described in this policy, unless a longer period is required by law. Zenzo seeks to use reasonable safeguards appropriate to the information and context, but no internet-based service can promise absolute security.

8. Your choices

Depending on where you live, you may have rights to request access to, correction of, deletion of, or information about certain personal data. Do not post sensitive personal information in a public repository issue. Zenzo will publish a dedicated privacy contact method before general availability; until then, use care when submitting any information through public channels.

9. Changes

Zenzo may update this policy as the beta and public site evolve. The current version will be posted on this page with an updated date. Material changes should be communicated in a manner appropriate to the context and applicable law.

10. Contact

For the current beta, refer to the official repository and public site to verify current contact channels. A dedicated privacy contact must be designated before general availability. Do not send sensitive personal information through a public GitHub issue.