Product privacy

Webhook Migration Auditor

This notice explains how the client-side utility handles Zendesk Webhook, Trigger, and Automation configuration.

Effective date: 2026-09-11

Short version: the app reads configuration in the Zendesk/browser session and does not send it to TCYM or another external product service.

1. Provider and scope

This notice is provided by TCYM, Japan, and supplements the TCYM Privacy Policy. Contact: support@tcym.jp.

2. What the product processes

The product reads Webhooks, Triggers, and Automations from the Zendesk account where an authorized operator opens the app. It may process names, IDs, endpoints, statuses, subscriptions, authentication type metadata, rule titles, active state, and 30-day usage values. Authentication data is reduced to a type and a non-secret username-pattern observation.

The app does not request or need Webhook passwords, API tokens, OAuth access or refresh tokens, client secrets, cookies, authorization headers, signing secrets, or secret custom headers.

3. Where processing occurs

4. Endpoint and export handling

Query strings and fragments are removed from endpoint display and exports. HTML output escapes text, and CSV output protects spreadsheet formula-like values. Exports contain summary information rather than raw API response bodies or credential fields.

5. Retention

The app keeps the derived audit in browser memory for the current page session. Refreshing or closing the app clears it. A user-controlled download is saved by the browser outside the product's control and remains the organization's responsibility.

6. Questions and changes

For privacy or security questions, contact support@tcym.jp. TCYM may update this notice when the product's data boundary changes.