Skip to content
DobrySoftware
← Kropelka

Kropelka

Privacy Policy

Privacy Policy

Kropelka App — last updated: 16 October 2026

In short:

  • Your profile, hydration, and Apple Health data are stored locally on your device.
  • We do not operate a central profile, hydration or health-data database or user accounts.
  • We do not use analytics, ads, or tracking tools.
  • The App does not sync your data via iCloud (CloudKit).
  • We make only limited network connections – for weather, to handle App Store purchases, and to fetch the list of our other apps (details in Sections 6 and 7).

The controller of your personal data is:

Company ADAKS MEDIA DANIEL DOBROWOLSKI
VAT ID PL6152062671
Address Mściszów 112B, 59-800 Lubań, Poland
E-mail adaks.media@gmail.com

Because the data is processed locally on your device and we have no access to it, in practice you retain full control over it.

We have not appointed a Data Protection Officer (we are not required to). For all privacy matters you can contact us at adaks.media@gmail.com.

The Kropelka App processes the following categories of data locally on your device. None of this data is sent to our servers.

2.1. Profile data (provided by the user)

  • Name (optional)
  • Body weight (kg)
  • Height (cm)
  • Sex
  • Date of birth / age
  • Physical activity level (including a separate setting for weekends)
  • Body type and perspiration level
  • Information about pregnancy, breastfeeding, and senior age (if you provide it – used for a more accurate hydration-goal calculation)

Some of the above data (relating to health, including pregnancy and breastfeeding) constitutes special-category data within the meaning of Article 9 GDPR. We process it solely locally and only on the basis of your voluntary decision to enter it.

2.2. Hydration data

  • History of beverage intake (type, amount, caffeine content, date, and time)
  • Daily hydration goal and caffeine limit
  • Favorite beverages and their configuration (including custom drinks and glass sizes)
  • Achievements and streaks
  • App preferences (units, theme, notification schedule and hours)

2.3. Apple HealthKit data

With your explicit consent, the App may read and write the following data in Apple Health:

Data type Read Write
Water intake ✓ ✓
Caffeine intake — ✓
Body weight ✓ —
Height ✓ —
Biological sex ✓ —
Date of birth ✓ —
Heart rate and resting heart rate ✓ —
Workouts (including calories burned) ✓ —

Data read from Apple Health is used solely to automatically calculate and calibrate your daily hydration goal. Apple Health integration is fully optional – the App also works correctly without it. The App does not process medical-records data (Health Records / clinical data).

2.4. Technical data

  • App installation date (stored in the device Keychain, to determine trial eligibility)
  • Subscription status (processed locally by Apple StoreKit 2; we do not handle payments ourselves)

2.5. Location data

The App may optionally use your approximate location (accurate to about 1 km) solely to fetch weather data used for the automatic adjustment of your daily hydration goal. Location is not stored in the App’s database. Details about sharing coordinates with the weather provider are described in Section 6.

Purpose Legal basis (GDPR)
Calculating the daily hydration goal Art. 6(1)(b) – performance of a contract
Tracking fluid intake Art. 6(1)(b) – performance of a contract
Processing health data from the profile (weight, height, pregnancy, lactation, etc.) Art. 6(1)(b) – performance of a contract, and Art. 9(2)(a) – explicit consent
Reading data from Apple Health (HealthKit) Art. 6(1)(a) – consent, and Art. 9(2)(a) – explicit consent
Local notifications (drink reminders) Art. 6(1)(a) – consent
Fetching weather data (location access) Art. 6(1)(a) – consent
Handling subscriptions and the trial period Art. 6(1)(b) – performance of a contract
Fetching the list of other apps and connection security/diagnostics (IP address) Art. 6(1)(f) – legitimate interest

