Protect keys and guest information

Protect credentials

Store production credentials in a server secret manager or Zapier’s credential field. Never put them in browser storage, URLs, public examples, telemetry, exception reports or chat. Display and copy a newly created key only in its one-time dashboard view.

Use a separate key for each integration, narrow scopes and resource restrictions, and a finite expiry. Rotate exposed credentials promptly and revoke the old key. Key management requires current manager authority and recent authentication.

Minimize personal data

Events use IDs, statuses and timestamps instead of contact data. Read guest details only when the workflow needs them and has guest:read. Do not place personal details in external references, callback URLs or your diagnostic logs.

Guest retention, account deletion and opt-outs continue to apply to integration workflows. Keep downstream copies only under your own documented retention obligations. Event recovery and idempotency windows are bounded operational stores, not long-term guest backups.

Respect tenant and destination boundaries

Tenant identity comes from the credential. Supplying another tenant’s resource ID does not change that authority. A scope never grants key issuance, billing changes, destructive guest deletion or raw SMS sending.

Webhook destinations are validated before use and delivery does not follow redirects. Custom endpoints are gated until their outbound network policy can enforce safe destinations. Report a suspected issue through LineBlink support with redacted request IDs.

• Contact support