SunsteadSUNSTEAD CONNECT / EARLY ACCESS
Data & privacy.
What the current service stores, where it lives,
and how your connections work.
Your Pi remains the source.
Your local Sunstead Pi collects equipment readings and keeps your energy history. Remote dashboard requests are relayed to that Pi. The cloud account database does not store your detailed telemetry history.
The Pi must be online for remote viewing. Local access on your home network works independently of Google sign-in and Sunstead Connect.
What your account saves.
Google sign-in provides a verified identity, name and email address. Sunstead stores that account information, login sessions and the viewing connections you explicitly save, including their names and device identifiers.
Google access and refresh tokens are not stored. Signing in does not automatically connect equipment or grant access to another person’s Pi.
Your connection choices.
You can remove saved systems from your account. Removing an entry does not delete the Pi’s history or revoke other browsers. Manage and revoke remote access from Remote & displays on your primary Pi.
Remote access currently provides viewing permissions. Equipment changes require your authorized local connection. Apple sign-in and full remote equipment controls are not available in this version.
The services involved.
Google handles authentication. Render hosts Sunstead Connect. MongoDB stores cloud account and connection information.
Remote dashboard traffic passes through Sunstead Connect. TLS protects data in transit, but the relay operator can access relayed telemetry; this connection is not end-to-end encrypted against the operator.