Skip to content

Hestova · iPhone · App Store

Privacy Policy

Version 1.3.1 — applies from 4 November 2026.

On this page

1. Who is the controller

The controller of your personal data is Enterla Stepan Kozurak, a sole proprietorship under Polish law (“Enterla”, “we”). Enterla develops and maintains the Hestova app and the hestova.enterla.app website.

  • address: ul. Michała Kleofasa Ogińskiego 11 lok. 9, 03-318 Warszawa, Poland
  • tax ID (NIP) 5223342496, business ID (REGON) 542334253
  • email for personal data matters: support@enterla.app

We have not appointed a data protection officer, because at the current scale of processing Article 37 GDPR does not require one. The owner of the business personally handles every data protection matter.

The Hestova app is currently available in Polish only. Where this policy names buttons or menus in the app, it gives the Polish name followed by an English translation in brackets.

2. What data we process

What data reaches us depends on whether you have an account.

Without an account. Everything you enter in Hestova — medications, doses, appointments, lab results, the wellbeing journal and your loved ones’ profiles — stays on your phone (and in your iCloud backup, if you have turned it on — section 7). We have no access to this data. The only exception is telemetry, if you turn it on (section 11).

With an account. Once you sign in, we store the following in the cloud (Supabase, Frankfurt):

  • account data: email address, account ID, your first name (or a nickname) as entered in the app, language and region setting, the dates you created the account and last signed in, sign-in session data (including the IP address and the app and system version you sign in from) and the record of your consent to storing health data (the text version and the moment you gave consent);
  • medications: name, dosage, number of pills per dose, supply and low-supply threshold, dose times, notes, prescription number and issue date;
  • dose log: scheduled time, time taken, number of pills and whether the dose was taken;
  • appointments: title, doctor, specialty, facility, date and time, notes, questions for the doctor and the answers;
  • lab tests and results: panel name, laboratory order number, sample collection date, whether the test was entered manually or imported, parameters (name, code, value, unit, reference range and how the value compares with the range);
  • wellbeing journal: energy, mood, nausea, headache, notes.

Medications, doses, appointments, results and the journal are health data (Article 9 GDPR). They concern you or the loved ones whose data you keep in the app (section 4).

What does not go to our cloud, even when you are signed in: your loved ones’ names and which person each entry belongs to, your date of birth (if you enter it) and your preferred form of address, and whether a medication has been archived. The app reads photos and PDF files with results on your phone. Only the values it reads go to the cloud, never the file itself.

Telemetry — only if you turn it on: pseudonymous information about how you use the app, with no health data (section 11).

Correspondence — when you write to support@enterla.app: your email address, the content of your message and any attachments, and our reply.

The hestova.enterla.app website — strictly necessary browser storage and visit analytics if you consent (section 12).

Purchases. Apple handles payments for the Premium plan. We do not receive your card number, your address or your purchase history. The app checks your subscription status on your phone and does not send it to our server. Withdrawal from Premium and refunds are also handled by Apple (Terms of Service, sections 6–8).

3. Why we process data and on what legal basis

