Privacy policy of the APPteczka app

In force from 11 October 2026. Applies to the APPteczka app for Android, iPhone and iPad and to the appteczka.eu website.

1. Who is responsible for your data

The controller of your data is Appifi Sp. z o.o., ul. Piotrkowska 276A, 90-361 Łódź, Poland. The company is entered in the register of entrepreneurs of the Polish National Court Register (Krajowy Rejestr Sądowy), kept by the Sąd Rejonowy dla Łodzi-Śródmieścia w Łodzi, XX Wydział Gospodarczy KRS, under KRS number 0001150929, NIP 7252351636, REGON 540700682. We publish the APPteczka app (in Italy the same app is called Cappsula). In this policy, “we” means Appifi Sp. z o.o.

You can also write to us by post at the company’s address. We reply to requests without undue delay, and within one month at the latest. In a complex case we may extend this period by two further months. If so, we will tell you why within the first month.

Data protection officer. We have not appointed a data protection officer. We handle all matters concerning personal data at rodo@appteczka.eu.

2. Why an account is needed

The app works only with an account. Medications, doses and the history of taking them belong to a particular person, not to a phone. An account lets you recover your medicine cabinet when you change phones, use it on several devices and manage it together with your family.

3. What data we collect, why and on what legal basis

Account data

Email address, name (you can enter any name you like) and the avatar colour the app uses to mark you among family members. If you create an account with a password, we store only a hash of the password computed with the scrypt algorithm. We don’t know the password itself. If you sign in with Google or Apple, we store the account identifier assigned by that company.

From version 2.14 we also store the account language (Polish, English, Spanish, French or Italian). The app sends it when you create an account, when you sign in and when you change the language in your profile. Older versions of the app don’t send it, and in that case we assume Polish. The account language determines the default name of your medicine cabinet and family, and after you sign in on another phone the app can open in the same language. We send the email with the code for creating an account in the language the app gives with the request for the code or, if it doesn’t give one, in the language of the phone’s settings.

For each medicine cabinet we store the cabinet country (currently Poland or Italy; existing cabinets are set to Poland). It determines which public medicines database we search when you scan a code or type a name. Any family member in that cabinet can change the country.

Legal basis: Article 6(1)(b) GDPR – the contract for the use of the app (terms and conditions).

Record of your consents and statements

When you accept the terms and conditions (together with the statement that you are at least 16) and give consent to the processing of health data, we record in your account the date, the version of the text (currently “2026-11”) and how you did it (for example sign-up by email, sign-in with Google or Apple, confirmation in the app). We record the statement and consent of a parent or legal guardian for child profiles in the same way (section 7).

Legal basis: Article 6(1)(c) GDPR in conjunction with Article 7(1) GDPR. The law requires us to be able to demonstrate that you gave your consent.

Health data

This is the core of the app. The following is sent to the server:

• medications: name, strength, form, active substance, codes (barcode, ATC code, register number), categories and colour;
• for medications added from a public medicines database (from version 2.14): which database it was (for example the Polish Register of Medicinal Products or AIFA open data) and the medication’s identifier in that database – the app uses it to open the package leaflet, also for family members;
• packs: boxes, number of units, expiry dates and stock;
• photos of packs, if you take them or the app picks them from the Open Food Facts database;
• schedules: times, days of the week, number of tablets per time and your notes;
• dose history: which dose you marked as taken or skipped, and when;
• child profiles and their medication plans (section 7);
• notification settings, for example whether your phone should remind you about a child’s doses.

This is data concerning health within the meaning of Article 9 GDPR. We process it solely on the basis of Article 9(2)(a) GDPR, that is, your explicit consent (section 4), and a child’s data on the basis of the explicit consent of a parent or legal guardian (section 7).

We use this data only to show you your plan, remind you of a dose, calculate your stock and show it to the people you choose to connect with in a family. We don’t analyse it for any other purpose.

APPteczka is a medication organizer — it is not a medical device and does not replace advice from a doctor or pharmacist.

Payments

You buy Premium on Google Play or the App Store. The store is the seller you deal with. The store handles payment, receipts and refunds under its own rules.

The store sends us confirmation of the purchase: a purchase token (Google Play) or a signed transaction (App Store). We verify it in order to turn on Premium. In your account we store: the plan, the store, the purchase confirmation and the date until which the plan is paid for. In the payment register we record the plan, the store, the list price and the date.

