1. Ordinary customer workspaces
The public PagerDuty connector is not currently available, so an ordinary workspace should have no connector-owned PagerDuty credential, synchronization state, or provider payload to delete.
2. Preview or test data
- Stop using the preview or test connection and revoke its authorization in the provider if one was issued.
- Contact privacy@tryseedling.ai from an address associated with the organization. Identify the Seedling workspace, PagerDuty account, test period, and your authority to request deletion.
- Do not include credentials, exports, record contents, or identity documents unless Seedling provides a secure transfer method.
- Seedling will verify authority, locate the exact test connection and owned data, perform the applicable purge, and confirm the result.
3. Data mistakenly sent to support
If a PagerDuty credential or customer record was mistakenly sent through email or an ordinary support channel, notify privacy@tryseedling.ai immediately. Identify the message safely without repeating the secret or content. Rotate or revoke the exposed credential in PagerDuty.
4. Policy when the connector launches
- Disconnecting will stop new synchronization and target the exact connection rather than every connection of the same provider kind.
- The durable purge will remove active credentials, connection-owned staging and source data, derived content, and audience contributions.
- Encrypted backups may retain deleted information until expiry, ordinarily within 35 days after active-system deletion.
- A bounded lifecycle audit may retain identifiers, actions, outcomes, reason codes, and timestamps without provider credentials or native payloads.