Privacy Policy

Last updated: 3 August 2026

healthbook.my is a personal health records service operated from Malaysia. Because it processes personal data, including health data, in commercial transactions, Malaysia's Personal Data Protection Act 2010 (PDPA) applies. This page is the written notice the PDPA requires and describes what we actually do, not what a template says we should do.

This notice is currently published in English. Section 7(2) of the PDPA requires the notice in both the national language and English; a Bahasa Malaysia version is being prepared and will be published on this page. Until it is up, this English text is the operative description of our practices.

What we collect

Everything below is data you choose to put in. We do not buy data about you or pull it from anywhere else.

  • Account data: your name and email address, used to create and sign in to your account.
  • Profile data: the family member profiles you create, including names and relationships. For a child you are the parent or guardian of, you provide the data and give consent on the child's behalf. For another adult, only that person can consent to their own health data being processed: add an adult's data only with their agreement. The app does not yet have an invite-and-confirm flow that records that agreement, so until it does, obtaining it is your responsibility.
  • Health data you enter: vitals, symptom logs, medications, appointments, moods, meals, growth metrics, vaccinations, milestones, emergency card details, and doctor contact details.
  • Documents you upload: lab reports, prescriptions, imaging results, and other medical files.
  • Billing data: paid plans are billed through Stripe. Stripe handles your card details; we do not store card numbers.
  • Technical data: standard server logs (such as request paths, timestamps, and errors) needed to run and debug the service.

Only your name and email address are needed to have an account. Everything else is voluntary, and the consequence of not providing something is only that the related feature will not work.

How we use it

  • To run the features you use: storing, organizing, and displaying your records.
  • To run the AI features when you use them: our servers read the relevant records or documents and send them to an AI model provider for processing. This is described in detail below because it involves a transfer outside Malaysia.
  • To send you the notifications you have enabled, by email.
  • To bill you for a paid plan, through Stripe.

We do not sell your data, we do not use it for advertising, and we do not share it with third parties for their marketing.

Where your data lives and how it is protected

Your files are stored in Cloudflare R2 and your records in Cloudflare D1. Both encrypt data at rest, and the site is served over HTTPS with HSTS, so data is encrypted in transit. Cloudflare operates a global network, so stored data may reside on infrastructure outside Malaysia.

Stated plainly: your data is not sealed with a key only you hold. Our systems can read your files server-side, and they do exactly that when you use the AI features. We say this here because marketing that implies otherwise would be false.

We hold no compliance certificate and have had no external security audit of any kind, and we will not imply otherwise.

Transfers outside Malaysia

When you use an AI feature, the relevant records or documents are sent to our AI model provider, OpenRouter, whose servers run outside Malaysia. This happens only when you actively use an AI feature, and only with the data that feature needs. Symptom logs you mark as private are excluded from the AI context and from the doctor PDF export.

Stating this here is part of the written notice section 7 of the PDPA requires. The Act separately restricts transfers of personal data outside Malaysia (section 129), and for health data, which the Act treats as sensitive personal data, it requires your explicit consent to processing (section 40). The app does not yet ask for that consent through a dedicated, recorded consent step; adding one at sign-up and at first use of an AI feature is a committed follow-up, and we say so here rather than claim that reading this page counts as explicit consent, because it does not. Until that step exists, the accurate statement is this: if you use an AI feature, your data will be processed outside Malaysia. If you do not want that, do not use the AI features; the rest of the app works without them.

Who processes your data for us

  • Cloudflare: hosting, file storage (R2), and database (D1).
  • Clerk: sign-in and account authentication.
  • OpenRouter: AI model routing, only when you use AI features.
  • Stripe: payments for paid plans.
  • Resend: delivery of notification emails.
  • Google Analytics: used on the public marketing pages only. The analytics script is not loaded on the signed-in app pages where your health data appears.

How long we keep it

Your data is kept for as long as your account exists. You can delete individual records inside the app at any time. There is no self-service account deletion yet: to delete your account and all data in it, email us at the address below and we will do it manually and confirm when it is done. We do not yet have an automatic deletion policy for inactive accounts; if that changes, this notice will say so first.

Your rights under the PDPA

The PDPA gives you the right to access the personal data we hold about you, the right to correct it, the right to withdraw consent to its processing, and the right to prevent processing for direct marketing (which we do not do in the first place).

To exercise any of these rights, email omarshabab55@gmail.com with the subject line "PDPA request". That is the operator's monitored mailbox; healthbook.my does not yet receive mail on its own domain, so we publish the address that actually works rather than one that does not. We will respond to access requests within 21 days, as regulation 6 of the Personal Data Protection Regulations 2013 requires.

Changes to this notice

If our practices change, we will update this page and the date at the top before the change takes effect.

See also our Terms of Service.