Caredmeds Privacy Policy
Last updated: November 12, 2026
Caredmeds is a medication reminder app. This policy explains what data is collected, why, on what legal basis, how long it is kept, who receives it, and what rights you have. It applies to the Caredmeds app on iPhone and Android and to the website caredmeds.com.
In short:
- Reminders work without an account, and your medications, doses, schedules and history are stored on your phone.
- We never receive them in readable form, except what is described in section 4 about the alerts to someone close: the times of the doses of the medications you chose, whether they were marked, and when to send a stock alert.
- The medication name, the dose and the gender wording travel between the phones end to end encrypted, and our server cannot read them.
- The app has no ads, no tracking and no analytics or measurement SDK. We do not sell personal information.
- The website caredmeds.com does not use cookies, analytics or tracking.
1. Who is responsible
The controller of your data is:
Oren Mintz, a sole proprietor (osek murshe) registered in Israel
Business registration number: 043020163
Address: Givatayim, Israel
Privacy email: support@caredmeds.com
Data protection officer: no separate officer has been appointed. Privacy requests go directly to the controller, at support@caredmeds.com.
Requests from the EU and the UK: you can contact us directly, at the same address: support@caredmeds.com.
2. Using the app without an account
You can use Caredmeds without an account. In that case reminders, history, profiles, the PDF report, backup export and stock tracking work on your phone only, and nothing about them is sent to us.
What is stored on your phone: medication names, doses, schedules, the history of what was marked, profiles (yours, or of another person whose medications you manage), stock and recorded purchases, and the Hebrew wording form you chose.
- Reminders are local notifications shown by your phone. They do not pass through us.
- Phone backup: if your phone backs up to iCloud or Google, the app data is included in that backup, according to your settings and to Apple's or Google's policy.
- Backup export and PDF report: the file is created on your phone, and you decide whether to send it and to whom.
- Camera: the app asks for camera access only to scan the QR code that connects someone close. The image is not stored.
3. Account
An account is optional. It is needed only to connect someone close, or to receive alerts about someone close. It is used to sign in, to keep your subscription, and to connect someone close.
What is stored: your sign in email, a random account identifier, and the sign in method (email code, Apple or Google). When you sign in with Google or Apple, our server removes the name and picture they hand over and does not keep them. If you sign in with Apple and hide your email, we only receive Apple's relay address.
The sign in code by email is sent through an email delivery provider (see section 7).
Why: to let you sign in, to identify who is connected to an alert, and to link the subscription to the account.
4. Alerts to someone close and the stock alert (the "Close Circle" subscription)
4.1 Alert when a dose was not marked
The alert to someone close is off until you turn it on, and it only covers the medications you choose. Before it is turned on, a separate consent screen is shown with a box that is not ticked in advance. When the medications belong to another person (for example a parent or a child), there is a second box where you confirm that they know and agree, or that you are their parent or guardian.
What the close person sees: the name, dose and time of a dose that was not confirmed, in their app and in their notifications, if you agreed to share names, and only for medications you did not hide. They also receive the wording form you chose, so that the alert is worded correctly, and they see the name they gave you on their own phone. What is shown on their phone is outside our control (for example a screenshot).
Encryption: the name, the dose and the wording form are encrypted end to end between the phones, with a key exchanged in the QR code. Our server stores them only in encrypted form and cannot read them.
What our server stores in readable form:
- A random pairing code.
- The account identifier of each paired person.
- The notification address of each close person's phone, its system (iOS or Android) and its language.
- The times the doses of the chosen medications are due, and whether each one was confirmed.
- When, in which version and in which language consent was given, and whether it was also given on behalf of another person.
The alert itself passes through the notification services of Expo, Apple and Google with a general text (for example "A scheduled dose was not confirmed (08:00)") and the encrypted details, never the name in readable form. The close person's phone decrypts the details. Whether a medication name appears on their lock screen depends on the settings on their phone; by default it is shown only after the phone is unlocked.
4.2 Stock alert
The stock alert is a separate switch and is off until you turn it on, and it is part of the subscription. How much you have left is kept on your phone only. The close person sees which medication is running low and about how many days are left, if you agreed to share names, and only for medications you did not hide. Otherwise they see only that a medication is running low, with no name. The name and the number of days are encrypted end to end, and our server stores only when to send the alert and how many medications it covers.
4.3 When the subscription ends
If the subscription ends, alerts to the close person are paused and the connection is not deleted. The close person receives a one time notice, with no medication name, that alerts are paused. Your stock data stays on your phone and is locked for viewing.
4.4 If you receive alerts (the close person)
To receive alerts you need an account (section 3). Our server stores your account identifier, the notification address of your phone, its system and its language. What you receive is shown in the app on your phone.
Scanning the code on Android: on Android, scanning the code on the close person's phone uses Google ML Kit. The scan itself happens on the phone. ML Kit sends Google diagnostics and usage data: an installation identifier that is not meant to identify you or your device, the device model and system version, the app package name and version, and performance metrics. This data does not reach us. On iPhone the scan does not use ML Kit.
5. Buying the subscription
The Close Circle subscription is bought through Apple or Google. The purchase is managed by RevenueCat, our purchase provider, which receives an opaque identifier of your account (or an anonymous identifier when you buy without an account) and the purchase details, with no medication name and no health information. Our server keeps an entitlement record: which subscription, the period type and the expiry date, so that it knows whether to send alerts. Whoever takes the medication pays, and the close person does not.
We do not receive card or payment details. Payment is processed by Apple or Google under their own terms and policies.
6. Purposes, legal bases and retention
| Data | Purpose | Legal basis under GDPR | How long it is kept |
|---|---|---|---|
| Medications, doses, schedules, history, stock, wording form (on the phone only) | Reminders and tracking | Does not reach us | Until you delete them in the app or delete the app. Phone backups follow your settings |
| Email, account identifier, sign in method | Sign in, connecting someone close, linking the subscription | Performance of the contract with you (Art. 6(1)(b)) | Until the account is deleted |
| Dose times and whether they were confirmed (health data) | Sending the alert to someone close | Explicit consent (Art. 9(2)(a) and Art. 6(1)(a)) | 48 hours after the dose is due. Turning the alert off deletes everything immediately |
| Encrypted name, dose and wording form | Showing the alert on the close person's phone | Explicit consent (Art. 9(2)(a)) | As for dose times |
| Stock alert time and number of medications | Sending the stock alert | Explicit consent (Art. 9(2)(a)) | 48 hours after the send time. Turning the switch off deletes what is waiting |
| Pairing code, member identifiers, notification address, language | Running the connection | Performance of the contract, and for the person taking the medication also consent | As long as the connection exists. Disconnecting deletes it immediately. A connection the medication taker's phone has not synced with for 30 days is deleted |
| Consent record (when, version, language, on behalf of another) | Proof that consent was given | Legal obligation to demonstrate consent (Art. 7(1)) | As long as the connection exists |
| Pairing invitation (QR code) | Connecting | Performance of the contract | The code is valid for 10 minutes and deleted one day after it expires |
| Failed join attempts | Protection against code guessing | Legitimate interest (Art. 6(1)(f)): security | One day |
| Subscription entitlement record | Checking whether to send alerts | Performance of the contract | Until the account is deleted |
| Purchase data at RevenueCat | Managing the subscription | Performance of the contract | Until the account is deleted, when we ask RevenueCat to delete it. For a purchase without an account, until you ask us by email to delete it (section 9) |
| Sign in event log (email and user identifier, without IP) | Securing sign in and troubleshooting | Legitimate interest (Art. 6(1)(f)): security | 7 days |
| Technical request logs, including IP addresses, at our hosting provider | Running and securing the server | Legitimate interest (Art. 6(1)(f)) | A short period, under the provider's policy |
| ML Kit diagnostics (Android, at Google) | Running the code scanner | Collected by Google directly and does not reach us. To the extent we are responsible: legitimate interest (Art. 6(1)(f)), a working scanner | Under Google's policy |
IP addresses and logs: we do not store the IP address or user agent of a sign in in our database. The sign in event log keeps the email and user identifier, without IP, and is deleted after 7 days. Our hosting provider keeps request logs that include IP addresses for a short period.
Temporary guest account: if a temporary guest account (with no email) is created on the server during connection, it is deleted automatically after 30 days unless it became a regular account.
Under Israeli law: you are under no legal obligation to give us any data. Giving it depends on your will and your consent. Without an account and without consent, reminders work as usual, and only the connection to someone close does not. The data is used only for the purposes in the table.
What we do not do: the data is not used for advertising, statistics or profiling, and is not passed to anyone other than the providers in section 7. There is no automated decision making with legal effect on you.
7. Providers that process data for us
| Provider | Role | What data | Where |
|---|---|---|---|
| Supabase | Server, database and account sign in | Everything in sections 3 to 5 that is stored on the server, and technical logs | Server in Frankfurt, Germany. US company |
| Expo (650 Industries) | Notification service for alerts to someone close | Notification address, general text and encrypted details | USA |
| Apple (APNs) and Google (Firebase Cloud Messaging) | Delivering notifications to the phone | As for Expo | USA |
| RevenueCat | Purchase management | Opaque or anonymous identifier and purchase details | USA |
| Apple and Google | App stores, payment, and Sign in with Apple or Google | Purchase and sign in data, under their own policies | USA and elsewhere |
| Resend | Sending the sign in code by email | Email address and sign in code | US company, data may be processed in the USA |
| Google (ML Kit) | Code scanning on Android | Diagnostics and usage data (section 4.4) | Under Google's policy |
Providers process the data under their data processing terms. For some of their services (the app stores, payment and sign in), Apple and Google also act as independent controllers, under their own policies.
8. International transfers
Our server is in the European Union (Frankfurt). The controller is in Israel, which benefits from an EU adequacy decision. Some providers in section 7 are US companies, so data may be transferred to the USA or be accessible from there. These transfers rely on the EU-US Data Privacy Framework where the provider is certified under it, or on the EU Standard Contractual Clauses (SCC).
9. Deletion
- Deleting the account in the app: Settings > Account > Delete the account. This deletes the account, the connections, our entitlement record, the customer record at RevenueCat, and the data on the phone. If you signed in with Apple, we also revoke the sign in authorization with Apple.
- Without an account: Settings > Your data > Delete all data. We hold no data about you on the server.
- Without the app: request by email, as described at https://caredmeds.com/delete
- Disconnecting a close person or turning the alert off deletes that connection's data from the server immediately.
Database backups at our hosting provider may contain deleted data until they are rotated in the provider's backup cycle. The deletion page lists what is deleted and what remains.
Deleting the account does not cancel the subscription in the store. To stop paying, cancel it in the App Store or Google Play settings.
Purchases without an account: If you bought the subscription without an account, we hold no data about you on our server. RevenueCat keeps a purchase record with an anonymous identifier. You can ask us to delete it by email at support@caredmeds.com, with the subject "Delete a purchase without an account". So that we can find the record, include the order number from your Apple or Google Play receipt. Once we find it, we will ask RevenueCat to delete it and confirm by email within 30 days at most. If we cannot find a record from the details you gave, we will tell you.
10. Your rights
Everyone
You can contact us at any time at support@caredmeds.com to access, correct or delete your data, or to withdraw consent. Withdrawing consent does not affect the lawfulness of what was done before. We answer within 30 days. To protect you, we will ask to confirm that the request comes from the account holder, usually by email from the account's address.
Israel
Under the Privacy Protection Law (5741, 1981) you have the right to review the data about you (section 13) and to ask to correct or delete data that is not correct, complete, clear or up to date (section 14). You can file a complaint with the Privacy Protection Authority.
European Union and United Kingdom
Under the GDPR and the UK GDPR you have the right to access, rectification, erasure, restriction of processing, data portability, to object to processing based on legitimate interest, and to withdraw consent at any time. You can lodge a complaint with the data protection supervisory authority in the country where you live or work, and in the UK with the ICO.
United States
We do not sell personal information and do not "share" it for targeted advertising, as those terms are used in the California Consumer Privacy Act (CCPA). We do not use sensitive information to infer characteristics about you. Residents of California and of other states with privacy laws may ask to know what data was collected, to correct and delete it, and to appoint an authorized agent to make a request on their behalf. We will not discriminate against anyone for exercising a right.
Consumer health data (including Washington's My Health My Data Act and Nevada): the health data we receive is the times of the doses of the medications you chose and whether they were marked, and the times of stock alerts, and in encrypted form also the medication name, the dose and the wording form. It is collected only with your consent, only to send the alert to the close person you connected, and is passed only to the providers in section 7 for that purpose. We do not sell it. You can ask us to confirm whether we hold such data, to receive a copy, to delete it, and to withdraw consent.
11. Children
Caredmeds is intended for adults aged 18 and over. People under 18 should not create an account or buy a subscription. You can manage a child's medications in the app, and that data stays on the parent's phone. If it is shared with someone close, the parent or guardian confirms this on the consent screen. If we learn that an account belongs to a minor, we will delete it.
12. Security
Communication with the server is encrypted (HTTPS). The medication name, the dose and the wording form are encrypted end to end, and the key never leaves the phones except in the QR code. In the database each user can access only their own connections. The server's administrative keys are not in the app. No system can guarantee complete security, and if a security incident requires notice, we will give notice as required by law.
13. Changes to this policy
If we change this policy materially, we will tell you in the app before the change takes effect. If the change affects what the close person sees, we will ask for consent again. The current version is always at https://caredmeds.com/privacy
14. Contact
Privacy questions and requests: support@caredmeds.com
Oren Mintz, Givatayim, Israel