NavBharatAI · Last updated 5 October 2026
Delete your NavBharatAI account
Last updated: 5 October 2026
This page explains how to ask us to delete your NavBharatAI account (Android app package com.navbharat.ai, and the website navbharatai.com) and the data associated with it.
The fastest way: delete it yourself, in the app
Open Settings, scroll to the bottom to the red Danger zone, and choose Delete account. You will be asked to type the word delete to confirm — a single accidental tap can never delete an account. Deletion runs immediately and you are signed out.
Or ask us to do it
If you cannot reach the app — or you would rather we handled it — email us from the address you signed up with:
info@navbharatai.com
Use the subject line:
Delete my account
In the message, please include:
- The email address or phone number you use to sign in to NavBharatAI.
- A sentence confirming you want the account deleted — for example, "Please permanently delete my NavBharatAI account and my data."
Sending it from your own registered address is how we confirm the request is really yours. If you cannot email from that address, tell us and we will ask you for another way to confirm — we will not delete an account on an unverified request, because that would let someone else erase your work.
We acknowledge every request within 72 hours and complete it within the timeline below.
What is deleted
When your deletion request is completed, we remove:
- your account record and profile (name, email address, phone number, profile picture);
- your chat history across every NavBharatAI assistant;
- your projects and built apps, including their files and any archives you uploaded, the review comments left on them, and the list of things the builder asked you to do for them;
- your build history and diagnostics tied to your account, including the reports of past builds, every saved version of every app you could have restored, and the record of which instructions each build ran with;
- your notifications and devices — the mentions sent to you inside NavBharatAI, and the push-notification address of each phone you signed in on;
- your wallet, token balance and usage records;
- any API keys and credentials you stored in the secrets vault;
- your NavBharatAI API keys — every developer key you made at Home → Other AI → Developer Tools, and
- your chat bots — every bot you connected, together with the token and app secret NavBharatAI held
- the addresses NavBharatAI posted your build events to — the webhook URLs you added, so nothing is
- your architecture decisions and tech-debt notes — what the builder recorded about the stack each of
- your App Lock PIN — the 4-digit PIN that locks parts of NavBharatAI, including that vault;
- your saved connected services — the MCP services you saved on your account to reuse across apps
- your gift-code purchase tally — the running count of how many gift codes you bought on a given
- your App Mart likes, dislikes and comments — every 👍 and 👎 you gave, every comment and reply you wrote, your App Mart notifications, the list of people you blocked, the creators you follow and the people who follow you, the profile photo you uploaded, and the link between your public creator code and your account (so your App Mart profile stops opening). Other people's replies to your comments are not theirs to lose, but they can no longer be reached once your comment is gone;
- your rating of NavBharatAI — the stars and the note you gave after one of your apps went live, and any "Not now" pause on that question;
- your cross-device workspace — the copy of your chat sessions and your last built app that we
- your chat and voice memory — what each NavBharatAI assistant remembered about you to keep a
- your builder settings and the record of what the builder learned from you — your saved
- your daily usage counters — terminal seconds, tool and picture calls, the AI usage rows behind
- the record of which screens and actions you used — the product-usage rows we keep to see where
- your professional pass, if you had one, and which admin notices you had already read;
- the files you uploaded — .zip archives and spreadsheets you gave to a build;
- your share links — a page you shared stops opening;
- your instantly-hosted apps — an app you published with instant hosting stops being served;
- your referral record — your own code and the claims against it. (A payout already recorded under
- your connected domains — NavBharatAI's record of a domain you pointed at one of your apps, and
- the engineering notes the builder kept for you — the design decisions it recorded for each
- the AI identity of each app you published — the record of which of your apps may use
- everything the builder kept about each app — its plan and roadmap, its build state, the trail of
- the live preview and deployment of each app — the sandbox it ran in, our record of where it
- the records your app stored in the NavBharatAI database — the small database started from Publish, including its records and the operation counters kept beside them;
- your team, if you made one — a team belongs to the account that created it, so it goes with
- your saved sessions and preferences;
- your connection to GitHub, if you had connected one. (This removes NavBharatAI's access. It does not delete anything in your own GitHub account — that stays yours.)
- your connection to Supabase, if you had connected one, and our record of which sleeping-database reminders we already sent you. (This removes NavBharatAI's copy of the access. It does not delete your Supabase projects or anything in them — they stay in your own Supabase account; to revoke the access fully, also remove the NavBharatAI app in your Supabase account settings.)
the daily usage counted against each one. A key that was still in use stops working the moment it is deleted, and the same key can never be used again;
for it, so the bot stops answering, and the conversations each bot had with the people who messaged it. (This removes NavBharatAI's copy of those credentials. The bot's own account on the messaging platform stays yours, and you can delete it there.)
ever sent to them again;
your projects chose, and the list of rough edges it was keeping track of;
(this removes NavBharatAI's saved copy of the address and key; it does not touch anything in the service's own account, which stays yours);
day. (The codes themselves are not deleted: once you have given a code to somebody, it is theirs to redeem, and a payment record is one of the things we are required to keep — see below.);
keep so they follow you from one device to another;
conversation going, the voice-chat turns, what a professional assistant had noted about you, and every build conversation you had with the builder;
preferences, the lessons it kept, the mistakes ledger it used so it would not repeat itself, and the diagnostics report of your own last build;
your spend, your free-build credit, and the balance warnings we had already sent you;
people get stuck. They are deleted after 30 days anyway; closing your account removes yours now;
somebody else's referral is their record, and is kept — see below.);
the uptime history we kept for it. (This removes OUR record. It does not change anything at your domain registrar or your own host, which are not ours to touch — remove the DNS records there if you want the name completely free.)
project and the list of rough edges it was tracking in your code;
NavBharatAI's AI, and as you;
decisions it took, the caches it reused between builds, the software bill of materials for each build, the app's own site settings, the note of which App Mart app it was remixed from, and the outside services it was wired to talk to together with the keys we held for them;
was deployed, and the saved copy of its last working build that we kept so its preview opened instantly;
yours: the list of its members (their names and email addresses are removed with it) and the shared library it held. Your own member record is also removed from every other team you had joined;
Your unused token balance is not refundable on deletion. Deleting the account ends access to it, so please spend or withdraw value first if that matters to you.
What is kept, and why
- Payment, invoice and tax records. Indian tax and accounting law requires businesses to keep records of money received. We keep the order identifier, the amount, the date and the payment status — not your card number, UPI PIN or banking credentials, which we never receive. These are retained for the period required by applicable law and are not used for anything else.
- Anonymous, non-identifying records. Technical logs and the platform's error-pattern learning contain no account identifier and cannot be traced back to you, so there is nothing personal in them to delete.
- Apps you published to the Nav App Store — the app stays, you do not. Your name, email address and
account link are removed from every listing you published, and the listing is taken out of the public store so it no longer appears to new visitors. The app itself is kept, and anyone who already bought it can still open and run it: a purchase is not refundable, so taking the app away would leave somebody paying for nothing. A paid app of yours can no longer be bought once your account is gone — there would be nobody to pay — so anyone who opens it from then on gets it free. Submissions that were never published (waiting for review, or refused) are deleted outright, because nobody ever saw them. If you want a published app removed completely as well, say so in your email and we will take it down.
How long it takes
Personal data is deleted or irreversibly anonymised within 30 days of a confirmed request. The payment and tax records described above are the only exception.
Backups are cycled on their own schedule, so a copy of already-deleted data may persist in an encrypted backup for a short additional period before it is overwritten. It is not restored to the live service and is not used for anything.
Questions
Email info@navbharatai.com. The same address is our grievance contact for the purposes of the Digital Personal Data Protection Act, 2023.
For the full picture of what we collect and why, see our Privacy Policy.