Your proposal, kept private
Privacy
The business that prepared your proposal is responsible for the property information it enters. Contact your proposal issuer using the contact details provided with your quotation to ask about access, correction, retention or deletion.
Information used
We store the proposal title, installation address, selected equipment, energy assumptions, calculated results and creation date. Expanded proposals also store itemised prices, grant amounts and conditions, financial assumptions and projections, issuer details, services, warranties, installation notes and payment terms. These details are visible to anyone holding the customer link. Avoid including unnecessary personal details or bank information in proposal titles or notes.
When staff request Google roof insights by address, the entered address is sent to Google Geocoding API and the resulting coordinates to Google Solar API. Manually selected coordinates bypass Geocoding and are sent directly to Solar API; the entered address remains the proposal label. A saved Google-based commercial proposal incorporates the relevant generation estimate and reference roof metadata. Visual proposals also contain fixed aerial/sunlight images, panel positions, dimensions, pitch and calculated per-panel yields. Raw raster grids are not stored as a reusable roof database. See Google's Privacy Policy.
If staff open the optional interactive satellite map, their browser connects directly to Google, sharing network information including its IP address and requested map views. The customer proposal does not load that SDK or request fresh Google data; saved images are served with the proposal.
Hosting and access
The application and saved proposals are hosted using Cloudflare Workers and D1. Staff access requires a shared password. A strictly necessary, HTTP-only session cookie lasts up to 12 hours. Hashed session tokens and short-lived, keyed login-rate-limit identifiers are stored to protect access. This application does not add advertising or analytics trackers.
Sharing and retention
Customer links contain random, unguessable identifiers and do not require a login. Anyone who receives or forwards a link can view that proposal. Pages request that search engines do not index them, but this is not a substitute for keeping links private.
Proposals are retained until the issuer deletes them. Staff can revoke a link, which prevents future access but does not delete the database snapshot or copies already downloaded, printed or shared. Ask the issuer for deletion where appropriate.