Skip to the privacy policy
KinPill.Privacy & your information
Your information, explained

Privacy Policy

Medication and family records are stored on your device. Account and subscription information is handled online.

Effective date:  ·  KinPill for Android and iPhone (iOS)

1. Who we are

KinPill is operated by Almeer Design ("we", "us" or "our"), based in Berlin, Germany. We are the controller of the account, subscription and support information we process to operate KinPill.

Operator
Almeer Design
Location
Berlin, Germany
Privacy contact
info@kinpill.com

This policy covers the KinPill mobile app and related support. KinPill manages records and sends reminders; it does not provide medical advice, recommend treatments or make treatment decisions.

Separate collection by the website hosting this page, such as website hosting logs or website analytics, is outside this app policy and must be covered by the website’s own privacy notice.

2. Information we handle

Medication, health and family records

The personal app records you enter are stored on your device and used there for the features you choose. Medication, health and family-record contents are not uploaded to our Firebase account database or sent to RevenueCat as part of KinPill’s normal operation. Reminders are scheduled locally.

Signing in does not itself back up or synchronize these records between devices. Your operating system’s backup or device-transfer features may include local app data, depending on the app configuration and your device settings. Copies made through those features are subject to the relevant provider’s settings and policies.

Firebase account and user profile

Firebase Authentication handles account creation and sign-in. It processes account identifiers, email and provider information, authentication timestamps, and any name or profile image supplied through sign-in. It also processes technical information, including IP addresses and user-agent information, for authentication and abuse prevention. Session tokens may be stored on your device.

KinPill’s separate Firebase user-profile record contains:

  • Your user ID and email address;
  • Your email provider and account creation time;
  • Whether you have completed onboarding;
  • Your subscription plan and subscription expiration date.

Subscriptions and RevenueCat

RevenueCat processes an app user identifier, purchase history, store receipts or purchase tokens, subscription status and dates, and technical information such as device/platform details and service-connection times. Its customer information can also include country information derived from a transaction or IP address.

This information supports purchase verification, subscription access, purchase restoration and subscription reporting. For purchases made through Apple or Google, the relevant store handles payment; KinPill does not receive your full payment-card details from that purchase.

We use your Firebase user ID (UID) as the account identifier shared with RevenueCat to associate your subscription with your KinPill account.

Support messages

If you contact us, we receive your contact details and the information in your message. Avoid sending sensitive health records unless necessary for your request. Information you send by email is no longer held only on your device.

3. Google and Apple sign-in

Google sign-in: Google provides information to identify your account, such as an identifier, email, name and profile picture.

Sign in with Apple: Apple provides an app-specific identifier and the name and email information you share, where available. If you use Hide My Email, we receive Apple’s relay email address instead of your personal email address.

Your Google or Apple password is not shared with KinPill. These providers process information about their sign-in services under their own privacy policies. You can manage KinPill’s connection in your Google or Apple account settings; removing the connection does not necessarily delete your KinPill account or its existing data.

4. Why we use information

We use account and subscription information to authenticate you, maintain your profile, remember onboarding completion, administer subscription access and provide support. Local records are used on your device for record management and reminders.

Where the GDPR applies to our processing of account, subscription and support information, the corresponding legal bases are:

Providing your account and subscription
Performance of the service contract with you, where necessary to deliver the account, subscription or related support you request (Article 6(1)(b)).
Security, service administration and subscription reporting
Our legitimate interests in preventing misuse, administering the service, understanding subscription activity and responding to general enquiries, balanced against your rights (Article 6(1)(f)).
Meeting applicable legal duties
Compliance with a legal obligation where a specific law requires processing, such as handling a valid regulatory request (Article 6(1)(c)).

Local medication records are used for the functions you initiate on your device. We do not receive their contents through account or subscription processing. This policy is a notice, not a consent form. If a future feature requires consent for a new use, we will request it separately before that processing begins.

Required sign-in information is needed to create and maintain a signed-in account. Purchase information is needed to administer a subscription. Without the relevant information, those account or subscription functions cannot be provided.

5. Sharing and service providers

  • Google/Firebase: authentication and storage of the account profile;
  • Google and Apple: their respective sign-in services and, when used for a purchase, store billing services;
  • RevenueCat: subscription management, purchase verification and subscription reporting;
  • Our email service provider: delivery and storage of support and privacy correspondence.

Providers processing information on our behalf act under the applicable service and data-processing terms. Google and Apple also have independent responsibilities for their own account and billing services. Information may be disclosed where required by law or where necessary and lawful to address fraud or protect legal rights.

KinPill does not display advertisements or use advertising SDKs. It does not use separate behavioral analytics or crash-reporting tools. RevenueCat’s processing of subscription transactions and subscription reporting still takes place as described above.

