Privacy Policy
Last updated 21 September 2026
This policy explains what personal information AmpOn collects, why we collect it, who we share it with, and what control you have over it. It covers ampon.io, the AmpOn Charge Point Management System, the AmpOn API, the hardware we supply, and every message programme we operate, including email, SMS and voice.
On this page
- Who we are
- Our role: when we are a controller and when we are a processor
- What we collect
- How we use it
- Mobile messaging and SMS consent
- Who we share it with
- Drivers and charging session data
- Payments
- Cookies and analytics
- International transfers
- How long we keep it
- Security
- Your rights
- US state privacy rights
- Children
- Changes
- Contact
1. Who we are
AmpOn provides software and hardware for deploying, operating and monetising electric vehicle charging infrastructure. Our customers are businesses: workplaces, fleet depots, multifamily properties, retail sites and public charging networks.
In this policy, “AmpOn”, “we” and “us” mean AmpOn.io. “You” means whoever the information is about: a visitor to this site, a person at a customer organisation, or a driver who uses a charger our software operates. You can reach us about anything here at support@ampon.io.
2. Our role: when we are a controller and when we are a processor
The distinction matters, because it decides who you ask about your information.
- We are the controller for information about visitors to this site, people who contact us or request a quote, and the users at our customer organisations who administer the platform. We decide why and how that information is used, and this policy governs it.
- We are a processor for information our customers put into the platform or generate by operating their chargers, including data about the drivers who use those chargers. Our customer decides why and how that information is used; we act on their instructions under our agreement with them.
If you are a driver and want to know why your charging data was collected, the site operator is the right place to start. We will help them answer you, and you can always contact us directly.
3. What we collect
| Category | Examples | Where it comes from |
|---|---|---|
| Identity and contact | Name, work email, phone number, company, job title, site address or ZIP | You, when you contact us, request a quote, book a demo or create an account |
| Account | Username, hashed password, role and permissions, organisation, preferences | You and your organisation’s administrator |
| Charging session | Start and stop time, energy delivered, connector and charger ID, tariff applied, cost | The charger, through OCPP, while the session runs |
| Charger telemetry | Status, faults, firmware version, power draw, availability, diagnostics | The hardware, continuously |
| Driver identification | RFID card or tag ID, app or account identifier, vehicle identifier where supplied | The driver, the charger, and the site operator |
| Payment | Transaction amount, currency, time, last four digits and card brand, payout records | Our payment processor. We never see or store full card numbers. |
| Messaging | Mobile number, the consent you gave, when and how you gave it, delivery and opt-out status | You, and the carriers that deliver the messages |
| Support | Your messages to us, tickets, call notes, voicemail and any transcript of it | You, when you contact support |
| Technical | IP address, browser and device type, pages viewed, referring page, timestamps | Automatically, when you use the site or the platform |
We do not collect special category data (health, biometrics, race, religion, political opinion or similar) and ask that you do not send it to us.
4. How we use it
- To run the service. Operate chargers, authorise and record sessions, apply tariffs, produce reports, and keep the platform working.
- To support you. Answer questions, diagnose faults, and fix problems.
- To bill and get paid. Invoice customers, process driver payments, and settle revenue to site operators.
- To communicate. Send service and account messages about your sites, your chargers and your account. See section 5 for text messages specifically.
- To respond to enquiries. Prepare quotes, including against a build you configured in our planning tools.
- To improve and secure the service. Understand how it is used, detect and prevent abuse and fraud, and maintain security.
- To meet legal obligations. Tax, accounting, and responding to lawful requests.
Where the GDPR or UK GDPR applies, our legal bases are: performance of a contract with you; our legitimate interests in operating, securing and improving the service; your consent, for marketing email and for text messages; and compliance with a legal obligation. Where we rely on consent, you can withdraw it at any time.
5. Mobile messaging and SMS consent
Mobile opt-in information, including phone numbers and SMS consent, will not be shared with third parties for marketing purposes. We use it only to send the messages you asked for.
If you give us your mobile number and opt in, this is exactly what you are agreeing to.
How we collect your consent
Consent is given by ticking an unticked checkbox on a form on this website: the quote request on our planning tools, or the contact, demo and support forms. The checkbox sits next to the full disclosure, is never pre-selected, and is separate from the submit button, so submitting a form is not by itself consent to be texted. We record the wording you were shown and the time you agreed to it.
Giving your phone number without ticking that box is not consent to receive text messages, and we will not text you. We use the number to call you about your enquiry, nothing more.
What we send
Informational messages only: appointment and site-visit reminders, account notifications, quote and order updates, and service alerts about your chargers. We do not send marketing or promotional text messages under this programme.
How often
Message frequency varies, and depends on your account activity and the sites you operate. Message and data rates may apply. Those rates are charged by your mobile carrier under your own plan, not by AmpOn.
How to stop, and how to get help
You can opt out at any time by replying STOP to any message. We will send a single confirmation and then stop. For help, reply HELP or email support@ampon.io.
Who sees your number
Your mobile number and your record of consent are used only to deliver the messages described above. We share them with the telecommunications providers that carry those messages for us, and with nobody else. They are never sold or rented. They are not passed to any third party for that party’s own marketing, and not to advertisers, data brokers or affiliates. If you opt out, we keep the minimum record needed to make sure we honour that opt-out.
6. Who we share it with
We do not sell personal information. We share it only in the following circumstances.
| Who | What for |
|---|---|
| Cloud hosting and infrastructure providers | Running the platform and storing data |
| Payment processors | Taking driver payments and settling revenue |
| Email and messaging providers | Delivering email, SMS and voice messages you have asked for |
| Telephony providers | Carrying calls and voicemail to our support line |
| Analytics and error monitoring | Understanding usage and diagnosing faults |
| Professional advisers | Accounting, audit and legal advice, where needed |
| Authorities | Where the law requires it, or to establish or defend legal claims |
| An acquirer | If the business is sold or merged, under the same commitments in this policy |
Each provider gets only what it needs to do its job, is bound by contract to protect it, and may not use it for its own purposes. We will name our current subprocessors on request.
7. Drivers and charging session data
If you charge a vehicle at a site running on AmpOn, the platform records the session: when it started and stopped, how much energy was delivered, which charger and connector, the tariff, and the cost. Where the site requires identification, it also records the RFID tag or account you used.
That information belongs to the site operator, who decides what it is used for. It is used to authorise charging, bill for it, settle revenue, and keep the site running properly. We do not use driver data to build advertising profiles, and we do not sell it.
Charging data can show where a vehicle was and when. We treat it accordingly: access is limited to the operator of that site and to AmpOn staff who need it to run or support the service.
8. Payments
Card payments are handled by a third-party payment processor. Card details go directly to that processor and are never stored on AmpOn systems. We receive a record of the transaction (amount, currency, time, card brand and last four digits), which we use to reconcile sessions, settle revenue and handle disputes.
9. Cookies and analytics
We use cookies and similar technologies that are necessary to make the site and the platform work: keeping you signed in, remembering preferences, and protecting against automated abuse. We also use a small amount of analytics to understand which pages are used.
The contact and quote forms on this site are protected by Cloudflare Turnstile, which checks that a submission comes from a person rather than a bot. It is subject to Cloudflare’s own privacy terms. You can block or delete cookies in your browser; parts of the platform will not work if you block the necessary ones.
10. International transfers
We operate from Australia and serve customers in the United States and elsewhere, so personal information may be transferred to and processed in countries other than your own. Where we transfer information out of the UK, the EEA or another region with transfer rules, we rely on an approved mechanism such as the European Commission’s Standard Contractual Clauses, and we apply the protections in this policy wherever the information is held.
11. How long we keep it
| What | How long |
|---|---|
| Account and contact information | While the account is active, then up to 24 months |
| Charging session and billing records | As long as tax and accounting law requires, typically 7 years |
| Charger telemetry and diagnostics | Typically 24 months, then aggregated or deleted |
| Mobile numbers held for messaging | Until you opt out, apart from the minimal record that keeps you opted out |
| Support tickets, call notes and voicemail | Typically 24 months |
| Enquiries that do not become accounts | Up to 24 months |
Where we act as a processor, retention follows our customer’s instructions and our agreement with them.
12. Security
We protect personal information with encryption in transit, access controls on a least-privilege basis, separation of customer data, logging of administrative access, and regular review of who can reach what. Passwords are stored hashed, never in readable form.
No system is perfectly secure. If a breach affects your personal information we will tell you and the relevant regulator without undue delay, and explain what happened and what we are doing about it.
13. Your rights
Depending on where you live, you can ask us to:
- Access the personal information we hold about you, and get a copy.
- Correct anything inaccurate or incomplete.
- Delete information we no longer have a reason to keep.
- Port information you gave us, in a machine-readable format.
- Restrict or object to certain processing, including processing based on our legitimate interests.
- Withdraw consent at any time, where we relied on it.
- Opt out of text messages by replying STOP, and of marketing email using the unsubscribe link.
Email support@ampon.io and we will respond within the time the law allows: one month under the GDPR, 45 days under US state law. We may need to verify who you are first. Using these rights costs nothing and we will not treat you differently for it. If you are unhappy with our response you can complain to your data protection authority.
14. US state privacy rights
If you live in California, Virginia, Colorado, Connecticut, Utah, Texas or another state with a comprehensive privacy law, you have the rights in section 13, and specifically:
- We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under the CCPA as amended by the CPRA.
- We have not sold or shared personal information in the preceding 12 months, including the personal information of anyone under 16.
- You may ask us to limit the use of sensitive personal information. We do not use it for purposes that require that option.
- You may designate an authorised agent to make a request for you.
- You have the right not to receive discriminatory treatment for exercising any of these rights.
15. Children
AmpOn is a service for businesses. It is not directed at children, we do not knowingly collect personal information from anyone under 18, and we will delete it if we learn we have.
16. Changes
If we change this policy we will update the date at the top of the page. Where a change materially affects how we handle your information, we will tell you directly, by email or in the platform, before it takes effect.
17. Contact
For any question about this policy, about information we hold, or to exercise any right in it: support@ampon.io.
See also our Terms of Service.