Delete your PhenoTrack account

Last updated: 2026-09-16

This page explains how to delete your PhenoTrack account and everything stored with it. Deletion is immediate and permanent — your account is erased outright rather than deactivated, there is no grace period, and we will not restore an account once it is gone.

Which app this applies to

  • App: PhenoTrack — an AI-assisted indoor grow journal.
  • Android package name: com.phenotrack.app. The same account signs in to the web app at app.phenotrack.com.
  • Developer: PhenoTrack, Denmark (EU). Data-protection contact: privacy@phenotrack.com.

Delete your account in the app

This is the fastest route and the one we recommend — it erases everything in one step, immediately.

  1. Open PhenoTrack on Android, or sign in at app.phenotrack.com.
  2. Go to Settings → Account → Delete account.
  3. Type DELETE to confirm. This is the last point at which you can still stop.
  4. Wait for the confirmation. The app signs you out and returns to the sign-in screen once the deletion is finished.

For your protection, deleting an account requires a sign-in from the last few minutes. If you have been signed in for longer, the app tells you so and nothing is deleted — sign in once more and run Settings → Account → Delete account again.

Export your data first (optional)

Deletion cannot be undone, so export anything you want to keep before you start. Settings → Account → Data → Export Data produces a ZIP archive with a JSON file, your photos, and CSV copies of your journal and environment readings. Once the account is deleted we cannot produce an export for you.

If you cannot sign in

If you have lost access to your account and cannot complete the steps above, write to privacy@phenotrack.com and ask us to delete it. We will verify that you control the account's e-mail address, confirm what is about to be erased, and carry out the deletion for you.

  • Use the subject line "Account deletion request".
  • Write from the e-mail address the account was registered with — we can only act on a request we can tie to the account.
  • We will never ask you for your password, and we will never ask you to send one.
  • We acknowledge within 72 hours. The deletion itself is completed within one month, the deadline GDPR Art. 12(3) sets for a request like this — in practice it is usually the same working day.
  • Ask in the same e-mail if you would like written confirmation once the deletion is complete.

What is deleted

All of the following is erased at once:

  • Your journal — plants, growspaces, grow runs, log entries, tasks, reminders, notes, and phenotype scores.
  • Every photo you uploaded, including the original files in cloud storage. The files stop being reachable immediately; see "What is kept" for the seven days before they are erased for good.
  • Your environment and sensor readings, along with the equipment and light profiles you configured.
  • Your Pro entitlement, your purchase links, and your AI credit records.
  • The sign-in account itself, so the e-mail address can no longer be used to sign in to PhenoTrack.
  • The local database on the device you run the deletion from — encrypted at rest on Android. On Android, the photo files the app saved on that device — including full-resolution originals, and any photos written there by a restore — are not removed. A full copy can also remain on any other device where you were signed in — signing out there does not erase it. To remove either, uninstall PhenoTrack on that device, or, if you used the web app there, clear the site data for app.phenotrack.com in that browser.

What is kept, and for how long

Some things outlive the deletion. None of them is used to rebuild your account, and none of them is readable in the app:

  • Encrypted database backups — up to 30 days. Backups run on a rolling 30-day cycle and are never edited in place, so a backup taken before your deletion still holds your data until it ages out. Backups are restored only for disaster recovery, never to retrieve an individual account.
  • Crash reports — about 90 days, and only if you opted in. Crash reporting is off by default. If you turned it on, reports already sent are held by our processor and purged automatically after roughly 90 days.
  • Analytics events — up to 14 months, and only if you opted in. Analytics is off by default. If you turned it on, the aggregated events already sent are held by our processor and purged automatically after at most 14 months.
  • Deleted photo originals — 7 days. When a photo file is deleted from our cloud storage it stops being reachable at once, but our storage provider keeps it restorable by us for seven more days before erasing it permanently. That window exists so an accidental deletion or a fault on our side can be undone. During it your photos are not served to anyone and not visible in the app; after it they are gone for good.
  • A record of your deletion request — only if you asked us by e-mail. We keep the date, the address the request came from, and the date we finished, because data-protection law requires us to be able to show that a request was handled. It is kept apart from your account data, it is never used for anything else, and unlike the items above it has no expiry timer.
  • A rate-limit counter carrying your account's internal ID — kept indefinitely. Our servers cap how often each account can call certain functions, and they do that by counting recent calls in a small record named after the account's internal identifier. The record holds nothing but those counts: it cannot be used to sign in, it is not tied to your e-mail address or to any of your content, and it is never read for anything but rate limiting. Like the record above, it has no expiry timer — the deletion does not remove it, and because the account can no longer make requests, nothing overwrites it either.

Nothing in that list can be used to sign in, and none of it is linked back to a live account after deletion.

Related pages

For the full picture of what we collect and why, see our Privacy Policy; for how it is protected while the account exists, see Security.