Delete Your Nabta Account

Last updated: September 2, 2026

You can permanently delete your Nabta account and its account-linked rows in Nabta’s database. The in-app database deletion is immediate and irreversible; the exceptions for provider records, unlinked crash aggregates, operational logs, and short-lived disaster-recovery backups are explained below.

Option 1 — Delete in the app (instant)

1. Open the Nabta app and sign in.
2. Go to Profile / Settings.
3. Tap Delete account and confirm.

After a successful request, the account-linked rows in Nabta’s database are erased immediately and you are signed out.

Option 2 — Request deletion by email

If you cannot access the app, email saleh.labs.dev@gmail.com from the Google account email you use to sign in, with the subject “Delete my account”. We verify ownership through that email address before processing the request.

What gets deleted

• Your Nabta profile (email, name, profile-photo URL, Google account ID, Nabta account ID, Clerk mirror ID, language, creation/last-seen times, and any legacy installation ID).
• Your garden: all plants, nicknames, site labels, latest/next watering timestamps, private garden photos and their metadata, and any previously saved weather location.
• Your local subscription/quota state, identification image fingerprints, idempotency/replay records, and account-linked usage/audit rows.
• Your plant identification/care reports, including selected reasons, optional details you wrote, bounded displayed-output snapshots, and review statuses.
• Any Ask Flora chat data: encrypted reply copies, usage counters, and any replies you reported.

Nabta does not persist Ask Flora prompts or conversation history as plaintext database rows. Private garden photos are deleted from the active database with their photo, plant, or account; deleted bytes can remain in access-restricted daily disaster-recovery backups under a 14-day deletion schedule. A failed cleanup can delay removal until maintenance succeeds.

What is separate

• Crash aggregates: diagnostic records have no account or device ID, so account deletion cannot select them. They are deleted by the 90-days-since-last-seen retention job.
• Operational logs: entries are removed under the infrastructure retention/rotation described in the Privacy Policy, not synchronously with the account row.
• Database backups: access-restricted daily disaster-recovery backups can retain deleted account rows and private garden photos under a 14-day deletion schedule; a failed cleanup can delay removal until maintenance succeeds.
• Clerk: Nabta requests deletion of its best-effort account mirror after the local database commit, but a provider failure does not roll back your already-completed Nabta deletion.
• Google Play and RevenueCat: their transaction/customer records are provider-side. Email us to request deletion where available; some transaction records may be retained under provider policies or legal duties.

Contact

Questions about deletion: saleh.labs.dev@gmail.com.