← Back to CareRing

Privacy Policy

Last updated: November 16, 2026

CareRing ("we", "us", "our") is a family caregiver coordination app operated by Vasil Nonchev, based in Sofia, Bulgaria. This Privacy Policy explains how we collect, use, store, and protect your personal data when you use the CareRing mobile application, the Wear OS companion app and related services.

We take your privacy seriously, especially given the sensitive nature of health-related information. We comply with the European Union General Data Protection Regulation (GDPR) and applicable Bulgarian data protection laws.

1. Data Controller

Vasil Nonchev
Sofia, Bulgaria
Email: privacy@carering.app

2. Data We Collect

2.1 Account Data (collected at sign-in)

DataSourcePurpose
NameGoogle Sign-InDisplay in care circles
Email addressGoogle Sign-InAccount identification

2.2 Health & Care Data (entered by you)

DataPurpose
Care recipient details (name, date of birth, primary diagnosis, insurance provider & policy number, emergency notes)Identifying and coordinating care for the person being cared for
Medication names, dosages, schedules, instructions, prescriber and pharmacy, and how a pill looks (colour, shape)Medication tracking and reminders
Medication administration logsAdherence tracking
Medication inventory (stock quantities, batches, expiry dates, storage locations, refills)Stock tracking and low-stock / expiry alerts
Storage locations you name (for example "Kitchen Cabinet", "Bathroom")Organizing medication inventory by room. These are only labels: we never collect GPS or location data
Daily check-ins (mood, pain, sleep, appetite, mobility, notes)Wellness monitoring
Medical conditions (name, diagnosis date, severity, notes) and allergies (allergen, severity, reaction)Medical information hub
Emergency contacts and emergency notesQuick access to important contacts
Appointments (type, doctor, location, address, phone, preparation and follow-up notes, date/time)Care schedule coordination
Care notesShared care documentation
Task assignmentsCaregiver coordination
Home / household organization and care circle invitationsGrouping members and inviting caregivers
Emergency (SOS) alerts you send from the phone or the watchAlerting the members of the care circle
Routines, achievements (streaks and milestones), your relationship to the care recipient and a nicknameOrganizing care and showing progress

2.3 Technical Data (collected automatically)

DataPurpose
Device push notification token (FCM)Sending medication reminders and task notifications
Crash reportsApp stability monitoring (via Firebase Crashlytics)
App version, device model, OS versionDebugging and compatibility
Time zone and notification preferencesScheduling reminders at the right local time
Subscription status (via RevenueCat)Managing your plan and entitlements
IP addressProtecting the service against abuse (rate limits) and server request logs. Kept in server logs for 30 days
Install information from Google Play (install referrer)Read once after install, to find an invite code or a referral code in the link you installed from
Account creation time, time of last use, the version and time of your consent, your email settingsRunning the account and proving consent
Your account identifier in our server logs and crash reportsTracing a support request or a fault back to your own activity, so we can fix it without asking you for more information. This identifier is a random account reference — it is not your name or your email address, and it is never linked to health or care content in the log. Server logs are kept for 30 days and crash reports for 90 days (Section 7).

2.4 Analytics Data (opt-in, off by default)

The app includes Firebase Analytics for anonymous product and usage metrics. Analytics is disabled by default and runs only if you explicitly opt in (consent under the GDPR and ePrivacy rules). You can withdraw that consent at any time in the app settings. The device advertising identifier is not collected — advertising-ID collection is turned off in the app, so no advertising ID is used even when analytics is enabled. No health or care data is ever sent to analytics.

DataPurpose
Anonymous usage events (screens viewed, features used)Understanding how the app is used, to improve it
Anonymous app-instance identifierDistinguishing analytics sessions; not linked to any advertising identifier

2.5 Problem Reports You Send Us

If you use Settings → Report a problem, the app prepares an email to support@carering.app and shows you its complete contents first. Nothing from the email is transmitted until you send it yourself from your own email app, and you can edit or delete any part of it before you do. One thing happens earlier: when you open this screen, the app stores the short report reference in our crash-reporting tool (Firebase Crashlytics, Section 5.2) next to your account identifier and device details, so that we can find the technical log for your report. This is sent the next time the app starts, even if you do not send the email.

The prepared email contains a short report reference, your app version and build, your device model and Android version, your app language, your account identifier, your care circle identifier, and the time of your last successful sync. It deliberately contains no medication names, no names of people, no notes and no tasks, and we do not capture a screenshot or a recording of your screen. Anything else in the message is what you chose to write. We keep problem reports only as long as needed to resolve the issue and any follow-up with you.

2.6 People You Invite to a Household

When you invite someone to your household by email, we process that person's email address so the invite can reach them, even if they do not use CareRing yet:

We use the address only to deliver and match this invite. The invited person can ask us to delete the invite at any time (Section 13).

2.7 The Referral Program ("Recommend CareRing")

When the referral program is offered, you can share a personal code so that you and a friend receive free Premium time. This section applies only if you share a code or use one.

3. Legal Basis for Processing (GDPR Article 6)

Health data is processed under GDPR Article 9(2)(a) — explicit consent. You may withdraw consent at any time by deleting your account.

4. How We Use Your Data

We do NOT:

5. Data Sharing

