Privacy policy

Last updated November 17, 2026

1. Who we are

Personal data controller: the developer of the IVORX app, hereinafter “IVORX”, “we”.

This policy applies to the IVORX app for Android and iOS, the web dashboard ivorx.pro/app, the website ivorx.pro, the IVORX Hub and IVORX Panel devices, and the IVORX cloud service.

Privacy contact: .

2. Summary

3. What data we process and why

3.1. Data on the phone and on the hub

The app stores on the phone the hub’s address in the local network, access tokens for the hub and panels, panel keys, and a copy of the data from section 3.3, so that it works during a blackout without internet. The hub’s address, tokens, panel keys and passwords never leave the phone and are not sent to us. The hub stores the name and password of your home Wi-Fi network, the tokens of connected phones and panels, settings, energy system history, the event log and, if you set up Home Assistant, the address and login credentials of the MQTT broker. This hub data is not sent to us unless you turn on remote access (section 3.4).

Without signing in, the app and the web dashboard open only the demo: a sample home with simulated data. Nothing about the demo is sent to us.

The phone or the hub also accesses the internet in these cases:

3.2. Account

To use the app and the web dashboard, you need to sign in with Google, Apple or a one-time email code; without signing in, only the demo is available (section 3.1). When you sign in, we receive and store:

Why: so that you can sign in, see your sites and hubs from any phone or browser, and store the settings of your sites (section 3.3). When you sign in by email, we send a one-time code to your address.

3.3. Site settings in the cloud

When you are signed in, the app and the web dashboard store the settings of each of your sites in the cloud database. The members of that site have access to them:

Separately for you, we store your notification settings for each site, your language and whether the demo is hidden.

The phone keeps a copy of this data (an offline cache) so that it works during a blackout without internet, and syncs it with the cloud when it is back online. The hub’s address in the local network, the hub access token, panel keys and passwords never reach the cloud. Why: so that a site has the same settings on all your phones, in the web dashboard and for the site’s members.

3.4. Remote access: a hub linked to the account

The owner turns on the cloud on the hub explicitly, at home, in the app. The hub then contacts our server by itself over HTTPS every 15-30 seconds (every 3 seconds while you are viewing it remotely) and sends:

The hub does not send the Wi-Fi password, the MQTT broker address and login credentials, or the voltages of individual battery cells.

We also store the commands that you or members of your site sent remotely (who, when, what) and the desired settings. Only a limited set of commands is allowed from the cloud, and the hub checks each one itself.

Why: to show the state and history when you are away from home, to pass your commands to the hub and to report the result.

3.5. Firmware updates

For updates, the hub and the app (when you are signed in) read the list of releases from our server and download a signed image. We store which version was offered to the device and the installation result. Why: to deliver updates and detect failed ones.

3.6. Outage schedule

If you selected the “Automatic” schedule, the app sends the region and the group to our server function. The schedule data comes from an open, unofficial mirror of DTEK data.

If you look up your group by address (Kyiv, Dnipropetrovsk region), the app sends our function the name of the town or city, the street and the house number that you enter. The function forwards this request to the public Yasno service on behalf of our server, without your identifiers and without your IP address. We do not store the address on the server; responses are temporarily cached in the function’s memory (for up to 1 day) without any link to you. The group found and the address label are stored in the site settings in the cloud and in the copy on the phone (section 3.3).

3.7. Notifications

Notifications about power, state of charge and alarms are created by the app itself on the phone from the hub’s data. We do not use push servers and do not collect push notification tokens.

3.8. Bluetooth

The phone connects over Bluetooth directly to your battery’s BMS (JK, Daly, JBD) to read its state, and to the hub or panel during setup to pass the Wi-Fi name and password. The password is transmitted encrypted. The battery state and the Wi-Fi password are not sent to us. If you add a BMS to a site, its name, model, Bluetooth address and alarm thresholds are stored in the site settings (section 3.3). On Android 11 and earlier, the system requires location permission to scan for Bluetooth devices; we do not receive or store your location.

3.9. Local network

On iOS, the “Local Network” permission is required to find the hub and panels in your home network and connect to them. In your home network, the app communicates with the devices directly.

3.10. Home Assistant

