Consumer Health Data Privacy Policy
Effective 1 October 2026.
This policy is required by the Washington My Health My Data Act (RCW 19.373). It exists because a small part of what BlinkWrite reads from your screen can, in some cases, be consumer health data under that law — information that identifies your own physical or mental health status. This policy tells you, specifically, what happens to that category of information. It supplements, and does not replace, our Privacy Policy, which covers everything BlinkWrite does with your data in full.
If you are not a Washington resident, most of this document still describes our practices accurately, but the specific rights in Section 6 are the rights Washington law gives you. See our Privacy Policy §12 for the rights that apply where you live.
1. What counts as consumer health data here
BlinkWrite does not build health profiles or tag your writing by health topic. The LLM provider has separate safety processing, described in Section 4. It reads the text in the window you're working in and masks identifiers before anything leaves your computer, exactly as described in our Privacy Policy §2.
Occasionally, that text includes a statement about your own health — for example, a sentence like "I'm out sick with the flu" in a draft email. When it does, and when it can still be linked to your account after masking, it is consumer health data for the purposes of this policy and Washington law. Most of what BlinkWrite reads is not this, and this policy does not apply to the rest of it — that's covered by our regular Privacy Policy.
2. Categories of consumer health data we collect, and why
| Category | Example | Why we collect it |
|---|---|---|
| Statements about your own physical or mental health status, appearing incidentally in text you're writing | "I'm dealing with a migraine today," "I've been diagnosed with X," "out sick," a reference to a therapy appointment | To generate your writing suggestion and protect the service, as described in Section 4 |
We do not seek this category out, do not detect it, and do not treat it any differently from any other text on your screen. It reaches us only because it was present in a window you were actively working in when you asked for a suggestion, in the same way any other sentence would.
We do not infer, derive, or guess at your health status from anything you write. There is no classifier, health-topic tagger, or model in BlinkWrite that does this — see our Privacy Policy §2.6 and the engineering findings referenced in Section 9.
3. Where this data comes from
The only source is you — specifically, the text visible in the application window you are actively using BlinkWrite in, read through the accessibility features of macOS or Windows or, where that isn't available, extracted on your computer from a screen capture. We do not obtain consumer health data from any other source: not from data brokers, not from partners, not from public records.
Full detail on how this reading works is in our Privacy Policy §2.1–2.4.
4. Categories of consumer health data we share, and with whom
We do not sell consumer health data. Text described in Section 2 can pass through our service providers when you request a writing suggestion.
Amazon Web Services hosts our application servers. Cloudflare provides the request gateway. An external LLM provider generates suggestions from the masked text and can perform service safety monitoring. The provider can receive incidental health information that masking does not remove. Provider retention is described in Section 7.
See Privacy Policy §9 for the service-provider categories and contact us for more information about processing arrangements.
BlinkWrite does not use consumer health data to train models, run advertising, or build health profiles. We do not opt in to provider training on API content.
5. Consent
When you sign in, the sign-in page links to this policy, and continuing past it gives your consent. BlinkWrite does not turn on until you do. That consent covers the categories of data described in Section 2, the purposes and provider processing described here, and the retention in Section 7. We do not sell it. You can withdraw that consent at any time — see Section 6.
6. Your rights, and how to exercise them
If you are a Washington resident, RCW 19.373.040 gives you the right to:
- Confirm whether we are collecting, sharing, or selling consumer health data about you, and to access it;
- Withdraw your consent to our collection or sharing of it, at any time, without affecting anything already generated;
- Request deletion of consumer health data we hold about you, including from providers that process it. We will assess the request and work with the relevant provider, subject to applicable retention exceptions in Section 7;
- Appeal if we refuse a request under this section.
To withdraw your consent, you do not need to contact us and you do not need to wait for us. You can stop BlinkWrite reading your screen yourself, at any time, and it takes effect immediately:
- pause BlinkWrite for one application or one website, for an hour, for the day, or until you turn it back on;
- pause it everywhere, or quit it;
- on a Mac, withdraw the Accessibility permission in macOS System Settings, which stops it reading altogether.
Any of these ends the collection described in this policy. Withdrawing consent should be no harder than giving it was.
To exercise any of these rights — including telling us in writing that you have withdrawn consent, so there is a record of it — email [email protected] with the subject line "Washington Consumer Health Data Request." We will confirm receipt and respond within a reasonable time.
To appeal a refusal, reply to our response noting you wish to appeal. A member of our team not involved in the original decision will review it and respond within 45 days. If we uphold the refusal, we'll explain why and give you a way to submit a complaint to the Washington Attorney General.
These rights sit alongside, and don't replace, the rights in our Privacy Policy §12.
7. How long we keep it
BlinkWrite does not save production writing, including incidental health information, in its application database or content logs. Production LLM requests disable API response storage.
Provider retention still applies. The LLM provider can retain prompts and responses for abuse monitoring for up to 30 days, with longer retention for legal requirements or to prevent harm. Encrypted prompt-cache data can remain on provider infrastructure for up to 24 hours. We do not currently promise Zero Data Retention for LLM processing.
See Privacy Policy §2.5 and Section 11 for the full retention schedule. Contact us to exercise your rights under Section 6.
8. Security
On-device masking attempts to remove supported identifiers before transmission. It can miss information and does not detect or remove health statements as a category. We use encrypted connections and disable production API response storage. See Privacy Policy §13 for application security controls. Provider retention remains subject to Section 7.
9. Our controls and their limits
Our production application does not log writing content or maintain a writing history. Usage counters record quantities rather than drafts or suggestions. The external LLM provider has separate safety processing and retention controls. Disabling API response storage does not disable those controls.
Do not use BlinkWrite for health records or other information you cannot send to the service and its LLM provider. You can pause BlinkWrite at any time. Contact [email protected] for questions about these controls.
10. Changes to this policy
We will update this policy if what's described above changes. Material changes — a new category of consumer health data, a new purpose, or a new recipient — will not take effect until we've disclosed them here and, where required, obtained your renewed consent, per RCW 19.373.020(1)(c)–(d). Everything in Privacy Policy §17 about versioning and notice applies here too.
11. Contact us
Previous versions
- 2026-08-24Effective 24 August 2026 · First published version.