Privacy
What the ChatGPT and MCP plugin can read and write, and why
What ResellerHQ's ChatGPT and MCP plugin can read and write in your account, who receives it, how long it is kept, and why.
Connecting an assistant to ResellerHQ (an OAuth sign-in, or an API key pasted into an MCP client) gives it a set of tools, each scoped to your own account. Every field below is what one of those tools can return or take in, grouped by what the tools do. Nothing here is collected beyond what the tool itself needs to answer the call it was given.
Account and wallet
Tools: get_account, get_wallet
Returns: your account name, environment (sandbox or live), status, which product lines are open, your wallet's available and held balance and its recent movements, and the billing defaults a new invoice falls back to (legal name, address, tax id, billing email).
Why: So an assistant can check there is enough in the wallet before it previews a purchase, and can fill an invoice's defaults correctly.
Who receives it: The assistant and the host you are using (ChatGPT, or another MCP client), for the one request that asked. ResellerHQ's own servers see it to serve the call, the same as any other API request to your account. Nobody else.
Kept for: This is a live read of your own account's existing records; ResellerHQ stores nothing extra because a tool was called. The call itself - which tool, whether it succeeded, how long it took - is logged the same as every other API request; the fields it returned are never written to that log.
Customers
Tools: list_customers, get_customer, create_customer, update_customer, assign_price_list
Returns or takes in: a customer's email, name and billing address, your own reference for them, their tax id, and which price list they are on.
Why: To look a customer up before quoting, buying or invoicing for them, and to record one you add through the assistant.
Who receives it: The assistant and host, for that one call; ResellerHQ's own servers to serve it. Nobody else - a customer's details are never sold, shared with a data broker, or forwarded anywhere outside your account.
Kept for: As long as the customer record itself exists in your account, exactly as it does today through the dashboard and the REST API. Marked as untrusted text in the tool's own result, since a customer chose those words, not you.
Your controls: Change or remove a customer's details from the dashboard or the API; both change what the plugin reads immediately, since it reads the same record.
Domains
Tools: search_domains, list_domains, get_domain, prepare_domain_registration, prepare_domain_renewal, confirm_purchase, update_domain
Returns or takes in: domain names, their status and nameservers, and the registrant/admin/tech/billing contact on file - name, organization, email, phone, address, city, state, postal code and country.
Why: To check availability and price before registering, to show what you already hold, and to change a domain's nameservers, lock or contacts when you ask the assistant to.
Who receives it: The assistant and host, for that one call; ResellerHQ's own servers, and the domain registry when a name is actually checked or registered - the same registrar call the dashboard makes. Nobody else.
Kept for: As long as the domain is registered through your account. Every contact field is marked as untrusted text in the tool's own result, since it was written by whoever set the contact, not by you.
Your controls: Change a domain's contacts or nameservers from the dashboard, the API, or the assistant itself; WHOIS privacy, where the ending offers it, keeps the contact off the public WHOIS record the same way it does today.
Phone numbers
Tools: find_numbers, list_numbers, get_number, read_messages, prepare_number_purchase, prepare_number_renewal, confirm_purchase, cancel_number
Returns: the numbers you hold, their status and rental details, and the SMS they have received - the sender and the message body.
Why: To buy, renew or cancel a rental, and to read messages a customer or a verification service sent to a number you hold.
Who receives it: The assistant and host, for that one call; ResellerHQ's own servers, and the carrier that routes the number. Nobody else.
Kept for: As long as the rental and its messages exist in your account, the same retention the dashboard shows them under. Every message's sender and body are marked as untrusted text, since whoever texted the number wrote them, not you - an assistant is told to treat that text as data to report, never as instructions to follow.
Your controls: Cancel a rental shortly after buying it, from the dashboard, the API or the assistant, and nothing further is charged or received.
Mailbox licences
Tools: list_licence_plans, list_licences, get_licence, list_licence_users
Returns or takes in: which plans are on offer, the licences you hold - plan, vendor, domain, seat count and status - each mailbox on a licence, with its first and last name, email address and provisioning status, and, when you buy licences, the admin mailbox's email and the organisation name set on the vendor account. Nothing about any mailbox's own contents.
Why: To buy mailbox licences on a domain, change a seat count, or see who the seats on a licence belong to, when you ask the assistant to.
Who receives it: The assistant and host, for that one call; ResellerHQ's own servers, and the mailbox vendor (Google or Microsoft) when seats are actually provisioned - the same provisioning call the dashboard makes. Nobody else.
Kept for: As long as the licence exists in your account.
Mailboxes
Tools: get_mailbox_price, connect_mailbox_domain, list_mailbox_domains, get_mailbox_domain, list_mailboxes, get_mailbox_credentials, delete_mailbox_domain, prepare_mailbox_order
Returns or takes in: the domains you have connected for mailboxes - domain, nameservers and status - and each mailbox on them, with its first and last name, email address and setup status. When you ask for them, a mailbox's sign-in details: its password, app password and two-step verification secret. Nothing about any mailbox's own contents.
Why: To connect a domain, order mailboxes on it, hand over their sign-in details or delete them, when you ask the assistant to.
Who receives it: The assistant and host, for that one call; ResellerHQ's own servers, where sign-in details are kept encrypted; and, when mailboxes are actually set up, the provider that sets them up for us and Google, which hosts them - the same calls the dashboard makes. Nobody else.
Kept for: As long as the domain is connected in your account. Sign-in details are erased when it is deleted.
Sales, invoices, orders and price lists
Tools: quote, list_sales, sales_summary, list_orders, get_order, list_invoices, get_invoice, create_invoice, issue_invoice, mark_invoice_paid, void_invoice, share_invoice, create_price_list, update_price_list
Returns or takes in: what a customer is quoted or charged, your margin, invoice line items and totals, a note shown on an invoice, the price rules a price list is built from, and an order's own status and dates -list_orders and get_order return the same domain, number or licence order details already covered above, not a new category. share_invoice creates a public, read-only link to one invoice.
Why: To price something for a named customer, bill them for what they bought, and record that they paid - ResellerHQ takes no payment itself; you collect it however you already do and record that here.
Who receives it: The assistant and host, for that one call; ResellerHQ's own servers. A shared invoice's link is readable by anyone holding it, exactly as the dashboard's own "share" feature already makes it. Nobody else.
Kept for: As long as the sale, invoice or price list exists in your account. An invoice's own note is marked as untrusted text.
No payment data: No card number, bank detail or payment-processor credential is ever read or written through this surface - only the wholesale cost, the price charged, and the resulting order or invoice id, the same figures the dashboard already shows you.
Docs
Tools: search_docs
Returns: the matching page from ResellerHQ's own public docs site, as Markdown.
Why: So an assistant can answer a question from the docs instead of guessing.
Who receives it: The assistant and host, for that one call. The docs are public pages with no personal data in them; nothing about your account is sent to fetch them.
Kept for: Not applicable - no account data is involved.
Every tool call is logged the same way any other API request is - which tool, the outcome and how long it took, against the account and the key or connection that made it - never the arguments sent or the data returned. A tool that changes your account (a purchase, an edit) additionally writes one line to your account's own activity trail, visible in the dashboard, the same as a change made there directly.