Data Deletion Instructions

TrainerDNA does not currently expose a one-click, in-product server deletion action. Account, workspace, provider, and client-record deletion is handled through a manual, ownership-verified request. To start that request, email support@trainerdna.app from the email address associated with your TrainerDNA account. Include the subject line “TrainerDNA Data Deletion Request” and tell us whether you want to delete your full account, a specific workspace, a connected platform, or specific client/prospect records.

Opening this page, opening an email draft, signing out, or using Settings → Data controls → Clear this browser does not submit or complete server deletion. The local reset removes app-owned storage from that browser only; signed-in server data may load again.

We may ask you to verify account ownership before deleting data. A request is not complete until its scope is verified and you receive a response through the manual request process. Requests are processed within a reasonable time and as required by applicable law, subject to limited retention needed for security, legal, accounting, fraud prevention, dispute resolution, or backup purposes.

Before clearing a browser, signed-in coaches can use Settings → Data controls to download the active workspace's scoped browser cache as JSON. Local-only accounts can export app-owned browser storage. The file excludes other workspace caches, server database rows, connected provider records, authentication credentials, and IndexedDB photos or other binary media. To request a broader portability export, include the desired account, workspace, client, date, and relationship-history scope in your email.

You can disconnect supported integrations inside TrainerDNA where the connection appears. Disconnecting removes or disables the connected account in TrainerDNA and stops future syncs. Where a provider supports token revocation, TrainerDNA attempts to revoke the token during disconnect or deletion workflows.

If you connected Instagram or Facebook, you can remove TrainerDNA from your Meta account settings:

• Open Facebook or Instagram account settings.
• Go to Apps and Websites or connected apps.
• Find TrainerDNA and remove access.
• Email us if you also want stored TrainerDNA records deleted.

Removing the app from Meta stops future access from Meta-side settings. Emailing us lets us remove stored connection records, encrypted tokens, provider identifiers, and related social sync snapshots we hold, subject to lawful retention.

If you connected TikTok, disconnect TikTok from inside TrainerDNA and/or remove TrainerDNA from your TikTok account settings. Email us if you want stored TikTok connection data deleted, including encrypted tokens, account identifiers, profile details, follower/stat snapshots, and recent public video metric snapshots.

If you connected Google Calendar or YouTube, you can revoke access from your Google Account permissions page and disconnect the integration in TrainerDNA. Email us if you want stored Google or YouTube connection data deleted, including encrypted tokens, provider account identifiers, synced calendar event records, channel details, and video metric snapshots.

If you connected Stripe, you can disconnect it in TrainerDNA and manage platform access from Stripe settings where available. Email us if you want stored Stripe connection metadata removed. Stripe may retain payment and account records under its own legal, compliance, and fraud-prevention obligations.

You can request deletion of client/prospect records, check-in data, proof notes, testimonials, progress photos or media, and related content you entered into TrainerDNA. Because you control the client/prospect information you enter, you are responsible for honoring any deletion or consent withdrawal requests you receive from those individuals.

Depending on the verified scope, a deletion request can cover a TrainerDNA account, workspace, provider connection, encrypted token, provider identifier, synced snapshot, client/prospect record, and associated operational records we are no longer required to keep. Some information may remain in aggregated, anonymized, security, audit, legal, accounting, or backup records for a limited period.

There is not yet an in-product deletion-status ledger or self-service completion certificate. Do not treat a local reset, integration disconnect, or sent email as proof that every requested server record has been deleted; use the response to the verified request for its actual status and scope.

See our Privacy Policy and Terms of Service for more information about data collection, use, retention, and your responsibilities when entering client or prospect data.