Consumer Health Data Privacy Notice

1. Categories, sources and purposes

You are the source of any profile conditions, symptom interests and check-in symptoms; mood, stress, energy and sleep-quality ratings; screening responses; practice reflections and activity plans you choose to enter. The app generates related timestamps, screening totals, practice selections, task scores, interactions and completion records. These support your journal, within-task feedback, activity discovery and selected exports. They are not used to diagnose you.

Condition browsing alone stays temporary. Saved profile, screening and journal information stays on the device unless optional cloud sync is enabled. Optional product telemetry contains generic interactions rather than clinical values, but use of a wellbeing service can itself be sensitive. We therefore provide a separate opt-in and minimize the telemetry collected.

2. Sharing and recipients

The optional private journal is processed by Supabase using your Firebase account identifier; Google/Firebase provides the associated authentication. Vercel serves the site and processes network requests. Authorized REDKO operators may access information when necessary for service operations or verified rights requests. These are the relevant processor and operator categories for the current preview. No separate REDKO affiliate receives the journal for its own purposes.

Optional GA4/PostHog receive generic product events only under their separate setting. First-party analytics are partitioned by product and do not contain your journal or account identifier. A public activity link omits the journal. If you export and send a personal summary, its recipients are the people you choose; review the data first. We do not sell consumer health data or use it for targeted advertising.

3. Consent and rights

Cloud health-record sync is an optional choice, separate from analytics and research participation. You can withdraw it in Your space. Withdrawal stops future sync and does not automatically delete an existing cloud copy. Use the separate cloud-delete action to request active-store deletion. Local deletion applies only to the device copy. First-party analytics has its own deletion action.

Where applicable, you may request confirmation/access, a copy, withdrawal of consent, deletion and an appeal of a denied request. Washington consumers may also complain to the Washington Attorney General under the My Health My Data Act. A public, verified REDKO privacy contact and appeals workflow must be finalized before this draft notice is made effective. Applicable legal response periods and deletion duties are not waived by using Synaptik.

4. Retention and limits

The retention, backup, security-log and export limitations in the Privacy Notice apply. A local device or recipient can retain copies beyond REDKO’s active systems. No new categories, recipients or uses of health information will be introduced under this draft without updated disclosure and any consent required by law.

5. Separate choices and changes

Accepting general service terms does not authorize optional collection or sharing of consumer health data. The feature notice must identify the information, purpose, recipients where applicable, and how to withdraw. Where law permits processing necessary for a service you request, only information necessary for that service may be used on that basis. Additional optional purposes need their own permission. A disclosure requiring a specific medical-information authorization cannot rely on a generic analytics or terms checkbox.

The present service does not authorize sale of consumer health data, health-based targeted advertising, or cross-product health profiling. No separate REDKO affiliate receives your journal for its own purposes. A change involving a new category, recipient or purpose requires the disclosures and permissions required by applicable law before it begins. A prospective notice change does not rewrite earlier privacy promises.

6. Requests, appeals and provider copies

For Washington requests, the response is due without undue delay and ordinarily within 45 days of receipt; authentication does not restart that period. A necessary extension of up to 45 additional days requires notice and reasons within the initial period. Appeals receive a reasoned response within 45 days of receipt and, if denied, information for complaining to the Washington Attorney General. Covered deletion requests must reach relevant downstream recipients; a permitted delay for backup deletion cannot exceed six months after authenticating the deletion request.

Other applicable laws, including Nevada’s consumer-health rules, may use different procedures. The final request channel must be secure, monitored, accessible without creating a new account, and accompanied by a visible appeal method. The current draft does not claim that these manual operations or every provider’s backup process have been verified. Existing legal duties continue while the operations are being completed.