Consumer Health Data Privacy Policy

Only the optional emergency medical information an account owner chooses to add: blood type; allergies; medical conditions; medications; free-text medical notes. Collected solely with the owner’s express, separate, opt-in consent, or as necessary to provide the emergency-information feature requested.

To display the owner’s chosen emergency information on that owner’s tag page (if published) and to operate the requested emergency-notification feature. It can also be captured incidentally in an error report when something goes wrong while a page holding it is being rendered, as described in section 4. Never for advertising, marketing, analytics, or profiling.

Primarily one: the information the account owner types in. The only thing we generate is the emergency alert itself, which by naming the owner and saying help may be needed is an inference about their situation rather than something they entered.

We do not sell consumer health data and will not without the signed authorization the law requires (we have no intention of seeking one). We do not share it with affiliates (we have none) or third parties for their own purposes. It is processed on our behalf and on our instructions, never for a provider’s own purposes, under each provider’s published data-processing and security terms, and only by the infrastructure processors needed to deliver the service: Supabase, Inc. (encrypted database hosting), Vercel, Inc. (page rendering), Sentry (Functional Software), Inc. (error monitoring), and Twilio Inc. (message delivery). Sentry is listed because if the app throws an error while rendering a page that contains health data, the error report can capture it: our scrubbers remove emails and phone numbers, but free-text medical notes are not reliably matched. Twilio is listed because an emergency alert names the tag owner and says the scan was flagged as an emergency and that they may need help, which is itself an inference about their condition; that alert never contains blood type, allergies, conditions or medications. In our database these fields are stored with field-level AES-256-GCM encryption; a copy that reaches an error report is not encrypted by us.

Confirm whether we collect, share, or sell consumer health data about you and access it (includingthe list of third parties it’s been shared with); withdraw consent; and have it deleted. Deletion removes it from our live systems. Encrypted infrastructure backups roll off on their own retention cycle rather than being edited to remove one record. Exercise in your account (Settings → Medical information / Delete account) or by emailing support@tyratag.com from your account email; we authenticate against your existing account and never require a new one. We respond within 45 days (extendable once by 45 days with notice). If we decline, you may appeal by replying to our decision; appeal outcomes include instructions for contacting the Washington Attorney General.

TyraTag Inc. · Winnipeg, Manitoba, Canada · support@tyratag.com