> ## Documentation Index
> Fetch the complete documentation index at: https://support.dripos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dripos connector privacy

> What the Dripos connector for Claude and ChatGPT accesses, what it records, how long it keeps it, and how to disconnect

This page covers the Dripos connector at `https://mcp.dripos.com/mcp`, used from Claude and ChatGPT. It supplements the [Dripos Privacy Policy](https://www.dripos.com/privacy), which governs Dripos as a whole.

> [!NOTE]
>
> The connector is read-only. It cannot create, change, or delete anything in Dripos, and it has no access to card numbers or other customer payment credentials.

## What it can access

Only your own Dripos reporting data, and only for the locations your signed-in account can already report on.

You sign in with the Dripos account you use for the dashboard, using a one-time code. The connector then resolves your permissions on every request: partners (owners) see their locations, and employees need the **Admin** or **Full Reports** permission on their role. Each person who connects sees only their own locations, so connecting inside a shared workspace does not share your data with the rest of that workspace.

Each connection is bound to one company. Accounts with more than one company choose which at sign-in, and the connection cannot read the others.

The data it can read is the same reporting data the dashboard shows: sales, products, categories, modifiers, discounts, payment methods, order platforms, order types, taxable sales, tax categories, labor cost against sales, and the list of your locations. It can also search the public Dripos support documentation.

## What it does not access

* Card numbers, bank details, or any customer payment credentials
* Your conversation with Claude or ChatGPT, including prompts and replies
* Chat history, memory, conversation summaries, or files you upload to those assistants
* Any Dripos company or location your account cannot already report on

## What Dripos records

For each request, Dripos records operational data to run and monitor the service:

| Recorded | Example |
| - | - |
| Which tool ran | `get_product_sales` |
| The report parameters | location ids, start and end date, day or hour filters |
| The outcome and timing | success or error code, duration, number of rows returned |
| Which connection made it | your Dripos account id and company id |

Dripos does **not** record the text of your conversation, the wording of your questions, or the contents of the reports returned.

Sign-in records an OAuth grant: your account id, the selected company, the permissions granted, hashed tokens, and timestamps. Tokens are stored hashed, never in plain text.

Report results are cached briefly, keyed to the connection that requested them, so a repeated question does not re-query the database. The cache is never shared between accounts.

## How long it is kept

| Data | Retained |
| - | - |
| Access tokens | 1 hour, then they expire |
| Cached report results | 60 seconds |
| Pending sign-ins and authorization codes | 10 minutes, and codes are single use |
| A connection (refresh grant) | until you disconnect, or 7 days idle, or 30 days total, whichever comes first |
| Operational logs and usage metrics | in line with the retention in the [Dripos Privacy Policy](https://www.dripos.com/privacy) |

## Third parties

The connector is served by Dripos and reads from Dripos systems. Your reporting data is not sold, and it is not shared with third parties for advertising.

Two services are involved in operating it:

* **Anthropic** (Claude) and **OpenAI** (ChatGPT) receive the report data you ask for, because they are the assistant you are using. Their handling is covered by their own terms.
* **Dripos infrastructure providers**, which host the service and collect the operational data described above.

The documentation search reads the public Dripos support site. It sends no account data.

## How to disconnect

Remove the Dripos connector in your assistant's connector or plugin settings. The connection stops working immediately, and the refresh grant can no longer be used.

To cut an employee's access, change or remove their reporting permission in **Team** > **Roles**, or remove them from the location. The connector re-checks permissions on every request, with a cache of up to one minute, so access ends within a minute. Access tokens already issued remain valid until they expire, up to one hour.

## Contact

Email [support@dripos.com](mailto:support@dripos.com) with any question about connector data, or to request deletion of a connection and its records.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.