Privacy Policy
Privacy Policy
[TO CONFIRM] need business confirmation before this page can be finalised.This Privacy Policy explains what information the DMS platform ("DMS", the "Platform", or the "Service") collects, how it is used and protected, and what choices you have. DMS is practice-management software for dental organizations; two very different kinds of information pass through it, and this policy keeps them distinct throughout: information about the businesses and people who use the Service directly, and patient information that dental organizations record in the Service on behalf of their patients.
1. Introduction and scope
This Privacy Policy applies to the DMS dental practice management platform operated by Bnet Innovations ("Bnet Innovations", "we", "us") through its websites, applications and APIs (collectively, the "Service"). It describes our handling of personal data when you visit our marketing site, register an account, use the staff application, or use the patient portal.
The Service is business software provided to dental practices, clinics and hospitals ("Organizations"). Most patient-related information in the Service is entered, controlled and owned by the Organization that serves that patient — for those records the Organization, not Bnet Innovations, is the party with the direct relationship to the patient and (in most legal frameworks) the data controller. We process that information as a service provider on the Organization's instructions, as described in sections 6, 7 and the Terms of Service.
This is a draft document (version 1.0-draft) published for legal review; bracketed [TO CONFIRM] items are facts not yet verified by the operator. Nothing in this policy grants rights beyond those required by applicable law.
2. Definitions
- Account Data: information about the individual staff users and patient-portal users of the Service — names, email addresses, roles, sessions and usage records that identify a person using the Service in their own right.
- Clinic Data: all content Organizations place in the Service — including Patient Data, appointments, clinical records, invoices and documents.
- Patient Data: health, demographic, appointment and financial information about patients that an Organization records in the Service about the individuals it treats.
- Organization: a dental practice, clinic or hospital that holds a subscription (a "tenant" in the Platform) and the staff accounts it provisions.
- you: the reader — an Organization owner, a staff user, a patient-portal user, or a visitor to the marketing site.
3. Information collected
What the Service collects depends on the role a person plays. The categories below reflect the Platform's actual modules and infrastructure.
3.1 Account and authentication information.
Human authentication is delegated to Clerk, an identity provider. For staff and patient-portal users we process: name, email address, profile image, email-verification status, and the authentication events Clerk reports to us (sign-ins, session lifecycle). Passwords are held by Clerk, not by us — our database stores no passwords or password hashes. We also store, per person, the Organization memberships, role assignments and branch/department assignments that determine what each account can see. Session records include access tokens (short-lived, 15 minutes) and hashed refresh tokens.
3.2 Organization and clinic information.
Organization name, type and settings; branches, departments, operatories/resources, working hours and holidays; procedure-price catalogs; roles and permissions configuration; subscription and billing entity details; and the staff directory the Organization manages.
3.3 Patient information.
At the direction of an Organization: patient demographics, contact details, consent records, clinical history the Organization enters (including medical/dental conditions relevant to treatment), insurance and guarantor details, portal credentials the Organization provisions, and uploaded documents and images (stored in Supabase Storage buckets; the Platform stores file metadata and links). Patient records carry an internal sequential patient number (PT-…) assigned by the Organization's tenant.
3.4 Appointment and scheduling information.
Appointments, waiting-list entries, provider availability and time off, visit records, check-in status and the operational history associated with scheduling.
3.5 Invoice and payment-related information.
Charges, invoices, payments, refunds, payment plans and installments recorded for patients or for the Organization's own subscription. Patient and staff payment card numbers are not stored in our database: subscription payments are handled by Razorpay's checkout, and we retain order/payment identifiers and status metadata needed to reconcile billing. Organization subscription invoices and their gateway references are stored.
3.6 Treatment plans and procedure records.
Clinical notes, dental-chart findings (tooth-level conditions), treatment plans and their items/stages, procedure records and prescriptions, as entered by licensed users of an Organization.
3.7 Communication and notification information.
Notification templates, the notifications generated for events (appointments, invoices, plans), their delivery status, and messages exchanged between Organization staff and patients through the portal. Where an Organization connects WhatsApp (section 11), phone numbers and message templates/status metadata are processed through Meta's WhatsApp Cloud API.
3.8 Technical information, cookies and usage data.
Server logs (request metadata, timings, redacted authorization headers), audit-log entries describing administrative and clinical actions taken in the Service (append-only, hash-chained with SHA-256), IP addresses used for rate limiting on auth endpoints, and client-side storage used by the applications: the theme preference and last active tenant in browser localStorage, and Clerk's session cookies on authenticated pages. The public marketing pages do not load third-party advertising or analytics trackers. [TO CONFIRM — whether any product analytics are planned.]
4. Purposes and legal bases for processing
We process Account Data and Clinic Data for the following purposes:
- Providing the Service: operating the modules an Organization subscribes to, including storage, display, search, scheduling and billing on the Organization's instructions.
- Account administration: authentication, authorization, role assignment, security of sessions.
- Contract performance: billing, subscription lifecycle (trial, renewal, expiry and the automatic freeze of expired subscriptions), support.
- Safety, integrity and compliance: abuse prevention, rate limiting, audit logging, fraud prevention, and compliance with applicable law or lawful requests.
- Improvement: diagnosing faults and improving reliability and usability; we do not use Patient Data for unrelated commercial purposes.
Where a privacy framework that requires named legal bases (such as the GDPR) applies to a given processing activity, we intend the bases above to correspond to contractual necessity, legitimate interests, legal obligation, and — for health data — the service-provider and explicit-consent pathways available under that framework, acting on the Organization's instructions. [TO CONFIRM — legal counsel to map each activity to bases for each applicable jurisdiction; this policy makes no compliance claim.]
5. Patient data and sensitive health information
Patient Data recorded in the Service frequently includes sensitive health information. That information is entered by, and belongs to the treatment relationship of, the Organization. Patients provide their data to their dental organization — not to Bnet Innovations — and the Organization is responsible for having a lawful basis to record it and to place it in practice-management software.
Bnet Innovations accesses Patient Data only to provide and secure the Service (hosting, backup, debugging with the narrowest access necessary, and responding to the Organization's requests). We do not sell Patient Data, and we do not use Patient Data for advertising or for training generalized machine-learning models. Where optional AI features are enabled (Hospital-tier "ai" feature, Google Gemini), the inputs and outputs of those calls are logged as AiInteraction records for review by the Organization's staff — see the Terms of Service for the medical-advice disclaimer.
6. Responsibilities of the dental organization
Organizations using DMS are responsible, in their own right and toward their patients, for: the lawful collection and quality of Clinic Data; staff access discipline (correct roles, branch scoping, timely deprovisioning of departed staff); obtaining any consents or notices their professional and privacy laws require, including for WhatsApp messaging and portal use; handling patients' privacy-rights requests, which we route to the Organization that holds the record (see section 14); and the confidentiality of credentials issued to their users.
The Platform supports these duties with enforced tenant isolation, server-side permission checks on every request, branch-scoped access for non-clinical roles, and an append-only audit log — but the choices about who sees what patient information remain the Organization's.
7. Responsibilities of Bnet Innovations as service provider
For Clinic Data we act as the Organization's service provider / data processor: we process it only to deliver the contracted features and as our documented subprocessors require; we maintain reasonable technical and organizational measures (section 8); we forward privacy requests and incidents to the controlling Organization; and on termination we make Clinic Data available and deletable per the contract and the data-deletion process. For Account Data of staff and portal users and for our own business records (billing, support), we act in our own right as the responsible operator. These role assignments are drafted for counsel review and may change per jurisdiction.
8. Data storage and security practices
The Service is delivered over HTTPS/TLS. Application data is stored in a PostgreSQL database managed by Supabase; uploaded documents and images are stored in Supabase Storage buckets; a Redis instance backs scheduled jobs. Production database hosting is currently documented as Supabase on AWS ap-south-1 (Mumbai, India) — [TO CONFIRM] final production regions before publication. Row-level security is enabled on database tables so the public API surface exposes no tables to anonymous access, and tenant isolation is re-verified server-side on every request.
Operational safeguards we actually run today include: short-lived JWT access tokens with audience separation between staff and patient-portal sessions; opaque refresh tokens stored only as salted hashes and rotated on use; role- and permission-based authorization evaluated from the database on every request; rate limiting and brute-force protections on authentication endpoints; redacted structured logging (authorization headers and passwords are never logged); an append-only, hash-chained audit trail; and application-level encryption of stored third-party integration credentials (for example Meta access tokens).
We do not claim certification. Statements elsewhere on this site about specific encryption standards, certifications or uptime SLAs are marketing copy pending verification and are not representations of this policy. No method of storage or transmission is perfectly secure; security of credentials and of the physical environment of your staff remains shared with your Organization.
10. Authentication and infrastructure providers (subprocessors)
The current named providers behind the Service are:
- Clerk — authentication and session identity for staff and patient-portal users (name, email, auth events).
- Supabase — managed PostgreSQL database and file storage (all application data, documents).
- Razorpay — subscription and patient payment checkout and gateway references (billing metadata; we do not store card data).
- Google Cloud (Gemini API) — optional AI assistance features when enabled; interactions are logged for organizational review.
- Meta (WhatsApp Cloud API) — only where the Organization completes its own WhatsApp integration (see section 11).
- Hosting/CDN and Redis providers — application hosting and job scheduling. [TO CONFIRM — final production frontend host and Redis vendor to be listed.]
A current subprocessor list can be requested by email; material additions are noted by updating this policy (section 19).
11. WhatsApp and Meta integration data handling
Clinic notifications (appointment confirmations, reminders, billing notices) can be delivered over WhatsApp once an Organization connects its own WhatsApp Business Account through Meta's Embedded Signup. When an Organization uses this feature: the Organization authorizes Meta to share its business-account information with us; we store the resulting integration configuration and credentials (encrypted at application level) linked to that Organization; phone numbers from the Organization's patient records and approved message-template parameters are sent to Meta's WhatsApp Cloud API to deliver messages; and Meta sends delivery-status receipts (sent/delivered/read/failed plus message ids) back to our webhook so staff can see delivery outcomes. Inbound replies are a planned capability, not an currently-enabled feature.
Meta's own privacy statement applies to Meta's processing, and data requests connected to Meta-platform authorization can be made through the data-deletion page as well as the Meta privacy tools. The legal basis and consent practice for messaging patients rests with the Organization.
12. Payment processing and billing information
Subscription billing: plans are priced in Indian rupees (SOLO, CLINIC and HOSPITAL tiers billed monthly, quarterly, half-yearly or yearly, with a 15-day free trial and no payment method collected at signup). Checkout, payment handling and the associated card/UPI credentials are operated by Razorpay under their terms and privacy policy; we keep order ids, payment references, statuses and invoice records. Patient-facing billing inside the Service (charges, invoices, payments, refunds, payment plans) is operated by Organizations for their patients and follows the same gateway arrangement for online payments.
13. Data retention and deletion
Clinic Data is retained for the life of the Organization's subscription and is deletable by (or on instruction to) the Organization at any time within normal operations, subject to the Organization's own record-retention duties for clinical, tax and financial records. Deleted records are removed from active databases; residual copies may persist in backups for the backup-rotation period [TO CONFIRM — state the actual backup retention window] and in the append-only audit trail, which deliberately preserves an event record (who deleted what, when) rather than the deleted content.
Account Data for an individual staff member is retained while the membership exists and is minimized (kept only for legitimate audit/legal purposes) after the Organization removes the user. Portal accounts follow the Organization's retention for the patient record. Individuals may request deletion of their own account data through the process published at our Data Deletion page; complete erasure may be limited where records are needed for legal, accounting, security or dispute-resolution reasons, as explained on that page.
14. Privacy rights and how to exercise them
Depending on your jurisdiction, you may have rights to access, correct, export, delete or restrict processing of your personal information, to object to certain processing, and to withdraw consent where consent is the basis. The practical routes in the DMS world are:
- Staff users: request changes through your Organization's administrator first (they control your membership), or contact us directly via the deletion request form / email; we will coordinate with your Organization.
- Patients: your dental clinic is the controller of your treatment record. Ask your clinic for access, correction or deletion; clinics that need technical help executing it can contact us, and we will process it as the clinic's instruction.
- Anyone: use the form at our Data Deletion page or email founder@bnetinnovations.in with "privacy request" in the subject. We verify identity/authority before fulfilling, acknowledge receipt, and respond within the time applicable law requires. [TO CONFIRM — operator to commit to an internal response-time target.]
We do not discriminate against users for exercising privacy rights. Where a right must be exercised through your Organization (patient records), we will tell you whom to ask rather than refusing silently.
15. International data transfers
Application data is hosted in India (Ap-South-1) as currently documented; vendors listed in section 10 operate global infrastructure and some (Clerk, Meta, Google, Supabase storage egress) may process or replicate data outside India. Patients of an Organization may themselves be international. If a transfer regime applies to your data (for example EU/UK transfers, or India's Digital Personal Data Protection rules on processing outside India), the safeguards depend on the vendors' own mechanisms — [TO CONFIRM — counsel to review vendor DPAs and transfer mechanisms before publication]. This policy does not assert that any particular transfer safeguard is in place.
17. Children's privacy
DMS is business software for dental practices and is not directed at children. Pediatric patients' records exist in the Service only as Patient Data created by clinics about the children they treat; those records include minors' health information and are handled with the same (or stricter) controls as any Patient Data, under the Organization's guardianship and consent processes. A minor's portal account is provisioned by the clinic with the relevant guardian's involvement. We do not knowingly collect personal information directly from children outside that clinical context.
18. Security incidents and breach handling
We monitor for security issues through logging, rate limiting, authentication failure patterns and external reports. If we determine that an incident has compromised Clinic Data, we will notify affected Organizations promptly with the information they need to meet their own duties to patients and regulators, and we will not publish inaccurate claims about the event. Reports of suspected vulnerabilities: email founder@bnetinnovations.in. [TO CONFIRM — breach notification timelines under the laws applicable to the operator's registered jurisdiction(s) and to typical Organizations' regulators.]
19. Changes to this Privacy Policy
We may update this policy to reflect changes in the Service, vendors or law. Material changes will be announced in the Service (for example an in-app notice or email to Organization administrators) before or contemporaneously with taking effect where reasonably practicable. The "Last updated" date at the top of this page marks the current version; prior versions can be requested by email.
20. Contact and privacy inquiries
Operator: Bnet Innovations. Privacy contact: founder@bnetinnovations.in. [TO CONFIRM — registered legal entity name, registered address, and any designated privacy officer/Grievance Officer details required by applicable law.] Deletion and data-request intake: our Data Deletion page.
Questions about this privacy policy?
Contact Bnet Innovations at founder@bnetinnovations.in. A registered business address and entity details are pending confirmation — see the contact section above.