Privacy Policy for TerriTool for ChatGPT

01What the plugin does

The plugin lets ChatGPT call the TerriTool MCP server on your behalf to work with your own TerriTool data: saved accounts, lead searches, contacts, notes, activities and routes. Managers additionally see team data that their TerriTool role already permits. The plugin runs every action as the TerriTool user who signed in. It does not grant any access that your TerriTool account does not already have.

We do not receive your ChatGPT conversation. ChatGPT sends TerriTool only the specific tool requests it decides to make (for example “search saved accounts in Oakland”), and TerriTool returns the results of those requests. Everything else you type in ChatGPT stays with OpenAI under OpenAI’s own terms and privacy policy.

02Information we receive

Sign-in and connection

When you connect, you are sent to TerriTool’s own hosted sign-in and consent page. You enter your TerriTool email and password on TerriTool, never in ChatGPT, and TerriTool never sees your ChatGPT or OpenAI password. TerriTool then issues OAuth tokens to ChatGPT that are tied to your TerriTool user ID and role. We record the OAuth client that connected, the tokens issued and when they were used, refreshed or revoked.

Tool requests and results

For each tool call we receive the arguments ChatGPT sends (such as a city and business type, a company or contact name, note or activity text, a route name, a confirmation flag) and we generate the result (such as matching accounts, lead candidates, contact records, route links and credit balances). We keep a diagnostic log of each call containing your user ID, the tool name, a truncated copy of the arguments and result, the related search, list or route ID, the connection session ID, the connecting client name, the time taken, the HTTP status and whether an error occurred.

Operational analytics

When enabled, we send operational telemetry to PostHog to troubleshoot requests and monitor reliability. Events include the authenticated TerriTool user ID and role, target account ID where applicable, tool name, API method and path, duration, status, sanitized error details, selected record IDs and a tracing ID. If the client explicitly supplies the current task-specific request in user_query, we may include a redacted excerpt limited to 1,000 characters. We do not receive or reconstruct the full ChatGPT conversation. Raw tool results, contact records, notes, authorization headers, passwords and confirmation tokens are not sent as event payloads. Automated redaction reduces sensitive content but cannot identify every possible personal detail in free text; do not include sensitive information in this optional field. TerriTool administrators can disable operational telemetry or query logging separately.

Technical information

Request logs include a limited set of HTTP headers: user agent, content type, accept, origin, referer and the MCP session ID. Authorization headers and tokens are not stored in these logs.

Operation records

For lead saves, contact purchases, lead searches and route creation, we store an operation record (including the result) so that an identical retried request is answered from the stored result instead of charging you or creating data twice.

Information we do not collect through the plugin

We do not collect payment card details, precise device location, or your ChatGPT account details through the plugin. Subscriptions and credit purchases happen in TerriTool, outside ChatGPT.

03How we use it

• To do what you asked. Run the requested search, save, note, activity, contact lookup or route and return the result to ChatGPT.
• To enforce your account’s permissions. Check your role, active status and subscription before any tool runs, and limit managers’ team actions to their own team.
• To account for credits. Show costs before a credit-consuming action and deduct credits only after you confirm.
• To prevent duplicate charges. Use operation records to replay a completed request rather than execute it again.
• To keep the service secure and working. Detect abuse, troubleshoot failures and provider errors, and improve reliability.
• To meet legal obligations and resolve disputes.

We do not use plugin data for advertising, and we do not sell personal information.

04Who we share it with

• OpenAI. Tool results are returned to ChatGPT so it can show them to you. OpenAI’s handling of that content is governed by OpenAI’s terms and privacy policy and your ChatGPT workspace settings.
• Google Maps Platform. Lead searches, address lookups and route building send place queries, business names and addresses to Google’s Places, Geocoding and Directions services.
• Business and contact data providers. Contact discovery sends the target company’s name, website domain and location to FullEnrich and OpenCorporates, and may use AI model providers as a secondary source. We send business identifiers, not your TerriTool account credentials.
• PostHog. Receives the operational telemetry described above when enabled, for service reliability and troubleshooting.
• Hosting and infrastructure providers that run TerriTool under contract.
• Your organization. If your TerriTool account belongs to a company team, your manager can see the saved accounts, activities and routes that your TerriTool role already shares with them.
• Legal. When required by law, legal process, or to protect TerriTool, its users or the public.

05Credits and purchases

Saving AI leads and redeeming contact details consume TerriTool account credits. The plugin shows a preview and the credit cost first and only proceeds after you confirm. The plugin never collects payment credentials. Buying credits or changing your subscription happens in the TerriTool web or mobile app.

06Retention and deletion

• OAuth tokens. Access tokens expire after one hour, refresh tokens after thirty days, and authorization codes after ten minutes. Revoked tokens are not reusable.
• Data you create (saved accounts, contacts, notes, activities, routes) is part of your TerriTool account and follows your account’s retention and deletion.
• Diagnostic logs and operation records are kept while your account is active and for up to twelve months after it closes, unless a longer period is required by law or to resolve a dispute. Deleting an operation record also removes the duplicate-charge protection for that request.

To request a copy or deletion of plugin data, email support@territool.com from the address on your TerriTool account. We respond within 30 days.

07Your choices and rights

• Disconnect any time. Remove or disconnect the TerriTool plugin in ChatGPT’s plugin settings. Tokens then expire and ChatGPT can no longer act on your account.
• Control what is sent. ChatGPT asks your permission before tool actions where its settings require it, and the plugin asks you to confirm every credit-consuming or route-publishing action.
• Access, correct, delete. You can manage your saved data in the TerriTool app and request access or deletion of plugin logs by email.
• California residents may exercise their rights under the CCPA/CPRA by emailing support@territool.com. We do not sell or share personal information for cross-context behavioral advertising.

08Security

All plugin traffic uses HTTPS. Authorization uses OAuth 2.1 with PKCE, and tokens are bound to a single TerriTool user and role. Every tool runs through the same permission, subscription and credit checks as the TerriTool mobile and web apps. No security measure is perfect; report concerns to support@territool.com.

09Children, changes, contact

TerriTool is a business tool for adults and is not directed to anyone under 18. We may update this policy; the effective date and version at the top will change and material changes will be noted on this page. Continued use of the plugin after a change means you accept the updated policy.

TerriTool LLC · support@territool.com · www.territool.com