Trust & transparency
Privacy Policy
Last updated: 23 September 2026
DentaSK provides software for dental clinics and organizations. This policy explains what DentaSK handles when you visit this website, request a demo, use an account, or connect a supported service. A clinic controls the patient and business information it places in its workspace; DentaSK processes it to deliver the services that clinic chooses.
1. Scope and responsibilities
This policy covers the DentaSK marketing website, clinic and organization consoles, and DentaSK mobile applications where the same account and backend services are used. For clinic-entered patient records, the clinic or healthcare organization decides why information is collected, who may access it, and how long healthcare records must be kept. DentaSK operates the software on that customer's instructions. For our own website enquiries, account administration, security and support, DentaSK decides the relevant processing.
If you are a patient, please contact your treating clinic for access to, correction of, or questions about your clinical record. We can help the clinic carry out a verified request.
2. Information we receive
| Category | Examples | How it reaches DentaSK |
|---|---|---|
| Website enquiries | Clinic name and WhatsApp/contact phone number | You submit the demo form or contact support |
| Account and team | Name, email, phone, login credentials, organization, branch, role and staff activity | You or an authorized administrator creates an account |
| Clinic operations | Appointments, admissions, billing, payments, staff, inventory and reporting records | Authorized clinic staff enter or import information |
| Patient and health information | Contact and demographic details, history, allergies, treatment-related records and documents | The clinic enters or imports them to provide care and manage its records |
| Connected channels | Provider account IDs, authorized asset names, reviews, comments, messages, media, campaign metrics and delivery status | An asset owner authorizes Google, Meta, Instagram or WhatsApp access |
| Optional AI and voice workflows | Prompts, draft responses, call details, transcripts or audio and usage records, depending on enabled features | The clinic configures and uses an AI or calling feature |
| Technical records | Session and device data, access and audit events, error logs and security signals | Generated as needed to operate and protect the service |
Fields and connected data vary by enabled module. A demo request does not require patient information. Please do not include patient or medical information in the public demo form.
3. Why we use it
- To arrange a requested demonstration and respond to support enquiries.
- To authenticate users, enforce organization/branch roles and run the clinic workflows they choose.
- To retrieve and display authorized connected-service data, prepare drafts, and perform approved actions such as replies or campaign publishing.
- To provide reporting, follow-up and optional AI features configured by the customer.
- To prevent abuse, investigate errors, keep audit records and meet applicable legal obligations.
We do not sell patient records or Google/Meta account data. DentaSK does not use connected Google user data for unrelated advertising or to train a general-purpose AI model. Customer-enabled AI features may send the data needed for a particular request to the configured AI or voice provider; see section 5.
4. Google, Meta, Instagram and WhatsApp access
A customer must authorize a connection with the relevant provider and select the business assets it may use. Depending on the feature and granted permissions, DentaSK may read Google Business Profile locations, reviews, posts and performance; Google Ads account and campaign information; Meta ad accounts, Facebook Pages and Instagram professional-account conversations, comments or insights; and WhatsApp Business conversations and delivery events. It stores the authorized account identifiers, tokens and records needed to show those features in the customer's workspace.
When an authorized user enables an action, DentaSK may publish a post, draft or submit a reply, send a permitted message, or manage a campaign on that customer's behalf. Access remains subject to the provider's API permissions, review status, messaging windows and business-asset ownership. A connected status alone does not mean every asset or feature is available.
DentaSK's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We request access for the features described here, do not sell Google user data, and do not use it for advertising unrelated to the user-facing service. You can disconnect an integration in DentaSK and revoke access in your Google or Meta account. Disconnecting stops future synchronization but does not itself erase data already stored in DentaSK; see Data Deletion.
5. When information is shared
Information may be available to authorized users within the clinic's permitted organization, franchise or branch scope. We send the minimum information required to a provider when a customer uses that provider's feature—for example Google or Meta for account data and publishing, WhatsApp for messaging, a configured AI or voice provider for a requested AI/call workflow, a payment processor for payment processing, and email/hosting providers to operate the service. Those providers have their own terms and privacy notices.
Optional AI functionality in the current platform can involve Google Gemini, Retell or ElevenLabs depending on the feature and customer configuration. Clinics should review the feature, notices and permissions before sending patient-sensitive content to any connected AI or calling provider. We may also disclose information when legally required or to protect users and the service. We do not disclose one clinic's data to another clinic except where the customer's organization structure and permissions expressly allow it.
6. Storage, security and retention
DentaSK uses authenticated access and organization/branch permissions. The application stores integration credentials and selected sensitive patient information in encrypted form; passwords are stored as hashes rather than plain text. Production connections should use HTTPS. No online service can promise absolute security, and customers should protect their users' accounts, devices and provider permissions.
We keep data for as long as needed to provide the service, respond to a request, preserve security/accounting records, or comply with legal and healthcare record obligations. Actual periods depend on the record and the customer's obligations; we do not promise that every category is deleted immediately when an account disconnects. Backups and audit records may take longer to expire. We review verified deletion requests and explain any information that must be retained.
7. Your choices and requests
Account users can ask their administrator to correct their details or permissions. Authorized administrators can manage staff access and connected assets. For an access, correction or deletion request, email support@dentask.in. We verify the requester's authority before revealing or changing workspace data. Patients should begin with their clinic; clinic administrators can then coordinate with DentaSK.
See Data Collection for a simpler category-by-category guide, Data Safety for security and sharing details, and Data Deletion for practical steps.
8. Children, updates and contact
Clinics may hold records for minors in the course of care, under their own authority and consent duties. The public DentaSK website and demo form are intended for business representatives, not for children to submit information. We may update this policy when our services or legal requirements change; the revised date will appear above. Contact support@dentask.in with privacy questions.