Last updated: October 2026
1Who we are and who decides about each type of data
Dr. BookPay is a product of LEARN & EDUCATION APOIO A EDUCACAO LTDA, CNPJ 43.946.548/0001-31, Av. Paulista, 1776, São Paulo/SP, CEP 01310-200 (“we”). Contact for personal data matters: suporte@drbookpay.app.
Dr. BookPay is used by doctors and practices to serve their patients. That is why there are two types of data, with different roles:
- Subscriber data (the doctor, the practice, and the staff): we decide how this data is used (controllers).
- Data about the patients of the practice: the doctor or the practice decides (controller). We process this data on their behalf and under their instructions (processors).
If you are a patient of a practice that uses Dr. BookPay, requests about your data go first to the practice itself. If you write to us, we forward your request to the practice and help with whatever is needed.
2What Dr. BookPay does
Dr. BookPay is the practice’s scheduling system. It brings together the booking page, RaVir IA (automated service with artificial intelligence on the practice’s WhatsApp), reminders and messages to patients, and billing and payment collection. Each part is turned on whenever the practice wants. This policy describes what each part processes when it is turned on.
Dr. BookPay is not an electronic medical record. It does not store diagnoses, tests, prescriptions, or treatment plans: these stay in the doctor’s medical record, outside Dr. BookPay.
3Minimum age
Dr. BookPay accounts are for doctors and practices. You must be 18 or older to create one.
4What data we process
From subscribers (doctor, practice, and staff)
- Account: Name, email, photo, and identifier from Google or Apple, or the name and email you enter. Your password stays with the authentication service (Google Firebase); we can’t see it.
- Practice (when you register it): name, CPF or CNPJ, address, office hours, appointment types, prices, and staff. Your CRM number, if you provide it.
- Payouts (if you enable this): the information the payment processor requires to register the payee, such as the account holder’s banking and identity details.
- Practice WhatsApp (if you connect it): the number and the messages exchanged through it with your patients.
- Technical logs: IP address, device model, operating system, app version, and access date and time. Used for security and operation.
From the practice’s patients (processed on the practice’s behalf)
- Contact: Name, phone or WhatsApp number, and email.
- Appointments: appointment type, doctor, date and time, amount, health insurance plan or private-pay, history, reschedulings, and cancellations.
- Conversations with RaVir IA or with the practice through the connected WhatsApp.
- Payments: amount, method, and status. Card details go directly to the payment processor and are not kept by Dr. BookPay.
- Notes that the practice writes to provide better care, such as “prefers mornings” or “comes with a companion.” Notes are not the place for clinical information: diagnosis, tests, and treatment plan belong in the doctor’s medical record.
Sensitive data. Booking an appointment with a doctor can reveal something about the health of the person booking, such as the specialty or the appointment type. That is why we treat patient data as sensitive personal data (LGPD, art. 5, II), with the same care throughout the system: access only for those the practice authorizes, and never used for advertising or ad measurement.
5How we use data
- Providing the service: accounts, scheduling, reminders, RaVir IA, billing, and payment collection.
- Account notices: confirm your email, change your password, and notify you about service operation and your subscription.
- Contacting you, the doctor or practice, about Dr. BookPay and other Learn & Education products: news, tips, and offers, by email, notification, or WhatsApp. You can turn off these messages anytime.
- Improving the product, preferably using aggregated, anonymized, or pseudonymized data.
- Security and legal compliance: preventing fraud and abuse, meeting legal obligations, and exercising rights in legal proceedings.
A practice’s patient data serves only what that practice requests. We do not offer anything of our own to these patients, and we do not take their data to another practice.
6Legal bases (LGPD)
| Purpose | Legal basis (Law 13.709/18) |
|---|---|
| Account, scheduling, RaVir IA, reminders, billing | Performance of a contract, art. 7, V |
| Payment records and tax obligations | Legal obligation, art. 7, II |
| Security, fraud prevention, product improvement | Legitimate interest, art. 7, IX |
| Defense in legal proceedings | Regular exercise of rights, art. 7, VI |
| Messages about Dr. BookPay to the doctor or practice | Legitimate interest or consent, which can be withdrawn at any time |
| Data about the practice’s patients | The legal basis is the practice’s, since it decides about this data: as a rule, health protection in a procedure performed by a health professional (art. 11, II, "f") and performance of the contract with the patient (scheduling, providing care, billing) |
7RaVir IA and artificial intelligence
RaVir IA runs on Google’s artificial intelligence models (Gemini). When a patient chats with it, or when the practice asks Dr. BookPay for something, the content is processed on Google’s servers. This happens on our behalf and under our instructions, only to respond, offer time slots, and do what was requested. Access keys stay on our servers, never on the device.
RaVir IA does not give health advice. It books, confirms, reschedules, sends receipts, and, if the practice has turned it on, collects payment. It passes questions about symptoms, medication, or tests on to the doctor and lets the patient know that the doctor will reply.
We do not use conversations to train artificial intelligence models. Neither does Google: we use the paid service, whose terms state that Google does not use prompts or responses to improve its products. Artificial intelligence can make mistakes. That is why the practice sees the conversations and can take over whenever it wants.
8Who we share data with
Only with service providers working on our behalf, and only what’s necessary:
| Provider | Purpose |
|---|---|
| Google (Firebase, Google Cloud, and Gemini) | Signing in, database, servers, storage, notifications, and RaVir IA’s artificial intelligence. Database in São Paulo |
| Google Calendar and Google Maps (optional features) | Showing and mirroring time slots in the Google Calendar of whoever connects it, and finding the practice’s address |
| Apple and Google | Sign in with Apple or Google, and app stores |
| Messaging and email providers | Reminders, account notices, and the messages the practice sends, including through the WhatsApp it connects |
| Payment processor | Patient payments and payment collection for the practice, when turned on |
| Network and security providers | Website addresses, network, and security |
We require all providers by contract to provide protection equal to or equivalent to this policy and to use data only under our instructions. They may not use data for their own purposes. We also share data when required by law or a competent authority, and in corporate transactions (mergers, acquisitions), with notice to you. We don’t sell data.
9International transfers
Dr. BookPay’s database is in Brazil (São Paulo). Some providers process data outside Brazil, mainly in the United States, under art. 33 of the LGPD, with contractual safeguards and recognized security standards.
10Analytics and advertising
In the app, we may use analytics and ad measurement tools (such as Google Analytics for Firebase and the Meta SDK) to understand product usage and learn which ads bring in new practices. These events indicate, for example, that an account was created or that a feature was used for the first time. We do not send names, emails, phone numbers, conversations, appointments, or patient data. No event carries specialty, appointment type, or any health data. On iPhone, the advertising identifier is used only if you allow it in the system prompt.
On the website, marketing pages may use Meta Pixel and Google Analytics to measure visits and ads. They may also use a session analytics tool that records how the page is used (clicks, scrolling, time spent). These tools use cookies and technical browser data and are also subject to those services’ policies. The app, the practices’ booking pages, sign-in pages, and legal pages do not receive this code.
You control cookies through your browser settings. We do not show ads in the app, and we do not sell data.
11Data received from Google
When you sign in with Google, we receive only your name, email, photo, and identifier, and use this data only to create and maintain your account. Our use and transfer of information received from Google APIs follow the Google API Services User Data Policy, including its Limited Use requirements. This means we do not use this data for advertising, do not sell it, and do not use it to train artificial intelligence models.
12Your rights
The LGPD (art. 18) grants rights to confirmation and access, correction, anonymization, blocking or deletion of unnecessary data, portability, information about sharing, and withdrawal of consent. To exercise these rights, email suporte@drbookpay.app. Some requests may require identity verification. Patients of a practice should contact the practice first (section 1).
13Delete your account and data
- In the app: Your account › Delete account.
- By email: suporte@drbookpay.app.
When you delete your account, we immediately remove the account, the practice’s data, and the patient data it stored in Dr. BookPay. If you signed in with Apple, we also revoke Dr. BookPay’s authorization in your Apple account. We retain only what the law requires: payment and tax records, and access logs required by the Brazilian Civil Rights Framework for the Internet (Law 12.965/2014, art. 15), for 6 months.
14Security
We use encryption in transit, access controls, and database security rules. No system is infallible. If a significant incident occurs, we will notify you and the ANPD, as required by law.
15Changes to this policy
If we make a significant change, we’ll notify you through the app, website, or email before it takes effect. The last updated date is always shown at the top.