Data and security

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.

How a request flows

  1. You ask your AI app (Claude, ChatGPT or Codex) for something in PATHwd.
  2. The app calls one of the connector's tools at 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.
  3. The connector runs the command as you against the PATHwd API at api.pathwd.app (and files.pathwd.app for file downloads and uploads), with your own PATHwd access.
  4. The result (records, lists, confirmations) goes back to your AI app, which shows it to you.

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).

Network destinations

DestinationWho connectsWhat goes there
mcp.pathwd.app (the connector, run by Endao, LLC)Your AI app, and your browser for sign-in, upload and download pagesSign-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 browserThe PATHwd sign-in and consent page
api.pathwd.app (PATHwd API)The connectorEvery PATHwd read and change, made as you
files.pathwd.app (PATHwd file server)The connectorRecord files downloaded or uploaded for you
chatgpt.com, *.oaiusercontent.comThe connectorChatGPT 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 connectorIts 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 the connector stores

WhatWhereHow longProtection
Your PATHwd sign-inNowhere on the connector. It exists only inside the encrypted tokens your AI app holdsUntil disconnect, or 30 daysAES-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 workspaceEncrypted in the connector's state store (Valkey); larger items in Amazon S37 days after the connection's last command (S3 copies 8 days after their last write); deleted at once when you disconnectEach 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 commandAmazon S3Deleted when a command that uses them succeeds (a preview or a failed command leaves them), and at the latest after 1 dayAWS KMS encryption; HTTPS only
Files a command produces for you (for example a downloaded record file)Amazon S3, behind a download link1 day. The link needs your PATHwd sign-in and works only for youAWS KMS encryption; the file itself is served through a link that expires after 5 minutes
Sign-in transactions, rate counters, lock and revocation markersConnector state storeMinutes to 30 days, each with its own expiryEncrypted at rest and in transit; sign-in transactions sealed
Service logsAWS CloudWatch30 daysAWS 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.

How commands are isolated

  • Each tool call runs in a separate process, in a temporary folder that holds only that connection's workspace, under Node.js's permission model: the process can read and write only that folder. The folder is deleted when the call ends, also on failure or timeout.
  • One command runs at a time per connection, so two of your chats never mix their state, and no two users ever share a process or a folder.
  • The address of the PATHwd API is fixed; commands can't be pointed elsewhere.

Protection at the edge

  • HTTPS only, behind an AWS load balancer and web application firewall with a per-address request limit and AWS's managed rule sets.
  • Sign-in follows the OAuth 2.1 practices the MCP specification sets out: PKCE, exact redirect checks, refresh-token rotation with reuse detection, and a consent page for apps the connector can't verify.
  • Rate limits per connection and per user (see Limits).

Your controls

  • What it can reach is what your PATHwd roles allow; your admin changes that in PATHwd.
  • When it asks you is set by your AI app's approval settings for each tool.
  • Disconnecting ends the connection and deletes its workspace at once (see Authentication and permissions).
  • Questions about your data: contact support.
Thank you! Your message was sent. We'll be in touch soon.
Something went wrong. Please refresh the page and try again, or reach out directly by email.

Privacy Contact

If you have any questions, concerns, or requests related to our privacy policy, please contact us.

  • privacy@pathwd.com