DataPurposeLegal basis
Account: email, ID, name, dates, sign-in sessionssigning in with a code sent by email and running your accountArticle 6(1)(b) GDPR — the contract for using Hestova (Terms of Service)
Your health data in the cloudstorage, sync between devices, protection against loss when you change phonesArticle 9(2)(a) and Article 6(1)(a) GDPR — your explicit consent (section 6)
Your loved ones’ health data in the cloudthe same, for the people you care forArticle 9(2)(a) and Article 6(1)(a) GDPR — the consent of your loved one or of their parent or legal guardian (section 4)
Doctors’ details you enter with appointments (name, specialty, facility)storage in the cloud and sync together with the appointmentArticle 6(1)(f) GDPR — your legitimate interest and ours in keeping your appointment calendar
Consent record: text version and the moment consent was givenshowing when you consented and to which text (section 6)Article 6(1)(c) in conjunction with Article 7(1) GDPR — the obligation to demonstrate consent
In-app telemetrychecking which features work and which fail, and improving the appArticle 6(1)(a) GDPR and Article 399 of the Polish Electronic Communications Law — your consent (section 11)
Correspondence and complaintsreplying to messages, handling complaints, handling data protection requestsArticle 6(1)(c) GDPR — the obligation to respond to complaints (Article 7a of the Polish Consumer Rights Act) and to requests under Articles 15–22 GDPR; in other matters, Article 6(1)(f) GDPR — our legitimate interest in replying to messages; health data you send us (e.g. in a screenshot) with a complaint, a withdrawal from a contract, a claim or a data protection request — Article 9(2)(f) GDPR; in any other matter — except reports and orders (Terms of Service, section 10) — we do not use such data and we delete it from our mailbox straight after replying, unless you explicitly agree to our using it (Article 9(2)(a) GDPR)
A report of illegal content or an order from an authority: name and email address of the person reporting, the content of the report, the entry concerned, the email address of the account with that entry and our decisionhandling the report or complying with the order, notifying the decision and handling an appeal and, where there is a suspicion of a criminal offence threatening life or safety, notifying law enforcement authorities (Terms of Service, section 10); we pass the reporting person’s data to the user whose entry the report concerns only when strictly necessaryArticle 6(1)(c) GDPR — obligations under the Digital Services Act (Articles 9, 10, 16, 17 and 18 of Regulation (EU) 2022/2065); health data in the entry, including loved ones’ data — Article 9(2)(g) GDPR in conjunction with that Regulation (substantial public interest), and where the matter concerns claims — Article 9(2)(f) GDPR; when handling a report or complying with an order, we look only at the entry it identifies and, if we need to locate it, only at entries of that type from the period given; we handle an appeal against our decision as a complaint — on the legal bases in the “Correspondence and complaints” row
Technical logsservice security, detecting abuse, diagnosing errorsArticle 6(1)(f) GDPR — our legitimate interest in securing the service
Account deletion recordshowing that we deleted the accountArticle 6(1)(f) in conjunction with Article 5(2) GDPR — accountability
Website analyticsaggregate visit statisticsArticle 6(1)(a) GDPR and Article 399 of the Polish Electronic Communications Law — your consent (section 12)

Do you have to provide data? Your email address and consent to storing health data in the cloud are needed only to create an account. Without them, you use Hestova on your phone, without sync. Telemetry and website analytics are optional — saying no does not block anything in the app.

No profiling, no advertising. We do not profile you or make automated decisions about you (Article 22 GDPR). We do not sell data, show ads or track you across other apps or websites. We use health data only to store and sync it for you and, at your request, to give you a copy of it or delete it. We will look at the content of an entry only when we have to handle a report or an order from an authority (Terms of Service, section 10).

4. Your loved ones’ data

In Hestova you can keep track of the medications, appointments, results and journal of people you care for — for example your parents, your partner or your child.

Enter their data with that person’s consent, or as their parent or legal guardian. The app reminds you of this next to the consent on the sign-in screen and when you add a new person. Tell your loved one that you keep their data in Hestova and show them this policy. We do not know who they are, so we cannot inform them ourselves (Article 14(5)(b) GDPR).

Who is responsible for what. When you keep your loved ones’ data for your own family needs, you are covered by the exemption in Article 2(2)(c) GDPR (a purely personal or household activity), so the GDPR does not impose controller obligations on you. For your loved ones’ data that goes to the cloud once you are signed in, we are responsible as the controller. The household exemption does not cover the provider of the tool (Recital 18 GDPR).

What is in the cloud. Your loved ones’ names and which entries belong to which person stay on your phone and do not go to our cloud (iCloud backup is covered in section 7). In the cloud, your loved ones’ medications, doses, appointments, results and journal entries sit in your account together with yours, with no information about whose they are — unless you write that down yourself, for example in a note or in a question for the doctor.

Your loved one’s rights. The cloud holds no information that would let us establish whom an entry concerns, so we cannot identify your loved one ourselves (Article 11 GDPR). Therefore:

  • the simplest route is through you — you can correct or delete any of your loved one’s entries in the app;
  • your loved one can also write to us at support@enterla.app and give the email address of the account in which their data is kept. We will forward their request to that address. We cannot tell their entries apart from the account owner’s, so we cannot delete them selectively — we will tell them so plainly (Article 11(2) GDPR);
  • your loved one can withdraw their consent to you keeping their data at any time. If they do, delete their entries.

Deleting one person’s data. In this version of the app, a loved one’s profile can be deleted only once it has no entries — you delete each medication, appointment and lab test separately. We erase the content of a deleted entry from the cloud immediately (section 9). Deleting your account erases everyone’s data at once.

