Privacy policy
Last Updated: 4 September 2026
This Privacy Policy describes how GetCargo Inc. (“Cargo”, “we”, “us”) collects, uses, shares, and retains personal data, and the controls available to you. It applies to:
- our websites, including https://www.getcargo.io and related pages;
- the Cargo cloud product (the “Services”);
- our hosted Model Context Protocol server at https://mcp.getcargo.io/mcp (the “MCP server”); and
- the Cargo app listed in ChatGPT (the “ChatGPT app”), which connects to the MCP server.
If you are using Cargo under an organization account, your organization is typically the controller of Customer Content (the data it puts into Cargo). Cargo is the processor of that data, on the terms of our Data Processing Agreement. Cargo is the controller of account, billing, website, and product-analytics data we collect for our own business.
Contact: legal@getcargo.io. Postal address: GetCargo Inc., 603 Tennessee St, San Francisco, California 94107, United States.
1. Information we collect
1.1 Account and workspace data (Cargo as controller)
When you create an account, join a workspace, or authenticate (including via the ChatGPT app or another MCP client), we collect:
- identifiers: name, email address, user uuid, workspace uuid and name;
- authentication data: login events, OAuth grants to connected apps (including ChatGPT), and session tokens;
- billing and plan data: subscription plan, credit balances, invoices, and payment-method metadata processed by our payment provider;
- profile and role data: workspace membership and permissions.
1.2 Customer Content (Cargo as processor)
Depending on how your organization uses the Services, Customer Content may include identifiers, contact details, professional information, CRM and GTM records, communications content, files, knowledge-base documents, workflow configuration, run history, and other data your organization submits or generates. Categories of data subjects may include your organization’s users, employees, customers, prospects, and business contacts.
Cargo does not require special-category or “prohibited” data. Do not submit it unless your contract expressly allows it.
1.3 Website and product analytics
When you visit our websites or use the product, we and our processors may collect IP address, browser and device type, pages viewed, referring URLs, timestamps, and similar usage events. We use Cookiebot for consent, RudderStack and related analytics tools for product usage, and Dub for referral attribution. Advertising cookies load only if you consent.
1.4 Support and communications
If you contact us, we receive the contents of the message, your contact details, and any attachments you send.
2. ChatGPT app and MCP tools
The ChatGPT app is a client of our MCP server. After you authorize it, ChatGPT sends tool inputs to Cargo and receives tool outputs back into the chat. Cargo does not receive the rest of your ChatGPT conversation unless that text is included in a tool argument.
OpenAI is the operator of ChatGPT. Data ChatGPT sends to or receives from Cargo is also processed by OpenAI under OpenAI’s terms and privacy policy. Disconnecting the app in ChatGPT or revoking the OAuth grant in Cargo stops further tool calls; it does not delete history OpenAI already holds.
2.1 Tool inputs we receive
Tools may receive, as needed to fulfill the request:
- identity of the signed-in user and bound workspace (from the OAuth token;
whoamitakes no extra input); - search strings, filters, limits, and timestamps you or ChatGPT supply (
search_actions,list_runs,query_models, context search); - action objects, field values, and record payloads (
get_action_schema,autocomplete_action,execute_action,execute_action_batch); - run or batch uuids (
get_run,get_batch); - model identifiers and SQL
SELECTtext (describe_model,query_models); - context paths, globs, and line ranges (
map_context,search_context,browse_context,read_context).
2.2 Tool outputs we return
Tools return only what is needed for the stated purpose. We do not return computed node configs, execution traces, Temporal workflow ids, trace ids, raw run or batch records, or internal object-storage keys.
| Tool | Categories returned |
|---|---|
whoami | User uuid, first name, last name, email; workspace uuid and name; plan name and credit balances |
get_usage | Credit usage for the last 7 days, grouped by integration, with day timestamps |
search_actions | Matching actions (name, slug, kind, integration, credit cost, autocomplete hints) |
get_action_schema | Input and output JSON schemas for an action |
autocomplete_action | Options from a connected system (for example Slack channel names, HubSpot object types) |
execute_action | Outcome; last-node action output (Customer Content such as contact or company fields the action produced); run uuid; credits used; or an error message |
execute_action_batch | Outcome; batch uuid; credits used; a time-limited download URL for the output CSV; or an error message |
get_run | Same shape as execute_action (action output, run uuid, credits). Not nested debug data |
get_batch | Same shape as execute_action_batch. Not the raw batch record |
list_runs | Run uuid, status, and error message |
list_models / describe_model | Model uuid, slug, name, description, kind, column labels and types |
query_models | Rows from workspace models. Those rows may include personal data your organization stored (names, emails, titles, and similar) |
map_context / search_context / browse_context / read_context | Knowledge-base paths, titles, summaries, matching snippets, and file text your organization stored |
Action output, SQL rows, autocomplete options, context files, and batch CSVs can contain nested fields (for example a contact object with email, name, and company). Those nested fields are Customer Content, not diagnostic telemetry. Error messages may quote a failed input or a provider error.
3. How we use information
We use the information in Section 1 to:
- provide, operate, secure, and support the Services, websites, MCP server, and ChatGPT app;
- authenticate you, bind an MCP session to one workspace, and enforce permissions;
- run the actions, queries, and context reads you (or an authorized client such as ChatGPT) request, and return the results to that client;
- meter credits, bill, and prevent fraud or abuse;
- understand product usage and improve the Services (on aggregated or controller-side analytics data, not by training foundation models on Customer Content except as your contract allows);
- communicate with you about the product, security, and — where permitted — marketing;
- comply with law and enforce our terms.
We do not sell personal data. We do not share it for cross-context behavioral advertising except where website advertising cookies run after Cookiebot consent.
4. Recipients
We disclose personal data to:
- the MCP client you authorized, including OpenAI when you use the ChatGPT app, which receives the tool inputs and outputs in Section 2;
- our subprocessors, listed in Schedule 3 of the DPA, including Amazon Web Services (hosting), Auth0/Okta (authentication), Temporal (orchestration), Datadog (observability), ClickHouse Cloud (analytics warehouse), and model providers (OpenAI, Anthropic) when you use Cargo-operated AI features;
- systems your organization connects (CRM, warehouse, enrichment, Slack, email, and similar). Those parties are your processors, not ours. Tool calls that read or write them send the relevant Customer Content to those systems;
- payment, support, and analytics vendors (including RudderStack, Snowflake, Dub, Cookiebot, and our support provider) as needed to operate the business;
- authorities when required by law.
Employees access Customer Content only as needed to provide the Services, with confidentiality obligations.
5. Retention
- Account and workspace data. Kept for the life of the account and a reasonable period afterward for security, billing, and legal claims.
- Customer Content. Kept for the term of the contract, then deleted or returned as described in the DPA (typically within 30 days after termination, except backups on their ordinary cycle and data we must keep by law).
- MCP OAuth grants. Kept until you or an admin revokes them, or they expire.
- Tool call payloads. Stored in run and batch history as part of providing the Services (so you can inspect what ran), for the same period as Customer Content. MCP responses themselves are not kept as a separate debug archive.
- Website logs and analytics. Kept on a rolling basis as needed for security and product analytics.
- Support tickets. Kept as needed to resolve the request and for a reasonable period afterward.
6. User controls
You can:
- review this policy before installing the ChatGPT app;
- disconnect the Cargo app in ChatGPT settings, and revoke the OAuth grant on the MCP server page in Cargo (Connected apps);
- update your name and email in account settings;
- ask a workspace admin to remove your membership or delete Customer Content where the product allows it;
- manage website cookies through Cookiebot (banner or cookie declaration);
- request access, correction, deletion, export, or restriction of personal data Cargo holds as controller by emailing legal@getcargo.io. We respond within one month. For Customer Content, we will direct you to your organization (the controller) or assist that organization under the DPA.
California residents also have the rights described in Section 8. We do not sell or share personal information as those terms are defined in the CPRA.
7. Cookies
Cargo uses cookies and similar technologies on the websites:
- strictly necessary — authentication, security, and Cookiebot consent;
- analytics — to understand how the site and product are used (RudderStack and related tools), if you consent;
- advertising / attribution — if you consent (including Dub referral cookies and any advertising partners Cookiebot lists).
You can refuse non-essential cookies in the banner or your browser. Cookiebot’s declaration on our site lists the current vendors. Cargo does not use Google’s DoubleClick DART cookie.
8. CCPA / CPRA (California)
California consumers may request that we disclose the categories and specific pieces of personal data we have collected as a business, delete that personal data, or correct inaccuracies. We do not sell or share personal data. We will not discriminate against you for exercising these rights. Email legal@getcargo.io. We have 45 days to respond, extendable as the law allows.
Where we process Customer Content as a service provider, those requests should go to your organization. We will not use Customer Content except to provide the Services, for security and debugging, and as otherwise permitted for service providers under the CPRA.
9. GDPR and similar laws
If European Data Protection Laws apply to personal data Cargo processes as controller, you have the right to access, rectification, erasure, restriction, objection, and portability, and the right to lodge a complaint with a supervisory authority. Email legal@getcargo.io. We respond within one month.
Transfers of Customer Content outside the EEA, UK, or Switzerland are handled under the DPA, including Standard Contractual Clauses where required. Subprocessor locations are in DPA Schedule 3.
10. Children
The Services and ChatGPT app are for business users. We do not knowingly collect personal data from children under 16. If you believe we have, contact us and we will delete it.
11. Changes
We may update this policy. We will change the “Last Updated” date above and post the new version at https://www.getcargo.io/privacy. Material changes that affect the ChatGPT app or MCP tools will be reflected here before those tools’ inputs or outputs change in a way this policy describes.
12. Contact
GetCargo Inc. 603 Tennessee St San Francisco, California 94107 United States
Related documents: Terms of Service, Data Processing Agreement, Security.
Give your agents a runtime
Bring the agents you have.Start free, deploy in one command.