Privacy policy

Version 1.4  ·  Effective 1 October 2026  ·  Previous version: 1.3 (28 September 2026)  ·  Supplemented: 14 October 2026 (2.11 — campaign links and QR codes)

This is the English edition of the Hungarian privacy notice. It describes the same service, operated by the same controller, under the same terms. This document is a translation of the Hungarian original at daymons.hu/adatvedelem; in the event of any discrepancy, the Hungarian version prevails.

1. The data controller

You can reach us at the e-mail address above on any data protection matter.

2. What data we process

2.1. Account data

• Guest (anonymous) use: a random identifier. We do not ask for a name or an e-mail address.
• Registered account: your e-mail address, or — if you sign in with a Google or Apple account — the identifier and e-mail address we receive from them. We never see or store your password; that is handled by Google Firebase Authentication.

2.2. Profile and health data

• age, height, weight, biological sex, activity level (to estimate your daily energy requirement);
• weight entries and their timestamps;
• fasting data: start and end time, target and actual duration, whether it was completed;
• goals (e.g. target weight, daily calorie goal, number of meals);
• shopping lists and daily menu selections;
• data from Apple Health or Health Connect — only if you switch the sync on: daily step count, average heart rate, sleep, workouts (type and length) and the measured active energy burned. The app only reads these, never writes back, and stores them as daily totals only.

Under Article 9 of the GDPR, weight and fasting habits may qualify as health data, and we therefore ask for your separate, explicit consent in the app before processing them.

2.3. Technical data

• a push notification device identifier (FCM token), if you enable notifications;
• error logs and crash reports (Firebase Crashlytics) and usage statistics (Firebase Analytics);
• subscription status and transaction identifier (RevenueCat, App Store / Google Play).

We never see or store payment card details — payment is handled by Apple and by Google.

2.4. Data sent to the AI features

The premium AI features (assistant, daily coach, weekly review and weekly Autopilot, in-fast messages, meal, fridge and menu photo recognition, personal challenges, trend watch) pass the request through our server to the OpenAI language model. These may contain:

