Augos deletes platform data only when asked: by an individual user for their personal information, or by a customer for its telemetry and organisation data. This policy covers augos.io, its gated offers and the Augos Mobile App. It sets out what is deleted, what stays and why.
Before any deletion starts, a customer signs, or an individual accepts, a data deletion agreement.
Send your request to the Information Officer at support@augos.io. Tell us who you are, which organisation you use the platform through, and what you would like deleted. We will confirm your identity, and for a customer request your authority, before anything is deleted. When we are done, we will tell you in writing what was deleted, what stayed and why.
How the platform uses personal information is set out in our Platform Privacy Policy.
This policy covers data held on the Augos platform at augos.io. It does not cover anything else Augos holds.
In scope
Out of scope
Platform data falls into two categories, and each is deleted under its own rules: personal information, and telemetry data.
| Personal information | Telemetry data | |
|---|---|---|
| What it is | Information that identifies a person, as POPIA defines it | Readings and state data from devices on the platform that do not identify a person |
| Examples | User account details (name, email, telephone, role, permissions); audit records of sign-ins, retrievals and control actions; alert and report recipients; support requests; named machine operators and their figures; household consumption in the Community Curtailment app; app-usage analytics | Consumption (electricity, water, gas, fuel), demand, power factor, voltage, current, frequency; flow, pressure, level, volume; temperature, humidity, vibration; equipment state (doors, beams, tamper, smoke, sound level, never audio); device health (battery voltage, signal strength) |
| Responsible party | Augos for user accounts and audit records. The customer for its named operators and for the information its organisation puts into the platform, including household consumption shown in the Community Curtailment app. | The customer. Augos is its operator. |
Telemetry data includes everything calculated from it: aggregates at every interval, tariff and cost calculations, bill verification and reports.
Where the two meet. A reading is telemetry unless it can be linked to a named person. A measurement point named after a staff member, a sub-metered tenancy with one occupant and a household meter all create that link. Where the link is only a name, removing the name returns the readings to telemetry. Where the link is built in, the readings are treated as personal information.
Augos deletes platform data only on a specific request, and only after it has checked who is asking and whether they may.
The Information Officer owns every deletion request from receipt to closure; platform engineering carries the deletions out.
| Role | Responsibility |
|---|---|
| Information Officer | Receives and logs requests, checks identity and authority, decides, signs off each deletion, replies to the requester and keeps the request register. Contact: support@augos.io |
| Support | Receives requests at support@augos.io or from staff, logs them the same day and passes them to the Information Officer |
| Platform engineering | Carries out approved deletions on the platform and the Augos Mobile App, tracks backup expiry and re-applies deletions after any restore |
| Chief Executive | Receives any request at risk of missing its target date |
| Customer administrator | Gives a customer's written instruction, confirms the scope and confirms they are authorised to give it |
| Individual user | Asks for their own personal information to be deleted |
On a verified request, each type of platform data is handled as the table shows.
| Data | Category | Deleted on request by | What happens | What stays |
|---|---|---|---|---|
| User account details (name, email, telephone, role, permissions) | Personal | The user, or the customer for its own users | Deleted | Nothing |
| Audit records of sign-ins, retrievals and control actions | Personal | The user | The link to the person is removed and replaced with an anonymous identifier | The record that an action happened, and when |
| Alert and report recipients | Personal | The user, or the customer | Removed from every recipient list and deleted | Nothing |
| Support requests raised on the platform | Personal | The user | Deleted | Nothing, unless an open dispute needs it. Email correspondence about a request is outside scope. |
| Named machine operators and their figures | Personal | The customer only | Deleted on the customer's written instruction | Nothing |
| Community Curtailment household consumption | Personal | The customer that runs the estate's programme. Augos is its operator. | Deleted on the customer's written instruction | Nothing |
| App-usage analytics (app opened, device type, app identifier) | Personal | The user | Held two months, then expires under the analytics setting. It is not deleted sooner. | Nothing after two months |
| Gated-offer registrations and acceptances | Personal | The user | Registration deleted | Any signed agreement the offer produced |
| Telemetry readings, every stored interval | Telemetry | The customer only | Deleted for the named points, devices or sites, or the whole account | Anonymised, aggregated platform statistics, where the customer agreement allows |
| Calculated data (aggregates, tariff and cost calculations, bill verification, reports) | Telemetry | The customer only | Stored calculations are deleted with the readings. Anything calculated on request can no longer be produced once the readings are gone. | Reports already emailed to people, which are outside the platform |
| Device records (identifier, point set-up, health metrics) | Telemetry | The customer only | Health metrics deleted with the readings. The device registration stays so the hardware can be reprovisioned. | Device registration |
The five-year archive. After a contract ends, Augos archives measurement data for at least five years in case the contract is reactivated. A customer's specific written request for deletion, with the data deletion agreement signed, overrides that archive.