What stays local in a solar monitoring system?

Follow the equipment data first

The Sunstead device at the property collects supported equipment readings and keeps energy history locally. Local network viewing works independently of Google sign-in and Sunstead Connect.

That arrangement still needs a functioning host and appropriate local access. A locally stored history is not automatically backed up, and a browser satellite is not a separate archive. Plan recovery for the host if the history matters to you.

Trace optional remote viewing

Remote dashboard requests pass through Sunstead Connect to the property device. The host must remain powered and connected to the internet. The cloud account database does not store the detailed telemetry history.

Traffic is protected in transit with TLS, but the relay operator can access relayed telemetry. The current connection is not end-to-end encrypted against that operator. This distinction belongs in any decision about enabling remote access.

Separate identity from measurements

Google sign-in supplies verified identity information. Sunstead stores account details, sessions and saved viewing connections, plus relevant invitation and membership records. Signing in does not automatically connect equipment or grant access to another property.

Order records are another category, including selected configurations and fulfillment information. Buying a monitor does not give the buyer access to someone else’s installation. Review the current data and privacy page for the full descriptions and retention details.

Treat website analytics as its own choice

Optional public-site analytics stays off until accepted. It measures website activity such as page visits and shop interactions rather than equipment readings. The public website’s Cookie settings control that choice in the browser.

Accepting website analytics is not a requirement for local monitoring, nor is declining it a way to revoke an invited viewer. These controls affect different data paths. Keep them separate when helping another household member manage access.

Use a privacy worksheet for your installation

• Where is detailed history stored, and what is backed up?
• Is remote viewing enabled, and through which service?
• Who owns the saved connection?
• Which people have invited or independently paired access?
• Which browsers retain signed-in sessions?
• What website analytics choice has each browser made?

Review the list when a device changes hands or a caretaker leaves. Removing invited access stops future reads through that membership; it cannot recall information already downloaded. Independent connections require their own review.

A clear data map avoids both extremes: assuming everything stays on the Pi because collection is local, or assuming every reading is permanently stored in the cloud because a phone can view it remotely.