We don’t see your card details. Your card number, billing details and address never reach us.

Legal basis: Article 6(1)(b) GDPR (contract) and, for the payment register, Article 6(1)(f) GDPR – our legitimate interest in settling accounts with the stores and knowing our revenue. After you delete your account, the entry in the payment register remains, but without any link to you (plan, store, amount, date).

Account security

The server records events that matter for security: failed sign-ins, exceeded request limits, rejected purchase confirmations and errors. The record includes the time, type of event, IP address, account identifier (if the event concerns a signed-in person) and a short description. Email addresses appear in it only in masked form, for example jo***@domain.com. We don’t record the contents of your medicine cabinet there. We delete the entries after 90 days.

Legal basis: Article 6(1)(f) GDPR – our legitimate interest in protecting accounts from takeover and the service from abuse.

Server logs

The web server records the IP address, date and time, type of request, address of the requested page without query parameters, response code, response size and the browser or app identifier (user agent). The server’s system log records technical messages about the operation of the service and errors. We delete both after 14 days.

Legal basis: Article 6(1)(f) GDPR – protecting the service and fixing faults.

Correspondence with us

If you write to us, we keep your message, your address and our reply. We need them to deal with the matter and to be able to show how we dealt with it. The @appteczka.eu mailboxes run on our server in Poland. Messages to rodo@appteczka.eu go to the info@appteczka.eu mailbox.

Notifications about new messages. To handle email quickly we use AppifiPanel – Appifi’s internal tool for checking the status of our services. It runs on a server rented from OVH Hosting Inc. in Montreal (Canada). For every new message in the info@appteczka.eu and pomoc@appteczka.eu mailboxes, the panel:

• retrieves the sender, subject, date and the first 200 characters of the message;
• keeps them in its database in Canada for as long as the message is in the mailbox;
• sends a notification (subject, sender and an excerpt of the message) to the phone of the company’s owner through Google Firebase Cloud Messaging (Google LLC, USA).

This is a transfer of data outside the European Economic Area. We describe it in section 14. So don’t write about your medications or illnesses in your message unless the matter requires it. If you do describe them, we will use them only to reply to you.

Legal basis: Article 6(1)(f) GDPR – handling correspondence and establishing, exercising or defending legal claims, and for requests to exercise your rights also Article 6(1)(c) GDPR. We keep correspondence while we deal with the matter and then for up to 2 years after it is closed.

Contact form on the website. On the appteczka.eu home page you can write to us using a form. You choose a topic and give an email address for our reply and the text of your message and, if you like, your name. Our server checks these details and passes them on as an ordinary email to the mailbox for that topic, on the same server in Poland: help requests go to the pomoc@appteczka.eu mailbox and all other topics to info@appteczka.eu. From then on it is correspondence with us like any other, and everything described above applies to it, including AppifiPanel. We don’t store the text of the message, the email address or the name from the form in the app’s database or in the server’s system log. We don’t send anything automatically to the address given in the form – we reply ourselves.

To protect the mailboxes from spam, the form has a hidden field that only spam programs fill in and a time stamp signed by our server (it lets us reject a message sent faster than it could be written). The server also counts messages from a single IP address – only in its working memory, without writing anything to disk – and deletes these counters after a day. We record rejected attempts (for example after the limit is exceeded) as security events (time, type of event and IP address, without the message text and without the email address). The web server logs the sending of the form like any other request (see “Server logs” above). The form uses no third-party services and no cookies.

Legal basis: Article 6(1)(f) GDPR – our legitimate interest in replying to your message and in protecting the form and the mailboxes from abuse. We keep messages sent through the form in the same way as other correspondence.

What we don’t do

We don’t collect advertising identifiers, location, contacts or the list of installed apps. There are no ads and no analytics tools in the app or on the website. We don’t profile you and we don’t make automated decisions about you. We don’t sell data or pass it on to advertisers, data brokers or insurers.

4. Consent to the processing of health data

How you give it. Before you create an account – by email or with Google or Apple – you tick two separate boxes:

• acceptance of the terms and conditions, confirmation that you have read this policy and a statement that you are at least 16;
• separate, explicit consent to the processing of data concerning your health.

Without ticking both boxes, you can’t create an account.

