PagerDuty Incident Config (BYOK) — Privacy Policy

Effective 16 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What PagerDuty Incident Config (BYOK) is. PagerDuty Incident Config (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own PagerDuty Incident Config data: Read your PagerDuty incident types, incident custom fields, incident workflows, workflow triggers and the workflow action catalog with your own REST API key. You bring your own PagerDuty Incident Config REST API key (read-only is enough); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one PagerDuty Incident Config call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.pagerduty.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If PagerDuty Incident Config rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What PagerDuty Incident Config receives. The request we make on your behalf, including the key and the arguments, under PagerDuty Incident Config's own terms and privacy policy (https://www.pagerduty.com/terms-of-service/). PagerDuty Incident Config acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer PagerDuty Incident Config gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your PagerDuty Incident Config data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. PagerDuty Incident Config (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at PagerDuty Incident Config at any time to end all access.

Children. PagerDuty Incident Config (BYOK) is a general-audience service operated by the adult using the assistant, under PagerDuty Incident Config's own age rules.

Changes. We will post changes here with a new effective date.