• Assistant: the question you type and a short numeric summary (current fast length and target, streak, today's health score);
• Daily coach: today's aggregate figures (fast, calories, protein, water, sleep, activity), your goals and the goal programme you chose;
• In-fast messages: your fast's target and the aggregate count and length of your previous completed fasts;
• Weekly review: that week's aggregate figures (fasts, water, calories, sleep, workouts, weight change);
• Weekly Autopilot: your week's aggregate figures;
• Personal challenges: a summary of your previous days;
• Trend watch: your trends over several days compared with your own average;
• Meal photo: the picture you take or choose;
• “What should I eat?”: the photo you take of your fridge, a menu or a buffet, solely for recognition, plus what is left of today's calorie and protein budget and your fasting window.
• Cycle phase (only if you switched the cycle calendar on): the daily coach is told which phase of your cycle you are in — not the dates and not your symptom entries, only the name of the phase;
• Today's symptom (only if you recorded one): the daily coach is told that you flagged yourself as unwell today (a cold, for instance), so it does not suggest a demanding day.

The request contains no name and no e-mail address — the model is not told who you are. The photos (meal, fridge, menu, buffet) are stored neither by us nor by the provider: they pass through in the request and are discarded once the answer comes back.

OpenAI operates in the United States; the transfer is based on the European Commission's standard contractual clauses (SCCs). Under the provider's own policy, data sent through the OpenAI API is not used to train models.

Using the AI features is voluntary: if you do not use them, no such transfer takes place. Before first use, the app asks for separate, explicit consent ("Accept & Enable AI Features"), and until you give it, no AI feature sends any data — not even automatically. You can withdraw consent at any time: Profile → AI features.

If you had already enabled the AI features, the app asks for separate, explicit consent again for the extended scope of the daily coach, “What should I eat?”, personal challenges, the weekly Autopilot and trend watch. Your earlier consent does not cover this scope: until you give the new one, no AI feature in the app sends any data.

2.5. Progress photos

With the premium Progress photos feature you can save photos you take or choose of yourself, to follow your change over time and compare it with an earlier picture. For this we store:

• the photo — before saving, the app scales it down to at most 1280 pixels and compresses it (JPEG);
• the date of the photo and, if you enter them, your weight and a short note (up to 200 characters);
• when it was saved and where the image is kept in storage.

Where we store it: the image in Google Firebase Storage, the related data in the Firestore database — both inside the European Union. To display photos faster, a temporary copy may be kept on your device; it is removed when you sign out and when you delete your account.

Who can see it: only you, with your signed-in account — this is enforced by server-side access rules. We do not publish the photos, do not send them to any AI provider, and do not use them for any other purpose. Only you can share them, by your own explicit choice; your weight is not on the shareable image by default.

Deletion: you can delete any photo individually in the app — the image is then deleted from storage as well. When you delete your account, all your photos and their data are permanently deleted.

Data portability: on request we provide your photos and their data (date, weight, note) in a machine-readable format — see section 7.

Under Article 9 of the GDPR, a photo of your body may qualify as special category (health) data, so we ask for your explicit consent to process it. Using the feature is voluntary.

2.6. Cycle and symptom data (optional)

If you switch on the cycle calendar, the app stores what you record: when a period starts and ends, how heavy it is, the symptoms that go with it (cramps, headache, bloating, fatigue and the like), your mood and energy level, and your own notes. From these the app works out your average cycle length, the likely date of the next period and the phase you are currently in.

If you switch on menopause mode, this can also include hot flushes, night sweats and disturbed sleep.

When you use home remedies, the symptom you pick (a cold, a sore throat, a headache) is saved to your journal so the app can adjust its suggestions for the day.

Under Article 9 of the GDPR these are special category personal data, so we ask for your explicit consent in the app before processing them. The features are voluntary: if you do not switch them on, no such data is created. You can switch them off at any time, and delete everything recorded so far with a single button while keeping the rest of your data.

We do not share this data with anyone, we do not use it for advertising, and we do not pass it to third parties. It lives only in your account, inside the European Union.

2.7. Location data and the “Where to eat?” place finder

“Where to eat?” shows restaurants near you. For this the app — if you grant permission on your device — reads your device's current location (geographic coordinates). The permission is while-in-use only: we do not track your location in the background. If you do not grant it, you can type a city or an address and the search runs around that instead.

• We do not store or log your location. For the search, the coordinates go to our server (European Union) and from there to Google's place search (Google Maps Platform — Places API), and are discarded once the answer comes back. Google receives the centre and radius of the search and the app language; it does not receive your account identifier, name or e-mail address. The request is sent by our server, so Google does not see your device's IP address either.
• City or address search: the text you type is sent to Google's Geocoding API, likewise without any identifier.
• Details of a place: when you tap a place, we send its Google identifier to fetch opening hours, phone number and website.
• Content received from Google (name, address, opening hours, rating) is not stored; it is shown live, marked “Powered by Google”.
• Favourites: if you mark a place as a favourite, we store its Google identifier and the time you marked it in your account — nothing else.
• Submitted places: if you suggest a place, we store the name, address and note you give, the centre of your search rounded to roughly 100 metres, and your account identifier. After moderation the submission is shown to others — without your account identifier or name. If you report a submitted place, we store the report together with your account identifier for moderation.
• Daily usage counter: to prevent abuse and runaway costs we count how many searches, detail requests and submissions you make per day. It is a count only: no location, search text or results.
• Featured places (advertising): for places marked “Featured — ad” we total the number of views and taps per day, without names or account identifiers.

If you ask for directions, open a place's website or call it, the app hands you over to the maps app, the browser or the phone — the respective provider's data practices apply there.

2.8. Weather: the city you enter

For the weather shown on the home screen you can enter a city in your Profile. It is optional, and we do not ask for location permission for it. The city name is stored among your account settings until you remove it.

Our server turns the city name into coordinates using OpenStreetMap Nominatim, and fetches the forecast for the city's coordinates from the Norwegian Meteorological Institute (MET Norway). OpenStreetMap receives the text you typed, MET Norway receives the city's coordinates — neither receives any identifier of you, and because the request is sent by our server, they do not see your device's IP address either. Our server remembers the typed text and its coordinates in a cache so it does not have to ask again; that entry is not linked to your account. Please enter a city name here, not a precise home address.

2.9. Family plan

With the family plan the subscriber can invite up to four more people using an invite code. For this we store: who owns the family and who its members are (account identifiers), the family's name, the invite code, the name you choose to use in the family, when you joined, and how long the premium received from the family lasts.

• What family members see about each other: the chosen name and the join date. Not your health data, journal or weight.
• Shared shopping list and “shared fridge”: each item's name, quantity and status, and which member added it. Every member of the family can see and edit it.
• Family group: the family has a leaderboard, shared challenges and messages; the results and messages you share there are visible to the family's members.
• Members' premium entitlement is set by our subscription provider (RevenueCat), which receives the member's account identifier for this.

2.10. Gift codes, one-off purchases and quotas

• Buying a gift code: we store the code, the buyer's account identifier, the time of purchase, the transaction and product identifiers, the store and the code's status (issued / redeemed). The buyer can see whether their code has been redeemed — not by whom.
• Redeeming a gift code: we store the redeemer's account identifier, the time of redemption and when the premium received expires. To prevent guessing we count failed attempts (at most five per hour).
• Streak restore and rest days: your account stores which day is covered by a rest day or a purchased streak restore, and the related transaction identifier.
• Processed purchases: for every one-off purchase (gift code, streak restore) we record the transaction identifier, the account identifier, the product and the time, so the same purchase cannot be credited twice.
• “What should I eat?” monthly quota: for free use, your account counts how many analyses you requested in the given month.
• Year in review: built on your device from your own, already stored data; no new data is created and no third party receives any of it. Only you can share it, by your own choice.

We still never see card details: payments are handled by Apple or Google.

2.11. Partner offers (advertising) and the merch shop

Some screens of the app may show partner offers marked “Ad”. They are chosen by the topic of the screen (a sleep-related offer on the sleep screen, for example), not by your data: we do not build an advertising profile of you, and the partner receives no data about you from us.

• Tap counting: when you tap an offer, our server increases that placement's counter for the day by one. The counter is a daily total with no name, account identifier, device or timestamp.
• Leaving for the partner: the tap opens the partner's site in your browser. From there on, the partner's own privacy notice applies.
• Merch shop: tapping a product opens an external web shop in your browser; the purchase and payment take place there, not in the app. The operator of the web shop is responsible for the data you give there.
• Campaign links and QR codes: when you open a Daymons link or QR code, we count, without your name, which campaign led to which page or feature. We store no user identifier, IP address or time with it. On Android, if you install the app from such a link, on first launch we read from the Google Play install referrer what you wanted to open; we use this only to open the right screen and for the anonymous counter.
• The images of offers, products and dietitian profiles are loaded from the web address given for them, so the server hosting the image may see your device's IP address.

2.12. Dietitians and sharing your journal

The “Talk to a dietitian” feature shows dietitians' professional profiles. Booking and payment take place on the dietitian's own site, in your browser; the dietitian is the controller of the data you give there. The link carries a “ref=daymons” marker, which tells the dietitian only that you came from Daymons — nothing about you.

• Tap counting: per dietitian and per month we count profile views and booking taps, without names or account identifiers.
• Sharing my journal: the summary is built on your device from the aggregate figures of the last 30 days (days logged, number and average length of fasts, average calories, protein, water and sleep, active days, weight change). It contains no name, e-mail address, individual days, foods, photos or cycle data. You see the exact text before sending, and you send it yourself through your own sharing options to whoever you choose. We do not pass it to anyone, and it never reaches our server.

2.13. Medication and vitamin reminder

The names of the items you add to the reminder, their times and your “taken” marks are stored only on your device. They never reach our server and we cannot see them; we do not send them to an AI provider and we derive no statistics from them. The reminders are your device's own local notifications.

A medication list is health data, that is, special category data — which is exactly why it stays with you. The price is that it does not carry over when you change device or reinstall the app. If your device uses the operating system's own backup (iCloud or Google), the app's local data may be included in it — that is governed by your device settings, not by us. You can delete the list in the app at any time; when you delete your account from the app, we delete it from that device as well.

3. Why we use it, and on what legal basis

You may withdraw your consent at any time (see section 7). Withdrawal does not affect the lawfulness of processing carried out beforehand. You can revoke the location permission in your device settings and remove the city in your Profile.

Medication reminder data is not in the table because we do not process it: it stays on your device (section 2.13).

4. Who we share it with (processors)

We do not sell your data and we do not use it for advertising: the partner offers shown in the app are not selected on the basis of your data, and partners receive no data about you from us (section 2.11). We rely on the following processors to operate the service:

• Google Ireland Ltd. / Google LLC (Firebase) — authentication, database (Firestore), file storage for progress photos (Storage), notifications, error logging, statistics. The database and the file storage are kept in the European Union.
• OpenAI, L.L.C. (USA) — the language model behind the AI features. It receives only the data listed in section 2.4, with no name and no e-mail address, and does not store the photos.
• RevenueCat, Inc. — subscription management and receipt validation; signalling one-off purchases (gift code, streak restore), and setting the premium entitlement of family members and of those who redeem a gift code.
• Google (Google Maps Platform — Places API and Geocoding API) — the “Where to eat?” searches. It receives the centre of the search (your location or the city/address typed), the radius and the identifier of the place opened, from our server, without an account identifier.
• Norwegian Meteorological Institute (MET Norway, Norway) — weather forecast. It receives the coordinates of the city you entered, without any identifier.
• OpenStreetMap Foundation (Nominatim, United Kingdom) — turning the city name into coordinates. It receives the text you typed, without any identifier.
• Apple Inc. / Google LLC — processing payments in the app stores.

Partners, the merch web shop and dietitians are not our processors: they receive no data about you from us. If you go to their site from the app, they handle the data you give there as controllers in their own right. Your family members see what is described in section 2.9.

Some processors may operate infrastructure outside the EU; in those cases the transfer is based on the European Commission's standard contractual clauses (SCCs) or on an adequacy decision.

5. How long we keep it

• Account and fasting data: for as long as your account exists. When you delete your account we delete it permanently.
• Shopping lists: deleted automatically after 14 days.
• Progress photos: until you delete them individually, and at most for as long as your account exists. When you delete your account we delete them permanently.
• Meal, fridge and menu photos: not stored. The text of a weekly AI review and of the daily coach stays in your account for as long as the account exists.
• Cycle and symptom data: for as long as your account exists, or until you delete it. Switching the feature off does not delete it on its own — there is a separate button for that, which keeps the rest of your data. Deleting your account deletes this too.
• Location for “Where to eat?”: not stored — used only for the duration of the search. We do not store the results or coordinates received from Google either (Google's terms would allow up to 30 days, but we do not make use of that); results live only in your device's memory until the app is closed.
• Favourite places: until you remove them from your favourites, and at most for as long as your account exists.
• Submitted places: a submission that is still pending or was rejected is deleted when you delete your account; an approved place remains as a community place, but your account identifier is removed from it.
• The place finder's daily usage counter: until your account is deleted.
• The city you enter: until you remove it in your Profile, and at most for as long as your account exists. The forecast cache is refreshed after 45 minutes (if the provider is down we show data at most 6 hours old). The city-name-to-coordinates cache has no expiry, but it is not linked to any account.
• Family plan: your membership data until you leave, are removed or delete your account; the family as a whole (with the shared shopping list and the family group) until the owner's account is deleted. Items you added to the shared list stay on the list after you leave.
• Gift codes and processed purchases: kept even after the account is deleted, for settlement and to prevent double crediting, with the random account identifier — no name and no e-mail address.
• Rest days, streak restores, monthly quota: for as long as your account exists.
• Aggregate tap and view counts: cannot be linked to a person; kept for as long as settlement requires.
• Medication reminder: on your device, until you delete the list, delete your account from the app, or uninstall the app.
• Error logs: for the period set by the provider (typically 90 days).
• Accounting records: for the period required by law (payments are handled by the app stores).

6. Deleting your account and your data

For the data introduced in version 1.4, deletion works as follows:

• deleted: the city you entered, your favourite places, the place finder's daily counters, your rest days and streak restores, your monthly quota, and your pending or rejected place submissions;
• your approved place submissions remain, but your account identifier is removed from them;
• as a family member you are removed from the family and the family group, and your seat is freed; as the owner, the family, the shared shopping list and the family group are deleted too, and the members' premium received from the family ends;
• the medication reminder list is deleted by the app from the device on which you delete the account. If you request deletion by e-mail, or used the app on another device as well, it is removed there by uninstalling the app;
• kept: the records of gift codes and processed purchases (with the random identifier of the deleted account), and the aggregate tap counts that cannot be linked to a person — see section 5.

If you cannot sign in, or you have already removed the app, you can request deletion by e-mail. For the exact steps, and for what is deleted and what is kept, see Delete your account.

7. Your rights

Under the GDPR you have the right to:

• be informed about the data we process about you (access);
• have inaccurate data corrected (you can also edit your profile directly in the app);
• have your data erased (the "right to be forgotten");
• request restriction of processing;
• object to processing based on legitimate interest;
• data portability (a machine-readable copy);
• withdraw your consent at any time.

Send your request to the e-mail address above; we will respond within 30 days at the latest.

Complaints

If you believe we have infringed your rights, you may lodge a complaint with the supervisory authority:

Hungarian National Authority for Data Protection and Freedom of Information (NAIH)
Falk Miksa utca 9-11, 1055 Budapest, Hungary · naih.hu · ugyfelszolgalat@naih.hu

If you are resident in another EU member state, you may also lodge a complaint with your local supervisory authority.

8. Security

Data travels over an encrypted connection (HTTPS/TLS) and is stored encrypted. Only your signed-in account can access your own data — this is enforced by server-side access rules.

9. Children

The service is not recommended for anyone under 16, and we do not knowingly collect data from them. If we become aware of such data, we delete it.

10. Important health notice

The values shown by Daymons (daily energy requirement, fasting stages, recommendations) are informational estimates and do not constitute medical advice. They do not replace the opinion of a doctor or a dietitian. Before starting a fast or a diet — and especially in case of illness, pregnancy, breastfeeding or medication — seek professional advice.

11. Changes to this notice

We may update this notice from time to time. In case of a material change we will notify you in the app and, where necessary, ask for your consent again. The version in force is always available on this page.

Version 1.4, effective 1 October 2026. English translation of the Hungarian original; in case of discrepancy the Hungarian version prevails.