What it covers. Consent version “2026-11” covers medications, doses and the history of taking them, photos of packs and – if you join a family – showing this data to family members (section 6). A parent or legal guardian gives separate consent for a child’s health data (section 7).

A new version of the consent. When we change the wording of the consent, the app asks you for it again. It also asks people who had an account before the app started asking for consent.

If you don’t give consent.

• If your account has no consent recorded and you choose “I don’t agree”, your account is suspended: the server doesn’t exchange health data with the app. For 30 days you can sign in again and give your consent. If you don’t, after 30 days we automatically delete the account and its data from the server.
• If you gave consent in an older version and don’t accept the new one, the app signs you out and asks again the next time you sign in. Until then we process data within the scope of your earlier consent. If you don’t want to use the app any more, delete your account or write to rodo@appteczka.eu.

How to withdraw consent. At any time. The simplest way is to delete your account in the app (section 15). You can also write to rodo@appteczka.eu. The app can’t work without health data, so withdrawing consent means deleting your account and its health data. Withdrawing consent doesn’t affect the lawfulness of processing before the withdrawal.

Deleting a single medication. When you delete a medication, we delete its contents (name, composition, packs, photo, dose history, times and notes) from the server immediately. Only a technical deletion marker (identifier and date) remains, which is needed so that the medication also disappears from other phones. We delete the marker after 30 days.

5. Ways to sign in

• Continue with Apple (on iPhone and iPad). Apple gives us a permanent identifier for your account and your email address. If you choose “Hide My Email”, we only receive a relay address (@privaterelay.appleid.com). Apple gives us your name only the first time you sign in.
• Continue with Google. Google gives us your account identifier, email address and name. We don’t receive your password or access to your email, drive or contacts.
• Email and password. When you create an account, we send a six-digit code to the address you entered. The code is valid for 15 minutes and can be entered at most five times. We store only a hash of it (HMAC). We delete the code entry once the code has been used, and an unused one when it expires.

If you sign in a second way with the same email address, we link it to the existing account.

A sign-in is valid on a given device for up to 365 days. Signing out removes the session from the phone.

Messages from @appteczka.eu addresses are sent by our own mail server. We don’t use mailing companies. We don’t send newsletters or advertising, only codes and important service messages.

Sign in with Apple and account deletion. When you delete your account, we don’t automatically revoke the link between APPteczka and your Apple ID. You can remove it yourself in your Apple ID settings, under “Sign in with Apple”.

6. Who sees your data

Just you. After you create an account, you have your own medicine cabinet. Nobody but you can see it.

Family. You can connect with your loved ones. Someone in the family shows you an invitation (a QR code or a link) that is valid for 24 hours. You ask to join, and someone in the family has to approve your request. Until then you don’t see the family’s data and the family doesn’t see yours. Before approval you see only the family’s name.

The person who approves your request chooses one of two settings:

• Shared cabinet (for example, you live together). Family members in the same cabinet see all the medications, packs, stock, expiry dates, photos of packs and child profiles.
• Own cabinet in the family (for example, Mum lives on her own and her children help her). Your list of medications, packs and stock stay yours.

In both settings every family member sees:

• your name, avatar colour and email address;
• your dose plan for today: the names and strength of the medications on your schedule, their times, the number of tablets and whether the dose has been marked as taken. That’s what the family is for, for example for people caring for older relatives.

Family members see only the plan for the current day. Because of time zone differences, the app may also download the plan for the previous and the next day. Family members don’t see older history of your doses.

Any family member can change the cabinet setting – including yours. Any family member can switch you to a cabinet shared with them or give you your own. If someone switches you to a shared cabinet, your medications are combined and the family members in that cabinet will see your full list of medications. You can check and change your setting in the app at any time.

Joining a family means showing family members your dose plan for the current day. If you don’t want that, keep a cabinet just for yourself. It works in exactly the same way.

Leaving the family. You can leave the family at any time. If you have your own cabinet, you take it with you, together with its medications and child profiles. If you were in a shared cabinet, the medications stay with the family members, because they are theirs too, and your schedules are no longer visible.

7. Child profiles

You can add a child under 16 to your medicine cabinet. The child doesn’t have an account and doesn’t use the app. The child’s data is entered by a parent or legal guardian in their own account. A person aged 16 or over creates their own account.

