Privacy Policy — Drugibly

Last updated: 22 August 2026 · Effective: 22 August 2026

Drugibly ("Drugibly," "we," "us") is operated by Orasit LLC, 1209 Mountain Road Pl NE Ste D, Albuquerque, NM 87110-7836, United States ("the developer"). This policy explains what information the app handles, how, and your choices. Contact: contact@drugibly.com.

1. Our core privacy promise

Drugibly is local-first. Your medication list, profiles, interaction history, and Emergency Card are stored on your device and are not uploaded unless you create an account and explicitly turn on cloud sync. We are built to need as little of your data as possible.

2. Information we handle

A. Stored only on your device (we cannot see it):

• Medications, doses, and the substances you check
• Profiles you create (e.g., family members), including any name/photo you add
• Interaction history (last 50 results) and your Emergency Card
• App settings and preferences

B. Sent to our servers to answer a check (anonymized):

When a check isn't answered from the on-device database, we send the substances and optional dose to our backend to compute a result via our AI provider. We store an anonymized event containing: the normalized substance names, dose bucket, a pregnancy flag if you enabled pregnancy mode, the resulting severity, your country code only (e.g., "MA"), and a random ID. This record contains no name, email, account ID, device ID, IP address, or any identifier that links it to you.

C. Account information (only if you create an account):

Email address and authentication identifier (via Firebase Authentication, Google or email). Used to sign you in and, if you enable cloud sync, to hold your backup.

C1. Cloud backup (only if you create an account AND explicitly turn on sync):

If you turn on cloud sync, a copy of your own data is stored against your account so you can restore it on a new device. It covers:

• your profiles (the people you track medicines for — name, relationship label, pregnancy mode),
• each profile's medicine list (substance, brand name you entered, dose, schedule),
• your interaction check history,
• your saved Ask conversations (text and voice),
• your app preferences (theme, simple language, analytics choice, clinical output).

This is health information about identified people (GDPR Article 9 special category). It is therefore:

• opt-in only — nothing is uploaded until you accept an explicit consent screen that names these categories;
• encrypted before it is stored, under a key held in Google Cloud KMS that our database cannot access;
• never used for anything except giving it back to you — not for advertising, not for model training, not for analytics;
• deletable at any time — turning sync off and deleting the backup removes the cloud copy entirely, and your device keeps its own data.

Profile photos are not uploaded. Your on-device data always remains the original; sync only ever adds to it.

D. Subscription information:

If you subscribe, our payment partner RevenueCat and Google Play Billing process the purchase. We receive your subscription status tied to an anonymous identifier. We never receive or store your card or payment details.

E. Diagnostics (optional, consent-based):

Anonymous, aggregated crash and usage metrics to keep the app stable. We never include any health information, medication names, or check contents in diagnostics. You can decline or turn this off in Settings.

3. What we do NOT do

• We do not sell your personal information.
• We do not use your medication data for advertising.
• We do not include health information in logs, crash reports, or analytics.
• We do not share your data with employers, insurers, or data brokers.

4. How we use information

To provide interaction results; to back up and restore your own data across your devices if you opt in (see §2C1); to manage your subscription; to keep the app secure and functioning; to improve accuracy in aggregate (e.g., reviewing reported-wrong results); and to comply with law.

5. Legal bases (GDPR / where applicable)

• Consent — cloud sync (Article 9(2)(a) explicit consent for the health data it carries), optional diagnostics, processing of health-related data you enter.
• Contract — providing the service and your subscription.
• Legitimate interests — security, abuse prevention, aggregate accuracy improvement (balanced against your rights).

Medication information can be special-category (health) data under GDPR Article 9; where we process it on our servers we rely on your explicit consent, and on-device data stays under your control.

6. Sharing with service providers

We use vetted processors under data-processing agreements, only as needed:

• Google Cloud (Vertex AI to compute results; Cloud SQL to store the anonymized vault; hosting)
• Firebase (optional authentication; optional sync)
• RevenueCat / Google Play (subscriptions)

We do not authorize them to use your data for their own purposes.

7. International transfers

Our servers may be located outside your country (including the EU/US). Where required, transfers use appropriate safeguards (e.g., Standard Contractual Clauses). Our servers are located in the United States (Google Cloud, us-central1).

8. Data retention

• On-device data: kept until you delete it or uninstall the app.
• Anonymized vault events: kept up to 90 days, then re-verified or deleted; because they are anonymized they cannot be tied back to you.
• Account/email: kept while your account is active; deleted on request (see §9).

9. Your rights and choices

Depending on where you live (EU/UK GDPR, California CCPA/CPRA, Washington My Health My Data Act, and others) you may have rights to access, correct, delete, port, or restrict your data, to withdraw consent, and to not be discriminated against for exercising them. Because most data is on your device, you can view or delete it directly in the app (Settings → Privacy & data). For account data or requests, contact contact@drugibly.com; we respond within the timeframes required by law.

Washington / health-data note: for "consumer health data" under applicable US state laws, we obtain consent before collecting, do not sell it, and honor withdrawal and deletion. [Confirm WA MHMD consumer-health-data scope with counsel; a separate Consumer Health Data Privacy notice may be required.]

10. Children

Drugibly is not directed to children under 16 in the EEA and UK, or 13 and we do not knowingly collect their data. ****

11. Security

We use encryption in transit (TLS) and at rest, on-device encryption for sensitive data, and access controls. No system is perfectly secure; we follow breach-notification obligations (including the FTC Health Breach Notification Rule and applicable state/GDPR rules) if a qualifying incident occurs.

12. Morocco — Law 09-08 (CNDP)

As a developer established in Morocco, we are subject to Law No. 09-08 on the protection of individuals with regard to the processing of personal data, supervised by the CNDP (Commission Nationale de contrôle de la protection des Données à caractère Personnel). Where required, we declare or seek authorization for relevant processing with the CNDP and honor the rights the law provides. [Confirm CNDP declaration/authorization obligations and cross-border-transfer formalities with counsel.]

13. Data sources

The reference information Drugibly displays (drug interactions, side effects, pill identification) is rebuilt from license-clean public sources with documented provenance; see our Data Sources & Licenses notice](/sources(DATA_SOURCES_NOTICE.md). This concerns the published reference content we show — not your personal data, which is handled as described above.

14. Changes

We'll update this policy as the app evolves and post the new date above; material changes will be notified in-app.

15. Contact

Orasit LLC · 1209 Mountain Road Pl NE Ste D, Albuquerque, NM 87110-7836, United States · contact@drugibly.com. EU/UK users: we do not currently offer the service in the EEA, so no Article 27 representative is appointed.**