The Home Assistant integration works through an MQTT broker in your network. The broker address and login credentials are stored only on the hub and do not reach the cloud.

3.11. Website and web dashboard

The website and the web dashboard are hosted on GitHub Pages. Like any web server, GitHub processes the IP address and technical request data to display the page. The website does not use cookies, analytics or third-party fonts. The web dashboard stores the sign-in session in your browser’s storage (localStorage).

3.12. Anonymized statistics

To develop the product, we count aggregate numbers: how many hubs run each firmware version, how many are active, which inverter and BMS models are used, update results, the number of outages per day, and the number of accounts and sites. The statistics contain no names, addresses, site names or identifiers; groups of fewer than 5 devices are merged.

3.13. What we do not collect

Device location, contacts, photos, microphone, advertising identifiers, browsing history, payment data.

4. Legal bases

We process data in accordance with the Law of Ukraine “On Personal Data Protection” and, for users in the EU and EEA, also in accordance with the EU General Data Protection Regulation (GDPR):

5. Where data is stored

6. Who else processes data

We do not sell data or share it for advertising. Data is processed only by the providers without which the service cannot work:

ProviderPurposeData
Supabase, Inc. (on Amazon Web Services infrastructure, EU region, Ireland)database, authentication, server functions, firmware storageall cloud data from sections 3.2-3.6
Google LLCSign in with Google (if you chose it)the fact of signing in to the app, email, name
Apple Inc.Sign in with Apple (if you chose it)the fact of signing in to the app, email or hidden address, name
Resend, Inc. (EU region)sending emails with the sign-in codeemail address, email text
GitHub, Inc.hosting the website and the web dashboardIP address and technical request data
Yasno (operator of the public schedule service)looking up the outage group by address (at your request)town or city, street, house; without your identifiers

Google Play and the App Store process download data and, with your consent in the phone settings, crash reports under their own policies.

Some providers are registered in the USA. Data transfers outside the EEA are based on the European Commission’s Standard Contractual Clauses or the EU-U.S. Data Privacy Framework. Supabase and Resend process data under their data processing agreements (DPA), which include the EU Standard Contractual Clauses; Resend is also certified under the EU-U.S. Data Privacy Framework.

We may disclose data if required by law or a court decision.

7. How long we keep data

DataRetention period
Account, profileuntil you delete the account
Site settings and your settings (section 3.3)until you delete the site or the account
Current hub state, diagnosticsonly the latest snapshot
5-minute history400 days
Event log90 days
Remote commands30 days
One-time hub linking codesvalid for 10 minutes, deleted 1 day after expiry
Firmware update recordsas long as the device is in your site
Sign-in sessionsuntil sign-out or session expiry
Server technical logsup to 1 day
Provider database backupsnone on the current plan; on a paid plan, daily backups are kept for 7 days

When you unlink a hub, it stops sending data immediately. Data already received from that hub remains in your site within the periods above and is deleted together with the site or the account.

8. Deleting your account and data

You can delete your account in the app (Account, “Delete account”), in the web dashboard ivorx.pro/app or by email. Step-by-step instructions: the “Delete your account” page.

Deletion is immediate and permanent. The following are deleted: the account and profile, your settings (section 3.3), your membership in sites, and sites where you are the sole owner, with all their hubs, state, history, log, settings and commands. A hub that was linked receives a refusal from the server and turns off the cloud by itself.

What remains:

9. Security

All connections to the cloud are encrypted (HTTPS/TLS); the hub verifies the server certificates against a pinned list of root certificates. Device tokens and linking codes are stored only as hashes. Access in the database is restricted by row-level security rules: each user sees only their own sites. Firmware is signed, and the hub will not install an unsigned image. The hub limits how often it writes to the inverter. No system is absolutely secure; if an incident affects your data, we will notify you and, where the law requires it, the supervisory authority.

10. Your rights

You have the right to:

To exercise your rights, write to from the address linked to your account. We will reply within 30 days and may ask you to confirm that the account belongs to you.

11. Children

The service is not intended for persons under 16, and we do not knowingly collect their data. If you believe a child has created an account, write to us and we will delete it.

12. Changes to this policy

We publish the new version on this page with a new date. We will notify you of material changes in the app before they take effect.

13. Contact

Email: