Wiggle App Privacy Notice

Version 2026-10-25

A shorter notice, reordered so each point is said once. What we collect, why and for how long is unchanged.

Who is responsible

NRB Tech Ltd is the controller of personal information processed for the Wiggle app and service. Company number 11590173; registered office Fairleigh, Coldhill Lane, New Mill, Holmfirth, West Yorkshire, HD9 7JX. Our ICO registration reference is ZC196238. For privacy questions or to use your rights, contact support@wiggle.energy. The website privacy notice covers website forms and enquiries.

In this notice, an owner is a household owner and a member is anyone in the household, owners included.

Your account and household

We collect your name, email address, household names, memberships, preferences, and the records we need to sign you in: depending on how you sign in, a password hash, passkey public-key information or a Sign in with Apple identifier. We do not receive your Face ID or Touch ID data. We record which terms you accepted and which privacy notices you acknowledged. If you sign in on an iPhone or Android phone, the app saves your email address and how you signed in to your own iCloud or Google account, so that a new phone can suggest them; Wiggle cannot read that copy.

We use this to provide the account and household service you ask for, based on performance of our contract with you. We keep proportionate sign-in and security records in our legitimate interest in protecting accounts and preventing misuse.

Your energy supplier

When an owner connects a supplier, we get the information described on its connection screen. This can include account, property and meter identifiers, equipment information, past and current energy readings, tariffs, billing or cost evidence, and supplier-managed charging plans and activity. From these we calculate estimates and modelled figures, which the app labels as such. Detailed readings can show patterns of household activity, including when people may be at home.

We use this to provide the monitoring, history and explanations you ask for, based on performance of our contract. The connection permission covers that use only, not unrelated purposes.

While Octopus sign-in is not available, an owner connects Octopus with an Octopus API key. We do not ask for your Octopus password. The app sends the key over an encrypted connection and then clears it. We store it encrypted, with its encryption keys kept apart from database records, and use it only as the Octopus entry of the Connected services list describes. If an owner allows it, that includes sending Octopus the smart-charging changes a member asks for; we record who asked and what Octopus answered. We never use the key to change your Octopus account or tariff.

Only the owner who provided a key can reveal it in the app, and only after confirming who they are each time with a passkey, their password or Sign in with Apple. We record each reveal, email that owner and limit how often it can happen. That owner can also use the key for another household they own; each household keeps its own encrypted copy. Disconnecting Octopus removes our usable copy but does not cancel the key at Octopus; to do that, make a new API key in your Octopus account.

Linked appliances

An owner can link appliances such as an electric car, EV charger, home battery, solar inverter, heat pump or heating system, or energy meter. Wiggle links each one through Enode, a device-connection service, or directly with the manufacturer's online service. The Connected services list names each service, what Wiggle sends and receives and where it is processed. It is in the app under About & legal and on the web beside this notice, and the screen before you connect shows that service's entry.

Through Enode, the owner signs in to the manufacturer's account in Enode's linking screen; Wiggle never receives that password. Enode keeps the manufacturer connection and gives Wiggle information about the appliances you choose. Some manufacturers ask you to confirm a device over Bluetooth while linking; the app uses Bluetooth only for that step. We do not ask for location permission. If Enode provides a location, a vehicle identification number or a serial number, we remove it.

Directly, the owner enters what the manufacturer needs to identify the system, such as a serial number, a check code or a system ID, and we send it only to that manufacturer. The manufacturer then asks the system's registered owner to confirm by email, for example with a code to enter in the app or a request to approve; Wiggle does not receive that email. We keep the system's identifier with your household while the connection is waiting or active, and the app shows only its last four characters. We do not store check codes or verification codes. Direct connections are read only.

What we receive: the manufacturer, device type, make, model and name, whether the device can be reached, and readings and settings such as charge level, charging or discharging power, whether a car is plugged in, solar generation, battery state and capacity, temperatures, heating targets and modes, and a meter's power flows. For a direct connection, we read current readings as often as the list says and record each when it arrives; about once an hour we also read recent readings, to fill any gap, for example while the system or Wiggle was offline. These readings join your household's appliance history. Unless an owner turns it off, a linked meter's grid readings can also serve as the household's grid readings.

We use this to show appliance readings and history beside your household energy information, based on performance of our contract. Manufacturers are independent controllers of what they hold in their own accounts and services, including any email they send, under their own privacy notices.

Changing appliances. Enode's linking screen asks for permission to read the appliance and, where the manufacturer supports it, to change it: starting and stopping charging for a car or EV charger, a home battery's operation mode, a solar inverter's power limit, and a heating or cooling appliance's mode and temperature. We ask then because Enode cannot add a permission to an existing connection. Holding a permission is not using it: Wiggle changes an appliance only if that change was allowed when linking and a member asks for it, never on its own. We send the change to Enode, which passes it to the manufacturer. We record who asked, the setting asked for, and whether the manufacturer confirmed it, to make the change, show members what happened and keep the service secure, based on performance of our contract and our legitimate interest in protecting accounts and preventing misuse.

Disconnecting an appliance stops new readings from it. For a direct connection, it also asks the manufacturer to remove Wiggle's access and removes the identifier from the connection; Retention says how long we keep it after that.

