User Data Deletion
User Data Deletion
[TO CONFIRM] need business confirmation before this page can be finalised.This page explains how data in the DMS platform can be deleted, who is allowed to ask for what, and what happens to records that cannot be erased immediately. It doubles as the public data-deletion instructions for users who connected third-party services (such as Meta/WhatsApp) to the platform. Submitting a request here starts a verified review workflow — it is not an instant delete button, and no deletion ever executes directly from this public page.
A. Data deletion overview
DMS stores two fundamentally different kinds of information (defined in the Privacy Policy): Account Data about the individuals and organizations that use the Service in their own right, and Clinic Data — patient records and related clinical, scheduling and financial content — that dental organizations hold on behalf of the people they treat. Eligibility for deletion depends on which kind of data you mean and who is asking: an individual can request their own account data; an Organization's administrator requests data their Organization controls; and patients exercise rights over their treatment record through their dental clinic.
Deletion requests submitted through this page are recorded, verified (we confirm you are the account owner, an authorized administrator, or the relevant clinic), reviewed against retention obligations, and then fulfilled by the operations team. You receive an acknowledgement with a reference id when you submit, and a confirmation or reasoned declination once the review completes.
B. Data categories
Requests should identify which category (or categories) of data they concern:
- Individual user account information — your name, email, profile image, Clerk-managed identity record, memberships, role assignments, sessions and action history tied to your user id.
- Organization / clinic information — the tenant: its name, settings, branches, departments, resources, working hours, roles configuration, subscription and billing records. Only an authorized administrator (or platform owner for closed accounts) may request this.
- Patient records — demographics, consents, documents, portal accounts. Requested by the Organization that holds them, or by the patient via their clinic (see section E).
- Appointment records — bookings, waiting-list entries, visit histories, provider availability linked to them.
- Invoice and payment records — charges, invoices, payments, refunds, installment plans, and subscription billing records.
- Treatment plans and procedure records — clinical notes, tooth findings, plans, plan items, prescriptions and procedure records.
- Uploaded documents and attachments — files in the Organization's document and image storage buckets and their metadata rows.
- Communication and notification records — generated notifications, delivery-status receipts, and portal message threads.
- Connected third-party integration information — the Organization's WhatsApp/Meta integration configuration, encrypted credentials and template snapshots; API keys and webhook subscriptions. See section F.
C. How to submit a deletion request
Use the form on this page (preferred), or email the same information to
A complete request includes:
- your full name and the email address registered with the account(s) concerned;
- the organization/clinic name, if the request involves data an Organization controls;
- the request category from section B (your own account, an Organization's data, a specific patient record, an integration);
- a clear description of what should be deleted and any record identifiers you know (patient numbers, invoice numbers, date ranges);
- the required consent confirmation that you are authorized to make the request — false statements may themselves be unlawful.
What happens next:
- Acknowledgement — the form returns a reference id the moment your request is recorded.
- Verification — we contact the registered email(s) and confirm identity and authority. For Organization data, an authorized administrator of that Organization must confirm; for patient records, the treating clinic must instruct us (section E). Requests that cannot be verified are declined without deleting anything.
- Review — we check the request against the retention exceptions in section D.
- Processing — verified requests are executed by the operations team within our response window [TO CONFIRM — commit to a target, e.g. "within 30 days of verification, extended for complex requests"].
- Confirmation — you are told when each item is completed or, if declined wholly or partly, the specific legal or operational reason.
Security note: this page only records requests. No deletion is exposed to anonymous callers, and account self-service inside the app follows the same verified path — a user cannot destroy an Organization's records by deleting their own login.
D. Data retention and exceptions
Deletion is not always immediate or total. Where a record falls into one of these buckets, the content (or a minimal residue of it) is retained for the period the obligation requires, after which it is deleted or anonymized:
- Legal and regulatory obligations — clinical-records, professional-conduct and health-data rules that bind the Organization as a care provider, and any applicable retention rules binding Bnet Innovations. Retention periods differ by jurisdiction and are the Organization's (and its counsel's) determination; we preserve what they must preserve.
- Accounting and financial recordkeeping — invoices, payment and tax records for subscriptions and patient billing are retained under financial-records and tax law.
- Security and fraud prevention — limited identity, session and abuse-prevention records may be kept where deletion would defeat security, or where an account is linked to confirmed misuse.
- Active disputes — data subject to a legal claim, investigation or regulatory request must be preserved until the matter concludes.
- Backups and technical limits — deletions apply to live systems; encrypted backup copies age out over the backup-rotation window [TO CONFIRM — state the actual window] and are not surgically edited.
- Audit trail — the append-only audit log records that an event (including a deletion) occurred, by whom and when. The deleted content is gone from the live tables, but the fact of the action is deliberately preserved so the log stays trustworthy evidence.
Accordingly we do not promise "instant, complete and unconditional erasure". We do promise: the categories above are the only reasons we decline or delay, the reason is told to you, and retention beyond the obligation does not occur.
E. Organization-managed and patient data
Staff member leaving a clinic: ask your Organization's administrator to remove your membership; they may also contact us to delete the residual Account Data linked to you, subject to the audit-log and retention rules above.
Deleting your own login never deletes your Organization: your personal account, its credentials and sessions are removed (after verification), while the tenant's Clinic Data — patients, records, invoices — remains with the Organization that owns it. Administrator accounts are the Organization's safeguard; we will not dismantle a tenant on the request of a single departing member. An Organization closes its whole tenant only via a verified request from an authorized administrator or owner, following section C.
Patients: DMS has no direct relationship with you — your dentist does. To see, correct or ask for deletion of your treatment record, contact the clinic that treats you; they operate the records and the legal duties around them. If a clinic asks us to erase a record (and no retention duty blocks it), we execute it as their instruction. If you believe a clinic is mishandling your data stored in DMS, you may still contact us and we will respond as the platform operator within our role — see section C — which may mean forwarding your concern to the Organization and telling you so.
Closed Organization: on termination, see the export-and-deletion terms in the Terms of Service — a defined window for the administrator to request export or deletion, mandatory-retention carve-outs, and final destruction afterwards.
F. Meta and third-party connected data
If you (or your Organization) completed Meta's Embedded Signup to connect a WhatsApp Business Account, three related mechanisms exist and you should use the right one:
- This page — the human-readable instructions URL registered with Meta. Send us a request through it as above; when it concerns data flowing from a Meta-platform login or authorization, write "Meta data deletion" in the description (or use the INTEGRATION category). We identify the stored integration by the Meta user/account identifiers supplied in the callback and remove the stored access credentials, integration configuration, and message/notification records associated with it, again subject to section D.
- Meta's own tools — you can revoke the DMS app's access to your Meta/WhatsApp business assets at any time from your Meta Business settings ("Business integrations" → remove DMS), which cuts off future data flow immediately; revocation is not the same as deletion of what we already store, so submit the request here as well to have stored data erased.
- Platform-side disconnect — an Organization administrator can disconnect its WhatsApp integration from Settings → Integrations; that drops the credentials and stops sends. Historical notification rows remain until the Organization or this process asks for them.
When Meta notifies us of your deletion request through its data-deletion callback, that event is recorded on our side as an INTEGRATION request awaiting the verification in section C — the callback alone does not delete anything, because we must first confirm which stored records belong to the requesting identity. Other connected providers (Razorpay, Google, Clerk) are covered by their own privacy tools plus the same request process here for anything we store.
Submit a data deletion request
Use this form to ask us to delete your account, your organization's data, or data you are authorized to remove. Submitting this form records the request — it does not delete anything immediately. Every request is reviewed, the requester's identity and authority are verified, and you are contacted at the email you provide before anything is actioned. For patient records, contact your dental clinic first (section E).
Questions about this user data deletion?
Contact Bnet Innovations at founder@bnetinnovations.in. A registered business address and entity details are pending confirmation — see the contact section above.