This page describes what the PATHwd connector sends where, what it stores, for how long, and how it is protected. For the legal terms, see the Endao, LLC privacy policy.
mcp.pathwd.app with the command and its options (for example "find records in Lead"). The connector receives only these tool calls. It does not receive your conversation.api.pathwd.app (and files.pathwd.app for file downloads and uploads), with your own PATHwd access.What your AI app does with results, such as keeping them in your chat history, is governed by that app's own terms and privacy policy (Anthropic's or OpenAI's).
| Destination | Who connects | What goes there |
|---|---|---|
mcp.pathwd.app (the connector, run by Endao, LLC) | Your AI app, and your browser for sign-in, upload and download pages | Sign-in, tool calls (commands and their options, which can include record data you ask to write), files you upload |
pathwd.app (PATHwd web app) | Your browser | The PATHwd sign-in and consent page |
api.pathwd.app (PATHwd API) | The connector | Every PATHwd read and change, made as you |
files.pathwd.app (PATHwd file server) | The connector | Record files downloaded or uploaded for you |
chatgpt.com, *.oaiusercontent.com | The connector | ChatGPT only: a file you attached in the chat, fetched when you ask for it to be used |
Amazon Web Services in us-east-1 (S3, ElastiCache, KMS, Secrets Manager, CloudWatch Logs, and the container services that run the connector) | The connector | Its own encrypted storage, keys and logs (below) |
The connector's network is closed to everything else: its DNS firewall resolves only the hosts above. The PATHwd plugin has no code of its own and connects nowhere; it only tells your app where the connector is.
| What | Where | How long | Protection |
|---|---|---|---|
| Your PATHwd sign-in | Nowhere on the connector. It exists only inside the encrypted tokens your AI app holds | Until disconnect, or 30 days | AES-256-GCM; only the connector holds the key |
| Your connection's workspace: the account you picked, PATHwd design metadata it caches (business objects, fields, pathways), saved pathway runs, and files you or a command put in the workspace | Encrypted in the connector's state store (Valkey); larger items in Amazon S3 | 7 days after the connection's last command (S3 copies 8 days after their last write); deleted at once when you disconnect | Each connection's data is encrypted separately (AES-256-GCM, bound to the connection); storage encrypted at rest with AWS KMS; TLS in transit |
| Files you upload for a command | Amazon S3 | Deleted when a command that uses them succeeds (a preview or a failed command leaves them), and at the latest after 1 day | AWS KMS encryption; HTTPS only |
| Files a command produces for you (for example a downloaded record file) | Amazon S3, behind a download link | 1 day. The link needs your PATHwd sign-in and works only for you | AWS KMS encryption; the file itself is served through a link that expires after 5 minutes |
| Sign-in transactions, rate counters, lock and revocation markers | Connector state store | Minutes to 30 days, each with its own expiry | Encrypted at rest and in transit; sign-in transactions sealed |
| Service logs | AWS CloudWatch | 30 days | AWS KMS encryption |
Logs hold ids and numbers only: user id, account id, connection id, command name, duration and exit code. They never hold command options or values, record data, command output, tokens or request headers.
The connector does not keep a database of users or their PATHwd tokens, and it does not read or store your conversations.
If you have any questions, concerns, or requests related to our privacy policy, please contact us.