GridBot AI MCP Connector — Privacy Policy
Last updated: 2026-10-02
This policy covers the GridBot AI MCP connector — the interface that lets an AI assistant you connect (for example Claude or ChatGPT) read and control your own GridBot AI grid-trading bots. It is written to the disclosure requirements of both connector directories: what is collected, why, who receives it, how long it is kept, and what you can do about it.
1. What the connector collects
| Category | What it is | Why |
|---|---|---|
| Account identifiers | your GridBot AI user id, tenant id, billing account id, and the email address on your account | to bind every request to your account and no one else's |
| Connection records | which AI client you connected, when you allowed it, which permissions it has on which grids, and when that access ends | so you can see, change and end each connection |
| Tokens | digests of the access and refresh tokens issued to that client. The tokens themselves are not stored | so a leaked token can be revoked |
| Approval records | that an action asked for your approval, the exact action it named, whether you approved, declined or stopped it, and how it ended | so an action runs only once, only as approved, and so you can see what happened |
| Extra safety code records | a keyed digest of each code, what it was for, and how many wrong tries were made | to check the code and to limit guessing |
| Activity records | which tool ran, on which grid, which client asked, whether it was allowed, and why not if it was refused | your action log, dispute resolution and abuse detection |
| Network metadata | the source address a request came from, and a request id | rate limiting and incident investigation |
2. What the connector never collects
- Your mailbox. GridBot AI sends you email; it never reads it. There is no inbox integration in this service — no IMAP, no Gmail or Outlook connection, no mailbox token, no polling, and no endpoint that could fetch a message. Nothing the connector does needs your AI assistant to read your mail either: approvals happen on a GridBot AI page you open yourself.
- One-time codes. An Extra safety code is never accepted as a tool input, never appears in a tool result, and is never written to a log. Only a keyed digest of it is stored, and only until it expires.
- Your exchange API credentials. They are held by the trading service, not by the connector, and no connector tool can read or return them.
- Your conversation with the AI. The connector receives only the arguments of the tool call it is asked to perform. It does not receive, request, store or reconstruct chat history, conversation summaries, or files.
- Payment card data, health data, or government identifiers.
3. Who receives data
- The AI platform you connected. Tool results travel back through the platform that made the call (Anthropic or OpenAI, for example). Their handling of that data is governed by their own terms, not this policy.
- The email provider that delivers GridBot AI's mail. Extra safety codes, and the notice sent when you use panic, go through GridBot AI's outbound mail provider. No email is sent for each action.
- The exchange. Trading actions you allow are carried out on the exchange your bot is set up for.
Nothing is sold, and there is no advertising, profiling, or third-party analytics in this connector.
4. Retention
| Record | Kept for |
|---|---|
| Activity records for actions that changed something, and all security events | 400 days |
| Routine read and discovery activity | 90 days |
| Approval requests | 7 days after they are made |
| Extra safety code records | 15 minutes |
| Approve links | about 30 minutes |
| Idempotency records | 24 hours |
| Refresh-token records | until the connection's access ends, plus 24 hours to detect a late replay |
| Connection records | while the connection exists. Removing an ended connection hides it; the record stays with the activity it explains |
A record past its period is never used again. Approval requests are deleted by the database automatically when theirs ends. Automatic deletion of the other expired records is not finished yet; until it is, you can ask for them to be deleted (see Deletion below).
5. Your controls
- Change or end a connection at any time on the AI connector page in the GridBot AI dashboard. You can take a grid away, remove a permission, or end the connection. A change applies to the very next call; ending a connection invalidates its tokens at once rather than waiting for them to expire.
- Answer approvals on the same page or on the approve page your assistant links to. Approving, declining and stopping all need you to be signed in.
- Turn on Extra safety to need a code from your email before you connect a new assistant, approve anything, or widen what a connection can do.
- Revoke everything with the panic control on the AI connector page. It arms the kill switch on every grid, cancels open buy orders, ends every connection, and ends every approval request.
- See the activity. The action log on the AI connector page and the
spotgrid.list_audittool both show your own MCP activity, scoped to your account. - Deletion. Ask at the support address below. Records that a financial or legal obligation requires us to keep are kept for that period and no longer; we will tell you which those are.
6. Legal basis and location
Data is processed to perform the service you asked for, and to meet the security obligations that come with an interface that can place and cancel real orders.
7. Contact
Privacy questions: support@gridbotai.com Security reports: security@gridbotai.com (see the security disclosure page) Support: support@gridbotai.com