Legal
Privacy Policy
Reading your meter is how this works, so we owe you a plain account of what that means. This is what we collect, why we need it, who else ever sees it, and what you can make us do with it.
Version 1.7 · in force from 4 October 2026 · says what we keep about the codes we send you and the changes of your password, and how long we keep backups (1.6, 4 October 2026: how you sign in with Google in the app, and when we link an account to Google; 1.5, 2 October 2026: how you delete your account yourself, and what it leaves; 1.4, 1 October 2026: how a forgotten password is reset; 1.3, 26 September 2026: what the app keeps on your phone; 1.2, 24 September 2026: how a withdrawn credential is erased)
1.Who is responsible
POMIGRO (“we”) decides what data is collected here and why, and is responsible for it. You can reach us through the contact page on this site; write to us there about anything in this policy, including a complaint.
Not every country our members live in has a comprehensive data protection statute in force. We have chosen to hold ourselves to the standard set out below regardless — in substance, the rights a European or British member would have — because the data involved is a detailed record of what happens inside your home or business.
2.Why meter data is sensitive
A reading every fifteen minutes describes your household, not just your electricity.
Interval consumption data shows when a building is occupied and when it is empty, when people wake and sleep, and when a business opens and closes. We would rather say this plainly than let you discover it later. It is why the safeguards in clause 5 exist, why we share nothing for advertising, and why you can end the reading yourself at any moment.
3.This website collects nothing
pmo.com.ps sets no cookies, runs no analytics, and carries no advertising or tracking script of any kind. You can read every page of it without telling us anything. Our web server keeps ordinary request logs, as any server does.
If you use the contact form, the name, email address and message you type are sent to our mailbox by email. They are not added to a database or a mailing list, and we use them only to reply to you.
The rest of this policy is about the member app at pmo.com.ps/app, which is a different matter.
4.Your account
- Email address
- Required. It identifies your account and is where verification codes, statements and notices go. We verify it with a six-digit code before you can sign in for the first time. The code itself is stored only as a salted hash, expires in fifteen minutes, and is void after five wrong attempts — it is sent to your inbox through our email provider (clause 7), and we keep no readable copy of it: never in a log or an API response. If you forget your password, a six-digit code sent to it lets you set a new one. That code is hashed with a key held only in our running server's memory, lasts fifteen minutes, is void after five wrong attempts, and is sent and kept the same way. A code that lets you delete your account, if you ask for one instead of typing your password, is made, sent and kept the same way. We send at most five of each kind of code to one account in a day. Once your password changes, we email you a notice.
- Password
- Stored only as a slow one-way hash with a salt unique to your account (PBKDF2-HMAC-SHA256). We cannot read it, and nobody at POMIGRO can tell you what it is.
- Your name and premises
- What you type at sign-up. They appear on our operations roster and on any document issued to you.
- Sign in with Google
- Optional, on the website and in the app. If you use it, Google tells us your account identifier, your name, your email address and whether Google has verified it, and also your profile picture's address and, for a work account, its domain, which we do not keep. When your account is made this way, Google's name — or, failing that, the part of your address before the @ — is the name on it. We ask for nothing beyond identity — no access to your Gmail, your contacts or your files — and we identify you by Google's stable identifier rather than by the address. We link an account that already exists to Google only when Google itself vouches for the address (a Gmail address, or a Google Workspace domain), and we email that address when we do.
- Your session
- When you sign in we set one cookie holding a random token that means nothing outside our server. It is not an advertising identifier and it follows you nowhere. Sessions expire when idle and again after a fixed period, whichever comes first, and every session ends when your password is reset or changed, or your account is deleted.
- On your phone or computer
- If you add the portal to your Home Screen, your browser keeps POMIGRO's logo and a short offline page so the app can open without a connection, and remembers whether you dismissed the add-to-Home-Screen hint. While you sign in with Google, the page keeps a random string for that one sign-in and Google sets a protective cookie of its own; both are discarded when the sign-in completes or the tab closes. None of these holds a reading, a balance or anything about you; no reading is ever kept on your device, and clearing the site's data removes them all. The POMIGRO app on a phone keeps only its sign-in token, in the phone's secure storage; signing out or deleting your account removes it. When you sign in with Google in the app, it holds a few random strings in its memory for that one sign-in; on an iPhone Google also gives it two tokens for your Google account, one of them long-lived, which it throws away unused. Google's own sign-in on your phone — Safari's on an iPhone, or the account Android remembers — is Google's, and signing out of POMIGRO does not end it.
5.Your inverter credentials
Depending on your manufacturer, connecting your plant either gives us a revocable authorisation issued by them, or requires the credentials of your own cloud account with them. The second is the more sensitive, and we treat it accordingly.
- It is encrypted before it is written down, with a key kept outside the database. A copy of the database alone does not open it.
- It is decrypted only at the moment it is used to fetch your readings, and is never retained in the clear.
- Every occasion on which it is decrypted is written to an audit trail recording who did it, when, and why. That trail cannot be edited or deleted — the database itself refuses, including to us.
- We never submit it anywhere but your manufacturer's own service, and we never transmit or receive it except over an encrypted connection.
- We read. We never send a command to your equipment. Where a manufacturer's own interface would grant us control, we ask them to withhold it.
You can withdraw at any time, from the app. When you do, we stop the poller that was using the credential, end our session with the manufacturer where they give us a way to, and delete the encrypted secret from our live database. Deleting a row does not by itself remove its bytes from the database's files, so we then have the database rewrite the table that held it, and our audit trail records when that rewrite was confirmed. This normally happens within a minute of your withdrawal; if a backup is being taken at that moment, it happens as soon as the backup finishes, and the app tells you when that is the case. The disk space the table occupied before the rewrite is released to the operating system rather than overwritten, and the database's write-ahead log — the journal it keeps so that it can recover from a crash — can still hold the encrypted secret until the database reuses that part of the log in the ordinary course of its work, which does not happen on a fixed schedule. Backups of our databases taken before you withdrew also still hold the secret in its encrypted form; clause 8 says how we keep them. If you want the secret to be useless everywhere at once, change the password with your manufacturer after withdrawing: an old copy then opens nothing. The audit trail of past access survives — that is the record that lets you hold us to this, so it outlives the secret on purpose. If your manufacturer keeps its own record of the authorisation, you can also remove it in their portal, and we will tell you where.
6.What we read from your plant
At intervals through the day, typically every fifteen minutes: how much your panels generated, how much your premises consumed, how much your battery charged and discharged and its state of charge, and how much energy crossed your connection point in each direction. We also keep the manufacturer's original response as we received it, because when a figure is disputed the only honest answer is what the meter actually said.
We use it for three things and no others: to show you your own energy position, to work out what you owe or are owed within the microgrid, and to run the quality checks that decide whether a day can be settled at all. We do not profile you, and we make no automated decision about you with legal effect.
8.Where it is kept, and for how long
Your data is held on servers POMIGRO operates. Readings arrive from your manufacturer's cloud, which may be outside your country — that is a consequence of the equipment you own, and it is the one transfer we cannot avoid.
Backups: what they hold, and for how long.
We copy our databases regularly so that a failed disk cannot lose your account or a settled record. Each backup is a copy of the databases as they stood at that moment. Backups are not separately encrypted. They are kept on POMIGRO's own systems together with the key that opens the credential store — so that service can be restored after a failure. Everything this clause says we delete, we delete from the live system, and a backup taken before your account was deleted keeps its copy until that backup is deleted: we delete each backup 30 days after it was taken.
Your inverter credential is deleted from the live system as soon as you withdraw it, and erased from the database's files as clause 5 describes. Your account details are kept until your account is deleted; we then send one confirmation to its address and do not keep the address. For each kind of code we send to your address, and for changes of your password, we keep how many there were in the most recent day and when the first and the last of them were, while your account exists.
As clause 5 explains for an inverter password, deleting from our live database leaves old copies in the database's files until the space is reused; only that password is then erased by a rewrite.
Your manufacturer's original responses — the verbatim record behind every figure — are deleted from the live system automatically after 90 days. That window is a whole dispute cycle: a day settles daily, a document issues monthly, payment terms are 30 days, and somebody who questions an invoice usually does so after paying it. A job on our server does the deleting every day; it is not a policy we remember to follow.
The interval readings themselves — the quarter-hour figures, without the manufacturer's raw envelope — are kept while your plant is connected, because they are what any account settled from them was computed from. When you delete your account we delete them, except where clause 9 says we cannot.
9.What you can ask us to do
- See what we hold about you, and get a copy of it.
- Correct anything that is wrong — a misspelt name, the wrong premises.
- Withdraw your inverter permission, which you can do yourself in the app without asking us.
- Delete your account yourself, at once: in the app (Me, then Account) or on the website (Account). You can also ask us to.
- Object to something we are doing, or complain about it. Write to us first; you may also take the matter to a competent authority or court.
One honest limit: what has been settled cannot be erased.
Once a day has been settled, the record of it — the amounts, the charge lines behind them and the ledger entries — is sealed. The database refuses to alter or remove it, and that refusal applies to POMIGRO too. It exists so that a figure cannot be changed behind your back after you have been shown it, which is a protection for you; the cost of that protection is that we cannot erase it on request either. It is also an accounting record we are required to retain.
Deleting your account takes effect at once; the erasure of a stored inverter password follows the timing clause 5 describes.
Goes at once: your name, phone, premises, address and sign-in; your inverter connections, withdrawn at the vendor where it allows, the stored password erased as clause 5 describes, normally within a minute; the readings of every day not settled.
Stays: any settled day's record, including what your inverter's cloud sent for those days, which the database refuses to change for anyone (none yet for most members); the history of your membership's states and the record of each time we used an inverter connection, under your member number only; a record that an account was deleted, which names no one; and the consent records of your inverter connections, with the login replaced by a fingerprint that can confirm it but cannot reveal it.
Backups taken before today keep a copy until each is deleted, 30 days after it was taken.
If you ask us by email instead, we act on the request only once it is confirmed from your account's own email address; if you can no longer reach that address, recover it with your email provider first. Our page at pmo.com.ps/delete-account sets out both ways.
We will answer a request within thirty days, and we will not charge you for it.
10.Keeping it safe
Credentials are encrypted at rest with a key held apart from the data. Passwords are hashed, never stored. Sessions expire, and repeated wrong passwords lock an account rather than let a guess run. The app refuses to accept an inverter credential at all unless the connection is encrypted. Settled records and audit trails are made unalterable by the database itself rather than by a rule we promise to follow.
No system is beyond reach. If your data is ever exposed in a way that puts you at risk, we will tell you what happened, what was involved and what we have done — without waiting to be asked.
11.Children
The service is for adults. We do not knowingly create accounts for anyone under 18, and we will delete one if we find it.
12.Changes to this policy
When what we do changes, this page changes with it, and the version and date at the top move. We will tell you in the app and by email before a material change takes effect — particularly any change to what we collect, who sees it, or how long we keep it.
See also the terms of service, which govern membership, metering and charges. Terms of service