Privacy Policy

Who is responsible

KeepWell is operated by an individual, not a company. The operator is responsible for determining how information is used to provide the service. Confirmed identification and contact details belong in the contact section below.

Information processed

Information you enter may include names of people or entities, vehicle details and registration numbers, important dates and deadlines, titles, notes, reference numbers, reminder preferences, and historical or archived records.

The application also processes internal account and authentication identifiers, device installation identifiers, push notification tokens, language preferences, timezone information, and operational records needed to process reminders. The scope of any separate website processing must be reviewed before this policy is finalized.

Why information is processed

Information is used to authenticate accounts, organize and synchronize records, calculate and process reminders, route notifications, and carry out account deletion. Language and timezone information help present content and process reminders appropriately.

The applicable legal basis for each purpose has not yet been finalized. This draft does not treat all processing as consent-based or assert independently verified legal compliance.

Authentication providers

KeepWell uses Firebase Authentication with Google Sign-In and Sign in with Apple on iOS. Authentication-related identifiers connect the provider sign-in to the KeepWell account. Apple and Google also process information under their own terms and privacy notices.

The application does not establish email/password authentication. Access depends on the provider originally used; matching an email address does not by itself establish account ownership.

Cloud storage and service providers

Firebase Cloud Firestore stores synchronized application records, and Firebase Cloud Functions performs backend operations, including reminder processing and asynchronous cleanup. Information is not restricted to storage on your device.

Expo Push Notifications is used for notification delivery. Platform delivery may also involve Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). The final provider disclosures and allocation of responsibilities require owner review.

Push notifications

Push tokens and installation identifiers help route reminders to a device. Reminder processing also uses relevant account, item, date, preference, and timezone records.

Notification text is generic, but routing metadata can include household and item identifiers. Generic text does not make all notification data anonymous. Delivery is best-effort, and exact delivery time is not guaranteed.

Information about other people

You may enter information relating to family members or other people. Consider whether you have an appropriate basis to do so and inform them where required. Enter only information needed to organize the date; avoid unnecessary sensitive details in names, titles, notes, or reference fields.

Retention and archived records

Archived and historical records may remain associated with the account. Archiving an item is not permanent deletion. Retention criteria for account data, reminder operations, backups, logs, and any legal preservation needs must be confirmed; this draft promises no fixed retention period.

Account deletion

Request deletion in the application’s Settings. Deletion requires confirmation and fresh authentication with the sign-in provider. Once deletion is accepted, access is blocked and backend cleanup runs asynchronously.

Acceptance does not mean that every record, backup, or log is immediately erased. Consult the Support page for the account deletion steps; the final retention and deletion disclosures must explain any remaining handling.

Your privacy rights

Depending on applicable law, you may have rights to access, correct, delete, restrict or object to processing, obtain portable data, or withdraw consent where consent is the basis. These rights can have conditions and exceptions. You may also have a right to complain to a competent supervisory authority.

Use the configured privacy contact for requests once available. Identity verification may be needed to protect account information. No self-service export feature was found in the audited application; that does not remove any applicable legal right to request data.

International processing

KeepWell is intended for global distribution and uses cloud and notification providers. Information may be processed outside your country. Specific regions, transfer mechanisms, safeguards, and any local requirements must be confirmed rather than assumed.

Security

Authentication and cloud services form part of the application architecture, but no system can be described as risk-free. Protect your Apple or Google account and your device. Do not assume that KeepWell provides end-to-end encryption; this has not been established.

Children’s privacy

The eligibility and minimum-age policy has not been finalized. This draft does not set an age restriction or claim that processing children’s information is authorized. The owner must resolve eligibility and the handling of children’s information before launch.

Policy updates

This policy may need to change as the service or applicable requirements change. The final version must identify its last-updated date and explain any required notice of material changes.

Contact and operator details

Some required operator or contact details are not yet configured. Only confirmed contacts are listed here. The missing details must be completed before public launch.