6. Storage locations and transfers

Local app records are stored on your device, subject to the device-backup arrangements described above. KinPill’s Firebase user database is hosted in Frankfurt, Germany (europe-west3).

Firebase Authentication processes authentication data in the United States. RevenueCat is based in the United States and may process subscription information there and through its service providers. The location of our Firebase database does not determine the location of these separate services.

For transfers covered by European data-protection law, the applicable provider terms provide safeguards such as a recognized adequacy framework where available and Standard Contractual Clauses for transfers requiring them. RevenueCat’s data-processing addendum incorporates those clauses for covered restricted transfers. You can review the terms below or contact us for information about the safeguards applicable to your data.

7. How long information is kept

  • Local records: kept on your device until removed. In-app account deletion also removes KinPill’s local records on the device where deletion is performed. Separate device-backup copies are managed through the backup provider.
  • Firebase account and user profile: kept while your account exists. In-app deletion is processed immediately when an internet connection is available. Email requests are completed within two working days after verification.
  • Firebase database backups: we have not enabled scheduled database backups or point-in-time recovery. This does not remove the separate infrastructure and retention practices of the service providers.
  • Firebase Authentication: Google states that logged IP addresses are retained for a few weeks and other authentication data is removed from live and backup systems within 180 days after deletion is initiated.
  • Support emails: retained for six months after the request is resolved.

RevenueCat records: your RevenueCat customer record is kept while your KinPill account exists. When your KinPill account is deleted, we delete the associated RevenueCat customer record within seven days of the account deletion. This applies to account deletion through the app or by email.

Apple and Google may retain their own billing records under their policies and legal obligations. Those store records are separate from the KinPill account records we control.

8. Deleting your information

In the app

Open Account → Delete account and confirm. An internet connection is needed to complete the process. When connected, deletion removes your Firebase Authentication account, its associated Firebase user record and KinPill’s local records on that device immediately.

This does not delete your Google or Apple account or erase separate device backups. Copies stored on other devices also need to be removed on those devices.

By email

Email info@kinpill.com with the subject “KinPill account deletion” and identify the account. We may verify that it belongs to you. Never send your Google or Apple password.

We complete deletion of the Firebase account and user profile within two working days after verifying the request. We cannot remotely erase records held only on your device; remove those using the app or your device’s app-data removal controls. Offloading an app or signing out may leave local records in place.

RevenueCat and subscriptions

Deleting your KinPill account through either method also results in deletion of the associated RevenueCat customer record within seven days of your KinPill account being deleted. See Section 7 for further retention information.

Account deletion and subscription cancellation are separate actions. Use the relevant store’s subscription settings to stop renewal of an Apple or Google subscription.

Uninstalling KinPill does not itself request account deletion. Use the in-app deletion option or email us to remove the account and user profile held in Firebase.

9. Security and notifications

Firebase security rules restrict each signed-in app user’s access to their own user record. Firebase and RevenueCat provide encrypted connections for their services. No storage or transmission method can guarantee absolute security.

Protection of local records also depends on your device and backup security. Use a device passcode and keep the operating system updated. Local storage alone does not establish that additional app-level encryption is in place.

KinPill notifications are scheduled locally on your device; they are not delivered through a remote push-notification service. Their contents may appear on the lock screen according to your settings. You can change notification permissions and previews in your device settings.

10. Your privacy rights

Depending on applicable law, you may have rights to access your information, correct it, request deletion, restrict processing, obtain a portable copy or object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.

Contact info@kinpill.com to exercise your rights. We may request proportionate information to verify your identity. Where the GDPR applies, we normally respond within one month and explain any permitted extension within that period. The two-working-day commitment in Section 8 applies to verified email requests to delete the Firebase account and user profile.

We do not hold server copies of your local medication or family records. We can help explain available device controls, but cannot retrieve or remotely erase those records for you.

You may complain to a data-protection authority, including where you live or work or where you believe an infringement occurred. In Berlin, you can contact the Berlin Commissioner for Data Protection and Freedom of Information. You do not have to contact us first.

11. Age and family records

You must be at least 16 years old to create a KinPill account. Accounts are not intended for children under 16.

If you record information about a family member or another person, make sure you have the appropriate permission or legal authority. An adult keeping a child’s records on their own device is different from that child creating a KinPill account. Family records follow the local-storage and backup arrangements in this policy.

If you believe someone under 16 has created an account, contact us so we can investigate and take appropriate action.

12. Changes and contact

We may update this policy when KinPill’s features, data practices or legal requirements change. We will update its effective date and provide additional notice of material changes where required. If a change requires consent, we will request it before beginning the relevant processing.

For privacy questions, rights requests or account deletion, contact Almeer Design at info@kinpill.com.