Notifications, the card and widgets. Notifications, the next-dose card (Live Activity) and widgets can show your loved one’s name and the medication name, including on the Lock Screen. Section 7 explains how to hide this.

5. Children

Hestova may be used, including without an account, by people aged 16 or over. Only such a person can create an account.

A child’s data can be kept by their parent or legal guardian — as a loved one’s profile in the parent’s or guardian’s own account. Consent to storing the child’s health data in the cloud is then given by the parent or guardian as the child’s legal representative. Everything in section 4 also applies to a child’s profile.

If you are a parent and believe that your child under 16 has created an account, write to us — we will delete it.

6. Consent to health data and how to withdraw it

When you give it. Before we send you a sign-in code, you tick the consent box — until you do, the “Wyślij kod” (Send code) button is disabled. The box is unticked every time the sign-in screen opens. The consent text (version 1), as the app shows it, with our translation:

Zgadzam się na przechowywanie moich danych o zdrowiu (leki i dawki, wizyty, wyniki badań, dziennik samopoczucia) przez Enterla, twórcę Hestovy, na serwerach w UE — żeby synchronizować je między urządzeniami i chronić przed utratą.

I agree to Enterla, the maker of Hestova, storing my health data (medications and doses, appointments, lab results, wellbeing journal) on servers in the EU — to sync it between devices and protect it from loss.

Below the box the app shows:

Dane bliskich, które prowadzisz w aplikacji, też trafią do chmury — wpisuj je za ich zgodą albo jako ich rodzic lub opiekun prawny. Zgodę wycofasz, usuwając konto w Ustawieniach. Logując się, akceptujesz Regulamin. Więcej w Polityce prywatności.

Your loved ones’ data that you keep in the app will also go to the cloud — enter it with their consent or as their parent or legal guardian. You can withdraw consent by deleting your account in Settings. By signing in, you accept the Terms of Service. More in the Privacy Policy.

What we record. When you create your account, we save in your account data the version of the consent text and the moment you gave consent (date and time in UTC). This lets us show when you consented and to which text (Article 7(1) GDPR). Later sign-ins do not change this record. If we widen the scope of what we ask you to consent to, we will ask for your consent again — your existing consent will not cover the new scope.

How to withdraw it. At any time:

  • in the app: Ustawienia → Konto → Usuń konto (Settings → Account → Delete account);
  • without signing in: write to support@enterla.app from your account’s email address (instructions: hestova.enterla.app/en/delete-account). We will reply to the account address asking you to confirm, and once you confirm, we will delete the account without undue delay, within one month at the latest.

In this version of the app, withdrawing consent means deleting your account and all data in the cloud — yours and your loved ones’. We delete it from the database immediately, and it disappears from backups within 10 days at the latest. Deleting your account in the app also erases the data on that phone (section 10 describes the exceptions). If you want to keep your entries, export them before deleting your account (a Premium feature) or ask us for a free copy of your cloud data.

Withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal (Article 7(3) GDPR). We delete the record of your consent — the text version and the date you gave it — together with the account.

Your other consents — to telemetry (section 11) and to website analytics (section 12) — can each be withdrawn separately, as easily as you gave them.

7. Where your data is

On your phone. Hestova’s data is kept in the app’s own storage on your iPhone, separated from other apps. If you have set a passcode, iOS protects this data with encryption. Without an account, it does not reach us.

In the cloud — once you are signed in. Supabase, servers in Frankfurt (Germany, EU). The connection with the app is encrypted (TLS), and so is the data on the servers (AES-256). Access rules in the database (Row Level Security) ensure that each account sees only its own entries.

Database backups. Supabase backs up the database every day and keeps each backup for about 8 days, so that we can restore data after a failure. Data you delete disappears from the backups within 10 days at the latest.

iCloud Backup. If you have iCloud Backup turned on, or you back up your iPhone to a computer, iOS also includes Hestova’s data in the backup: all entries, your loved ones’ names, unprocessed PDF files and widget data. Apple stores the iCloud backup in your account under the terms of your agreement with Apple, and a computer backup stays on your computer. We have no access to either of them and cannot delete them. If you do not want Hestova’s data in iCloud, turn Hestova off in the list of apps in the iCloud Backup settings for this iPhone. You can also turn on Advanced Data Protection — your iCloud backup is then end-to-end encrypted. You can encrypt a computer backup with a password in your iPhone’s backup settings on the computer. Hestova does not sync data through iCloud; that is what the account is for.