Telling us about a missing appliance. If you tell us a manufacturer or model is missing or your device is not supported, we store what you type and the appliance type, without your account, household or address, to choose which appliances to support next. This is in our legitimate interest in improving which appliances Wiggle can connect. You do not have to tell us. If you also tick the box to let us contact you, we keep the request with your account, and staff who look after appliance support can see your name and email address beside it, so that we can contact you about testing or adding support for that device. We do this with your consent, which you can withdraw at any time at support@wiggle.energy.

Weather and grid carbon

An owner can give a postcode so that Wiggle can show local weather and how much carbon the local grid is emitting. We keep only the postcode district, the first part such as RG10. We may suggest it from the address on your Octopus account, but we do not store that address. We send the district, with no name, account or household identifier, to postcodes.io for its approximate centre and to the National Energy System Operator's Carbon Intensity API for its grid region. We send that centre, rounded to about a kilometre, to the Norwegian Meteorological Institute (MET Norway) for a forecast. We store the results by district and region, shared by every household in the same area. The lawful basis is performance of our contract.

Testing Wiggle's planning

We are developing a feature that plans when a household's battery, car or heating uses energy. Before we offer it to anyone, we test it on the records of households we select. For a selected household, our servers work out what Wiggle would have planned with the information it had at the time, and later compare that with what the household did and what it cost. We use the readings, tariffs, smart-charging plans, appliance readings and local weather we already hold, and work out from them when your car was plugged in and the temperatures your heating kept, because a plan has to meet those needs. Testing sends no command to any device and makes no decision about you.

Only NRB Tech staff see the detailed results. If your household is selected, the app may also show you what Wiggle estimates it would have saved, labelled Estimated.

To improve the planning, we may export these records. An export does not contain your name, email address, address or postcode, and gives each household a random code that changes with each export. It is still personal information. We keep each export encrypted within NRB Tech.

This is in our legitimate interest in making Wiggle's planning safe and cost-effective before it controls any household. If you object, we stop testing on your household and delete its test records.

Sharing within a household

Members can see the household's shared energy information, including readings from linked appliances, ask for the changes an appliance was linked to allow, and see who asked for recent changes. Owners manage membership and linked appliances. People in another household cannot see yours. Members never see your sign-in credentials. Household readings can concern other occupants as well as the account holder.

Email and alerts

We use your email address for invitations, verification, recovery, security notices, messages about a privacy request that affects you, and other messages needed to provide or secure the service. We use Mailjet to send them.

If you turn alerts on, we keep your preferences, limited delivery records and your device's push address: an Apple push token on iOS, a Firebase Installation ID on Android, or the push subscription your web browser gives us. Our servers decide which alerts to send and write their title and message.

- iPhone: Apple Push Notification service delivers them.

- Android: we send the full title and message, the installation ID and a random delivery reference to Google Firebase Cloud Messaging (FCM), with no Wiggle account, household or event identifier. Alert text can still reveal household energy or charging activity. Google also receives the technical information it needs to deliver the alert. If FCM cannot deliver an alert within five minutes, it discards it.

- Web browser: we encrypt the title, message and a random delivery reference so that only your browser can read them, and send them to your browser's push service, for example Apple, Google, Mozilla or Microsoft. That service gets the technical information it needs to deliver the alert, but cannot read it.

You can turn alerts off in Wiggle Settings or deny notification permission on your device or browser. The household Timeline and in-app inbox stay available.

Support and diagnostics

When you contact support, we process your message, case status, and the app version, build and operating-system version, to investigate and reply. This is in our legitimate interest in providing a reliable, secure service.

The app also keeps diagnostics on your device: bounded technical events, such as whether a request succeeded, and any crash or hang reports your device provides. They do not contain household readings or supplier credentials. They are sent to us only if you choose to attach them to a support request, which is off unless you turn it on. They are then sent once, with that request, and removed from your device. Diagnostics you attach to a support request are sent with your consent, which you give each time by turning the option on and can withdraw by contacting us. Apple may also provide crash or TestFlight feedback under its own settings.

We do not need marketing consent for you to use Wiggle. If we offer marketing updates, they have their own optional sign-up and opt-out.

Who helps us

- OVHcloud hosts the main database in the UK.

- Scaleway stores encrypted production backups in Paris, France. We manage the encryption and access.

- Mailjet delivers account email.

- Google Workspace holds our email, including what you send to support@wiggle.energy and our replies.

- Apple provides Sign in with Apple, iPhone alerts and app distribution.

- Google Firebase Cloud Messaging and browser push services deliver alerts, as described above.

- Enode links appliances for us as our processor: it uses information only on our instructions.

- postcodes.io, the Carbon Intensity API and MET Norway receive only a postcode district or an approximate location.

- Infrastructure providers process limited service and network information to run their services.

Your supplier and appliance manufacturers process their own account information, and the requests we make for you, under their own privacy notices. The Connected services list names each one. Authorised NRB Tech staff can access information where they need to, to run, secure or support the service. We do not sell personal information or share it for advertising.

Information outside the UK

