Delete your NoiseOff data, connections, and cloud session.

Before You Delete

SW Cosmos Inc. provides NoiseOff, which creates an anonymous, installation-scoped Supabase cloud session automatically. NoiseOff does not ask you to create a separate username or password. A short prefix for that private cloud session is shown in NoiseOff Settings.

Use the full in-app deletion flow before uninstalling whenever possible. Uninstalling by itself does not reliably revoke provider access or delete NoiseOff server data, and it can remove your easiest way to resume an interrupted deletion.

Delete The Full NoiseOff Account In The App

1. Open NoiseOff.
2. Go to Settings → Privacy & Storage → Delete NoiseOff account.
3. Review the consequences and confirm the permanent deletion.
4. Keep NoiseOff open until it confirms completion. If the process is interrupted, reopen the app and use the deletion recovery screen to retry.

This is the full account-deletion control. You do not need to email support or disconnect every platform first. NoiseOff requests revocation of each connected provider’s access and only reports completion after the required provider, NoiseOff cloud, authentication, and local deletion steps finish.

What Full Deletion Removes

Provider access: NoiseOff requests revocation or deauthorization for the connected Instagram, Threads, and YouTube credentials and removes its encrypted Facebook Page token. Meta may keep Facebook’s account-level app permission after that Page token is removed. To clear that permission too, remove NoiseOff in Facebook Settings → Apps and Websites. You may also verify the result in every provider’s own account-permission settings.

NoiseOff cloud and authentication: NoiseOff deletes the session’s encrypted imported items and source references, settings and protection state, moderation and synchronization records, platform-connection records, encrypted provider credentials, and other user-owned service rows. It then hard-deletes the anonymous Supabase authentication account.

This device: NoiseOff purges local imported records, pending synchronization work, app preferences and setup state, provider sessions held by the app, temporary evidence bundles, and the device-only Keychain encryption key. Once that key is removed, encrypted originals cannot be recovered from the device.

Interrupted Deletions And Limited Receipts

If a provider revocation, network request, or server step cannot be confirmed, NoiseOff does not report the account as deleted. It enters a restricted recovery state and lets you retry the same deletion without reopening the normal app or creating a replacement anonymous account.

While a deletion is incomplete, a protected retry receipt may contain the anonymous Supabase authentication UUID, a one-way HMAC of a random deletion token, deletion status, and timestamps. It is retained only as needed to finish or safely replay that deletion and expires no later than 60 days after it began.

After the account and its user-owned data are deleted, the completion receipt no longer contains the authentication UUID or any provider identifier. The identifier-free receipt contains only the deletion-token HMAC and completion timestamps and expires within 60 days. NoiseOff does not use deletion receipts for advertising, analytics, or tracking.

Exports And Source-Platform Data

Files you exported from the Evidence Vault are outside the encrypted NoiseOff app and cloud store. Full account deletion cannot remove a PDF, image, JSON manifest, checksum, or other copy that you saved or shared elsewhere. Delete those files from each destination yourself.

Deleting a NoiseOff account does not delete or change a post, reply, comment, channel, Page, profile, or account that remains on Instagram, Threads, YouTube, or Facebook. Use the source provider’s controls for source-platform content or account deletion.

If You Already Uninstalled NoiseOff

If you already uninstalled NoiseOff or cannot resume the recovery screen, email info@swcosmos.com with the approximate date last used, connected platforms, the deletion message shown, and only non-sensitive account labels. Do not send passwords, one-time codes, access tokens, device passcodes, full comment text, payment details, or identity documents.

Because NoiseOff uses an anonymous installation-scoped identity, support may be unable to identify the correct session without a safe verification path. Separately revoke NoiseOff from every connected provider’s permission settings. Reinstalling can create a different anonymous session and does not by itself delete the original one.