How to delete ShipCadence workspace data.

This Data Deletion Policy explains how ShipCadence customers can request or perform deletion of ShipCadence-held account and workspace data, what ShipCadence attempts to delete, what may remain, and what customers may need to remove directly from connected third-party providers.

This policy applies to the ShipCadence website, application, onboarding flows, integrations, product cycles, AI features, hosted builder features, billing flows, and related support services.

A workspace owner may delete a workspace from Account settings when signed in. ShipCadence may require current-password confirmation, an active authenticated session, rate-limit checks, or other verification before deletion is accepted.

If you cannot access the workspace, you may contact ShipCadence support from the email address associated with the account. ShipCadence may request additional verification before acting on the request.

To delete a workspace in the product, sign in, open Account settings, review the deletion warning, confirm the current password, and submit the deletion request. ShipCadence will sign out active sessions and redirect to signup after deletion completes.

To request assistance, email the support address listed on this page with the account email, workspace name, product name, and a clear request to delete the workspace. Do not include passwords, access tokens, private keys, payment card numbers, or highly sensitive data in the request.

Workspace deletion is intended to remove ShipCadence-held workspace records, including workspace profile data, product name, company context, onboarding state, selected source records, integration records, encrypted provider access records, imported signals, backlog items, build briefs, agent run records, hosted run queue records, measurement snapshots, review history, usage records tied to the workspace, and active sessions associated with the deleted workspace.

ShipCadence also attempts to clear or anonymize workspace-linked audit records where appropriate, except for limited deletion, billing, security, fraud-prevention, legal, or operational records described below.

ShipCadence may attempt supported provider revocation before deleting local workspace records. Provider revocation depends on provider APIs, token validity, network availability, account permissions, and provider behavior.

Deletion from ShipCadence does not necessarily delete provider-side records. You may need to separately revoke ShipCadence access in GitHub, Google, Slack, analytics tools, Stripe, or other connected services. You may also need to remove provider-side artifacts such as pull requests, branches, workflow files, repository secrets, Slack messages, Gmail messages, analytics events, provider audit logs, or billing records.

Deleting a workspace is separate from canceling a paid subscription unless the product flow or support confirmation expressly says cancellation was completed. Customers should cancel paid access from the Plan page or Stripe billing portal before deleting the workspace when possible.

Stripe and other payment processors may retain invoices, receipts, payment records, tax records, customer identifiers, dispute records, and compliance records according to their own policies and legal obligations. ShipCadence may retain limited billing metadata where required for accounting, tax, dispute, fraud-prevention, or legal reasons.

ShipCadence may retain limited data when necessary for legal compliance, security, fraud prevention, abuse prevention, accounting, tax, billing disputes, backup integrity, product reliability, or enforcement of the Terms of Service.

Examples may include redacted deletion audit events, payment and subscription metadata, support communications, security logs, rate-limit records, aggregated or de-identified analytics, operational logs, and records preserved in encrypted backups until those backups expire or are overwritten under normal retention cycles.

Deleted workspace data may remain for a limited period in backups, disaster recovery systems, logs, caches, or other operational copies. ShipCadence does not use deleted workspace data from backups for active product features unless restoration is needed for security, legal, or disaster recovery reasons.

Backup and log retention periods may vary by provider, environment, and operational need. ShipCadence deletes or overwrites backup data according to normal backup lifecycle processes.

After deletion, the workspace, product context, imported signals, source selections, build records, measurement snapshots, agent records, and related workspace data may no longer be recoverable from the active ShipCadence application.

Deletion may prevent ShipCadence from providing support for past workspace activity, reconstructing product decisions, restoring integrations, reproducing historical measurements, or proving what sources were connected unless retained records are available for a permitted reason.

Depending on your location, you may have rights to access, correct, export, delete, restrict, or object to certain processing of personal data. ShipCadence will respond to verified requests as required by applicable law.

If ShipCadence cannot fulfill a request fully, ShipCadence may explain the reason, such as inability to verify the requester, legal retention obligations, security limitations, provider-side records outside ShipCadence control, or data that has been aggregated or de-identified.

In-product deletion usually starts immediately after verification and submission. Support-assisted deletion requests are reviewed after verification. Completion time can vary based on request complexity, provider availability, operational load, legal obligations, and whether additional verification is needed.

ShipCadence aims to handle verified deletion requests within a reasonable period and will take longer only when necessary for security, legal, operational, or provider-related reasons.

ShipCadence may update this Data Deletion Policy from time to time. If changes are material, ShipCadence will take reasonable steps to notify customers through the product, website, email, or another appropriate channel.

Deletion questions, access problems, or requests for help with account or workspace deletion can be sent to the support address listed on this page.