Consumer Health Data Privacy Policy
Effective July 25, 2026 · Supplements our Privacy Policy
This notice describes Junie's practices for consumer health data, including information covered by the Washington My Health My Data Act and Nevada Senate Bill 370. It applies when those laws cover the person or information involved.
Consumer health data we may collect
Junie is practice-management software for doulas and birth workers. The information stored depends on what an account holder and their client choose to enter.
| Category | Examples | Sources |
|---|---|---|
| Pregnancy, reproductive, and birth information | Pregnancy status, estimated due date, birth date, birth preferences, health history, conditions, symptoms, or other details included in an inquiry, message, note, document, or free-text field | The client, the account holder, or records imported at the account holder's direction |
| Services and care-related activity | Requested doula services, appointments, visits, on-call dates, postpartum hours, contracts, messages, and notes about services | The client, the account holder, imported records, and information created as they use Junie |
| Payment, coverage, and reimbursement information | Service charges, payment status, refunds, superbill details, and insurance or Medicaid information entered for reimbursement records | The client, the account holder, Stripe, and transaction events |
| Inferences from the information above | A client's service stage or whether an appointment, birth, payment, or postpartum milestone has occurred | Generated from records and activity in Junie |
| Health-related website activity and inferences | Visits to pages about pregnancy, doula services, Medicaid, reimbursement, or other health-related topics; referring page; campaign information; approximate location derived from IP; and an inferred interest in that content | The visitor's browser, page URL, referrer, cookies, local storage, and advertising attribution data |
Junie does not ask for biometric identifiers, genetic test results, or precise location for tracking visits to health facilities. If someone puts that information in a message or free-text field, we handle it as consumer health data under this policy.
Why we collect and use it
We collect and use consumer health data only as needed to:
- provide the product or service requested by the client or account holder, including client records, scheduling, documents, communications, payment tracking, and superbills;
- carry out the account holder's instructions, including importing, exporting, correcting, or deleting records;
- generate a draft or perform a safety check when the account holder turns on and uses an AI feature;
- with the visitor's separate opt-in choices, understand visits to health-related marketing pages and measure whether a marketing-site visit or lead followed an OpenAI ad;
- when the server-side OpenAI Ads conversion is configured, measure an account registration using a registration event and hashed email; the current signup code does not read the marketing-site advertising choice;
- protect accounts, prevent fraud or abuse, debug failures, and respond to incidents; and
- comply with law or establish, exercise, or defend legal claims.
When consent is required, the request must identify the health data and purpose involved. A person may withdraw that consent for future collection or sharing as described below.
Consumer health data disclosed to service providers
Junie does not sell consumer health data. The providers below may process the listed categories to operate Junie, analyze the website, or measure advertising:
| Provider category and name | Categories disclosed and purpose |
|---|---|
| Cloud hosting and storage: Google Cloud | All categories stored in Junie, for application hosting, database service, backups, and operational telemetry |
| Email delivery: Postmark | Contact details and any health information included in email content, for sending and receiving account and client email |
| Payments: Stripe | Service, transaction, and reimbursement-related information needed for connected accounts, client payments, refunds, and disputes |
| AI processing: Anthropic or OpenAI | Content submitted to an enabled AI feature and the resulting draft or classification. Inquiry text may contain health details the writer chose to share. The configured provider for the task receives the content. |
| Website analytics: PostHog | Health-related page URLs, referring and campaign information, approximate location, browser or device details, and analytics identifiers, for page-view and conversion analysis. Junie does not intentionally send Client Records to PostHog. This tool is off until the visitor chooses analytics collection. |
| Advertising measurement: OpenAI Ads | Health-related page visits, OpenAI ad-attribution information, browser identifiers, and lead or registration events. Account registration can also include a SHA-256 hash of the normalized signup email for matching and deduplication. The marketing-site pixel is off until the visitor separately chooses advertising measurement and sharing. The current server-side account-signup conversion, when configured, does not read that marketing-site choice. |
| Error monitoring: Sentry, when configured | Technical and diagnostic information needed to identify a failure. Junie does not intentionally include consumer health data in error monitoring. |
On the marketing site, analytics collection and advertising measurement use separate opt-in controls. Neither optional browser tool loads before the relevant choice. Use “Privacy choices” in the footer to change or withdraw either choice for future collection or sharing. That choice is not currently shared with the Junie app or its server-side account-signup conversion. Until Junie adds one consent flow across both sites, the server-side conversion should not be enabled where prior opt-in is required.
We may also disclose consumer health data when directed by the account holder or client, when required by law, or to investigate and respond to fraud, abuse, or a security incident. The current recipient list above does not include a corporate affiliate. This policy must be updated before a new recipient uses consumer health data.
How Junie protects this data
Junie limits production access, uses HTTPS for browser connections, isolates each practice's records with database rules, and applies additional field encryption to private client notes and optional birth notes. Client-access links use random tokens that are stored as hashes, expire after 30 days without use, and can be revoked. Daily database backups retain the 14 most recent copies.
Your rights
Depending on the law that applies, you may ask Junie to:
- confirm whether we collect, share, or sell consumer health data about you;
- give you access to that data and a list of the third parties or affiliates that received it;
- stop future collection or sharing by withdrawing consent;
- delete the data from active systems and notify relevant providers; and
- review an appeal if we deny a request.
Email hello@junie.app with "Consumer health data request" in the subject. Describe the right you want to exercise and the doula or practice connected to the record, if known. We will use reasonable steps to verify your identity. You do not need to create a Junie account. An account holder's client may also ask that account holder directly, but contacting the account holder is not required.
We respond without undue delay and within the period required by applicable law, generally 45 days after receipt or verification. If more time is legally permitted and reasonably needed, we will explain the extension. Junie has not verified that the in-app account-deletion control works with production permissions, so send deletion requests to hello@junie.app instead of relying on it for now. Fixed backup copies age out as the 14 daily backups rotate; applicable law may allow extra time for deletion from an archived or backup system. We do not discriminate against anyone for exercising these rights.
To appeal a decision, reply to it or email hello@junie.app with "Consumer health data appeal" in the subject. We will provide a written response and, if an appeal is denied, information about contacting the relevant state attorney general.
Policy changes and contact
We will not collect, use, or disclose a new category of consumer health data, or use the data for a new purpose, without updating this notice and obtaining consent where the law requires it. Contact Verios LLC at hello@junie.app with questions or requests.