Notifications, widgets and Live Activities. iOS schedules dose reminders on your phone, without involving our server. Notifications, widgets and the next-dose card (Live Activity) can show the medication name, including on the Lock Screen. If you keep two or more people in Hestova, they also show the name of the person the dose is for. To stop notifications from revealing their content before you unlock your phone, set this in iOS: Settings → Notifications → Show Previews → When Unlocked. This setting does not hide the card or widgets. To hide them while your iPhone is locked, go to Settings → Face ID & Passcode (Touch ID & Passcode on iPhone with Touch ID) → Allow Access When Locked and turn off Live Activities and Lock Screen Widgets. This setting applies to all apps. To turn off only the Hestova card, go to Settings → Hestova → Live Activities. You can remove widgets from the Lock Screen and the Home Screen like any other widget.

8. Who we share data with

We use a few service providers. Each of them processes data only on our instructions, under a data processing agreement (Article 28 GDPR).

ProviderWhat it doesWhat dataWhere the data is and the basis for transfers
Supabase, Inc. (USA)database, sign-in, account deletionaccount, health data (yours and your loved ones’), consent record, technical logs, account deletion recordservers in Frankfurt (EU); possible support access from the USA under standard contractual clauses
Resend (Plus Five Five, Inc., USA)sending emails with sign-in codesemail address, content of the message with the codethe company is certified under the EU-U.S. Data Privacy Framework
PostHog, Inc. (USA)in-app telemetry — only once you turn it onpseudonymous events (section 11)servers in the EU (Frankfurt); access from the USA under the Data Privacy Framework and standard contractual clauses
Vercel Inc. (USA)website hosting, website analytics — with your consentIP address and browser data when you visit the website, visit statisticsthe website is served from the servers closest to the visitor; transfers to the USA under standard contractual clauses
OVH SAS (France)the support@enterla.app mailboxyour messages and email addressservers in the EU

Apple (Apple Distribution International Ltd., Ireland) sells Premium as our agent (Terms of Service, section 6), but it does not process data on our instructions — it acts as a separate controller. It runs the App Store, handles payments, subscriptions and refunds and, if you turn it on, stores your iCloud Backup. If you share analytics with app developers in your iOS settings, Apple gives us crash reports and aggregate statistics, without data that would identify you. Apple processes data under its own privacy policy: apple.com/legal/privacy.

Public authorities — we will disclose data to a court, a public prosecutor, the President of the Personal Data Protection Office (UODO) or another authority only when the law requires it.

Transfers outside the European Economic Area. We store health data in the EU. Some of our providers are US companies. Where they have access to data, it is based on the European Commission’s adequacy decision of 10 July 2023 for the EU-U.S. Data Privacy Framework or on standard contractual clauses adopted by the Commission (Implementing Decision (EU) 2021/914). We will send you a copy of these safeguards on request.

9. How long we keep data

DataHow longWhy
Account and health data in the cloud — yours and your loved ones’until you delete your account; it disappears from backups within 10 days of deletion at the latestthat is how long the service you asked for lasts
An entry you delete in the appwe erase the content from the cloud immediately; until you delete your account, a marker without content remains: the entry ID, its links (to the account and to the parent entry), the creation and deletion dates and, for a dose or an appointment, the scheduled timethe marker passes the deletion on to your other devices
Consent record (version and date)until you delete your accountproof of consent for as long as we store data on that basis
Account deletion record: SHA-256 hash of the account ID and the date3 years from account deletionshowing that we deleted the account; the hash does not contain the email address and does not let us work out whose account it was
Technical database and sign-in logs (IP address, account ID, time, type of operation)7 dayssecurity and error diagnosis
Log of emails with sign-in codes (email address, message content with the code)30 days at Resenddelivering messages and investigating delivery problems; the code itself expires after 15 minutes
Telemetry12 months from when the event was sentcomparing changes in the app over a year
Correspondence with us, including reports of illegal content, orders from authorities and our decisions (Terms of Service, section 10)one year from closing the matter; for a complaint or claim — until the limitation period expires; health data sent to us in a matter other than a complaint, a withdrawal from a contract, a claim, a data protection request, a report or an order (Terms of Service, section 10) — we delete it straight after replying or, if you explicitly agree to our using it (section 3), once the matter is closedreplying and defending against claims
Website logs (Vercel)up to 1 daydelivering the website and security
Website analyticsaggregate data; the hash Vercel uses to count visits is discarded after 24 hoursvisit statistics
Browser storage: hestova_cc and hestova-theme180 days (hestova_cc); until you delete it (hestova-theme)remembering your choice
Data on your phoneuntil you delete it, your account or the appit is under your control

