1. Controller and contact
The controller of personal data processed in connection with HealthMe is Tomasz Cichoń - IT. For data protection enquiries and rights requests, contact cichonmail@gmail.com.
This Policy describes processing when using the app, accounts, orders, scanning and external services. The scope depends on the features you use. Reading this Policy does not authorise unrestricted use of your data.
2. Data stored on your device
The product and shared recipe library, its images, favourites and ordinary meal changes are stored locally. They are not synchronised to the server as a shared catalogue. In guest mode, the profile and plan remain on the device for local features.
The app also stores settings, including language and reminders. Selected next-meal information may be shared locally with the HealthMe widget. Device data may be included in system backups depending on iOS and Apple account settings.
Local use does not mean every feature works offline: starting a scan that uses an external service, sending a photograph or requesting generation requires the relevant data to be transmitted.
3. Accounts, profiles and orders
The server stores account information, including an identifier, email, name, authentication and session data. Sign in with Apple involves the provider identifier and account information Apple shares. Apple may provide a relay address instead of your private email.
A profile may include age, sex, height, weight, goals, activity level, meal number and timing, food exclusions, allergies, calorie and macronutrient targets. An account user's profile is available locally and on the server.
Order data includes dates, the selected option, required ingredients, notes, a profile snapshot from the time of ordering, fulfilment status, private results and images. Uploaded product photographs form part of the data used to perform that function.
Processing may also include Apple transaction identifiers and status, package entitlements, a device token for notifications and technical security data, such as IP address, request time and error information. HealthMe does not receive payment card numbers.
4. Purposes and legal bases
Creating accounts, signing in, handling ordinary profile data, fulfilling orders and providing results serve performance of a contract or steps taken at your request before entering one — Article 6(1)(b) GDPR.
Purchase verification and paid access also serve performance of the contract. Required records and other statutory duties rely on Article 6(1)(c) GDPR. Security, abuse prevention and establishing or defending claims rely on the Controller's legitimate interests — Article 6(1)(f) GDPR.
Contract-related correspondence relies on Article 6(1)(b) GDPR; other app enquiries rely on the legitimate interest in responding, Article 6(1)(f). Where processing requires consent, the basis is Article 6(1)(a); consent must cover the specified purpose and may be withdrawn.
5. Health information
Allergies and some information about your body or dietary restrictions may be health data. Processing requires an additional condition under Article 9 GDPR; where consent is used, it must be separate, explicit, freely given and specific to the purposes — Article 9(2)(a) GDPR.
Entering information, creating an account, accepting the Terms or granting system access to a photograph does not replace that consent. Do not include diagnoses, medical records or third-party health data in notes or photographs.
At first sign-in or registration, the app shows two switches, both initially off: consent to health data processing in the profile and optional consent to sharing data with OpenAI. Choosing the confirmation button accepts the Terms and acknowledges reading the Privacy Policy. OpenAI consent is not required to use an account; without it, the app asks for consent before starting a feature that sends data to OpenAI. Current consents are not requested again on subsequent sign-ins. Another account without its own acceptance record must complete this step before profile synchronization. The version, scope and date of acceptance are stored locally for the account; reinstalling the app requires consent again.
You can withdraw OpenAI consent in Settings (AI processing). To withdraw health data consent, contact the Controller; you can also delete your account in Profile. Withdrawal does not affect the lawfulness of earlier processing. It may prevent further use of features that require the data. Changing the current profile does not automatically remove a snapshot retained in an earlier order; contact the Controller to request deletion or restriction.
6. AI generation and scanning
For OpenAI generation, data needed for the requested feature is sent to that provider, including selected profile fields, targets, allergies and exclusions, order requirements, notes and uploaded photographs. Generation requests do not include the account name or email as profile fields, but content may contain personal information you enter yourself. This does not mean the requests are fully anonymous.
Dish images are generated from descriptions of the meal, ingredients and preparation. AI output is for inspiration, may contain errors and is not a medical assessment.
The scanner may use on-device Apple Vision recognition, the Open Food Facts database and, depending on the feature and configuration, OpenAI or TypeSafe (Jev). Product database requests send a barcode; assessment services receive product information, recognised ingredients or a photograph where the feature requires it. Direct connections also reveal technical connection data, such as your IP address, to the provider.
If you configure your own scanner API key, it is stored in the system Keychain and used to authenticate with the relevant provider. Use of your key may be subject to the terms and charges of your provider account. Remove faces, documents and other unnecessary information before sending a photograph.
7. Recipients
Recipients, to the extent needed for a feature, may include Amazon Web Services for account, profile and order infrastructure; OpenAI for generation and analysis; Apple for sign-in, payments and notification delivery; and the email provider for account and order messages.
Relevant features also involve TypeSafe (Jev) and Open Food Facts. Orders involving an operator may be accessed by people authorised to fulfil them; an order notification does not mean a dietitian prepares the result.
Legal and technical support providers may receive access as necessary, as may public authorities where required by law. Providers act as processors or separate controllers depending on the service and applicable agreements.
8. Processing outside the EEA
International providers may process data outside the European Economic Area, including in the United States. The location of the HealthMe server does not mean every provider operation takes place exclusively in the EEA.
Transfers require an appropriate basis under Chapter V GDPR, such as an applicable adequacy decision or standard contractual clauses with required safeguards. The specific basis and documents depend on the agreements and configuration of each service. Information about the applicable safeguards is available through the contact address.
9. Retention and deletion
Account data, synchronised profiles, orders and private results are generally linked to the lifetime of the account. Uninstalling the app does not delete a server account. You can delete the account in the app (Profile → Delete account), which removes the account, profile, orders and private results from the server. You may also request deletion through the contact address, with identity verification limited to what is necessary to protect the data.
Local data remains on the device until deleted by the user or system; device backups may exist separately. Expired authentication materials are subject to periodic cleanup. Records needed for statutory obligations or claims may need to be retained for periods determined by applicable law.
Deleting active account data does not mean immediate deletion of every technical copy.
10. Your rights
Subject to GDPR conditions, you may request access and a copy, rectification, erasure, restriction and portability of your data. You may object to processing based on legitimate interests and withdraw consent where consent is the basis.
Send requests to cichonmail@gmail.com. Responses are generally provided within one month; the GDPR permits extensions in certain cases with an explanation. The Controller may ask for information necessary to verify your identity securely. We do not require your account password.
You may complain to the President of the Polish Personal Data Protection Office or the competent supervisory authority in your country. Some rights depend on the legal basis, data involved and statutory exceptions.
11. Optional data, automation and permissions
Providing data is voluntary, but without information necessary for an account or order those features cannot be provided. Available local features can be used without an account. Do not provide information unnecessary for the selected action.
Profile data is used to calculate targets and tailor suggestions automatically; this may constitute profiling. Results are informational and are not used for decisions producing legal effects or similarly significantly affecting you within Article 22 GDPR.
Access to selected photographs, the camera, device motion and notifications depends on the feature and iOS mechanisms. You can change permissions in device settings. System resource permission is not general consent to processing for other purposes.
12. Security and Policy updates
Local data benefits from iOS protections. The app uses secure connections to external services, account authentication and the system Keychain for relevant credentials. No system provides absolute protection; protect your device, account and API keys.
Material changes to purposes, recipients or processing rules require updated information and, where legally required, new consent before that processing starts. Updating the Policy does not replace required consent.
13. This website
HealthMe information pages are hosted by Cloudflare Pages. Cloudflare processes connection information, such as your IP address, to deliver and secure the website. We do not add advertising, analytics, cookies or data collection forms to these pages. Language selection uses ordinary links and does not store a preference in your browser. Email contact sends the information you provide through email providers to handle your enquiry.