Privacy
How Zana handles beta workspace data.
Zana collects only the information needed to run property-readiness workflows, invite helpers, show checklists, capture proof, and support operators during beta.
Last updated: June 19, 2026
This page is a practical beta privacy draft and should be reviewed by qualified counsel before broad commercial launch.
1. Information We Collect
Zana may collect account information, names, emails, phone numbers, property names, property addresses, market details, checklist items, schedules, helper invite status, task notes, proof photos or filenames, issue logs, messages, login/session data, and technical health or diagnostic information.
2. How We Use Information
We use information to provide the Zana software, authenticate users, create workspaces, invite helpers, display assigned checklists, support readiness workflows, troubleshoot the service, improve beta features, and communicate about account or support matters.
3. Helper Contact Data
Operators are responsible for having permission or another lawful basis before adding helper names, emails, phone numbers, scores, or notes. Zana uses helper contact data to create claim links, show helper status, and route assigned checklist access.
4. Sharing
Zana shares workspace data only as needed to operate the service: for example, an operator may see their property and helper records, and a claimed helper may see assigned checklist details. Zana may also use infrastructure providers for hosting, email, database, logging, and security.
5. Security
Zana uses role-based access, organization scoping, password hashing, secure session cookies in production, backend-only database credentials, and restricted direct database access. No system is perfect, so operators should avoid entering unnecessary sensitive information.
6. Cookies
Zana uses essential cookies to keep you signed in, protect your session, and operate the public demo. These cookies are required for the service to work and are not used for advertising. You can clear cookies through your browser settings; signing out removes the session cookie from your device when your browser accepts the logout response.
7. Data Retention
During beta, Zana retains workspace data while accounts are active or as needed to test, improve, secure, and support the product. Operators can request deletion of beta data by contacting Zana.
8. Your Choices
Users can request access, correction, or deletion of their beta account data by contacting Zana. Some records may be retained when needed for security, audit, legal, or dispute-resolution purposes.
9. Children
Zana is not intended for children or for collection of children’s personal information.
10. Contact
For privacy requests, contact the Zana operator through the email address used for your beta workspace invitation.
Data Principle
Collect less than you could.
Zana should store enough information to coordinate and document readiness work, but operators should avoid entering unnecessary personal, financial, medical, government-ID, or highly sensitive details.