Profile, hydration and health data is stored locally using Core Data / SQLite. We do not operate a central database of that data or user accounts. The app does not use CloudKit synchronisation; system iCloud backups may include data according to device settings. An App Group container shares data with widgets and Siri on the device, and Apple Watch Connectivity exchanges data between the phone and watch. Technical connections to dobrysoftware.com are a separate process described below.

Commitments regarding HealthKit data:

  • HealthKit data is not sold, shared, or transferred to any third parties.
  • HealthKit data is not used for advertising or marketing purposes.
  • HealthKit data is used solely to provide the App’s core functionality (hydration tracking, goal adjustment).
  • HealthKit data is not stored on our servers. It remains in Apple Health, which you control.

The App may request access to your approximate location to fetch current weather data, used for the automatic adjustment of your daily hydration goal (e.g. on hot days). Location access is fully optional – the App also works correctly without it.

To fetch the forecast, your approximate geographic coordinates (without your name, identifier, or other data allowing direct identification) are sent to Apple’s weather data provider:

  • Apple WeatherKit – the only weather provider used by the App. Requests are subject to the Apple Privacy Policy and the WeatherKit terms. Apple may therefore process data also outside the European Economic Area, on the terms described in the Apple Privacy Policy.

Coordinates are sent only at the moment the forecast is fetched. The coordinates are not stored by the App – only the weather result (e.g. temperature) is cached locally, without any location data.

The Kropelka App:

  • Does not use any external SDKs or analytics libraries (no Google Analytics, Firebase, Facebook SDK, Sentry, etc.)
  • Contains no tracking tools (in line with Apple’s privacy manifest, the App does not perform tracking)
  • Does not display ads
  • Does not sell, share, or transfer your personal data to any third parties for marketing purposes
  • Does not profile users and does not create user accounts

The App makes network connections only in the following limited cases:

Service Purpose What is sent
Apple WeatherKit Fetching weather (goal adjustment) Approximate coordinates (Section 6)
Apple StoreKit / App Store Handling subscriptions and purchases Transaction data is handled by Apple
dobrysoftware.com Fetching the developer’s list of other apps (informational section) No hydration or health data is sent; the server receives the IP address and technical connection data

The connection to dobrysoftware.com serves solely to display the list of our other apps and does not transmit any of your hydration, profile, or health data. As with any web server, the device’s IP address is processed to establish the connection and for security and diagnostic purposes (basis: legitimate interest, Art. 6(1)(f) GDPR).

Your data is stored on your device for as long as you use the App. You can delete it at any time by:

  • Deleting the data from the App settings (the delete-all-data function)
  • Uninstalling the App (removes hydration and profile data from the local database on that device)
  • Manually deleting the hydration data saved in the Apple Health app

Technical note: the installation date stored in the device Keychain (used to determine trial eligibility) may – in line with how iOS works – remain in the Keychain after the App is uninstalled and reinstalled. This is a single date, unrelated to your health data.

Apple Watch: for technical reasons of the Apple system, deleting data from the App on the iPhone may not cover data stored locally on the paired Apple Watch. To permanently delete the data from the watch, uninstall the App from the Apple Watch as well.

Subject to the GDPR’s conditions and exceptions, you have rights of access, rectification, erasure, restriction and data portability where automated processing is based on consent or a contract. You may object to legitimate-interest processing on grounds relating to your particular situation, and to direct marketing at any time. Consent can be withdrawn without affecting the lawfulness of earlier processing. Statutory conditions and exceptions apply, including for legal duties and claims.

For data actually held by the operator, use the contact address in this Policy. We may request proportionate information needed to verify identity. We provide information on action taken in response to a request without undue delay, generally within one month of receipt. Where necessary, this may be extended by a further two months due to the complexity or number of requests; we explain any extension and its reasons within the initial month.

The operator cannot remotely access or erase data remaining solely on your device. App and system tools let you manage that data; this does not replace rights concerning data held by the operator. You may lodge a complaint with the President of the Polish Personal Data Protection Office, ul. Stanisława Moniuszki 1A, 00-014 Warsaw, Poland, uodo.gov.pl, or another competent supervisory authority.

