SolarRoof.asiaPrivacy is part of the product.
What SolarRoof.asia processes
When you request an estimate, SolarRoof.asia processes the postal code, address, coordinates, and place identifier needed to locate the building and request roof information. If you are signed in, a saved history record contains the selected address, coordinates, and compact estimate summary so you can reopen the search.
Property and solar data
Signed-in history stores a compact summary such as roof area, maximum panel count, system size, annual energy, imagery date, and quality. It does not store raw Google responses, satellite imagery, map tiles, or roof/panel geometry. History is retained for up to 365 days and can be deleted from the account page; reopening a record requests a fresh provider analysis.
Language preference
SolarRoof.asia stores an English or Japanese language preference in an HTTP-only cookie for up to one year. The cookie contains only the selected language code.
Contact requests
If you request a consultation, SolarRoof.asia stores the contact details, planning answers, and the property context you explicitly consent to share. A configured notification channel may receive that compact context so an installer can review the right property. Raw provider geometry is not shared.
Google sign-in
If you choose to sign in with Google, SolarRoof.asia receives your Google account identifier, name, email address, and profile image. Google authentication tokens are exchanged on the server and are not exposed to the application’s browser code. SolarRoof.asia uses an HTTP-only signed cookie to maintain the session.
Service providers
SolarRoof.asia may use Google Identity for optional authentication, Google Maps Platform for location, maps, and solar information, Resend for email delivery, and Railway for application hosting. Each provider processes information under its own terms and privacy policy.
Operational security
Logs should exclude full addresses, exact coordinates, API keys, provider response bodies, and email content. Short-lived, non-identifying request information may be used for abuse prevention and service reliability.
Before production launch
Replace this draft with the operating company’s legal identity, contact details, retention periods, applicable regional rights, and final counsel-approved terms before collecting real customer data.