Deleted entries on your phone. A deleted entry disappears from the app’s screens immediately. Deleting a medication or an appointment also deletes the entries that belong to it: doses and wellbeing journal entries, lab tests with their results, questions for the doctor. One exception: without an account, this version of the app does not delete the questions for the doctor from a deleted appointment — they stay in the app’s storage and are included when you export your data. In this version of the app, however, the content of a deleted entry may remain in the app’s storage on your phone — and so in its backup (iCloud or computer) — until you delete the app or your account, or use “Usuń wszystkie dane z urządzenia” (Delete all data from device) in Ustawienia → Eksport i dane (Settings → Export and data), and a backup made earlier keeps it until that backup is replaced by a newer one or deleted.

10. What disappears and what stays after you delete your account

Disappears immediately when you confirm “Usuń konto” (Delete account):

  • your account in the cloud: email address, name, consent record, sign-in sessions;
  • all health data in the cloud — yours and your loved ones’, together with the markers of deleted entries;
  • the data on that phone: entries, your loved ones’ profiles and names;
  • the telemetry ID — if telemetry was on, the app turns it off, and if you turn it on again, the app generates a new random ID.

Stays for a while, then disappears on its own:

  • database backups — up to 10 days;
  • technical logs with the IP address and account ID — up to 7 days;
  • the log of emails with sign-in codes at Resend — up to 30 days;
  • telemetry events sent before the account was deleted — up to 12 months from sending. They are not linked to the account, so we cannot single them out or delete them sooner;
  • the account deletion record (hash of the ID and the date) — 3 years;
  • your correspondence with us, if you wrote to us — as set out in section 9.

Is not deleted together with the account:

  • iCloud backups and computer backups made before the account was deleted — you can delete them in your iCloud settings or on the computer;
  • your Apple subscription — deleting the account does not cancel it. Cancel it in the App Store (on iPhone: Settings → [your name] → Subscriptions).

If you delete only the app, or use “Usuń wszystkie dane z urządzenia” (Delete all data from device) in Ustawienia → Eksport i dane (Settings → Export and data), the data on your phone disappears, but your account and your data in the cloud remain. They come back when you sign in again — without your loved ones’ names and which entries belong to whom, because those were only on the phone. To delete your data from the cloud, delete your account.

11. In-app telemetry

Off by default. You turn it on yourself in Ustawienia → Prywatność (Settings → Privacy). Without your consent, the PostHog tool does not start at all and the app sends nothing to it.

What we send once it is on:

  • events from a closed list (about 25), such as “medication added” or “appointments opened”, with numbers, yes/no values and values from a fixed list — never the name of a medication, doctor or test parameter, the content of a note, or anyone’s name;
  • a random installation ID, not linked to your account or email address;
  • technical data that the PostHog tool attaches to every event: device model, system and app version, language and region, time zone, network connection type and session ID.

What we do not collect. Location — we have turned off IP-based location lookup, and PostHog does not store the IP address itself. We do not link telemetry to your account or to health data.

Pseudonymous, not anonymous. The random ID together with the device data makes it possible to tell one installation apart from others. That is why we treat telemetry as personal data (Recital 30 GDPR). You cannot see the ID in the app and we do not link it to you, so we cannot pick out your events at your request (Article 11 GDPR). You can, however, stop sending them at any time.

Turning it off — at any time, with the same switch. At the moment you turn it off, the app may send events it has collected but not yet sent; after that it sends nothing. Withdrawing consent does not affect the lawfulness of earlier processing. We keep events for 12 months.

12. Website: cookies and analytics

Strictly necessary browser storage. The hestova.enterla.app website stores two things in your browser:

  • hestova-theme (localStorage) — your choice of light or dark theme; it has no expiry date, and you can remove it by clearing the website’s data in your browser;
  • hestova_cc (cookie) — your choice in the cookie banner; valid for 180 days.

Both are strictly necessary for the website to work in line with your choice, so they do not require consent (Article 399(3)(2) of the Polish Electronic Communications Law). We do not use them for anything else.

