Last updated: 14 October 2026
This policy describes how WE uses data when you set reminders, receive them, or use optional features.
WE is an app for medication, check-in and supply reminders for yourself or for a person you care for. The person who sets reminders up is called the caregiver here; the person who receives and confirms them is the person being cared for.
Contact: we.reminder.app@gmail.com
This data is treated as health-related information. See §4.
A caregiver may add a voice note of up to 5 seconds to a hug. The note is stored in our database (Google Firestore, which encrypts data at rest). Only the person the hug was sent to can play it, through our server; other accounts cannot read it. It can be played for at most 24 hours and is deleted automatically after that. This is separate from the voice message recorded for a reminder (§2).
If you use "schedule from a photo", your selected image is sent to our server and Google Vertex AI (Gemini) to extract reminder details. Our application does not save the image to its database or server files. We record scan usage; extracted details you choose to save become reminders. Google processes these requests under its cloud service terms.
If you subscribe, we store the record needed to verify the subscription with the App Store or Google Play: the store's transaction or purchase identifier, product, status, expiry and renewal state. Payment itself is handled by Apple or Google. We never see your card details.
Only when the weather line is turned on in the app's settings (the switch "Show today's weather"), the app requests a one-time approximate location from the phone each time the line refreshes, while the app is open. The phone asks for location permission only after that switch is turned on. The coordinates are sent to our server, which rounds them to a grid of about 28 km and sends only that grid point to a weather provider (Open-Meteo or Google's weather service) to get the forecast. The coordinates are not stored with the account. The forecast for each grid square is kept temporarily for up to one hour and is not linked to any account. To limit abuse, a counter of the account's recent weather requests is kept; it contains no location. The weather line can be turned off at any time in the app's settings, and location permission can be withdrawn in the phone's settings.
The app includes Firebase Analytics and Firebase Crashlytics SDKs (Google).
Our custom analytics events record actions such as creating or confirming a reminder, plus role, plan and scheduling flags. They omit reminder text, medication names, doses and personal names. These events also record whether the weather line was turned on or off and, when it could not be shown, a general reason (for example: no location permission, no location available, or no network connection), never a location. When analytics collection is active, the SDK can also collect app-instance identifiers, usage and purchase events, and coarse geography derived from masked IP addresses. Crash reports include technical error and device information. We do not explicitly attach the Firebase account UID, but device or installation identifiers still distinguish installations; this data should not be understood as anonymous.
These services support usage analysis and failure diagnosis. See Google Analytics data collection and Firebase disclosures.
We use data to provide and maintain the service:
We never use your data for advertising, sell it to third parties, or use it for marketing profiling.
Data is stored in Google Firebase/Firestore (Google Cloud infrastructure, in the United States). Our server code runs on Google Cloud Functions in the United States, and prescription photos are processed by Google Vertex AI there. Subscriptions are verified with Apple's and Google's store servers. Google acts as our data processor. Their policy: https://firebase.google.com/support/privacy
App access to reminders, confirmations and recordings is restricted to the linked caregiver and recipient by server-side access rules. Authorized server processing and administrative maintenance also access the data.
The reminder itself, the one that names what to take, is scheduled on the device as a local notification or, on supported iPhones, an AlarmKit alarm. Its title and dose are not sent through any push service.
Some notifications are sent from our server through Firebase Cloud Messaging (and, on iPhone, Apple's push service): telling the caregiver that a reminder was confirmed or is still unconfirmed, a hug, a notice that reminders have changed, and a backup ring when a phone has not yet picked up a new reminder. These may contain a person's name (the name the caregiver typed, or the sender's account display name for a hug) and a time. They never contain the reminder's title or dose.
The app is not directed at children and does not knowingly collect data from children.
The date above will be updated whenever this document changes. Material changes will be communicated in-app.