Privacy policy: Vega Charging AI connectors
How the Vega Charging connectors for Claude and ChatGPT handle personal data.
Last updated: 11 November 2026 · Back to the connector documentation
1. Who we are
The Vega Charging platform and its AI connectors are provided by RadX SHPK, NIPT M41615026M, Tirana, Albania ("RadX", "we").
- Business data in Vega Charging — chargers, rates, offers and offer messages — belongs to the charging company that uses Vega Charging. That company is the controller, and RadX processes the data on its behalf.
- Records of connector use, described in section 4, are kept by RadX to run and secure the connectors.
Contact for privacy questions and requests: info@radx.app.
The Vega Charging app for drivers has its own privacy notice; this policy covers only the AI connectors used by staff of a charging company.
2. What the connectors are
The connectors let a staff member of a charging company who already has a Vega Charging account work with Vega Charging through an AI assistant: Anthropic's Claude or OpenAI's ChatGPT. The assistant connects to Vega Charging's server (https://api.radx.app/mcp/vega-charging/claude for Claude, https://api.radx.app/mcp/vega-charging for ChatGPT). The person approves the connection on Vega Charging's own sign-in page at vegacharging.radx.app.
3. What data the assistant can access
- Only the person's own company. Company staff see only the company their account belongs to; RadX staff see every company. The account, its role and its company are read again on every request.
- Within that company the assistant can read:
- chargers and connectors: their names, identifiers and current status;
- problems the chargers reported: the charger, the connector, the error code, the status and the time;
- rates: their names, types and prices;
- offers: name, code, discount, the rate given, the conditions and period, the customer role it is for, and whether it is switched on;
- offer messages: their title and text, and after how many charges they are sent;
- charging sessions on the company's chargers, through Claude: the charger, its location and connector, the day, the start and end time, the energy (kWh), the duration, the status and whether it was a roaming session, one by one or added up per charger, location or day. Never who charged: no customer, account, card or customer group, and no price or amount;
- the person's own name, role and company.
- Not accessible through the connectors: customers' accounts and personal data, who charged in a session, the price or amount of a session, revenue, payments, wallets, cards, invoices, vouchers and their codes, passwords, login tokens and other secrets.
- Changes are possible only for the Company Admin, Company Operator and RadX Admin roles, and only when the connection was approved while the person held such a role. The assistant can create and change offers, switch offers and offer messages on or off, and create offer messages. Anything customers will see needs a one-time confirmation that the assistant must show to the person first. Changes are recorded under the person's name. The connectors cannot delete anything.
The assistant provider's own terms and privacy policy, and the person's or organisation's settings with that provider, govern what the assistant does with the data it receives. This covers how conversations are stored, whether they are used for training, and how long the provider keeps them. See Anthropic's privacy policy and OpenAI's privacy policy.
4. What we store about connector use
| Data | Why | What it contains |
|---|---|---|
| Connection records | To know which assistant may act for which person, and until when | The assistant's registered name and return address, the person's Vega Charging account and company, when the connection was approved, whether it may make changes, when it ends, and the IP address and browser of the sign-in request |
| Tokens | To check each request | Only a SHA-256 fingerprint of each token and a short readable prefix, never the token itself. Access tokens last one hour. Refresh tokens last 30 days and are replaced each time they are used. |
| Request log | Security, troubleshooting and accountability | For every request, including refused ones: the account, the company, the connection, the tool used, its arguments (shortened), the result status, the number of results, the time taken and the IP address |
| Confirmation codes | To make sure a change customers will see was shown to the person first | A SHA-256 fingerprint of the code and of the change, the account, the tool, a short summary, and when the code expires or was used |
| Change history | Accountability for changes made through an assistant | The same history Vega Charging keeps for changes made on the website: who made the change (marked "via Claude" or "via ChatGPT"), on which record, the values before and after, the IP address and the user agent |
Vega Charging does not store the assistant's answers or the conversations.
5. How long we keep it
| Data | Kept |
|---|---|
| Sign-in requests that were never finished, or were declined, and sign-in codes that were never used | Deleted after 1 day |
| App registrations that never connected and have no connection left | Deleted after 90 days |
| Expired tokens | Deleted 1 day after they expire |
| A connection | At most 90 days from approval, however often it is refreshed. The person then approves again. |
| Ended connections (disconnected, expired, or ended for security reasons) | Kept 90 days after they end, then deleted with their tokens |
| Request log and confirmation codes | Up to 12 months |
| Change history | Kept with the rest of Vega Charging's change history |
7. Security
- Sign-in uses OAuth 2.1 with PKCE. Sign-in codes go only to exact, pre-approved return addresses, and each code can be used once.
- The sign-in page is tied to the browser that started the connection, so a forwarded sign-in link cannot connect someone else's account.
- A token works only for the Vega Charging address it was issued for (Claude's or ChatGPT's), and only for the connector.
- All secrets are stored as fingerprints (hashes) only.
- Access ends at once, on the next request, in any of these cases:
- the person's account is switched off;
- their role no longer may connect, or their account is no longer linked to a company.
8. Your choices and rights
- Disconnect at any time in the assistant's own settings (Claude: Customize → Connectors; ChatGPT: Settings → Apps & Connectors); the assistant then stops using the connection. To have a connection ended on Vega Charging's side as well, write to info@radx.app.
- Ask your company's Vega Charging administrator about the access your role has.
- Under Albanian Law No. 124/2024 on the protection of personal data, and the GDPR where it applies, you may ask for access to, correction of or erasure of your personal data, and you may object to its processing. Send requests to info@radx.app.
- You may complain to the Information and Data Protection Commissioner of Albania (IDP).
9. Changes and contact
When the connectors change, we update this policy and the date at the top of this page.
RadX SHPK · NIPT M41615026M · Tirana, Albania · info@radx.app