Effective from June 12, 2026 · Last updated October 25, 2026
DaktariSheba is a product of KiyanSolutions UG, a company registered in Germany. This policy applies to all users of our platform: patients, doctors, and ambulance service providers. It explains what data we collect when you use our platform, why we collect it, and how we keep it safe.
We do not sell, rent, trade, or otherwise monetise your personal or health data. We do not use health data for advertising or behavioural profiling for marketing purposes.
Data Controller: KiyanSolutions UG, operator of DaktariSheba. Where required by applicable law, we will designate a Data Protection Officer or EU Representative and publish the contact details accordingly. Until then, all privacy enquiries should be sent to [email protected] (Subject: Privacy Request).
Because DaktariSheba is operated by a German company, we process your data in line with the EU General Data Protection Regulation (GDPR) and applicable Bangladesh laws. Our legal bases are:
You can withdraw consent at any time from the app settings or by emailing [email protected]. Withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal.
AI features on DaktariSheba are optional and require your explicit consent before activation. AI systems are probabilistic, may be trained on historical patterns, and may produce inaccurate, incomplete, misleading, or outdated outputs — including outputs that appear confident. AI outputs are informational and educational only and are not a medical diagnosis, prescription, or substitute for professional medical advice.
Several features on DaktariSheba use third-party AI services to process your data. Specifically:
When you use these features:
You may decline or withdraw consent for AI feature usage at any time from Settings → Privacy → AI. Withdrawing consent does not affect the lawfulness of processing that occurred before withdrawal and does not affect your ability to book appointments, access records, or use other platform features.
AI infrastructure region. Backend AI orchestration runs on our infrastructure hosted on Amazon Web Services in Singapore (Asia Pacific). When OpenAI or Google Gemini is invoked, the relevant inputs may be processed in the providers' US (or other) regions under Standard Contractual Clauses. Operational logs from AI features (used for debugging and abuse prevention) are retained for up to 30 days, after which they are deleted or anonymised, unless longer retention is required by law.
DaktariSheba is operated by KiyanSolutions UG in Germany. Our primary infrastructure is hosted on Amazon Web Services in Singapore (Asia Pacific), and several of our service providers are also located outside the European Economic Area (EEA). This means your personal data, including health data, is transferred to and stored outside the EEA — in particular:
For transfers outside the EEA, we rely on the Standard Contractual Clauses (SCCs) approved by the European Commission and, where available, supplementary technical and organisational measures such as encryption in transit and at rest. You can request a copy of the safeguards used for a specific transfer by contacting us at [email protected].
We engage carefully selected service providers (“Subprocessors”) who process personal data on our behalf under written data processing agreements that require confidentiality, security safeguards, and compliance with applicable data protection laws. Subprocessors act solely under our instructions and may not use personal data for their own independent purposes.
| Subprocessor | Purpose | Location |
|---|---|---|
| OpenAI, L.L.C. | AI Health Chat (GPT), voice transcription (Whisper) | USA |
| Google LLC | Gemini OCR for documents, Google Maps for nearby services | USA / Global |
| Agora Lab, Inc. | Real-time audio/video infrastructure for live doctor video consultations (calls are not recorded) | USA / Global |
| Amazon Web Services (AWS) | Application hosting, database, file storage, and video transcoding (AWS Elemental MediaConvert) for clinical video — all in the same Singapore region | Singapore (Asia Pacific) |
| Apple Push Notification service (APNs) | Push notification delivery on iOS | USA / Global |
| Firebase Cloud Messaging (FCM) | Push notification delivery on Android | USA / Global |
| Expo / EAS (Expo Application Services) | Over-the-air updates, build pipeline, crash symbolication | USA |
| SMS gateway providers | OTP and transactional SMS delivery | Bangladesh / Global |
| Email service provider | Transactional email delivery (verification, receipts, alerts) | EU / USA |
| Payment gateway partners | Processing payments and refunds | Bangladesh / Global |
| Meta Platforms, Inc. | Measuring whether an advertisement led to an app install (Android only). Receives a device advertising ID and app install / account-verification events. Receives no health data. | USA / Global |
| Sentry (Functional Software, Inc.) | Crash and error diagnostics for the mobile app | EU (Germany) |
This list may be updated as our infrastructure evolves. We will reflect any material change here and, where required by law, notify affected users.
Our mobile app is built with Expo and React Native. We keep the SDK footprint deliberately small, and no SDK in the app receives your health data. The third-party components used in the mobile app are:
What the Meta SDK never receives: your name, email address, phone number, patient ID, or any health information whatsoever — no symptoms, conditions, medicines, prescriptions, documents, doctors, or appointments. The account-verification event is a bare signal that somebody completed sign-up; it carries no description of who or of anything about them. We do not use Meta's advanced matching, and we do not build advertising audiences from health-related activity.
We do not use Firebase Analytics, Google Analytics for Firebase, Crashlytics, Mixpanel, Amplitude, AppsFlyer, or any other advertising or behavioural-tracking SDK, and the app displays no advertisements. If we add any of these in the future, we will update this policy and, where required, ask for your consent before they are enabled.
Opting out of advertising measurement: resetting or deleting your advertising ID in Android Settings → Privacy → Ads stops Meta from linking app activity to your device. Everything in DaktariSheba continues to work exactly as before.
On the web, we use minimal first-party analytics for page-view counts and error reporting. See our Cookie Policy for details.
To understand which parts of DaktariSheba people actually find useful, we record a small number of first-party usage events. This is our own measurement, stored in our own database: it is not an analytics SDK, it is never shared with an advertising network or a data broker, and it is never sold.
What we record. Which feature you opened (for example the ambulance service, doctor search, or the video consultation section), whether a search returned anything, which listing or profile card you opened, and when you tapped call, WhatsApp, or directions. Each event carries a coarse distance band rather than a distance — “under 2 km”, not your position — and, where relevant, the identifier of the provider you looked at and how urgent a request was marked.
Video consultations are deliberately narrower. We record that you opened the video consultation section, whether you still had a free consultation left that week, that a list of doctors was shown to you and how many were on it, and that you opened one of them to look at their availability. We never record which doctor — a doctor’s speciality would say something about your health — and we never record what you wrote as the reason for your visit. Anything about a consultation you actually book stays in your medical record, where only you and the people treating you can see it.
What we never record. No symptoms, conditions, diagnoses, medicines, prescriptions, documents, test results, or appointment details. No names, phone numbers, or addresses. No pick-up or destination location, no GPS coordinates, and no free text you have typed. The kind of emergency you select when booking an ambulance is deliberately excluded, and so is the identity of any doctor you consult — a doctor’s speciality would say something about your health, so it is never attached to you here. Only a fixed list of these events and their permitted fields can be recorded at all, so nothing else can be captured by accident.
Who it is linked to. If you are signed in, the event is linked to your account so we can count people rather than taps. If you are browsing without signing in — the ambulance directory can be viewed without an account — it is linked only to a random identifier generated on your device. That identifier is not your advertising ID and is not a device fingerprint.
How long we keep it. Individual events are deleted after 90 days. We keep only day-by-day totals after that, which cannot be traced back to a person.
Which days you use DaktariSheba. When you are signed in, we note each day (Bangladesh time) on which the app or website contacted our servers for your account, the time of the first such contact that day, and your account type, such as patient or doctor. We record nothing about what you did, which feature you used, your device, or where you were. This is used only to count how many people use the platform each day, week and month: our staff see those totals, never a list of who was active. These records are deleted after 400 days, and when your account is deleted.
The AI health chat and document scanning are free up to a limit that is the same for everyone: an amount of AI chat each day, and a number of scanned pages for life and then each month. Limits keep these features free, and stop automated misuse that would otherwise make them unaffordable for everyone.
What we count. For AI chat, how much AI processing your requests used each day, taken from our own cost records. For scanning, the date and number of pages of each scan, and whether our scanner could read it: a scan we failed to read is not counted (up to a monthly limit on such refunds), while a photo the scanner judged not to be a medical document is counted. We do not use what you wrote, or what a document says, to apply a limit.
Tied to you, not to an account. So that a free limit cannot be reset by deleting an account and signing up again, we keep a one-way, keyed fingerprint of the verified phone number your account had when we first applied a limit to it (or of its verified email address, if it had no verified phone; an account with neither is counted on its own). An account keeps that fingerprint even if you later change or add a phone number or email. Several accounts with the same fingerprint share one limit. With the fingerprint we keep when you first used AI chat, the internal account numbers that share it, and for each free scan its date, its number of pages and whether it counted. The fingerprint cannot be turned back into your number or address, it is useless without a secret key held only on our servers, it is never shared, and it is used for nothing except applying free limits.
How long we keep it. These records are kept after your account is deleted, for as long as we offer free limits, on the basis of our legitimate interest in preventing misuse (Art. 6(1)(f) GDPR). They contain no name, no contact details and no health information; they do contain the internal account number of the deleted account, which identifies no one on its own. You can object by writing to [email protected], and we will remove them.
Two limits are built into the app rather than left to your settings. We never ask for background location — the permission is not in the app at all, so nothing reads your position while the app is closed. And we never ask to read your photo gallery: the app can write a file you asked it to save into your gallery, but it cannot browse what is already there. Choosing an existing photo to upload goes through your device’s own picker, which hands us the single file you picked and nothing else.
You can control permissions any time from your device settings. If a permission is denied, some related features may not work.
When you join a video consultation with a doctor, your live audio and video are transmitted in real time through our real-time communication provider, Agora Lab, Inc., solely to connect you with the doctor for that session. The stream is encrypted in transit.
These live consultations are not recorded or stored by DaktariSheba — neither the audio nor the video is captured or retained on our servers. Anything the doctor separately documents from the consultation (such as a prescription, notes, or referral) is saved to your health records as described elsewhere in this policy. We do not permit recording of consultations within the app, and you should not record a consultation without the consent of all participants.
This is different from a doctor deliberately photographing or filming a clinical finding, which is described immediately below. A consultation is never captured; a clinical photograph or clip is one the doctor chooses to take and keep as part of your record.
A doctor treating you can photograph or film a clinical finding — a wound, a rash, a range of movement, a step of an operation — and keep it in their consultation notes or in your surgical case file. This is ordinary medical record-keeping, and the recording becomes part of the clinical record.
If a doctor uses DaktariSheba to plan and run an operation on you, the case file holds considerably more than an ordinary consultation: the procedure and the side of the body it is on, your pre-operative assessment, anaesthesia and who administered it, the surgical safety checklist, the operative note, any specimen sent for testing, any implant left in place, the recovery notes and the follow-ups.
Consent forms. When a consent form is prepared and signed, we store the text you were shown, the language it was in, who signed, their relationship to you, their phone number, and the name and phone number of any witness. If the signed paper is scanned, the scan is stored with it. A witness who signs is not a DaktariSheba user and did not give us their details directly — they gave them to the hospital or clinic, which recorded them here. A witness can ask us to remove their details by writing to [email protected], and we will do so unless the consent record has to stay intact by law.
A surgical case is a medical record. It is kept for as long as medical record-keeping rules require, and deleting your account does not erase the clinical content of an operation that took place: the case is de-identified instead. See Account Deletion for exactly what that means.
A doctor can give a receptionist, nurse or chamber assistant their own login to help run the practice — booking your appointment, preparing a case, ticking off a checklist item before an operation. An assistant is not a separate account holder on the platform: they act for one doctor, they see only that doctor’s work, and the doctor is responsible for what they do.
Every action an assistant takes is recorded against that assistant by name, so there is an accurate history of who did what. A doctor can deactivate an assistant at any time, and access stops immediately.
A doctor can write a prescription or book a walk-in appointment for somebody who has never used DaktariSheba. When that happens we hold a record for that person even though they never signed up: their name, and whichever of phone number, email, age or date of birth, gender, address, district, blood group, occupation and marital status the doctor entered, together with the visits and prescriptions that follow.
The doctor or clinic that entered those details is the one that decided to, and our Terms require them to have the patient’s agreement first. The record is visible only to that doctor and their authorised assistants. If you learn that a record exists about you and you do not want it to, or you want to see it or correct it, write to [email protected] and we will act on it — you do not need an account to exercise that right. If you later register with the same phone number, the doctor can link the two so your history follows you.
Booking an ambulance means exchanging locations with a stranger, so it is worth being precise about what moves and when.
We never sell your personal or health data to advertisers or marketing companies, and we never share health data for advertising. Measuring whether an advertisement led to an install is the only advertising-related sharing we do, and it involves no information about you or your health.
If a relative also uses DaktariSheba, the two accounts can be connected so that one of you can see the other's health information — for example, a son abroad helping his mother manage her care at home. This is entirely optional, and nothing is shared until you agree to it.
How it works:
Two limits worth knowing. If you allow a relative to book appointments for you, the appointment belongs to you — it appears in your account, the clinic contacts you, and any prescription is filed under your name. And connecting an account never gives anyone access to your video consultations: only you can join your own calls.
We record when a connection is created, changed or ended, and when connected information is accessed, so that there is an accurate history of who could see what.
Your data is encrypted both in transit and at rest. We use access controls, security audits, and monitoring to prevent unauthorized access. That said, no online system is perfectly secure, so we do our best but cannot guarantee absolute protection.
On your own device. The app keeps a working copy of some of your records on the phone so it stays usable on a poor connection — documents you opened, images and video you viewed, prescriptions you looked at. That copy is capped in size and the oldest of it is discarded as it fills. Signing out erases it, along with your session, so a shared or handed-on phone does not keep your health data behind a logged-out screen.
We keep your data while your account is active and as needed to meet legal, medical, accounting, and anti-fraud obligations under applicable Bangladesh laws and regulations. You can request deletion from within the app (Account Deletion) or by contacting us at [email protected]. Once a deletion request is confirmed, we delete or de-identify data that we are not legally required to retain.
Under GDPR and applicable Bangladesh laws, you can:
You can permanently delete your DaktariSheba account and all associated data in two ways:
Visit our dedicated Account Deletion page for instructions on how to request deletion by email. You can also email [email protected] from your registered email address or phone number.
What gets deleted (patients): Your profile, personal details, health records, prescriptions, scanned documents, appointment history, family connections, and the documents you shared with a doctor are permanently deleted.
One exception, and we would rather state it than bury it: an operation that actually happened. If a surgeon documented a surgical case for you, that case is de-identified rather than erased — the link to your account is cut and the record is marked as belonging to a deleted patient, but the clinical content, including the operative note, the consent record and any clinical photograph or video, remains in the surgeon’s records. Medico-legal rules require an operating surgeon to be able to account for what they did, and that obligation does not end because a patient closed an app account. The record can no longer be traced back to you through DaktariSheba.
A record a doctor created for you as a walk-in patient, when you had no account of your own, is not attached to an account and so is not covered by account deletion. Ask us and we will remove it — see If You Do Not Have an Account.
Doctor accounts work differently. A doctor's prescriptions, consultation notes and case replies are part of their patients' medical records. Erasing them would destroy the health history of people who never asked for anything to be deleted, and who may need it for future care. So when a doctor deletes their account we anonymise it instead: the login is permanently disabled, the public profile is removed from search, upcoming appointments are cancelled and the patients notified, and every personal detail is scrubbed. What remains is the clinical content itself, no longer attached to an identifiable person.
What may be retained: anonymised, aggregated data that cannot identify you, kept for platform analytics; financial and transaction records, where Bangladesh law requires it (typically up to 7 years); the minimum records needed for healthcare regulation, audit, fraud prevention, or a legal hold; and a one-way fingerprint of your verified phone number or email with your free-usage counts, so free limits cannot be reset by signing up again (see Free Usage Limits). Retained records are kept only as long as legally required or stated here, and are not used for any other purpose.
Retention period: Deletion is processed within 30 days, and you will receive a confirmation once it is complete.
The Services are intended for users aged 18 and above. We do not knowingly allow children under 18 to create their own DaktariSheba account or to provide personal data directly to us.
Health records for children under 18 may be managed by a parent or legal guardian through our Family Health Hub, using the guardian's own DaktariSheba account. In that case the guardian is responsible for the lawful basis to upload and manage the child's data.
If we become aware that an account has been created by a person under 18 without the required consent, we may suspend the account and delete associated data in accordance with applicable law.
If we make meaningful changes, we will let you know through the platform or by email. Continued use after an update means you accept the revised policy.
Data Controller: KiyanSolutions UG (Germany), operator of DaktariSheba.
For anything privacy-related:
Email: [email protected]
Phone: +880 1895-603456
Address: 56 Inner Circular (VIP) Road, Eastern Trade Center (3rd Floor), Room 07-10, Nayapaltan, Dhaka-1000