Privacy Policy
Effective date: 16 August 2026 Last updated: 26 September 2026
Summary
The Remedies iOS application (the “App”) does not collect personal data.
The App has no user accounts and no server-side component. It makes no network requests of its own; the only network activity associated with it is Apple’s in-app purchase flow. It contains no analytics, advertising or crash-reporting services. Data entered into the App is stored on the user’s device in encrypted form and is not transmitted to the Developer or to any third party. The Developer has no access to that data and is therefore not in a position to disclose it.
The sections below set this out in detail.
1. The Developer
The App is developed by Ivan Davydov, an individual entrepreneur registered in Georgia (the “Developer”). No company or other legal entity is involved.
Contact: ivandavy@remediesapp.com, Batumi, Georgia. The Developer’s full registered address is available to a supervisory authority on request.
The Developer does not process the personal data entered into the App (see Section 3) and is therefore not a controller of that data. The Developer is a controller only of data that a user sends to the Developer directly, such as the contents of a support email.
2. Scope
This Privacy Policy applies to the App. It does not apply to the App Store, which is operated by Apple under Apple’s own privacy policy.
3. Data collected
The Developer does not collect personal data through the App.
In particular, the App does not:
- create user accounts or request a name, email address or telephone number;
- transmit data entered into the App over the network, whether to the Developer or to any third party;
- include analytics, attribution, advertising or crash-reporting software development kits;
- track users across apps or websites, and for that reason does not request tracking permission;
- access contacts, location, health records, the calendar or the microphone.
The only network activity associated with the App is Apple’s in-app purchase flow (see Section 9).
4. Data stored on the device
The data listed below is stored on the user’s device only. None of it is transmitted to the Developer.
| Category | Storage |
|---|---|
| Medicines, strengths, quantities, expiry dates, labels and user notes | Encrypted app storage |
| Courses, schedules and logged doses | Encrypted app storage |
| Photographs of packaging and patient leaflets | Encrypted files in the App’s private storage |
| Reminder settings and the in-app reminder history | Encrypted app storage |
| Language, theme and other preferences | Encrypted app storage |
Encryption. The data is encrypted with a key that is generated on the device and stored in the iOS Keychain. The key does not leave the device and is not accessible to the Developer.
Device backups. An iPhone backup, whether to iCloud or to a computer, includes the App’s data in encrypted form. The encryption key is included in the Keychain portion of the backup so that the data remains readable after a restore. An unencrypted computer backup does not transfer Keychain items to a different device; if such a backup is restored to new hardware, the App’s data will be unreadable. Before moving to a new device, the user should either use an encrypted backup or export the data (see Section 8).
5. Camera and photo library
The App requests the following permissions only when a feature that requires them is used:
- Camera — to photograph packaging or a patient leaflet.
- Photo library — to attach an existing image; and, separately, “add only” access, to save an image from the App to the photo library at the user’s request.
Images obtained in this way are stored in the App’s encrypted storage and are not uploaded.
6. Smart Scan
Text recognition on packaging and leaflets is performed entirely on the device, using Apple’s on-device text recognition and on-device language model. Neither the image nor the recognised text leaves the device, and neither is sent to the Developer or to any third party.
7. Reminders
Reminders are scheduled locally by iOS. The App does not use a push-notification server and has no means of sending notifications from outside the device. The content of reminders shown on the lock screen is set by the user; by default, a reminder does not include the name of the medicine.
8. Data subject rights
As all data is held on the device and the Developer holds none of it, most rights are exercised directly in the App:
- Access and portability. Settings → Data → Export a backup creates a zip archive of all data in the App — the records in JSON format, together with the packaging and leaflet photographs — and passes it to the iOS share sheet. So that it can be opened on any device, the archive is not encrypted. It should be handled with the same care as the data it contains and stored in a private location. The App does not send the archive anywhere; its destination is chosen by the user. Settings → Data → Restore from a backup restores an archive, replacing the data currently in the App.
- Erasure. Deleting the App removes its data from the device. The Developer holds no copy. Copies in device backups or exported archives remain under the user’s control.
- Rectification. Any record can be edited in the App.
Users in the United Kingdom or the European Union also have the right under the GDPR to lodge a complaint with a data protection supervisory authority, and to request from the Developer access to, rectification, erasure and restriction of processing of personal data the Developer holds about them, to object to its processing, and to receive it in a portable format. In practice these rights extend only to correspondence the user has sent to the Developer, as the Developer holds no other personal data.
9. Disclosure to third parties
The Developer does not sell, rent or otherwise disclose user data, as the Developer does not hold it. The Developer uses no third-party processors, advertising providers or analytics providers.
Purchases of Remedies Plus are processed by Apple. Apple informs the Developer that a purchase has been made; the Developer does not receive the purchaser’s name, payment card details or billing address. Apple’s processing of that data is governed by Apple’s privacy policy.
10. Children
The App is not directed at children. It is intended as a household organiser, and the information in it is entered by the adult using the App.
11. Security
Data held by the App is encrypted at rest, and the App makes no network connections of its own. The App runs within the iOS app sandbox, which prevents other apps from reading its files. The remaining risks are those common to any data stored on a phone, in particular use of an unlocked device by another person and unencrypted computer backups (see Section 4).
12. Changes to this Privacy Policy
If the App begins to collect any data — for example, if optional cloud synchronisation is introduced — this Privacy Policy will be updated before that version of the App is released, and the change will be indicated in the App. The “Last updated” date at the top of this document shows when it was last amended.
13. Contact
ivandavy@remediesapp.com