YoCharge MCP Connector Privacy Policy
Last updated 21 October 2026
This policy covers the YoCharge MCP connector (setup and tools): the service that lets an AI agent such as Claude connect to a YoCharge CPO Admin account and answer questions about that organization’s charging network. It does not cover the YoCharge platform, the yocharge.com website or the YoCharge mobile apps. For those, see the YoCharge Privacy Policy.
Summary
The connector is a stateless bridge, not a data store. It does not keep a copy of your stations, charging sessions or user records. Each tool call becomes a live, read-only request to the YoCharge platform API, scoped to your organization and made with your own authorization. The response goes back to your AI agent, and the connector keeps nothing from it.
What the connector stores
To make the connection work, the connector stores a small amount of operational data, kept separately from your charging data:
| Data | Why we store it |
|---|---|
| OAuth client registration (client ID, redirect URI, client name) | Identifies which AI product is connecting |
| Access token and refresh token | Lets your AI agent make tool calls without you signing in every time |
| Your YoCharge platform authorization | Sent with each tool call so requests run under your own account’s permissions |
| Organization identifier and token timestamps (issued, expires) | Lets a credential be looked up, expired or revoked |
| Request logs (time, client ID, tool name, success or failure) | Fixing problems and detecting abuse |
Tokens and authorizations are stored in our database and in an in-memory cache for fast lookups. We do not store the contents of tool responses: station lists, charging sessions and user records pass through the connector and are not written to any database or log.
What leaves YoCharge
- The AI product you connected (for example Anthropic’s Claude) receives only the data returned by the tool calls it makes in your conversation. Depending on the question, that can include station details, charging session records and user records, including email addresses and mobile numbers (from the List Users tool). User records cover every account in your organization: drivers, and also your own admin and staff accounts. How the AI product then handles that data is governed by its own terms and privacy policy.
- The YoCharge platform API receives each tool call, because it holds the data being asked for. This is a call within YoCharge, not a share with a third party.
- We do not share stored tokens, credentials or request logs with anyone else.
Only connect the connector, and only grant access, to people in your organization who are allowed to see this data.
How we use this data
- To authenticate your AI agent’s requests and confirm they’re limited to your organization.
- To send each tool call to the right YoCharge API with your own authorization.
- To let you or YoCharge support revoke one connection without affecting anything else on your account.
- To fix connection problems, such as a failed sign-in or an expired token.
We do not use this data for advertising, and we do not sell it.
How long we keep it
- Access tokens expire after 30 days and refresh tokens after 90 days, unless revoked sooner.
- Authorization codes used while connecting expire within minutes and work only once.
- Revoking a connection (For Developers → AI Integrations in the CPO Admin portal) deactivates its token immediately.
- Request logs are kept only as long as needed to fix problems, not indefinitely.
Security
- All connections use HTTPS.
- Sign-in uses OAuth 2.1 (authorization code flow with PKCE). Your password is entered only on YoCharge’s own page and is never shared with the AI product.
- The connector has no standing access of its own. It acts only with the authorization issued to the connection you approved, and only within your organization.
- It offers a fixed, individually reviewed set of read-only tools. There is no general “call any endpoint” tool.
Your choices
- Revoke a connection at any time from For Developers → AI Integrations in the CPO Admin portal, or remove the connector in your AI product’s settings.
- Revoking a connection does not affect your other API keys or integrations.
Changes to this policy
If we change what the connector collects or how it’s used, we’ll update the “Last updated” date above and, for material changes, note it on the AI Integrations page.
Contact
Questions about this policy or the connector: support@yocharge.com.