5.1 With your care circle members

When you join a care circle, other members of that circle can see the care data within it (medications, tasks, check-ins, notes, medical info). You control which circles you join. You can leave a circle at any time, unless you are its owner; the owner can delete the circle. Members of your household can see the household's medication cabinet: medication names, stock, batches, storage locations and inventory history.

5.2 Third-party service providers

The providers below act only as processors on our behalf. Because Google Firebase, Resend and RevenueCat are operated by Google, Resend and RevenueCat on their own global infrastructure, some of this data may be processed outside the EU/Switzerland, including in the United States, under appropriate safeguards.

ProviderPurposeData sharedLocation
Google Firebase (Authentication)User sign-inEmail, name, profile photo (the photo is held by Google; CareRing does not store or show it)Google infrastructure, may include the US (SCCs / EU-US Data Privacy Framework)
Google Firebase (Cloud Messaging)Push notificationsDevice token, notification contentGoogle infrastructure, may include the US (SCCs / EU-US Data Privacy Framework)
Google Firebase (Crashlytics)Crash reportingDevice info, crash logs, your account identifier, a problem-report reference (no health data)Google infrastructure, may include the US (SCCs / EU-US Data Privacy Framework)
Google Firebase (Analytics)Anonymous usage metrics — only if you opt in (Section 2.4)Anonymous usage events (no health data, no advertising ID)Google infrastructure, may include the US (SCCs / EU-US Data Privacy Framework)
Resend (email delivery)Sending account, notification, and optional daily-digest emailsYour email address and email content. A daily digest may include the care recipient's name, the number of doses taken and missed with their times, adherence percentages and the number of coming appointments. It never names a medication. For a household invite, the invited person's address (Section 2.6)Sent from the EU (Ireland); Resend is a US company and may process data in the US (SCCs)
Google Cloud Platform (Cloud Run, Cloud Logging)Application hosting and server logsAll app data while it is processed; your account identifier and IP address in server logsServers in europe-west1 (Belgium, EU). Server logs are stored by Google Cloud Logging and may be kept outside the EU (SCCs / EU-US Data Privacy Framework)
SupabaseManaged database hostingAll app data (encrypted at rest)Switzerland (eu-central-2, Zurich) — EU adequacy decision
RevenueCatSubscription management; adding free Premium time from the referral program (Section 2.7)Your account identifier (a random reference, not your name or email), purchase receipts, subscription status, the length of free Premium timeUS (SCCs / EU-US Data Privacy Framework)

We do not share health or care data with any third party for its own use. Your core care records are stored only on our EU-hosted application servers, our Swiss-hosted database (see Section 6), and your device. Limited care-related content may additionally pass through the notification and email providers listed above — for example, a reminder or a daily digest that names a care recipient — solely to deliver the messages you have set up.

6. Data Storage & Security

7. Data Retention

8. Your Rights (GDPR Articles 15-22)

You have the right to:

To exercise any of these rights, use the in-app settings or contact us at privacy@carering.app. We will respond within 30 days.

9. Account Deletion

You can delete your account at any time from Settings within the app. This will:

Deletion is permanent and cannot be undone. Deletion of the records held by Firebase and RevenueCat is carried out on a best-effort basis immediately after your account data is removed. Some non-identifying entries in shared care circles may be retained — without your name — so that the other members' care history stays intact. These entries keep a random account reference that no longer belongs to any account. If you are the person cared for in a circle that another member owns, the care record in that circle stays; ask the circle owner or us to delete it. When an account is deleted we keep one statistics row that holds no identifier (the date, the number of days since sign-up, whether a dose was ever logged, and whether the account was alone in its circles), and a technical record that the deletion at Firebase and RevenueCat was done or failed (the random account reference, the date and the result). If you used a referral code, a one-way code of your email address stays on the referral record, so that the same address cannot use a referral code again (Section 2.7).

10. Children's Privacy

You must be at least 18 years old to create a CareRing account. Care recipients whose information is entered in the app may be of any age, including minors — their information is entered and managed by a responsible adult caregiver, who must have the authority to provide it. CareRing is not intended to be used directly by anyone under 18, and we do not knowingly allow a person under 18 to create their own account. If you believe someone under 18 has created an account, please contact us and we will delete it.

11. International Data Transfers

Our application servers run in the EU on Google Cloud Platform (europe-west1, Belgium). Our database is hosted by Supabase in Switzerland (eu-central-2, Zurich). Switzerland is not part of the EU/EEA, but the European Commission has granted it an adequacy decision, so storing your data there is a lawful transfer under GDPR Article 45 and your data receives protection equivalent to EU standards. Beyond this, some limited data — push notifications, emails (including daily digests that may name a care recipient), crash reports, opt-in analytics, subscription status and server logs — is handled by Google (Firebase and Cloud Logging), Resend (email) and RevenueCat and may be processed outside the EU/Switzerland, including in the United States, under appropriate safeguards (Standard Contractual Clauses and/or the EU-US Data Privacy Framework). Your core care records in the database remain in Switzerland.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes through the app or by email. The "Last updated" date at the top reflects the most recent revision.

13. Contact Us

For privacy-related questions or requests:

Email: privacy@carering.app
Vasil Nonchev
Sofia, Bulgaria