Statement and consent. When you add a child profile:

• you state that you are the child’s parent or legal guardian;
• you give separate, explicit consent to the processing of data concerning the child’s health (medications, doses, the history of taking them) and to showing it to the adults using the same cabinet.

We record the date, version and manner in which the statement and consent were given.

Legal basis: explicit consent (Article 9(2)(a) GDPR), given on the child’s behalf by the person with parental responsibility or by the legal guardian.

What we store: the child’s name (or any nickname) and colour, the child’s medications in the cabinet, schedules with times, doses and notes, the dose history including which adult marked each dose, and whether a given parent wants to receive reminders about that child’s doses. Each parent turns on reminders for themselves separately.

Who sees the child profile: all the adults in the same cabinet. Each of them can change the child’s plan and mark doses. Family members with their own cabinet don’t see the profile.

Older children. A teenager’s medications can be a private matter. Before you add a profile for an older child, talk to them about the fact that all the adults in the cabinet will see their medications.

For how long: until you delete the profile or for as long as the cabinet exists. The profile moves together with the cabinet, for example when you combine households. When you delete the profile, we delete the child’s name from the server immediately and the profile disappears from all phones. We delete the child’s medication plan and dose history from the server together with the technical deletion marker of the profile, within 30 days at the latest. If you delete your account and you are the only person in the cabinet, we delete the child profiles immediately, together with your account. If another adult remains in the cabinet, the profiles stay with them.

Withdrawing consent and the child’s rights. You can withdraw consent for the child’s data by deleting the child’s profile or by writing to rodo@appteczka.eu. The child’s other rights are exercised on the child’s behalf by a parent or legal guardian in the same way.

8. Shared code database

The app recognizes medications by their barcode. It takes the data from the public medicines database of the cabinet’s country (section 13) and, in Poland, the names of food supplements from the register of the Polish Chief Sanitary Inspectorate (GIS). Cosmetics and some medical devices are not in any of these databases.

If you scan the code of a product that isn’t in the databases and give it a name, the code together with the name (and the strength, form and manufacturer, if you enter them) goes into the shared code database. Other users will see this name as a suggestion when they scan the same code. With the entry we also record who added it (account identifier). We don’t show this to other users, and we remove the identifier from the entry when you delete your account.

Don’t enter personal data in the product name, for example “syrup for Annie K.”. Other users will see it.

Your photos don’t go into the shared database. A photo of a pack stays in your medicine cabinet and is seen at most by the family members in the same cabinet. Photos in the shared database come exclusively from the open Open Food Facts database.

Other users can’t see who has a given product in their cabinet or whether anyone takes it.

9. Reminders and widgets

Dose reminders are scheduled and shown by the phone itself. We don’t send you notifications over the internet (push). The “Today’s plan” and “Child’s plan” widgets read the plan from the phone’s memory.

Lock screen. A reminder contains the medication name and dose and, for a child, the child’s name too. On Android, reminders are marked as private: if you hide sensitive content on the lock screen in your phone’s settings, the phone shows only a general notification without the medication name. On iPhone, use the “Show Previews” setting in the notification settings.

The app asks for permission to send notifications and, on newer Android versions, for permission to use exact alarms. You can refuse. The app will work, but without punctual reminders.

When Premium ends, reminders for medications over the free plan limit are paused, but those medications and their history don’t disappear (details in the terms and conditions).

10. What stays on your phone

The app keeps a copy of your medicine cabinet in the phone’s memory: medications, plan, dose history, photos, the plan for the widgets and your sign-in details. This is why it works offline and reminders arrive on time.

After you sign out, the cabinet data stays on the phone. We delete it when another account signs in on that phone. If you want to delete it sooner, for example before giving the phone to someone, choose Profile → “Data on this phone” → Clear in the app. This deletes medications, dose history, photos and scheduled reminders from the phone. The copy on the server remains. You can also uninstall the app or clear its data in the phone’s settings.

After you delete your account, the app (from version 2.12.4) also deletes the data from the phone: medications, dose history, photos, reminders and the widget. If you delete your account in an older version or outside the app, uninstall the app or clear its data in the phone’s settings.

Phone backups.

• On Android, the app is excluded from backup, so its data doesn’t go into the backup in your Google account or to a new phone. After you sign in on a new phone, your cabinet comes back from our server.
• On iPhone and iPad, the app’s data may go into your iCloud backup, if you have it turned on. You decide about this backup in the device settings, and Apple stores it.

