Privacy Policy — r1-mcp Addendum
Summary: r1-mcp connects an AI agent (such as Claude) to your cloud network-management platform. Unlike the servers covered by the MCP Products Addendum, it stores a substantial part of what it handles: events your platform sends it, a record of the client devices seen on your network, configuration backups and snapshots, and floor-plan images. It can also work with your own on-premises probe through Probe MCP. This addendum describes what it keeps, for how long, and who else sees it.
Contents
What r1-mcp is
r1-mcp signs in to your cloud network-management platform with API credentials you create there, and lets an AI agent query and change your network through the platform's own API. It also offers:
- Event analysis: your platform can send r1-mcp events (webhooks) about your network, which r1-mcp stores so your agent can analyse them later.
- Backups, snapshots and copies of venue configuration, so a configuration can be restored or copied to another venue.
- Test beds and procedures: records of switches you test with, their running configurations, and the output of the procedures you run against them.
- Floor plans, and live client positions on them, drawn from your platform and from location-service data sources you connect.
- An AI chat console, available to accounts we enable it for.
- A link to Probe MCP, for on-premises data your own probe collects.
Why this addendum exists separately
Our MCP Products Addendum covers MCP servers that relay what a platform returns and keep no copy of it. r1-mcp keeps copies, as described below, and when linked to Probe MCP it works with data from inside your network. It therefore has its own addendum.
Data collected
1. Account data
You sign in with Google. We request the openid, email and profile scopes and store:
- Your email address (which Google must report as verified), your name and the address of your profile picture
- Your Google account identifier, so we can recognise you on your next sign-in
- The Terms and Privacy Policy versions you have accepted, the features enabled for your account, and your branding preferences (including any logo you upload)
When you accept our Terms and Privacy Policy, we record which versions you accepted, when, and the IP address and browser user agent you accepted from.
We do not receive your Google password, and we do not ask Google for access to any other Google service.
2. Platform credentials and tokens
For each platform connection you add, we store the API client ID, the client secret, your region and your tenant identifier. The client secret is encrypted at rest.
When r1-mcp signs in to your platform, the platform issues an access token. We cache it, unencrypted, until shortly before it expires (usually under an hour). Short-lived tokens for device command-line sessions are cached the same way for up to 15 minutes.
If you connect a location-service data source, or link Probe MCP, the password or shared secret for it is encrypted at rest.
3. Events your platform sends us
If you point your platform's webhooks at r1-mcp, we store each event as the platform sent it. Events can include client device MAC addresses, access point MAC addresses, user names from authentication events, and administrator activity, including administrator email addresses.
From these events we also build:
- A client device registry: for each client device, its MAC address, host name, operating system type, the networks and radio bands it used, how much data it transferred, and the last access point and venue it was seen at. A MAC address and host name can identify a particular person's phone or laptop.
- Summaries of client roaming between access points, event counters, and notices and alerts your watches produce
4. Configuration data
- Venue backups and configuration snapshots, which can include wireless network passphrases and authentication-server secrets. The configuration content is encrypted at rest.
- Switch running configurations for test-bed devices, which can include password hashes and management secrets. Encrypted at rest. The device serial number, software version and a checksum are stored alongside, unencrypted.
- Test-bed records: switch serial numbers, models and venues
- Procedure runs: the steps of each procedure and up to 4,000 characters of command-line output per step as evidence
5. Floor plans and client positions
- Floor-plan images fetched from your platform, encrypted at rest
- Live client positions from your platform or a connected location service, held for 15 minutes or less to draw the current view. We do not keep a history of positions.
6. Notes
Your agent can save notes about API endpoints and data sources, to help it on later requests. They are kept with your account. We may promote a note that contains no customer data to a shared note visible to all r1-mcp users.
7. MCP tokens
When you connect an MCP client, we issue it access and refresh tokens. Your dashboard session is also a token. We store every one of these only as an irreversible hash.
8. Usage data
For each tool call your agent makes, we record the name of the tool, the time, whether it succeeded, and how long it took. We do not record the arguments your agent sent or what came back.
9. Operational logs
Our servers log errors and operational events. Some of these log entries include your email address, for example when an account is created or a sign-in is refused. Error entries can include part of an error message returned by your platform or by Google. Webhook event contents are not logged.
How r1-mcp uses this data
- To run the operations you and your agent request, and to sign in to your platform on your behalf
- To store and analyse your network's events, backups, test beds and procedures for you
- To debug errors and prevent abuse
- To operate the features enabled for your account
r1-mcp is currently free. We do not use your network data for any other purpose, and we do not sell it.
Sharing
- Your platform: we send your requests to your cloud network-management platform, and it sends us the events you configure. It has its own privacy policy; review it.
- Your AI agent: what r1-mcp returns is sent to the MCP client you connected, and so to the AI provider behind it (for example, Anthropic if you use Claude). You choose that agent, and its provider's terms govern it. r1-mcp does not send your data to Anthropic itself.
- Cloudflare: our servers, database, storage and logs run on Cloudflare. If your account has the AI chat console enabled, your chat messages and the network data the chat retrieves are sent to open-weight language models run on Cloudflare Workers AI. Chat conversations are not stored by r1-mcp. PDF exports are rendered with Cloudflare's browser rendering service.
- Probe MCP: if you link r1-mcp to your Probe MCP account, r1-mcp sends Probe MCP your Google account identifier and email address (to confirm the link), the location-service credentials you connected, and switch configurations you ask to restore through your probe. It also reads data your probe has collected. Probe MCP is a NeuralConfig service, and its addendum describes what it keeps.
- Google: for sign-in. The dashboard also loads fonts from Google, which exposes your IP address to Google when a page loads.
- Support chat: the dashboard includes NeuralConfig's own support chat, served from support.neuralconfig.com. It is not a third party.
- No other third parties except as described in the Master Privacy Policy (legal process, for example).
Retention
r1-mcp deletes data automatically on the schedule below. A sweep runs every hour.
| Data | Kept for |
|---|---|
| Client connection events | 7 days |
| Access point and authentication events | 30 days |
| Administrator activity events | 90 days |
| Incident events | 365 days |
| Client device registry | 180 days after a device was last seen |
| Roaming summaries | 90 days |
| Event counters | 120 days |
| Configuration snapshots | 30 days |
| Test beds and their switch configurations | 365 days after last change |
| Procedure runs | 7 days; test-plan runs 90 days |
| Draft procedures | 30 days |
| Usage data | 90 days |
| Expired or revoked MCP tokens and sessions | 7 days after expiry or revocation |
| Cached platform tokens | Until they expire, usually under an hour |
| Live client positions | 15 minutes or less |
Some of these also have a per-account limit on the number of records, and the oldest are removed first.
Kept until you delete them, or until your account is deleted:
- Venue backups (up to 50 per account)
- Floor-plan images. Only the newest 50 per platform connection are kept.
- Finished procedures, notes, your logo, and your platform credentials
Deleting a platform connection removes its credentials and cached tokens. It does not delete the events, device records, backups, snapshots, floor plans or test beds already collected through it. To remove those, delete your account, or ask us as described under Your rights.
Deleting your account removes everything r1-mcp stores for you, except what Your rights lists as kept.
Terms acceptance records, including the IP address and user agent, are kept for as long as we may need to show what you agreed to and when. They are kept even after you delete your account.
Request logs: Cloudflare keeps the logs of requests to our servers for a limited period set by Cloudflare.
Operational logs, which can include your email address, are kept by Cloudflare for a limited period and then deleted automatically. They cannot be deleted individually, including when you delete your account.
Security
- Platform client secrets, location-service and probe-link secrets, venue backups, configuration snapshots, switch configurations and floor-plan images are encrypted at rest with AES-256-GCM, using a key derived separately for each record.
- MCP tokens, sessions and webhook secrets are stored only as hashes.
- Each account's data is separated by the application: every query is limited to the signed-in account.
- Platform access tokens are cached unencrypted for their short lifetime.
- Device command-line sessions pass through your platform's own relay. r1-mcp keeps their scrollback in memory only, for at most 13 minutes, and does not store it.
You are responsible for keeping the tokens we issue to your MCP client, and your webhook address, secret. Treat them as passwords.
Your rights
- Delete a platform connection, revoke your MCP connectors, delete your logo, a data source, a backup, a snapshot, a test bed or a procedure: at any time, from the dashboard or through your agent.
- Delete your account: at any time, from the dashboard, by typing your email address to confirm. This deletes your account and everything stored with it: platform connections and credentials, data sources and your Probe MCP link, collected events and device records, backups, snapshots, test beds, procedures, floor plans, notes, usage data, your logo, and your MCP connectors, webhook address and sessions. It takes effect straight away. - What is kept: your terms acceptance records, as our legal record of what you agreed to. So that they stay linked, your user record remains, with your name, picture and preferences removed and your email address replaced by a one-way hash of it. The hash is pseudonymous: it cannot be turned back into your address, but it can be matched if the same address is presented to us again. Signing in again later creates a new, empty account. - Shared notes: a note we promoted to a shared note (see Notes) stays available to other users, no longer linked to your name or email address. - Outside r1-mcp: if r1-mcp set up location-service connections in your platform or on your probe, we try to remove them. Anything we could not remove is listed for you when the deletion finishes, so you can remove it yourself. - When it is refused: while a network test or an unattended procedure is still running on your network. Stop it or let it finish, then delete your account.
- Delete collected events and device records without deleting your account, or export your data: email [email protected] from the address you sign in with. There is no self-service control for these yet. We will act on your request within 30 days.
- Standard rights from the Master Privacy Policy (access, correction, and so on) apply where relevant.
Contact
← Back to the Master Privacy Policy