Privacy Policy

PatchOps Privacy Policy

PatchOps is a custom-built MCP management platform. This page explains the data we need to run your dashboard and MCP workflows. We never sell user data.

Last updated: April 21, 2026
Quick Summary
  • We collect only what we need to run your dashboard and MCP connections.
  • Stored connection credentials and tokens are encrypted.
  • We track tool usage so your analytics and billing stay accurate.
  • You decide which third-party providers to connect.
  • We never sell your data.

This Privacy Policy explains how PatchOps (“we,” “us,” “our”) collects, uses, and protects information across the PatchOps website, dashboard, APIs, MCP servers, code execution features, and connected integrations (collectively, the “Service”). We keep data collection focused on what is needed to run the dashboard, power MCP workflows, and keep accounts secure.

Data We Collect

We collect information necessary to provide the dashboard and integrations you use, keep the Service reliable, and comply with legal obligations.

Account & Profile

  • Name, email, and profile details so we can create your account and show them in the dashboard.
  • Role, account status, and login timestamps so we can manage access.

Authentication & OAuth

  • OAuth identifiers, tokens, scopes, and expirations so your connected providers stay linked.
  • Session cookies and JWT data to keep your sessions secure.

Connections & Credentials

  • Connection names, provider type, MCP server URLs, and instance IDs so the dashboard can manage each integration.
  • API keys and tokens you provide, stored in encrypted form so calls can be made on your behalf.

Usage, Analytics & Logs

  • Tool call metadata (provider, tool name, timing, success) so we can show usage analytics and support billing.
  • Prompt sessions and code execution inputs so MCP workflows can be tracked and improved.
  • IP address, device/browser identifiers, and user agent to keep accounts secure and troubleshoot issues.

Billing & Payments

  • Plan name, usage totals, and overage settings so invoices and limits are accurate.
  • Stripe customer and subscription IDs. Payment card data is handled directly by Stripe.

Communications

  • Support requests, feedback, and delivery status for emails we send you.
  • Waitlist submissions when applicable.

How We Use Data

  • Power the dashboard and MCP workflows you use.
  • Authenticate users, secure sessions, and protect credentials.
  • Operate MCP servers, route tool calls, and show usage analytics.
  • Debug issues, keep uptime reliable, and maintain audit logs.
  • Calculate usage limits, overages, and subscription billing.
  • Send account, billing, and security notifications.
  • Comply with legal obligations and enforce our Terms.

Sharing & Disclosure

We do not sell user data. We share information only as needed to provide the Service and your dashboard:

  • Service providers for hosting, databases, and email delivery (e.g., Supabase, Azure Communication Services).
  • Payment processing via Stripe for subscriptions and invoices.
  • Third-party connectors you enable (e.g., Corva, Enverus, GeoForce, Google, Microsoft, and similar providers).
  • Legal or regulatory requests when required by law.
  • Business transfers in the event of a merger, acquisition, or asset sale.

Third-Party OAuth Data

PatchOps' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

When you connect a third-party provider through OAuth, PatchOps accesses only the scopes you explicitly authorize and only the account data needed to provide the feature you choose.

Google user data. When you connect a Google service to PatchOps, PatchOps accesses your Google account profile and the specific Google user data covered by the scopes you approve. Access is always limited to the authenticated user's own account and only while your connection is active.

  • Gmail — Under the gmail.modify scope, PatchOps can list, read, search, send, draft, label, archive, and trash messages on your behalf so the AI assistant can summarize, compose, and manage your mail at your explicit request.
  • Google Calendar — Under the calendar and calendar.calendars scopes, PatchOps can list calendars, list/create/update/delete events, and create or delete secondary calendars so the AI assistant can read your schedule and manage events at your explicit request. The calendar.calendars scope is required for creating and deleting calendar containers themselves, in addition to events.
  • Google Drive — Under the drive.file scope, PatchOps can create, read, modify, share, and delete only the files and folders that the AI assistant creates on your behalf or that you explicitly open with PatchOps. PatchOps does not have access to your other Drive files. We use the narrower drive.filescope to follow Google's minimum-scope guidance.
  • Google Docs — Under the documents scope, PatchOps can create, read, insert text into, and format Google Docs at your explicit request, so the AI assistant can produce or edit documents on your behalf.
  • Google Sheets — Under the spreadsheets scope, PatchOps can create spreadsheets and worksheets, read cell values and ranges, append rows, update cells, and apply formatting at your explicit request, so the AI assistant can produce or edit spreadsheets on your behalf.
  • Google Slides — Under the presentations scope, PatchOps can create presentations, add new slides, read slide structure, update slide content, and delete slides at your explicit request, so the AI assistant can produce or edit presentations on your behalf.

