Request account deletion

Email a request without using the app

Email a MeetThread deletion request
developer@blackandblue.co.in

Use the subject MeetThread account deletion request. If you have a hosting account, send from its sign-in email where possible. State whether you are requesting hosted-account/card deletion, provider-record review, or both. If you cannot access that email, explain this without sending credentials.

Black and Blue may need proportionate identity verification or a minimum locator to find provider records. Anonymous purchase history may not be identifiable from email alone. Do not send passwords, authentication links/tokens, raw purchase tokens, payment-card details, reviewer codes or your private contact book.

The link opens your email application so you can choose whether to send. There is no account-deletion form, automatic backend call or receipt on this website. Black and Blue can review the account and relevant provider records after verifying ownership. Applicable legal, accounting, security or fraud-prevention obligations may limit deletion of some records. Sending an email is not confirmation that a request was received or completed; contact support if you need help following up.

In-app hosting-account deletion

1. Open MeetThread’s Account screen and sign in to the account that owns the hosted cards.
2. Enter that account’s password for reauthentication.
3. Choose Delete account, review the confirmation and choose Delete account & cards.
4. Read the result. If the app reports an unconfirmed or partial outcome, check whether you can still sign in, then retry or contact support. Do not treat a timeout as complete deletion.

The app checks account-cleanup configuration before requesting deletion of up to three hosted cards, trusted hosted-Pro cleanup and Firebase sign-in-account deletion. It saves cleared local hosting markers during this process. With a missing/invalid endpoint, the cleanup does not proceed. With a configured service, failures can occur after some hosted data is removed while sign-in deletion remains unfinished.

Downloaded copies cannot be recalled. Your local contacts and notes remain on the device after hosted-account deletion. The app must confirm the result; a request, timeout or partial outcome does not establish complete deletion.

Delete local card and contact records

In Settings → Delete data on this device, review and confirm the local-record deletion. Hosted cards must be unpublished first so the app does not lose track of public copies. This resets profiles, saved contacts, notes, tags, follow-up outcomes and reminders on that device; reviewer-access removal is attempted separately and may require retry.

The book reset is not a promise to remove SDK diagnostic caches, consent settings, exported files, recipient copies or remote provider records. Android’s clear-storage/uninstall controls remove app-private storage and settings, but not files already exported elsewhere or hosted accounts/data. Do not use uninstall/clear storage if you are trying to recover an unreadable saved file.

What may remain or require a separate request

• Purchase/provider records: deleting a hosting account is not deletion of Google Play transaction records or RevenueCat history. Provider-specific handling and lawful retention may apply.
• Diagnostics already sent: pending-report controls do not recall reports already queued/sent or erase provider-held data. Request review through the privacy contact.
• Server suppression marker: when the account-cleanup service is used, it retains a keyed account hash and deletion timestamp to block delayed entitlement recreation. This marker has no automatic expiry. You can ask Black and Blue to review it; removing it can affect protection against delayed callbacks.
• Copies outside the app: recipients, CSV destinations and downloaded cards can retain copies that MeetThread cannot recall.

See retention details and support. If you need help with retained information, identify the relevant account or provider record without sending passwords or raw tokens. We may need additional proportionate verification before handling the request.