Haruyak Privacy Policy

1. Core local features

Medication names, reminder times, repeat intervals, reference dates, weekdays, end dates, schedule history, dose-check dates and times, notification settings and family profiles are stored on your phone. Core features need no account. Notification preparation, rescheduling, duplicate-prevention state and the daily encouragement selection are also stored locally.

Deleting a medication reminder preserves past records and totals. Clearing app data or uninstalling deletes local records and internal restore copies.

2. Optional family record sharing

Google Firebase Authentication processes email and authentication data for sharing accounts. Sign-in alone does not share medication data. After confirming the person's consent, the selected family member's name, today's medication names, scheduled times, check status and check times, plus daily checked/scheduled counts and aggregation status for the last 7 days, are sent to Google Firebase Firestore.

Other local family profiles, full history and encrypted backups are not uploaded automatically. Account IDs, original device/family IDs, time zones, upload sequence numbers, sync times, caregiver UIDs/display names, and connection codes with expiry/usage data support access and update management.

Server medication data is updated to the latest content and is viewable only by connected caregivers. Caregivers cannot change checks on the person's behalf. Caregiver names are visible only to the sharer and that caregiver.

3. External services and security

The Firestore database region is Seoul (asia-northeast3). Authentication and app protection use Google Firebase and Play Integrity. Firebase SDKs may process technical data such as IP addresses, app/SDK/platform information, authentication tokens and app-integrity tokens to secure authentication and provide the service. Authentication and app-protection processing locations cannot be inferred solely from the Firestore database region.

Family sharing involves server-side processing. It is not end-to-end encrypted sharing like an encrypted backup. For Google's processing practices, see Firebase privacy information.

4. Stopping sharing and retention

Stopping sharing first clears the shared server content and blocks caregiver access, then cleans up related connections and invitations. The app retries after connection failures; check that the operation has completed. Identifiers recording the stopped state may remain until account deletion.

A connection code cannot create new connections after 10 minutes. Generating a new code, stopping sharing or deleting the account cleans up related invitations. Signing out or uninstalling does not delete the server account or data. Information already viewed by others cannot be retrieved.

5. Deleting a sharing account and server data

In the app, choose Family record sharing → Delete sharing account and server data. Recent sign-in may be required. Remote sharing, caregiver connections and related invitation/index data are cleaned up before the Auth account is deleted. Local records are kept.

Without the app, use the account deletion request page to request deletion by email. After verifying ownership, we remove the account and related server data and reply with the outcome. Requests are processed within 7 days of verification; any delay will be explained. External backups, local records on each phone and information already viewed by others are not subject to remote deletion.

6. Encrypted backups and restoration

You can save medications, schedules, records and settings as a password-based AES-256-GCM file. The app does not store the password, and the developer cannot recover it if lost. If you choose a cloud file provider, its policy also applies. You must delete external backups yourself.

A password-encrypted internal copy of the records immediately before restoration is kept and replaced on the next restoration. Automatic full cloud backup/device transfer is excluded; backup and restore are manual. Sharing uploads pause after restoration and resume only with renewed consent.

7. Permissions and feature scope

Notification and exact-alarm permissions are used for on-device medication reminders. Battery saving, permissions and device conditions may delay or restrict delivery. Backups access only documents you select and do not request full-storage permission.

There are no advertising or analytics SDKs, automatic family push notifications, FCM token registration, Health Connect or medical decision features. A user's check does not prove actual medication use or a health effect.

8. Website, contact and changes

The app and ITLAND website process data separately. For website access logs, cookies and email inquiries, see the ITLAND Website Privacy Policy. Do not attach passwords, ID documents, medication records or backups to inquiries or deletion requests.

If sign-in/sharing or SDK processing changes, we update the public policy, in-app guidance and Google Play Data safety information together.