Depending on the providers and connectors you enable, PatchOps may access account profile information and limited categories of third-party data needed for the feature you choose, such as files and file metadata, emails and mailbox labels, calendars and events, spreadsheets and documents, tasks, contacts, and meeting or workspace metadata.

Specifically, PatchOps:

  • Uses third-party account data only to provide and improve user-facing features of PatchOps that are visible to you.
  • Does not sell third-party account data to third parties.
  • Does not use third-party account data for advertising, including retargeting, personalized advertising, or interest-based advertising.
  • Does not transfer third-party account data to data brokers, information resellers, or similar parties.
  • Does not allow humans to read Google user data, except: with your affirmative consent for specific items (e.g. a support ticket you share), for security purposes, to comply with applicable law, or when the data has been aggregated and anonymized for internal operations.
  • Does not use third-party account data to determine credit-worthiness or for lending purposes.
  • Does not use Google user data to develop, improve, or train generalized or non-personalized AI or machine learning models. Any AI features in PatchOps operate only on the signed-in user's own data, at that user's explicit request, and only for the session in which the request is made.

You can revoke PatchOps's access to a connected third-party account at any time through the provider's account permissions settings or from the PatchOps dashboard.

You can also revoke PatchOps' access to your Google account at any time via your Google Account permissions page at https://myaccount.google.com/permissions.

Security & Retention

We use encryption for stored credentials and secure cookies for sessions. We retain data only as long as necessary for the purposes described in this policy.

Retention Periods

  • Account data — retained for the duration of your account plus 30 days after deletion to allow for recovery.
  • Tool call and usage logs — retained for 12 months for analytics and billing accuracy, then automatically purged.
  • Prompt sessions and code execution logs — retained for 12 months, then automatically purged.
  • Billing and payment records — retained for 7 years to meet tax and accounting obligations.
  • OAuth tokens — access tokens expire after 1 hour; refresh tokens expire after 30 days. Expired tokens are cleaned up automatically.
  • Audit logs — retained for 24 months for security and compliance purposes.

You can request early deletion of your data by contacting support. Account deletion removes all associated data except where retention is required by law.

Your Choices

  • Update account information and manage connection settings in your dashboard.
  • Revoke OAuth access at any time through your provider or in PatchOps.
  • Opt out of non-essential emails and usage alerts where available.
  • Request account deletion or data export by contacting support.

Children's Privacy

PatchOps is not directed to children under 13. We do not knowingly collect personal information from children under 13. If we become aware that we have collected data from a child under 13, we will delete that information promptly. If you believe a child has provided us with personal data, please contact us at support@patchops.ai.

International Users

PatchOps and its service providers may process data in multiple regions, including the United States, to keep the Service reliable. If you are located in the European Economic Area (EEA), United Kingdom, or other regions with data protection laws, you may have the right to access, correct, delete, or port your personal data, as well as the right to restrict or object to certain processing. To exercise these rights, contact us at support@patchops.ai. We process data based on your consent, contractual necessity, or our legitimate interests in operating the Service.

Governing Law

This Privacy Policy is governed by the laws of the State of Texas, United States, without regard to conflict of law provisions.

Contact

Questions about privacy? Email us at support@patchops.ai.