Skip to content
Dietly!
English
Application legal documents

Privacy Policy

Last updated: October 28, 2026

This policy describes how Dietly! ("Software") handles data, and it has two parts. Part A describes the data processing of the licensor of the Software ("Licensor"): the data that you or the app store send to the Licensor — for these, the Licensor is the data controller. Part B describes how the Software handles patients' data on your computer: for these, you are the data controller, and the Licensor has no access to them. Part B gives you facts for your tasks as a data controller (for example for your records and for informing your patients); it is not legal advice.

Part A — The Licensor's Data Processing

1. The data controller

Gábor Pap, sole trader (egyéni vállalkozó; registration number: 62788496; registered seat: Egry József utca 7. D ép., 2330 Dunaharaszti, Hungary; e-mail: gdlabs@outlook.hu; further details: dietly.hu/en/imprint), the licensor of the Software.

The Software contains no analytics, tracking or advertising modules, and has no server to which it would send data: the Licensor collects no data through the Software. The Licensor only receives the data that you send yourself or that the app store passes on — these are described in sections 2–4. The Licensor does not carry out automated decision-making or profiling.

2. Bug reporting (Feedback & Diagnostics)

The Software creates a bug report package only when you start it yourself.

  • What the package contains: the package (.drep) contains the operational log, technical details of the environment (the version of the Software, the type of operating system, the language, the performance class of the computer, the time) and your description; and — unless you turn it off — the ingredient and recipe catalogue too, including the items you added yourself (this helps to reproduce the error).
  • Redaction: the Software tries to redact patients' identifiers, file and folder names and recorded values from the log, but this cannot be fully guaranteed; it cannot redact names from the description you write. Please do not write patient data into the description.
  • Encryption and sending: the Software encrypts the package with the Licensor's public key — only the Licensor can open it — and never sends it anywhere: the file is created on your computer, and you decide whether to forward it.
  • Purpose and legal basis: investigating the reported error or question and fixing the Software; legal basis: the Licensor's legitimate interest in investigating and fixing errors of the Software (Article 6(1)(f) GDPR) or, where the error concerns the performance of the End User License Agreement, the performance of the contract (Article 6(1)(b)).
  • Retention: until the investigation is closed; the Licensor then deletes the package.
  • If patient data arrives nevertheless: the Licensor processes it on your behalf under section 7 of the End User License Agreement, and deletes it when the investigation is closed.

3. E-mail and support

  • Data: your e-mail address, your name (if you give it), the content of the message and its attachments.
  • Purpose and legal basis: answering your questions, comments and complaints; legal basis: the Licensor's legitimate interest in answering enquiries (Article 6(1)(f) GDPR) or, where the message concerns the End User License Agreement, the performance of the contract (Article 6(1)(b)).
  • Retention: until the matter is closed; the Licensor keeps a consumer complaint and the reply to it for three years under the Hungarian consumer protection act (legal obligation, Article 6(1)(c)).
  • Recipient: the e-mail provider that handles the correspondence (a processor). The provider may also process the data outside the European Union; the provider's privacy terms and the EU safeguards for data transfers (an adequacy decision or standard data protection clauses) apply.
  • Patient data: please do not send patient data by e-mail; should you do so, the Licensor processes and deletes it under section 7 of the End User License Agreement.

4. App store licence validation and subscription

The edition installed from an app store validates your subscription through that store's systems; this validation contains no patient data. The purchase takes place in the store's own purchase window; payment details (such as your card details) are handled by the store alone and never reach the Software or the Licensor. The store gives the Licensor sales reports (for example the number of purchases), from which you cannot be identified by name. The part below that applies to your store gives the details.

Microsoft Store (Windows)

The edition installed from the Microsoft Store validates your subscription through Microsoft's systems. This communication concerns licence and subscription status only and contains no patient data, meal plans, or health information. Microsoft's own privacy statement also applies to this process. Buying the subscription happens inside the application, in Microsoft's own purchase window.

Apple App Store (macOS)

The edition installed from the App Store validates your subscription through Apple's systems. This communication concerns licence and subscription status only and contains no patient data, meal plans, or health information. Apple's own privacy policy also applies to this process. Buying the subscription happens inside the application, in Apple's own purchase window.

TestFlight (macOS)

