Effective date: 27 August 2026
Last updated: 27 August 2026
App: Family Health Card (Android: com.ackbiz.family_health_card, iOS: com.ackbiz.family-health-card)
Provider / data controller: ACKPlus Solutions Private Limited ("we", "us", "our"), B-216 RK Iconic, Nr Sheetal Park, 150ft Ring Road, Rajkot, Gujarat, 360001
Privacy contact:contact@ackplus.com
The short version
Family Health Card is offline-first. What you enter is stored on your device in an encrypted database, and we never receive it, store it, or transmit it to our servers — we cannot see it. There are no accounts, no ads, and nothing is sold.
Three things can leave your device, and each is off until you turn it on:
- Cloud backup to your own Google Drive. The backup is encrypted on your phone before it is uploaded, with a key we never receive. Neither we nor Google can read it.
- Anonymous diagnostics (crash and usage data) sent to Google Firebase. Never includes health information.
- Anything you share yourself — a PDF summary, an emergency QR code, a backup file.
One thing can be seen without unlocking your phone, and it too is off until you turn it on: the emergency card, described in Section 6.
One thing happens without being switched on: when the app starts it asks our server whether a newer version exists. That request carries the app's package name, the platform, and the version you already have — no health information, no account, and no identifier for you or your device. Section 4 has the detail.
1. What the app handles, and where it lives
a) Your health and family data — on your device
For each family member you can enter: name, relationship, sex, date of birth, blood group, photo; allergies, medical conditions, medications and reminder schedules, vaccinations; appointments and visits; health records (photos and scans, imported PDFs, text extracted from scans, doctor / clinic / reference details); lab values and their reference ranges; emergency contacts; organ-donor preference; and optional insurance details.
This is saved in a database on your device encrypted with AES-256. It is never sent to us. We cannot see it and have no access to it.
b) Emergency contacts are somebody else's information
You may list up to three people to contact in an emergency for each family member — their name, phone number, and relationship to that person. Those people are not users of this app and have not agreed to be listed. Please add only people who would expect to be contacted on that person's behalf. Their details are stored on your device with everything else, and are shown on the emergency card described in Section 6.
c) On-device scanning (OCR)
When you scan a document, text recognition runs locally on your device — Google ML Kit for Latin and Devanagari scripts, and Tesseract for Gujarati. Neither the image nor the extracted text is uploaded to anyone.
2. Cloud backup — optional, and encrypted before it leaves
Cloud backup is off until you turn it on. If you turn it on:
- You sign in with Google, and the app asks for one narrow permission: drive.appdata. That gives it access to a private, app-specific folder in your own Google Drive. It cannot see, read, or touch any other file in your Drive.
- Every backup is encrypted on your phone before it is uploaded (AES-256-GCM), using a key that is generated on your device and never sent anywhere. The key is protected by a passphrase you choose, plus a recovery code the app shows you once.
- We never receive the backup or the key.Google receives the encrypted file but cannot read it, because the encryption happens before upload and Google never has the key.
- If you lose both the passphrase and the recovery code, nobody can recover the backup — including us. This is a consequence of the design, not an oversight.
- You can turn it off, and delete the backups, from inside the app at any time.
The backup contains your health records, including attachments. So while your health data is not stored on our servers or anyone else's in readable form, enabling this feature does mean an encrypted copy of it leaves your phone and is held in your Google account. That is a change you are choosing to make, and you can undo it.
You can also export an encrypted backup file (.fhvbak) yourself and save it wherever you like. We never receive those either.
3. Optional diagnostics
If you enable Settings → "Share anonymous diagnostics" (off by default), the app sends limited technical data to Google Firebase (Crashlytics and Analytics), acting as our processor:
- Crash reports: error and stack traces, device model, OS version, app version.
- Usage analytics: screen views, basic interaction and session events, approximate region, and a non-identifying app-instance identifier.
Diagnostics never include health information and are used only to find crashes and improve the app. You can turn them off at any time in Settings. They are never collected in development builds.
4. Checking for a newer version
When the app starts it makes one request to a server we run
(apps.ackbiz.com) to ask whether a newer version has been released. It sends
only:
- the app's package name (for example com.ackbiz.family_health_card),
- the platform (Android or iOS),
- the version you currently have installed.
It sends no health information, no account, and no identifier for you or
your device. As with any request over the internet, our server sees the IP
address it came from; we use it only to serve the response and do not build a
profile from it.
If the request fails, times out, or you are offline, the app carries on
normally and says nothing. If a newer version exists the app shows you a
dialog with the release notes; you can postpone an ordinary update, and you
can check manually at any time from Settings → "Check for updates".
This is the only request the app makes to a server we operate.
5. What we do not do
- No user accounts with us, and no server of ours holds your health data.
- No advertising, no ad trackers, no profiling.
- No selling, renting, or sharing of your data.
- No third-party data sharing beyond the optional diagnostics in Section 3 and the encrypted cloud backup in Section 2, both of which you control.
6. The emergency card, and what it shows without unlocking
The app can show an emergency card to somebody who cannot unlock your phone. This exists because the person who needs it is a paramedic or a bystander helping someone who cannot answer questions.
It is off until you turn it on, and turning it on means naming one specific person whose card may be shown (Settings → "Emergency card on lock screen"). When it is on, anyone holding the phone can, without a passcode:
- see that person's blood group, allergies, medical conditions, current medicines, organ-donor preference and primary doctor;
- see the names and relationships of the emergency contacts you listed for them, and place a call to those contacts.
To limit what a lost or stolen phone gives away, the emergency card does not display contacts' phone numbers — it can dial them, but the digits are not shown. Inside the app, past your device lock, the numbers are visible normally.
The emergency card shows only that one person, and shows only the summary above. Your records, scans, documents, history and settings remain locked and are not reachable from it.
You can turn this off at any time, and it is off by default.
The emergency QR code works the same way in spirit: it is generated on your device, encodes only emergency-relevant fields (never your records), and is only shown when you choose to show it.
7. Device permissions
The app asks for permissions only when a feature needs them:
- Camera — to scan records and take member photos.
- Photos / files — to attach images, import PDFs, and save exports.
- Notifications — to remind you about medicines and appointments.
- Biometrics / passcode — for the optional app lock. Handled by your operating system; we never receive biometric data.
- Google sign-in and drive.appdata — only if you enable cloud backup (Section 2).
8. How your data is protected
- The on-device database is encrypted with AES-256 (SQLite3MultipleCiphers). The key is generated on your device, kept in the OS secure store (iOS Keychain / Android Keystore), and never hardcoded or transmitted.
- Cloud backups and exported backup files are encrypted with AES-256-GCM before they leave the device.
- An optional app lock (biometric or passcode) can gate the app.
- On Android, the app marks its screens so they do not appear in screenshots, screen recordings, or the recent-apps preview.
No method of storage is completely secure. Because your health data stays on your device unless you enable backup, the principal risk is physical access to your unlocked phone — which the app lock reduces, and which the emergency card in Section 6 deliberately makes a bounded exception to.
9. Sharing — always your decision
- PDF summaries and exports are produced on your device and leave it only when you send them.
- The emergency QR and emergency card are described in Section 6.
- Encrypted backups, local or in your Drive, are described in Section 2.
The only data shared with a third party without you sending it yourself is the optional diagnostics in Section 3, and only while you have them enabled. The version check in Section 4 reaches a server of ours but carries nothing personal.
10. Your choices and rights
In the app, wherever you are:
- Access and portability — export an encrypted backup at any time.
- Deletion — delete individual records or a whole family member; erase all data from Settings; or uninstall the app, which removes all on-device data. Backups you made are yours to delete, including from Drive, from inside the app.
- Turn diagnostics off — Settings → "Share anonymous diagnostics".
- Turn cloud backup off — Settings → "Cloud backup", including deleting what is stored.
- Turn the emergency card off — Settings → "Emergency card on lock screen".
Because your health data lives on your device and we never hold it, we cannot access, retrieve, correct, or delete it for you. You control it directly. This is a deliberate design choice, and it is the reason we cannot help if you lose your device and your backup credentials.
Region-specific rights. Depending on where you live you may have additional rights — for example under the EU/UK GDPR, India's Digital Personal Data Protection Act 2023, or the California CCPA/CPRA — including access, correction, deletion, portability, and the right to complain to your data protection authority. In practice these concern the limited diagnostics data, since that is the only personal data we ever receive. To make a request, write to contact@ackplus.com. We do not "sell" or "share" personal information as those terms are defined under California law.
11. Children's data
The app is intended for an adult to manage their family's health records, which may include information about children. It is not directed to children, and children should not use it independently.
By adding a minor's information you confirm you are their parent or guardian (or otherwise authorised) and consent to it being stored on your device. If you enable cloud backup, an encrypted copy of that child's records is placed in your own Google Drive. If you enable the emergency card for a child, their emergency summary can be read by anyone holding that phone.
Because health data stays on the device and diagnostics are off by default, we do not knowingly collect personal information from children. If you believe a child has enabled diagnostics, turn it off in Settings and contact us.
We aim to align with COPPA (US, under 13), the GDPR's rules on children (under 16 or 13 depending on member state), and India's DPDP Act (under 18).
12. Data retention
- Your health data: kept on your device until you delete it or uninstall the app. We hold none of it, so we have nothing to retain or delete.
- Cloud backups: kept in your Google Drive until you or the app's retention setting removes them. You can delete them from inside the app or from your Drive.
- Diagnostics, if enabled: retained by Google/Firebase according to their retention settings and policies. We keep no separate copy.
13. International transfers
Your health data does not leave your device unless you enable cloud backup.
- If you enable cloud backup, the encrypted archive is stored in your own Google Drive account and may be held on Google's servers outside your country. It is encrypted before it leaves your phone with a key Google does not have, so what crosses a border is ciphertext we and Google are both unable to read.
- If you enable diagnostics, that limited technical data is processed by Google and may be processed outside your country, under Google's safeguards.
14. Third-party services
- Google Drive (via Google Sign-In, drive.appdata scope) — optional cloud backup of an encrypted archive to your own account. See Google's Privacy Policy.
- Google Firebase (Crashlytics and Analytics) — optional diagnostics only. See Firebase Privacy & Security and Google's Privacy Policy.
- Google ML Kit — on-device text recognition. Nothing is uploaded.
- Tesseract OCR — on-device text recognition for Gujarati. Nothing is uploaded.
- Our own version-check endpoint (apps.ackbiz.com) — see Section 4. No health data, no account, no device identifier.
15. Not a medical device, and not medical advice
Family Health Card is a personal record-keeping tool. It is not a medical device and does not provide medical advice, diagnosis, or treatment. It stores and displays what you put into it; it does not interpret results and does not tell you what a value means. Always check scanned or extracted text against the original document, and consult a qualified clinician before making any medical decision.
16. Changes to this policy
If we change how the app handles data, we will update this policy and its "Last updated" date, and for material changes you will be told inside the app. Continuing to use the app after an update means you accept the revised policy.
17. Contact
Questions or privacy requests: contact@ackplus.com
ACKPlus Solutions Private Limited
B-216 RK Iconic, Nr Sheetal Park, 150ft Ring Road, Rajkot, Gujarat, 360001