This policy covers the eGrow Model Context Protocol (MCP) server at mcp.egrow.com. It supplements the broader eGrow Privacy Policy, which governs the underlying eGrow account.
What this server does
The eGrow MCP server is a thin gateway that lets MCP-compatible AI clients (Claude, ChatGPT, Cursor, etc.) read and write your eGrow account data through a tool-based interface. It does not store your business data — every request is forwarded to the eGrow API in real time, and responses are returned to the calling client.
Data we collect
Authentication credentials. OAuth 2.1 access tokens or API keys you present in the Authorization header. Tokens are used to authenticate the request to the eGrow API and are not retained beyond the lifetime of the request.
Tool-call audit logs. For each tool invocation we log: tool name, category (read / write / destructive), duration in milliseconds, outcome (success / error / rate_limited / user_declined), error code if any, and the (non-secret) input arguments. These logs are retained for operational and security auditing. They do not include response payloads.
Operational telemetry. Standard HTTP access logs (IP, user-agent, status code) for abuse detection and performance monitoring.
Data returned to your AI client
Tool responses contain data from the eGrow account you authorized, limited to what your eGrow role can access. Depending on the tool, this can include:
Your user profile. Name, email, phone number, profile picture, country, language, role (owner, admin, invited), online and presence status, last connection time, and account settings such as currency.
Your customers. Names, phone numbers, email addresses, shipping addresses and cities, notes, tags, groups, blacklist and duplicate flags, and order history.
Your orders. Order numbers, line items, prices, totals, pipeline stages, tracking numbers, shipping carriers, assigned team members, sources, and UTM parameters.
Your products. Names, SKUs, variants, prices, stock levels, categories, and images.
Analytics. Aggregated order, confirmation, delivery, and revenue metrics for your account.
Internal identifiers. Record IDs for orders, customers, products, and pipelines, used so the AI client can reference the same record in a follow-up call.
This data is returned to the AI client you connected (for example Claude or ChatGPT) and is then handled under that client's own privacy policy.
Data we do not collect
We do not store tool responses or business data returned from the eGrow API.
We do not train models on your data.
We do not share data with third parties beyond what is required to fulfill the request (the eGrow API itself).
How your data flows
Your AI client sends a tool call to mcp.egrow.com/mcp with your bearer token.
The MCP server validates the token (OAuth introspection or API-key lookup), then forwards the corresponding GraphQL query to the eGrow API.
The eGrow API returns the response, which the MCP server passes back to your client unchanged.
The tool name and metadata are written to the audit log.
Retention
Authentication tokens: not retained server-side beyond request lifetime.
Audit logs: 90 days.
HTTP access logs: 30 days.
Third parties
The MCP server itself does not share data with third parties. The eGrow API it forwards to may use sub-processors documented in the main eGrow Privacy Policy.
Your rights
Your account-level rights (access, deletion, export, correction) are exercised through the eGrow account dashboard — they are not separate for the MCP server.
Security
All traffic is TLS-encrypted.
OAuth tokens are validated via introspection against the eGrow auth server on every request.
Tools that change data (refunds, merges, bulk stage moves, ad-hoc mutations) are marked destructive, so clients like Claude ask the user for approval before each call.
Per-tool rate limits and audit logs are enforced for abuse detection.