Data Deletion

Last updated date:

This guide explains how authorized administrators and individuals can disconnect integrations, delete Seedling workspaces or accounts, and request deletion of personal information.

Choose the right deletion action

Disconnect an integration
Removes that provider’s credentials and provider-derived data from the selected Seedling workspace while leaving the workspace active.
Remove a marketplace app
Revokes provider authorization. Where the provider sends a verified deauthorization event, Seedling runs the same local integration purge.
Delete a workspace or account
Removes the applicable Seedling workspace or user account and its active data after authority and identity are verified.
Submit a personal-data request
Allows an individual or authorized agent to request deletion when they cannot use workspace controls or when applicable law provides a separate right.

Disconnect an integration in Seedling

When disconnect completes, Seedling deletes the saved credential, webhook payloads, synchronization records, provider sources, indexed objects, chunks, embeddings, source entitlements, and source-linked content owned by that integration. Original information in the provider is not deleted or changed.

Where approved operating configuration must remain as part of Seedling’s human-review and verification history, Seedling removes the provider evidence and source-derived text and retains only the redacted approval or materialization record and bounded audit metadata.

  1. Sign in as an administrator of the affected Seedling workspace.
  2. Open Apps or Connections and select the connected provider.
  3. Choose Disconnect, review the deletion warning, and confirm.
  4. Wait for the disconnect to complete before reconnecting the same provider account.

Provider-specific removal guides

Marketplace removal controls, deauthorization events, and short-lived delivery records vary by provider. The applicable guide explains how provider-side removal interacts with Seedling’s local integration purge.

Delete a workspace or account

Send the request from the account’s work email to privacy@tryseedling.ai. Include the workspace name, whether the request covers a user account, one workspace, or the entire customer relationship, and the name of an administrator who can verify authority.

Seedling may ask for additional verification, confirmation from another administrator, or evidence of authority. We will not delete an organization’s workspace based only on an unverified request from an individual member. A verified request is ordinarily completed in active systems within 30 days.

Personal-data deletion requests

Individuals and authorized agents may send a request to privacy@tryseedling.ai. Include the person’s name, relevant email address, organization, relationship to the workspace, and enough information to locate the record. Do not send identity documents unless Seedling specifically requests them through a secure method.

When a Seedling customer controls the information, Seedling may direct the request to that customer and assist it as a processor. We may deny or limit a request when identity or authority cannot be verified, an applicable exception permits retention, or deletion would adversely affect another person’s rights. We will explain the result and any available appeal right required by law.

What may remain after deletion

Active systems
Integration data is removed when the provider purge completes. Verified account and workspace deletion requests are ordinarily completed within 30 days.
Backups
Encrypted, access-restricted backup copies expire or are overwritten within 35 days after active-system deletion. They are not restored except for disaster recovery and are deleted again if restored.
Integration delivery records
Provider payloads and authorization records follow the applicable integration guide. Successfully processed payloads are erased promptly where Seedling uses a durable webhook receipt.
Security and lifecycle audit
Seedling may retain identifiers, action, outcome, bounded reason codes, and timestamps needed to demonstrate deletion, investigate abuse, and protect the Service. These records do not contain provider credentials or raw provider payloads.
Legal and commercial records
Seedling may retain limited records required for disputes, fraud prevention, tax, accounting, sanctions, or other legal obligations for the applicable statutory period.

Effects and limitations

  • Deletion from Seedling does not delete original information held by a connected provider or another customer-controlled system.
  • Deleting a user account does not necessarily delete records the person created for an organization when the organization must retain them.
  • Disconnect and deletion are generally irreversible. Reconnecting later creates a new authorization and may require a new synchronization.
  • De-identified information that cannot reasonably identify a customer, user, workspace, or source record may be retained for reliability and capacity analysis.

Confirmation and help

Seedling will confirm receipt of an emailed deletion request and will provide a completion or decision notice after verification and processing. Questions about deletion may be sent to privacy@tryseedling.ai; product troubleshooting may be sent to support@tryseedling.ai.