Website analytics — only with your consent. We use Vercel Web Analytics. It does not store cookies or any other data in your browser. On each page view, your browser sends Vercel the address of the page, the address of the page you came from and the time of the visit. From the request, Vercel determines your approximate location (country, region, city), operating system, browser and device type. It counts visits using a hash created from the request, which it discards after 24 hours; it does not store the IP address. We see only aggregate statistics. Legal basis: your consent (Article 6(1)(a) GDPR, Article 399 of the Polish Electronic Communications Law). You can change your consent at any time using the “Cookie settings” link in the footer.

13. Your rights

You have the right to:

  • access your data and get a copy of it (Article 15 GDPR) — you can see your cloud data in the app, and we will send you a free copy in CSV format on request;
  • have your data corrected (Article 16) — you can correct any entry in the app;
  • have your data erased (Article 17) — delete an entry or your whole account (sections 6 and 10);
  • restrict processing (Article 18);
  • data portability (Article 20) — we will send you a free copy in CSV format; with the Premium plan you can also export your data yourself, in the app;
  • object (Article 21) — described separately, below this list;
  • withdraw consent at any time (Article 7(3)) — sections 6, 11 and 12;
  • lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa, Poland, uodo.gov.pl), or with the supervisory authority of another EU country where you live or work or where the alleged infringement took place, if you believe we process your data unlawfully.

Right to object. On grounds relating to your particular situation, you may object at any time to processing that we base on our legitimate interest: technical logs, correspondence, the account deletion record and doctors’ details entered with appointments. We will then stop processing that data, unless we demonstrate compelling legitimate grounds that override your interests, or we need the data to establish, exercise or defend legal claims (Article 21(1) GDPR).

How to exercise your rights. Write to support@enterla.app — preferably from your account’s email address, so that we can confirm it is you. We will reply without undue delay, within one month at the latest. In a particularly complex case we may extend this period by two months — we will then tell you why within the first month (Article 12(3) GDPR). Exercising your rights is free of charge.

Without an account, your data does not reach us and we have no access to it. You view, correct and delete it yourself, in the app.

Your loved ones’ rights are described in section 4.

14. Security

  • Passwordless sign-in — with a one-time code sent by email, valid for 15 minutes.
  • Encryption — TLS protects the connection between the app and the server, and AES-256 encrypts the data on the servers.
  • Separated accounts — Row Level Security rules in the database ensure that each account can access only its own entries.
  • Files do not reach our servers — photos and PDFs with results are read on the device; only the values read go to our cloud. Your loved ones’ names do not go there either: the data sent to the cloud has no place for them, and automated tests check that entries carry no information about which person they belong to.
  • Backups — daily, each kept for about 8 days.
  • Administrative access — only the owner of the business has access to the database and to the providers’ dashboards, signing in with two-factor authentication. This access is used only to maintain the service, to fulfil your requests and to handle reports and orders concerning illegal content (Terms of Service, section 10).
  • No end-to-end encryption — cloud data is not encrypted on your phone before it is sent, so we technically have access to it.

Breaches. If a personal data breach occurs, we will notify the President of UODO within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to your rights (Article 33 GDPR). If it is likely to result in a high risk to you, we will inform you without undue delay (Article 34 GDPR).

15. Changes to this policy and versions

Version 1.3.1 applies from 4 November 2026. It clarifies sections 4 and 7: the next-dose card and widgets can show a person’s name, and section 7 explains how to hide or turn them off.

Before that, version 1.3 applied, from 30 October 2026 to 3 November 2026, version 1.2 from 20 October 2026 to 29 October 2026, and before it version 1.0, from 11 June 2026 to 19 October 2026. Version 1.1, published in September 2026 to take effect on the launch date, never took effect — version 1.2 replaced it. We will send previous versions on request.

We will inform you of significant changes at least 14 days before they take effect — by email to your account address, and, if you have no account, in the App Store update notes and on this page. A change that requires new consent will not apply to you until you give that consent. Minor corrections that do not change your rights or the scope of processing (for example typos or contact details) are made without notice and marked with a new version number.

16. Contact

For all matters concerning personal data — including your loved ones’ data — write to support@enterla.app. The owner of the business replies personally, in Polish or English.

Postal address: Enterla Stepan Kozurak, ul. Michała Kleofasa Ogińskiego 11 lok. 9, 03-318 Warszawa, Poland.

Deleting your account without access to the app: hestova.enterla.app/en/delete-account.