The edition installed from TestFlight checks through Apple's systems whether the Software was installed from TestFlight; this check contains no patient data either.

TestFlight is a service of Apple. While you use the edition installed from TestFlight, Apple also collects data and passes part of it on to the Licensor; Apple's privacy notice for TestFlight governs this:

  • Crash logs and usage data (for example the number of installs, sessions and crashes, the installed version, your device's model and identifier, and your system's version and language): Apple collects these automatically and passes them on to the Licensor; this collection cannot be turned off. The Software adds no patient data to them.
  • Your name and email address: the Licensor sees these only if you joined the test through an email invitation; for testers who joined through a public link, they are not shown.
  • Feedback and screenshots: these reach the Licensor only if you send them in TestFlight. Please make sure your feedback and screenshots contain no patient data.
  • Purpose, legal basis and retention: investigating errors and fixing the Software; legal basis: the Licensor's legitimate interest in testing and fixing the Software (Article 6(1)(f) GDPR); the Licensor uses the data until the investigation is closed, and Apple keeps them under its own terms.

5. Your rights and how to lodge a complaint

Regarding the data described in sections 2–4, you may request access to them, their rectification or erasure, or the restriction of their processing, you may request data portability, and you may object to processing based on legitimate interest. We receive your request at gdlabs@outlook.hu and reply within one month at the latest.

