Skip to main content

Last updated: 18 August 2026

Privacy Policy

This policy covers both the Helios PV Dashboard web application and the Helios Inverter Sync browser extension. It explains what data we collect, where it goes, and what we never do.

1. The browser extension — data stored on your device

Everything below lives in your browser's local extension storage. It never leaves your device except where stated in Section 2.

ItemWhat it isWhy it's needed
System configurationYour Helios system UUID(s), inverter portal identifier(s) (e.g. Aurora Entity ID, Fronius pvSystemId, SolarEdge Site/Device ID), provider name, optional system label, and backfill day countIdentifies which systems to sync
Authentication sessionA short-lived JWT issued by Helios when you sign inAuthenticates uploads to your account
Sync metadataTimestamp of last successful sync, last synced date, last error messageDisplayed in the popup; decides whether to auto-sync on browser start
Note: No inverter portal credentials are ever stored. The extension uses your existing browser session (cookies already set when you are logged in to the portal). Your portal username and password are never read, captured, or stored.

2. The browser extension — data sent to Helios servers

The extension sends the following to the Helios backend:

ItemWhenPurpose
Solar energy production dataDuring each syncUploaded to your account so the soiling model can calibrate to your real generation data
Helios authentication tokenWith every requestVerifies you own the system being uploaded to
System UUIDIn the upload URL pathIdentifies which system the data belongs to
Subscription tier checkBefore sync startsConfirms your account is on the paid tier

No data is sent to any third party. The only destination is the Helios backend and the database that backs it, both operated by the Helios service.

3. The browser extension — portal access

During a sync the extension calls your inverter portal's own internal data API directly — the same API the portal's own dashboard chart uses — using the session cookies already set by your logged-in browser tab:

  • Calls the portal's data API for the dates being synced.
  • Reads the JSON response (solar energy production values).
  • For Aurora Vision only, may open a background browser tab to your existing Aurora session if you don't already have one open, purely to get an authenticated context to call the API from — it does not interact with anything on that page.

Nothing is downloaded to your computer, and no clicking, form-filling, or navigation of the portal's UI is performed. Beyond the energy production values themselves the extension does not read, store, or transmit any other information from the portal — no account settings, personal details, or other system data.

4. The browser extension — permissions

PermissionWhy it's needed
storageStore local configuration and auth session
tabsFind or open a tab on the inverter portal so sync requests run with an authenticated session (Aurora Vision only), and to auto-detect the Fronius pvSystemId on first use
alarmsSchedule the daily automatic sync
notificationsShow a desktop notification when auto-sync completes or fails
Host access to inverter portal domainsRequired to call each portal's own data API and read the response
Host access to Helios APIRequired to authenticate and upload data

5. The web application

When you use the Helios dashboard we collect:

  • Account data — email address and password (hashed, never stored in plain text) provided during registration.
  • System configuration — panel details (tilt, azimuth, area, location) you enter during onboarding.
  • Uploaded CSV data — energy production history sent by the extension or uploaded manually.
  • Computed results — soiling ratios, cleaning recommendations, and performance metrics derived from your data and public weather/air quality APIs.

We use PostHog for anonymous product analytics (page views, feature usage). No personally identifiable information is attached to these events.

6. What we never do

  • Store your inverter portal username or password.
  • Read anything from inverter portal pages beyond daily energy production data.
  • Sell, rent, or share your data with advertisers or data brokers.
  • Track your browsing history.
  • Read data from any website other than the configured inverter portal and the Helios API.

7. Supported inverter providers

The extension currently supports:

  • Aurora Vision
  • Fronius Solar.web
  • SolarEdge (MySolarEdge monitoring)

All providers follow the same model: only daily energy production data is accessed via the portal's own data API, no credentials are stored, and data is uploaded exclusively to your Helios account. All permissions needed for a new provider will be described in the updated version of this policy.

8. Data retention and deletion

Data on Helios servers is retained for as long as your account is active. You can delete your account at any time from Settings → Account — this permanently removes all your data from our servers.

To remove all local extension data, click Disconnect in the extension popup, or uninstall the extension. Both wipe all data from browser local storage.

9. Contact

Questions about this policy? stavris97@gmail.com