11. Where we store data and for how long

We keep app data on a server in Warsaw, rented from OVH Sp. z o.o. The connection between the app and the server is encrypted (TLS). APPteczka runs on the server as a separate service, under its own system user, isolated from other services.

Database backups. Every day at 3:30 we make a backup of the database. The backups are kept on the same server, in a directory accessible only to the APPteczka service. They don’t include photos and are not separately encrypted. We keep each backup for 14 days and then delete it. So data deleted from the database also disappears from the backups, within 15 days at the latest.

How long we keep data:

• Account and record of consents – for as long as you have an account.
• An account suspended for lack of consent – 30 days from the refusal. After that we delete it automatically together with its data (section 4).
• Your schedules and dose history – for as long as you have an account.
• Medications, packs and photos – until you delete them or for as long as the cabinet exists. A shared cabinet belongs to all the family members in it, so it remains for as long as at least one person is in it.
• Cabinet country – for as long as the cabinet exists.
• Child profiles – until the profile or the cabinet is deleted (section 7).
• Deletion marker of a medication, schedule or child profile – 30 days.
• Verification code when signing up – until it is used or, if unused, until it expires (15 minutes).
• Invitation to a family – valid for 24 hours. Request to join – until it is approved, rejected or withdrawn.
• Subscription and purchase confirmation – for as long as you have an account.
• Payment register – after you delete your account it remains without any link to you: plan, store, amount and date.
• Security events – 90 days.
• Web server logs and system log – 14 days.
• Cache of medicines database results (section 13) – a result is considered current for 7 days (an empty result for 24 hours), and the entry is deleted automatically 90 days after it was last fetched from the database. The entry is not linked to any account.
• Correspondence – while we deal with the matter and then for up to 2 years after it is closed. Entries in AppifiPanel – for as long as the message is in the mailbox.
• Contact form – the message in the same way as correspondence; counters of messages from a single IP address – in the server’s working memory, for up to a day.
• Names in the shared code database – without a time limit, with no link to your account once it is deleted (section 8).

Add to each period the time during which data still remains in the database backups (15 days at the latest).

12. Who at our company has access to the data

Only authorized Appifi personnel who are bound by confidentiality have access to the data. We manage the service through our own administration panel, protected by a password and a one-time code (TOTP). Every action in the panel is recorded in a log from which an entry can’t be removed unnoticed.

The panel deliberately doesn’t show the contents of medicine cabinets: medication names, doses, schedules or photos. It shows only account data (for example email, name, family name, plan) and server events. People with administrative access to the server can technically look into the database. We say this openly. We do it only when we need to fix a fault or carry out your request.

13. Who we share data with

We don’t sell data or share it for marketing purposes.

Companies that process data on our behalf (processors)

• OVH Sp. z o.o., ul. Swobodna 1, 50-088 Wrocław, Poland – rental of the server in Warsaw that holds all app data, the database backups and the appteczka.eu email.
• OVH Hosting Inc., Montreal (Canada) – rental of the server on which AppifiPanel runs. It receives excerpts of email messages (section 3, “Correspondence with us”) and service statistics. The statistics are only numbers – of accounts, subscriptions, revenue and server events – with no email addresses, IP addresses or account identifiers. They are not personal data.
• Google LLC (USA) – the Firebase Cloud Messaging service, through which AppifiPanel sends the company’s owner a notification about a new email message (subject, sender, excerpt of the message).

Companies acting as separate controllers

• Google Ireland Ltd. – if you sign in with Google (confirmation of identity) and if you buy Premium on Google Play (sale and payment).
• Apple Distribution International Ltd. – if you sign in with Apple and if you buy Premium on the App Store (sale and payment).

Barcode scanner

The barcode is recognized by the phone itself. We don’t send the camera image anywhere. On Android, the scanner uses the Google ML Kit library. Google may collect diagnostic data about how this library works, without the camera image and without the contents of your medicine cabinet. On iPhone and iPad, Apple’s built-in scanner is used.

External medication and product databases

The app uses public databases:

