Privacy and Data Handling
The current CitizenSolar public release is a static frontend focused on documentation, commercial surfaces, and partner conversion. Its data-handling posture is intentionally narrow and should be described precisely.
Privacy Surface
Privacy, browser-state usage, and public-release data handling should stay explicit and sober
Use this page to explain what the static release does and does not collect, store, or expose.
Privacy statements stay specific to the current public release.
No enterprise-grade storage or analytics claims are implied where they are not implemented.
Audience
Core Focus
Best Next Route
What To Review First
Quick Route Actions
Open the next commercial surface, move into buyer guidance, or start a scoped inquiry without leaving the current page.
Jump To Section
Privacy Scope
What The Public Release Does Today
The site provides public-facing pages, documentation, contact-intake flows, and optional local browser state for theme and session preferences. It is not presented as a live operational energy-management backend.
- • Static public pages and downloadable briefs
- • Email-draft contact flow for pilot, partner, technical, and disclosure requests
- • Local browser storage for theme and limited user-interface preferences
- • Illustrative or preview data in some legacy reference surfaces
What Is Not Claimed
This release does not claim enterprise analytics, large-scale telemetry collection, consumer-facing settlement records, or a public identity-processing backend. Future operational deployments may require additional privacy controls and documented data-processing agreements.
- • Google tag / GA4 measurement may be used for aggregate site analytics and search diagnostics
- • No claim of operational device telemetry storage through the public site
- • No consumer account data platform is claimed here
- • Operational deployments may require additional contracts, controls, and data-processing terms
Contact And Disclosure Handling
If a user opens a contact flow, the site prepares a direct email draft based on the stated inquiry. Security disclosures should follow the private reporting path first.
- • Pilot and partner inquiries are handled through the documented email-draft contact model
- • Security issues should be reported privately first
- • The public release keeps data-handling statements bounded to current behavior
- • Future operational systems may introduce additional logging and role-based access controls