If you believe that the processing of your personal data infringes the GDPR, you may lodge a complaint with a data protection supervisory authority — in particular in the EU Member State of your habitual residence, your place of work or the place of the alleged infringement (list of authorities: https://edpb.europa.eu/about-edpb/about-edpb/members_en). The competent authority for the Licensor is the Hungarian National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság, NAIH), 1055 Budapest, Falk Miksa utca 9–11., postal address: 1363 Budapest, Pf. 9., www.naih.hu, ugyfelszolgalat@naih.hu. You may also go to court; you may also bring the action before the court of your place of residence or stay.

Part B — Guide for the Data Controller: How the Software Handles the Data

6. Storage and encryption

The Software stores the data you record — including patients' names, contact details, health (for example anthropometric, body composition and laboratory) data and food diaries — on your computer: the database with industry-standard AES-256 (SQLCipher) encryption, and the documents uploaded for patients (for example a signed form or a lab report) in a separate folder, one by one, also with AES-256 encryption. It does not need a server of the Licensor to work, and the Licensor has no access to the data.

Windows The Software stores the encryption key encrypted with the operating system's data protection service (Windows DPAPI), bound to your user account. The program's data folder is in the roaming part of the user profile: if the computer runs with a roaming profile in an organisation's network, the profile — and with it the encrypted database and its key — may also be copied to the organisation's server; the organisation's system administrator can tell you more.

macOS The encryption key is stored securely in your operating system's keychain (macOS Keychain).

This protection works against other user accounts and against anyone who accesses your account without its password, but not against malicious programs running in your logged-in account (e.g. ransomware) — protecting your user account and your computer is therefore your task. The master password is the lock of the Software, not an encryption key: if you forget it, you can unlock the Software with the recovery code; if you lose both, the Software cannot be unlocked. If the key store of the operating system is lost (for example when the system is reinstalled), the database can only be restored from a backup or — with cloud sync turned on — from the sync folder. The Licensor cannot help in either case.

7. What can leave your computer?

The Software sends nothing on its own. Data can leave your computer in three cases:

  • Cloud sync — if you turn it on (section 8).
  • Bug report — if you create and forward it (section 2).
  • Licence validation — through the app store, without patient data (section 4).

In addition, the files you extract (section 9) go wherever you save them.

8. Cloud sync

If you turn on cloud sync in the Settings, the Software also writes the database and the documents, encrypted (AES-256) with a key derived from your sync passphrase, to a folder you choose — typically a folder synchronised by a cloud storage provider — and from there they reach your other connected computers.

  • Who has access: only someone who knows the sync passphrase can read the content; the Licensor cannot, and the cloud provider sees only the encrypted files.
  • What is visible unencrypted: only the technical data needed for coordination: the names and identifiers of the computers, the times and sequence numbers of synchronisation, the version of the Software, and a fingerprint used to check the passphrase (not the passphrase itself). The name of a computer may also contain your name.
  • Earlier states: the five most recent earlier states remain in the folder and are deleted automatically after five further synchronisations; the Software has no influence on the cloud provider's own version history and recycle bin.
  • The role of the cloud provider: the cloud provider is your processor (Article 28 GDPR), and depending on its seat or data centres, the data may also be transferred to a third country (Chapter V GDPR). Choosing the provider and your legal relationship with it — the data processing agreement (typically offered for organisational and business accounts, not for personal ones) and the safeguards for the transfer — are your decision and responsibility as the data controller; the Licensor is not a party to them.
  • The passphrase: if you lose the sync passphrase, the content of the sync folder cannot be recovered.

9. Outgoing files and the GDPR export

  • Backup (.ddb): a backup created with the built-in feature is encrypted and can be opened with the password you set; if you lose the password, the backup cannot be recovered.
  • Unencrypted files: the GDPR export (JSON), the ZIP package that also contains the documents, PDFs and CSVs are unencrypted, and their file names may contain the patient's name — storing, transferring and, where required, deleting them is your task.
  • What does the GDPR export contain? The patient's personal and health data, the history of measurements and the weight log, diagnoses, notes, medications and lab results, the entries recording the confirmed addition of meals containing a recorded allergen, the food diary and the list of uploaded documents; the files of the documents are provided by the separate ZIP package. Meal plans are not part of the export; you can provide them, where required, with the Planner's PDF. The export is a tool: you, as the data controller, are responsible for fulfilling a request for access or data portability.

10. Your tasks as the data controller

Because you are the controller of patients' data, the following are your tasks:

  • Legal basis: you must determine and document the legal basis for processing patient data (Article 6 GDPR) and, for health data, the condition under Article 9(2). The Software lets you store a consent form or another document; this does not mean that consent is the appropriate legal basis, and the Software provides no legal templates.
  • Informing patients about the processing (Article 13 GDPR) — this Part B gives you the facts for it — and about the Software recording among the patient's data when you add a meal containing an allergen recorded for the patient to the meal plan after confirming the signal.
  • Protecting the computer and the user account (a strong password, a screen lock, system updates, antivirus software) and making regular backups with the Software's built-in feature.
  • Choosing the cloud provider and the agreement with it, if you use cloud sync (section 8).
  • Responding to data subjects' requests (access, rectification, erasure, portability) — sections 9 and 11 help with this. Without a subscription, patients' data can be exported and deleted, and every other function — including opening and editing a patient's record — is locked (End User License Agreement, section 5). The data of a patient archived on the Entry plan — together with their documents — can be exported and deleted; they can be rectified with a Pro subscription (End User License Agreement, section 5).

11. Deletion and retention

Deleting a patient removes the patient's record and the documents uploaded for them from the Software; with cloud sync turned on, the deletion reaches your other connected computers at the next synchronisation. Before deleting, you, as the data controller, must check whether a retention obligation applies — for example, if you keep health records, their retention period is set by law (Article 17(3) GDPR). The Software does not set a retention period; its notice about patients inactive for 6 months is a reminder to review, not a legal deadline. Archiving a patient is not deletion and does not count as the patient's activity: an archived patient's data are kept, and the 6-month notice offers them for review too.

Deletion does not affect copies outside the Software or elsewhere on the computer; deleting them is your task:

  • the five most recent earlier states of the sync folder (deleted automatically after five further synchronisations), and the cloud provider's own version history and recycle bin;
  • the .ddb backups you created;
  • exports (JSON, ZIP), PDFs and CSVs created earlier;
  • an encrypted safety copy in the program's data folder, made before an import (restore) or before joining cloud sync;
  • the PDF previews (of the Patient Summary and of the meal plan) in the temporary folder, until the next launch of the Software;
  • traces of deleted data in the free space of the database file — encrypted — until they are overwritten.

A factory reset deletes the database, its temporary and safety copies and the document store from this computer; it does not delete the sync folder, the backups or the exports. It cannot be started while cloud sync is turned on.

Ingredients and recipes: if you delete an ingredient or a recipe from the catalogue, its name and nutritional values are preserved inside previously created meal plans, so that earlier calculations are not distorted after the fact. This applies to the catalogue, not to patient data.

Changes to This Policy

The Licensor may update this policy with updates of the Software. The version currently in force is always available inside the Software under About → Privacy Policy, carrying the "Last updated" date shown above.