1. Disconnect Incident.io in Seedling
Disconnecting one personal connection removes only that member's connection, sources, and audience contributions. An independently observed object remains only when another active connection still observes it, with access recomputed from the remaining connection.
- Sign in to the Seedling workspace as a workspace administrator.
- Open Apps or Connections, select the exact Incident.io connection, and choose Disconnect.
- Confirm the request. Seedling stops new synchronization, captures the exact connection and source identifiers, deletes active credentials or connection secrets, and starts a durable purge.
- Wait for the disconnect operation to report completion before reconnecting Incident.io.
2. Retire access in Incident.io
Revoke the API key in Incident.io Settings → API keys.
Also disconnect Incident.io in Seedling to purge incidents, configuration, receipts, and derived evidence for the exact connection.
3. Request deletion without workspace access
Email privacy@tryseedling.ai from a work address associated with the organization. Include the organization name, Seedling workspace name if known, the Incident.io account identity, and your authority to request deletion. Never include credentials, customer content, or identity documents unless Seedling provides a secure method.
Seedling verifies identity and authority before acting and will explain any information needed to locate the tenant safely.
4. What the purge removes
Disconnecting does not delete or modify the original information in Incident.io. Approved Seedling configuration may retain a bounded approval record, but its Incident.io evidence and source-derived content are removed or redacted.
- Encrypted Incident.io credentials or connection secrets and the tenant connection record.
- Incident.io sources, provider staging rows, synchronization state, and audience contributions owned by the connection.
- Incident.io incidents, actions, follow-ups, timeline events, statuses, severities, types, users, teams, custom fields, receipts, and staging rows.
- Source objects, chunks, embeddings, identifiers, and source-linked activity, fieldwork, chat, exploration, and verification evidence owned by the integration.
5. What may remain
- Backups
- Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion. It is deleted again if a backup is restored for disaster recovery.
- Lifecycle audit
- Seedling may retain workspace and connection identifiers, action, outcome, bounded reason codes, and timestamps needed to demonstrate deletion and protect the Service. These records contain no Incident.io credentials or native payloads.
- Legal and security records
- Limited records may be retained longer when required for security, fraud prevention, disputes, accounting, or law.
6. Confirmation and related guidance
Seedling will confirm receipt of an emailed deletion request and provide a completion or decision notice after verification and processing. Questions may be sent to privacy@tryseedling.ai; product troubleshooting may be sent to support@tryseedling.ai.