The main database is in the UK, but not every provider processes everything in the UK. Some are in the European Economic Area, for example Enode in Norway. FCM may process information anywhere on Google's global infrastructure, and browser push services may process delivery information outside the UK. The Connected services list says where each connected service is based and where it processes information.

Where UK transfer rules apply, we rely on an adequacy regulation or on contractual safeguards, such as the UK International Data Transfer Agreement or UK Addendum. Contact us for details of a safeguard and a copy.

For some manufacturers of directly connected systems, no adequacy regulation or transfer agreement covers what we send; the list says which. We send it only with the explicit consent of the owner who connects the system (UK GDPR Article 49(1)(a)). The connection screen asks for that consent after it explains that manufacturer's risks: for example, that the law there may protect the information less than UK law, that authorities there may be able to access it, and that you may find your rights harder to use. We record the consent. Disconnecting the system withdraws it and stops the transfer; what the manufacturer already holds stays under its own privacy notice.

How we protect information

Connections to Wiggle are encrypted. The database is on an encrypted volume. Supplier credentials are encrypted again, with keys kept apart from database records. Passwords are stored as secure hashes. Household permissions limit who sees what, and administrative access is restricted. Routine logs are designed to leave out supplier credentials, energy readings and support messages. Our servers process your information to provide the service, so it is not end-to-end encrypted between your devices.

Retention and deletion

We keep your account and household history while you use the service, including for historical comparisons and to correct supplier information. Disconnecting a supplier or appliance stops new collection, and for a supplier removes its usable credential, but does not erase the history already recorded. Disconnecting all appliances also asks Enode to delete the household's Enode connection.

Deleting your account. Start it in Settings, under Account. We remove your sign-in credentials, sessions and personal account information, and support content attributable to you. If an older support record in a shared household needs review to identify its author, we tell you, and do not call it erased. Deleting your account never deletes anyone else's account.

- Each household where you are the only owner is erased with its energy history, even if you share it. Its other members lose access but keep their accounts and other households.

- You leave a household that has another owner, and one where you are only a member; they remain.

- For each erased household, we ask Enode to delete its connection and each directly connected manufacturer to remove Wiggle's access.

If an owner deletes a household, it is erased for everyone in it, and each member keeps their account. Before anyone confirms, the app names the households to be erased or left and the members who will lose access.

How long we keep other records:

- Diagnostics sent with a support request: normally 30 days. Diagnostics on your device: 24 hours.

- Support cases: while active and up to 24 months after closure, unless you ask us to erase them sooner or a specific legal requirement applies.

- Account-email, alert-delivery and expired session records: most after 30 days. Short-lived sign-in attempt records: one day.

- Disabled alert installations: normally 90 days. Turning off Android alerts or signing out unregisters the device from FCM, but does not delete Google's Firebase Installation ID. Google says it keeps that ID until someone asks it to delete it, and then removes it within 180 days; Wiggle does not currently ask.

- Notes of a missing manufacturer or model: 365 days. If you let us contact you about one, we remove the link to your account sooner: when we add support for that device, when you withdraw consent or when you delete your account.

- Planning test records: 24 months after the day they describe. Exports of them: 30 days after we make them.

- The identifier we need to remove a connection at its service, such as an Enode user identifier or a system's serial number or ID, after a disconnection or erasure: until the removal is done, then no more than 30 days. The Connected services list gives each service's period.

Encrypted production backups expire under a lifecycle schedule beginning after 31 days; object locking, version expiry and provider processing mean removal is not immediate. Backup copies are used for recovery with deletion requests reconciled before restored personal information is made available. We keep only the limited records needed to complete and account for a deletion or meet a specific legal obligation, and explain any exception that applies to your request.

Your choices and rights

In Settings you can correct your account information, manage alerts, and disconnect suppliers and appliances. Without signing in to the app, you can ask for account deletion, deletion of particular data or a copy of your information at wiggle.energy/privacy-request/. We send a single-use link to verify your email. When you confirm it, we email you what you asked for and how long each step normally takes; we normally review a request within one working day. Then we check any further identity or household authority we need.

If we approve deleting information, however you asked, we first email the people it affects at their verified address: you, and for a household deletion every member who will lose access. The email says what will happen and when, without household information. Nothing is deleted for 24 hours after approval, and the link in each email stops the request until then. If you ask for a copy of your information, we send it once we have checked your request, without that wait or email, because a copy deletes nothing.

You can ask for access to your personal information, correction, erasure, restriction or a portable copy where the right applies. If we rely on your consent, you can withdraw it without affecting earlier lawful processing. Acknowledging this notice is not blanket consent. You can object to processing based on our legitimate interests by telling us at support@wiggle.energy what you object to, and to direct marketing at any time.

Where the law requires it, we respond without undue delay and within one month. Some rights depend on the purpose and lawful basis. We make no solely automated decisions with legal or similarly significant effects.

You can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint. You do not have to contact us first.

Changes to this notice

If our processing changes, we update this notice and show the new version in the app with a summary. Earlier versions stay available. We ask you to acknowledge the notice so we can record what you were shown; this does not replace any separate consent needed for optional processing.