• the Polish Register of Medicinal Products on rejestry.ezdrowie.gov.pl (Centrum e-Zdrowia);
• if the cabinet is set to Italy, AIFA open data (Agenzia Italiana del Farmaco): we download the list of packs to our server periodically and search this copy;
• the European Medicines Agency (EMA) – Polish package leaflets of medications authorised across the European Union (the Polish register doesn’t hold them); once a day our server also downloads the public list of these medications;
• Open Food Facts – names and photos of products that are not in the medicines register;
• the register of food supplements of the Polish Chief Sanitary Inspectorate (GIS) – we download the list to our server periodically and suggest names from it.

The phone connects only to our appteczka.eu server. It’s our server that queries these databases, and it passes them only the search phrase or barcode, without your IP address and without account data. The databases don’t know who is asking.

Cache. We store results from databases that the server queries in real time (currently the Polish Register of Medicinal Products) in a cache: the search phrase or pack code, the medication found and the date it was fetched from the database, with no link to an account and no IP address. This way the same question doesn’t go to the register a second time, and if the register doesn’t respond, the app gets the last known result. The cache is a separate file on our server and is not included in the database backups (retention periods – section 11). For AIFA data, the server searches its own copy and doesn’t query anyone outside. From version 2.14 the app sends the phrase and code as query parameters, so they don’t end up in the web server logs (section 3, “Server logs”). In the system log, the server records only a short description of a database connection error. The server counts the number of requests to medicines databases from one account (protection against abuse) only in memory, in one-minute windows, and deletes the count within a few minutes at the latest.

Package leaflets. From version 2.15.1 the app shows the leaflet in its own viewer. Our server downloads the file from the Polish Register of Medicinal Products or from the European Medicines Agency and passes it to the app – neither the register nor the EMA sees your IP address. The server receives the medication’s identifier and register name as query parameters, so they don’t end up in the web server logs, and it doesn’t record who opened which leaflet. The result of checking whether a medication has a leaflet (for up to a day) and the file itself (for up to an hour) are kept only in the server’s memory, not linked to any account and without IP addresses. A leaflet from AIFA open data (cabinet in Italy) is downloaded by the phone directly from the AIFA server, and the “Open in browser” button and older versions of the app open the leaflet in your browser. In those cases you connect to the source service directly, as with any website you visit.

Public authorities

We may disclose data to a court, public prosecutor or other authority if it demands it on the basis of the law. We don’t do so in response to informal requests.

14. Transfers of data outside the European Economic Area

App data – account, medications, doses, photos, child profiles – does not leave the European Economic Area.

Only data from your correspondence with us (sender, subject, date and the first 200 characters of the message) goes outside the EEA:

• to Canada (AppifiPanel on the OVH Hosting Inc. server) – on the basis of European Commission Decision 2002/2/EC, which recognizes an adequate level of data protection in Canada (PIPEDA);
• to the USA (notification through Google Firebase Cloud Messaging) – Google LLC participates in the EU-US Data Privacy Framework, for which the European Commission adopted an adequacy decision on 10 July 2023.

Signing in with Google and Apple and purchases in the stores take place under the rules of those companies as separate controllers. Their own privacy policies describe this.

15. Your rights and how to exercise them

We accept requests at rodo@appteczka.eu. Write from the address linked to your account so that we know it’s you. You can take care of some things yourself in the app.

• Access and data portability. In the app: Profile → Download my data. You get a JSON file that contains:
  • account data: email, name, sign-in method and the record of your acceptance of the terms and of your consent to the processing of health data;
  • the medications in your cabinet and the medications you take on your own schedule, together with photos;
  • your schedules and dose history;
  • the child profiles in your cabinet with their plans and doses;
  • subscription and payment records;
  • the names you gave to products in the shared code database;
  • security events concerning your account.
  The file doesn’t contain medications from other family members’ own cabinets, because that is their data. We will provide other data (for example the record of consent for child profiles, correspondence) on request sent to rodo@appteczka.eu.
• Rectification. You can correct your name, medications and schedules yourself in the app. We change your email address on request sent to pomoc@appteczka.eu.
• Erasure. In the app: Profile → Delete account, confirmed with your password or – for a Google or Apple account – by entering your own email address. Deletion takes effect immediately. Instructions are also on the account deletion page. You can also write to rodo@appteczka.eu – we will then delete the account without undue delay, within one month at the latest.
• Withdrawal of consent to the processing of health data – at any time (sections 4 and 7).
• Restriction of processing – for example when you contest the accuracy of the data.
• Objection to processing based on our legitimate interest (security events, logs, correspondence, payment register).

