Privacy and data handling

Keep personal data and integration credentials under your organization’s control.

Order and attendee resources can contain names, email addresses, billing details, and custom registration answers. Limit your integration to the fields required for its purpose.

Minimize stored data

Map the specific fields your workflow needs rather than retaining every legacy property or complete response. Separate operational IDs from display information. Avoid forwarding payment related metadata or unrelated custom registration answers to another tool.

Protect credentials and logs

Store credentials in a server secret manager, send requests over HTTPS, and restrict access to imported data. Exclude passwords, Authorization headers, session cookies, and full attendee response bodies from logs. Operational logs usually need a path, timestamp, status, and correlation information.

Respect changes and deletions

Apply deletion IDs and reconcile your own copies periodically. A successful API read is not permission to retain that data indefinitely. Follow your organization’s retention, access, and deletion procedures for data copied outside Paydro.

Connected services

Before enabling HubSpot or Mailchimp, verify which organization and provider account are connected and which data should be synchronized. Apply the relevant consent and subscriber status rules.

Review your obligations

Consult your organization’s privacy policy and processing agreements when designing an integration. See Paydro privacy information and use support for questions about the data exposed by a resource.