# Privacy note

Plain language throughout. If anything here is unclear, write to us and we will fix the wording.

Version 1.7Updated 19 October 2026Change history

## The short version

**On the sensor**Appliance recognition happens on the sensor, not in our cloud.
**Protected**We measure electricity. Your data is protected and is not shared beyond the services that run Visiwatt.
**Never sold**We never sell your data, and it is not part of the business model.
**Your call**You can request a copy of your data or delete your account.

## What we collect

First, your account: name, email, the country we ship to, and the units you reserved. Second, energy data: the aggregate power drawn at your panel, the appliance events the sensor recognises, and the names you give them. Third, what you add in the app: your profile name and optional picture, home details such as the home’s name, the place you set for it, home type and number of occupants, the alert email addresses and family contacts you add, and your notification settings. We also keep technical records needed to run the service: app push tokens, sign-in sessions (device, app and system version, last IP address) and learned appliance templates.

A form on this site sends what you typed in it — your name, your email address and your message — to us, and we keep it so we can answer you. With it we record your browser’s user-agent string and a keyed hash of your IP address. Nothing from a form goes to a mailing list.

Depending on your phone and the feature you use, the app may request Bluetooth or nearby-device access for sensor setup, camera access for QR scanning, local-network access, and notification permission for alerts. Android setup permissions can also depend on the Android version: on Android 11 and earlier, Android also requires location permission for Bluetooth scanning during setup, and the app does not read your phone’s location.

## Data on the sensor

Recognition runs on the sensor’s own chip. Measurement and recognition continue during an internet outage; stored readings can be uploaded after reconnection, within the sensor’s storage capacity. App history and remote alerts need connectivity. The cloud service handles energy readings and appliance metadata, and diagnostic recording can upload electrical waveform data.

Account access, history and shared household features use the Visiwatt cloud service. Sensor setup also uses local connectivity. The current release does not provide a local-only switch in Settings.

## Sharing

We share data with service providers that run the service for us. Our hosting provider runs the servers that hold the data described above. A storage provider holds our off-site backups, which are copies of our databases. Our email provider carries transactional messages, so it receives each recipient’s address and the message. Push notifications reach your phone through Apple Push Notification service on iPhone or Google Firebase Cloud Messaging on Android. Depending on how the app registered for notifications, our servers send them either directly to Apple or through Expo’s push service, which forwards them; whichever carries a notification receives your phone’s push token and the notification’s title, text and data. On iPhone, watchdog Live Activity updates go directly to Apple and include the watched appliance’s name and its alert state. Reservations take no payment, so no payment provider is involved.

For business pilots, the customer of record is the company. Site-level data is visible to the people they nominate, and we say so in the pilot agreement.

## Your rights

- **Export**Contact ilia.kamyshev@iesllc.ge to request a copy of your data. The current app has no self-service export.
- **Correction**Rename appliances in the app; teaching is available for devices the sensor does not recognise yet.
- **Deletion**Delete the account and we erase cloud copies within 30 days.
- **Objection**Write to ilia.kamyshev@iesllc.ge; we answer within 30 days.

## Cookies

These public pages set no analytics or advertising cookies and load no third-party scripts. We measure visits with our own analytics, which runs on our own server and sends nothing to another company. It stores no cookie and no IP address. A visitor is a short code that changes every day, so one person cannot be followed from one day to the next. We count page views, how long a page stays open, how far it is scrolled, where the visit came from, the country, the device and browser type, and which buttons and forms were used. We skip visits that send Do Not Track or Global Privacy Control, and visits from signed-in staff. Contact forms and reservations send the information you enter to Visiwatt so we can respond. Account and application services are separate from these public pages.

## Change history

- **19 October 2026 · v1.7**Described the website's own visit measurement: no cookie, no IP address stored, a visitor code that changes every day, what is counted, and the visits we skip.
- **2 October 2026 · v1.6**Listed the backup-storage and push-notification providers, including Google Firebase Cloud Messaging for Android, and what each receives. Removed the payment provider, because reservations take no payment, and the general statement about processor agreements. Listed the app, home and technical data we keep, the website form records and the Android location permission. Corrected the export description.
- **30 September 2026 · v1.5**Corrected permission, cloud-connectivity, export, diagnostic-recording and website-cookie descriptions. Clarified that offline measurement does not provide local-network alerts.
- **14 May 2026 · v1.2**Named our payment processor for pre-orders.
- **2 March 2026 · v1.1**First public version alongside the pre-order launch.

Write to [ilia.kamyshev@iesllc.ge](mailto:ilia.kamyshev@iesllc.ge) or use the [contact page](https://visiwatt.tech/en/contact). A person answers, usually the same day.

Source: https://visiwatt.tech/en/privacy