Elimina il tuo account Ember

Delete your account in Ember

Ember is provided by Geordan Gesink. You can delete the complete account in the app or request deletion without opening the app as described below.

1. Open Ember and select the Settings tab.
2. Under Account, select Delete account.
3. Confirm Delete.

Once the request succeeds, the live backend account and the account-linked records listed below are permanently deleted. Deleted account data cannot be restored.

Before you delete

Account deletion does not cancel an Apple App Store or Google Play subscription. Manage or cancel an active subscription separately in the store where you purchased it. You do not need to cancel before deleting your Ember account, and deletion remains available immediately.

If you cannot access the app

Email support@emberalarm.com with the subject “Delete my Ember account.” Send the request from the email connected to your account when possible, and include your Ember handle and sign-in method. Never send your password. We may ask for limited information to verify that the account is yours. Verified requests are normally completed within 30 days. We will reply to confirm when the request has been completed. Deletion completed in the app signs you out as soon as the backend confirms success.

Data deleted with the account

• the authentication record, including the Ember user ID, account email, optional verified phone, and linked sign-in-provider identifier where applicable
• display name, handle, and profile timestamps
• a former pre-release access request associated through the email address, access code, or account ID, including its email address, optional answers, and account-linked claim and benefit records
• account-linked ember grants, including First Light
• friend requests, accepted friend relationships, friend-invite keys, leaderboard scores, wake-ranking participation and daily wake-time records, contact-matching consent, pseudonymous contact-matching tokens, and friend-removal suppression records
• the cloud-backup snapshot, including any backed-up alarms, challenge settings, saved code values and vocabulary pairs, preferences, emergency-override passkey, wake-up history, scores, embers, achievements, per-installation cumulative lifetime counters, and the random app-installation and wake-session IDs used to merge and deduplicate offline progress, plus the private next-wake checkpoint used to preserve a missed wake across local-data deletion

Delete only your cloud backup

To keep your account but remove its backup snapshot, open Settings → Cloud Backup, select Delete cloud backup, and confirm the deletion. This also removes the wake-occurrence checkpoint. Your account, verified phone, contact-matching data, profile, friend relationships, leaderboard data, ember grants, and on-device data remain until you delete the whole account or remove the local data yourself. Turning off Sync this device only pauses syncing and retains the latest cloud snapshot.

Disable only contact matching

Disabling contact matching immediately deletes your stored matching tokens and stops further address-book processing. Your verified account phone remains until you ask us to remove it or delete the account. You can also revoke Ember's Contacts permission in your device settings. Existing friendships remain. You can remove them separately; Ember keeps a suppression record so contact matching does not automatically recreate a friendship you removed.

Leave only the wake-time ranking

Open Ranks → Friends → Wake-up and turn participation off. Ember immediately deletes your uploaded wake-time rows and hides every participant's wake time from you. Your friendships, score rankings, and wake-up history stored on your device remain unchanged.

Data that may remain

• Ember increments one global counter when an account is deleted. The counter stores only the total number of deleted accounts. It contains no per-account record, date, identifier, or account attribute.
• If you activated or claimed access during the former pre-release program, Ember retains only one-way, server-keyed verification values derived from the invite code and token. This lets Ember recognize the same credential after reinstalling the app or creating a replacement account. The retained values do not contain the raw code or token, an account or access-request identifier, your email address, request answers, activation or claim time, or an individual benefit record.
• A pseudonymous contact token uploaded by another user for your former verified number can remain in that user's contact set until they resync or inactive contact data is cleaned up. It is not linked to your deleted account and can no longer match it after your verified-number token is deleted.
• Previously loaded non-wake leaderboard entries can remain temporarily in another participant's local offline cache until their app reconnects and refreshes or its data is cleared. Ember does not retain wake-time boards for offline display.
• After deleting only the cloud backup, Ember retains an empty deletion marker linked to your backend user ID, with the deletion time and revision. It contains no backup contents and only prevents another signed-in device or older app version from recreating the deleted snapshot. Enabling backup again clears the marker; deleting the account removes it.
• Alarms, settings, and progress stored only on your device remain there after account deletion. Clear Ember’s app data in your device settings or uninstall the app to remove that local copy, subject to device or operating-system backups you control.
• Optional Usage analytics is available from app version 1.2.0 and is off by default. If you enable it, deleting your account stops analytics on that device. It does not automatically delete events already received by PostHog. Contact support@emberalarm.com to request deletion of those events and the analytics profile. Events are retained for up to one year. Turning analytics off in Settings stops new client events and discards the device queue. Verified purchase-summary forwarding is planned and is not active in the public app. For that feature, account deletion would remove account-linked backend consent and withdrawal records and cancel pending deliveries. Turning analytics off would request withdrawal of backend purchase analytics. That backend change requires a successful network connection; an offline choice cannot immediately stop events already being processed remotely.
• Optional advertising measurement is available from version 1.2.2 on iOS and Android. Its AppsFlyer and Meta connections are enabled; Reddit remains inactive. If you enable measurement in a supported build, opting out or deleting an Ember account does not automatically erase records already held by AppsFlyer or advertising partners. Settings → Advertising measurement offers a deletion request email to support@emberalarm.com, including available AppsFlyer and RevenueCat identifiers retained on your device. You choose whether to send it. We process the request with the relevant providers. Changes to server-side sharing require successful synchronization, including after going offline; earlier customer identifiers may require manual cleanup.
• The purchase ledger omits direct account IDs. Deleting an account would remove the separate planned analytics-consent link and cancel pending deliveries, while financial summaries and delivery metadata without that account link could remain. A daily cleanup removes purchase-ledger records once their event date is more than 24 months old, together with the associated delivery metadata. The Privacy Policy describes the separate retention periods for planned consent and withdrawal records.
• Apple, Google, and RevenueCat may retain store transaction and entitlement records as needed under their own policies and legal obligations. Deleting your Ember account does not cancel an app-store subscription.
• A deletion request, support correspondence, and limited security logs may be retained where required to document the request, meet legal obligations, prevent abuse, or resolve disputes. Residual copies in service-provider backups may remain until overwritten through their normal rotation and are not used to recreate the account.

See the Privacy Policy for more information about Ember’s data handling.