Delete your Heard account

Document key: heard-account-deletion
Version: 1.0.0
Last updated: September 5, 2026
Effective date: September 5, 2026
Canonical URL: https://discoverheard.com/delete-account

You can permanently delete your Heard account from the app or through Heard's web deletion form. You do not need to reinstall the app to use the web route.

Heard is published by Justin Lauinger as an individual.

Account deletion is permanent. It is not a temporary suspension, and your account cannot be recovered after deletion completes.

Delete in the Heard app

1. Sign in to the account you want to delete.
2. Open Settings.
3. Under Account Actions, choose Delete account.
4. Review what deletion does.
5. Re-enter your current password.
6. Type DELETE and confirm Permanently delete account.

The app will stop playback, clear the native queue, remove local Heard sessions and files, and return to the welcome screen after the server confirms completion.

Delete without the app

Use Heard's canonical account-deletion page. It provides the deletion form without requiring the Heard app. An API-hosted form is also available at:

Current API-host deletion fallback

On the form:

1. enter the email address for the Heard account;
2. enter the current password;
3. type DELETE;
4. acknowledge that deletion is permanent and private-audio retention applies; and
5. select Permanently delete account.

Your email and password are sent directly from the browser to Supabase Auth. Heard's application API receives the resulting short-lived access token, whose claims include the account ID and email, not your raw password. The form clears the password field after the attempt.

What happens to your data

After a valid deletion request, Heard's system is designed to:

• delete your category preferences and supported relationship and interaction records;
• stop active upload and audio-processing work;
• remove your posts from public feeds and content-detail responses;
• remove personal report details;
• delete identifying fields and minimize or pseudonymize the profile, content, and audio-asset records that remain for integrity or audit;
• permanently delete your Supabase Auth user after database erasure succeeds; and
• clear the Heard app's AsyncStorage, cached files, document files, session, playback state, and local drafts when mobile completion succeeds.

Your published posts become unavailable through Heard's feed and content API as part of the deletion transaction.

Audio deletion timing

Audio bytes have two different storage paths:

• Previously public audio: After a valid deletion decision, Heard removes the post from current public APIs and playback eligibility and queues the public object for origin and CDN deletion. Heard's internal technical target is denial of ordinary and byte-range access within five minutes. The target does not guarantee that third-party copies disappear.
• Private-quarantine audio: Originals and private derivatives remain inaccessible and become eligible for scheduled physical deletion after the applicable retention cutoff, ordinarily 30 days. Eligibility is not a promise that provider copies, logs, replicas, or backups have all been erased on that exact day. A valid restricted legal or safety hold can delay deletion.

The five-minute process cannot remove a copy another person, device, cache, or service obtained while the audio was public.

Records that may remain

Heard may retain limited records that no longer have an active authentication link or presence in current public APIs, including:

• one-way deletion hashes, request status, bounded failure codes, and timestamps;
• stable internal profile, content, asset, or request identifiers, some of which may have been public before deletion;
• policy-document and creator-attestation receipts tied to a minimized or pseudonymized profile, plus immutable per-upload provenance/content-warning declarations tied to minimized internal upload/content records;
• technical upload, inspection, automated-moderation job/attempt/minimized evidence, versioned moderation-case/decision/evidence-access, media-revocation action/attempt/event, storage-disposition, and deletion proof;
• minimized security, fraud-prevention, and abuse-review records; and
• content or context preserved in restricted private custody under a valid legal hold or legal duty, including child-safety evidence, under an approved operating procedure.

These retained records are not necessarily anonymous because a stable identifier may remain linkable to a prior public copy or restricted operational record. Heard retains them only while reasonably necessary for integrity, security, enforcement, dispute resolution, legal compliance, or proof. Provider logs, replicas, caches, and backups may follow separate security, continuity, legal, and backup-cycle periods under provider configurations and terms.

If deletion is interrupted

The deletion request is designed to be retry-safe. Database erasure occurs before Supabase Auth deletion. If Auth deletion temporarily fails, your content and identifying application data remain unavailable, while a limited internal association with the authentication account remains only so you can authenticate again and resume the same request.

If a success response is lost, the app or web form can check the durable request status. Repeating the request does not intentionally create a second deletion operation.

Before you delete

• Save anything you want to keep. Heard does not currently provide a self-service data-export button.
• Deleting the app from your phone does not delete your Heard account.
• Signing out does not delete your account.
• Deleting an individual post does not delete your account.
• Heard does not currently offer subscriptions that must be canceled separately.

Need help?

If you cannot sign in or complete the form, contact support@discoverheard.com from the email address associated with the account and write Account deletion in the subject line. Do not send your password.

Heard may request information reasonably necessary to verify the account and the request. The support address is active and operated by Heard's individual publisher but is not staffed 24 hours a day and is not an emergency service.

Privacy details
Heard Support