Deleting your glumea account
Contents
You can delete your glumea account yourself from inside the App. This page explains the supported route, what it deletes, and what it does not reach.
Before you start: this cannot be undone
Deleting the account removes the production account rows and the local data on that device. Existing backups, provider records and subscription logs are outside that cascade and can persist as described below. The production deletion has no user-facing recovery route.
If you may need those records later, for your healthcare team, for example, export them first. In the App, Settings → Data & privacy → Data import & export creates an encrypted .glumea archive of your entries, medications, profile, therapy targets and reminders; app settings such as units, language and theme are not in it. The glucose screens can also export a CSV or a PDF.
A .glumea file can only be imported back into the account that created it. Once that account is gone, nothing can open the file again, not you, not a new glumea account, not your healthcare team, because it is an encrypted container rather than a readable document. So if you want records you can still read afterwards, export a CSV or PDF as well. Save the files somewhere outside the App before you continue.
If you have the App installed
- Open Settings → Account details.
- Tap Delete account at the bottom of the screen.
- Type the confirmation word shown in the dialog, then confirm.
The App deletes your account on our servers first, and only wipes the copy on your device once that has succeeded. If the server cannot be reached, nothing is deleted and you can try again later.
If you only want to remove the cloud copy
Open the Sync sheet with the cloud button at the top of the Summary or History screen, turn Cloud sync off, then tap the delete your data link underneath it and confirm. The App insists on the switch being off first, so that the wipe cannot race an upload already in flight, and it will tell you if there is nothing on the server to delete.
This erases the entries, medication catalogs and medication schedules we hold on our servers. It does not delete your account: your email address, your profile and your glucose targets stay with us, and the diary on your phone is kept. If you switch Cloud sync back on later, the App uploads that whole diary back to our servers.
Use this route if you want to stop using cloud sync but keep using glumea.
Sync can also stop on its own, without you turning anything off. If your session expires, the App does not log you out and nothing is deleted, it parks sync instead. The Sync sheet then shows “Session expired - nothing is being synced. Log in again to resume.”, the switch stays on but reads Paused, and neither it nor the delete your data link can be used until you sign in again. Your diary stays on your phone and whatever is already on our servers stays there; nothing new joins it. So if you are relying on the cloud copy to survive a lost phone, it is worth opening that sheet now and then.
If you no longer have the App
There is currently no supported off-app or email account-deletion workflow. [email protected] is a general contact address, but sending a deletion request there does not trigger an automated identity check or account deletion. This limitation does not reduce any statutory requirement for an additional request channel.
Cancel your subscription separately
Deleting your glumea account does not cancel a glumea+ subscription, and does not refund it.
glumea+ is bought through the Apple App Store or Google Play, and the subscription belongs to the store account that bought it, not to your glumea account. Cancel it there before you delete your glumea account:
- iPhone or iPad: Settings → your name → Subscriptions → glumea → Cancel Subscription.
- Android: Google Play → your profile picture → Payments & subscriptions → Subscriptions → glumea → Cancel subscription.
If you have already deleted your account, the cancellation steps above still work, the subscription belongs to your store account, not to your glumea account.
The Terms of Service are the authoritative version of both routes, cancelling in section 15.6, refunds in section 15.7, including the desktop routes, and the fact that cancelling stops the next renewal without shortening the period you have already paid for.
What is deleted, and what remains
| Where | What happens |
|---|---|
| Our database | Your account and every record linked to it are deleted outright, not marked as hidden. |
| Our server backups | A backup taken before account deletion still contains the account until that backup expires: 7 days. Individual rows are not removed from existing backups, and a disaster-recovery restore can temporarily reintroduce deleted rows. |
| Your device | The App empties its local database and removes sign-in credentials and stored preferences. Deleting the account, signing out, or switching to a different account can all empty that local database. Clearing stored analytics or diagnostics preferences does not reliably disable an SDK that was already initialized until the running process ends. Export first. |
| Apple / Google | Your subscription and payment history belong to your store account and stay with them under their own policies. We never receive your payment details and cannot delete anything held there. |
| RevenueCat | Our backend keeps each purchase notification for 90 days. The database cascade does not reach that log. RevenueCat also holds a subscriber record under the account identifier, and account deletion does not reach it. No manual provider-deletion workflow is currently implemented. |
| Diagnostics | If error reporting ran, past crash reports may still exist. They carry no name, email address or glumea account identifier configured by our code, so there is no supported lookup for one person’s reports. Native crashes may contain SDK or platform fields outside the App filter. |
| Product analytics | A PostHog profile linked to the account is outside the database cascade, so deleting the glumea account does not remove it. Pre-sign-in events use a pseudonymous device identifier instead of the account identifier. No manual profile-deletion workflow is currently implemented; retained data expires under 12 months. |
| Copies you made | Any .glumea archive, CSV or PDF you exported is yours and stays wherever you saved it. We have no access to it and cannot delete it. |
Your other options
Deleting your account is not the only control in the App. Usage analytics and Error reporting can be switched off in Settings → Data & privacy → Privacy & diagnostics. Cloud sync controls are in the Sync sheet opened from the cloud button on the Summary or History screen. The Privacy Policy describes the controls and their current limitations.
Questions
General contact: [email protected]. This address is not an off-app deletion workflow. The Privacy Policy describes the available controls.
Washington’s Consumer Health Data Privacy Policy describes the statutory 45-day response period and appeal requirement. Nevada’s Nevada Consumer Health Data Privacy Notice describes its 30-day deletion period after authentication. Both notices identify where the implemented controls do not satisfy the full statutory process.