You may complain to the President of UODO or another competent supervisory authority; contact details appear in the rights section.

The Kropelka App is not directed at children, and we do not knowingly collect personal data from children. The App should not be used by persons under 13 years of age. Persons under 16 should use the App only with the consent and under the supervision of a parent or legal guardian – in particular regarding access to health data (HealthKit) and location. If we learn that a child’s data has been provided to us in breach of the above rules, we will take steps to delete it.

The Kropelka App is not a medical device and does not constitute medical advice. It serves informational, general-wellness purposes only. The calculated hydration goal is an estimate and does not account for individual medical needs. For any health concerns related to hydration, always consult a physician.

We update this Policy when features, processing, providers or law change. Material changes are communicated through an appropriate channel before implementation. If a new activity requires consent, it is requested separately. Continued use or acceptance of the Policy does not replace required consent.

If you have questions about this Privacy Policy or the processing of your personal data, please contact us:

ADAKS MEDIA DANIEL DOBROWOLSKI

Mściszów 112B, 59-800 Lubań, Poland

E-mail: adaks.media@gmail.com

VAT ID: PL6152062671

The dobrysoftware.com website, including its legal-document pages, app catalogue and version-check services, uses hosting provided by Contabo GmbH. We process and store technical connection data on this infrastructure, such as IP addresses, request times, requested resources, User-Agent and other technical headers, as well as data voluntarily submitted through the website’s forms. Technical data may be recorded in logs used to operate, diagnose and secure the services. Hosting does not mean that data described as remaining solely on the device is automatically uploaded.

The Contabo hosting server serving dobrysoftware.com is located within the European Union. This Policy describes processing by other providers, including any transfers outside the European Economic Area.

Contact and support: we process your email address, message, voluntary attachments and information necessary to deal with the matter. Email is handled by Google through Gmail; website-form submissions may also be stored on the Contabo server. Do not send passwords, full payment details or unnecessary information about other people.

Legal bases for data actually processed by the operator: performance of a contract or pre-contractual steps — providing purchased access and related support; compliance with a legal obligation — required accounting and consumer-rights handling; legitimate interests — service security, diagnostics, other correspondence and establishing, exercising or defending claims. These correspond to Article 6(1)(b), (c) and (f) GDPR. Where a specific optional activity relies on consent, Article 6(1)(a) GDPR applies. Correspondence data is voluntary but may be needed to handle your request. Technical data is necessary to handle a connection. A device’s system permission is not general consent to unrelated processing.

Technical data and server logs are retained for the time necessary to operate services, detect and investigate incidents and diagnose problems. The criteria are the nature and date of an event, the time needed to identify a problem, the risk of repeated abuse and specific legal duties. Further retention of data isolated for a particular incident requires a reason related to investigating it or protecting legal claims.

Correspondence and support requests are retained while the matter is handled and afterwards only as needed to comply with a legal duty or protect claims within the applicable limitation period. Accounting records are subject to statutory retention duties. Store, email-service and system-backup data is also subject to the relevant providers’ rules. Removing the app does not automatically erase correspondence, website submissions or store records.

Depending on the feature used, recipients may include Contabo for hosting, Google for email, Apple for App Store services, necessary technical-support and accounting providers, and legally authorised authorities. Only data necessary for the relevant purpose is disclosed. Stores and services selected by the user may act as independent controllers.

Email and store services may involve processing outside the European Economic Area, including in the USA. Google describes reliance on adequacy decisions, including the EU–US framework within its applicable scope, and standard contractual clauses for transfers covered by them. Apple describes standard contractual clauses for transfers of data from the EEA. This does not mean that the operator has personally entered into every such instrument or that all services operate solely within the EEA. Information on safeguards and how to obtain copies: Google — data transfers, Apple — privacy; for the operator’s processing, use the contact address in this Policy.