What disappears when you delete your account:

• your account, record of consents, your schedules and your entire dose history, subscription, requests to join a family and notification settings;
• if you were the only person in your cabinet (including your own cabinet in a family): its medications, photos and child profiles;
• your traces in shared data: we remove your identifier from entries in the code database and from children’s doses you marked, and we delete invitations you created;
• in security events we remove the link to your account and mask email addresses; the entries expire after 90 days;
• in the payment register only a record without any link to you remains (plan, store, amount, date);
• the data on your phone, if you delete your account in the app from version 2.12.4 (section 10).

Medications in a family’s shared cabinet stay with the family members, because they belong to them too. Data disappears from the database backups within 15 days at the latest (section 11). Deleting your account doesn’t cancel your subscription in the store – do that on Google Play or the App Store.

Providing data is voluntary, but without an account and without consent to the processing of health data the app can’t work. It’s impossible to remind you about medications without knowing anything about them.

16. Complaint to a supervisory authority

If you believe that we process your data unlawfully, you have the right to lodge a complaint with a supervisory authority, in particular in the EU Member State of your habitual residence, place of work or place of the alleged infringement (Article 77 GDPR).

Our only establishment in the European Union is in Poland, so the lead supervisory authority for our processing (Article 56 GDPR) is the President of the Polish Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warsaw, Poland (uodo.gov.pl). You can contact UODO directly. If you lodge a complaint with the authority in your own country (in Italy, the Garante per la protezione dei dati personali), that authority receives it and handles it in cooperation with UODO, under the rules of the GDPR.

We encourage you to write to us first at rodo@appteczka.eu: the matter can often be resolved more quickly.

17. Security

We use an encrypted connection (TLS), password hashes computed with the scrypt algorithm, limits on sign-in attempts, separate accounts and one-time codes for the administration panel, and isolation of the service on the server. We accept photos only as JPEG files of limited size. No security measure is perfect.

If a personal data breach occurs, we will report it to the President of UODO within 72 hours of becoming aware of it, unless the breach is unlikely to put your rights at risk. If the breach is likely to result in a high risk to your rights, we will also inform you, without undue delay.

If you find a security vulnerability, write to rodo@appteczka.eu. We don’t take action against people who report bugs in good faith.

18. The appteczka.eu website, cookies and logs

The website uses only one cookie, and only if you choose a language in the language menu: the “lang” cookie remembers that choice for a year (365 days). It contains only the language code (for example “en”) and is used only so that the website opens in the language you chose. It isn’t used for tracking and doesn’t go to anyone other than our server. It’s a cookie that is strictly necessary for the service you request, so we don’t ask for consent to cookies. You can delete it at any time in your browser settings. The website doesn’t use any other browser storage and has no analytics tools. It doesn’t embed social media plug-ins, and it loads fonts and images from our own server. When you open the home page without this cookie, the server may send you to the version in your browser’s language. You download the app from Google Play or the App Store – the website only links to them.

When you visit the website, the server records the same logs as when you use the app (section 3, “Server logs”). We delete them after 14 days.

19. Age

You must be at least 16 to create an account. You confirm this by accepting the terms and conditions when you create the account. A child under 16 can have only a profile in APPteczka that is managed by a parent or legal guardian in their own account (section 7). If we learn that an account was created by a younger person, we will delete it together with its data.

20. Changes to this policy

We will tell you about important changes in advance, in the app or on the website. You will find the date of the version in force at the top of this page. If a change extends the scope of health data, we will ask you for new consent. Silence is not enough.

21. History of changes

• 11 October 2026 – package leaflets inside the app (from version 2.15.1): our server downloads leaflets from the Polish Register of Medicinal Products and the European Medicines Agency, the phone downloads AIFA leaflets; what we don’t record (section 13).
• 7 October 2026 – contact form on appteczka.eu: what data it passes on, where it goes, on what basis and how we protect it against spam (sections 3 and 11).
• 5 October 2026 – first English version. It corresponds to the Polish version of the policy in force from 5 October 2026 (as of version 2.14 of the app: account language, cabinet country, source database of medications, cache of medicines database results, language cookie on the website).