Sub-processors
Last updated: September 25, 2026 · Operator: TyraTag Inc.
These providers process personal information on our behalf, on our instructions. Our Privacy Policy explains what we collect and why; this page lists who handles it.
| Provider | Role | Data it receives | Location |
|---|---|---|---|
| Supabase Inc. | Database, sign-in, sign-in emails | All account, tag, contact and alert records, including our encrypted phone numbers, medical details and messages; sign-in email addresses and sign-in activity, including IP addresses | United States (Northern Virginia) |
| Vercel Inc. | Hosting | Every request to the app: IP address, browser and page address, in its platform logs | United States (Washington, D.C.); requests enter through its worldwide network |
| Twilio Inc. | Texts, verification codes, phone-number checks, masked calls where switched on | Phone numbers; message content (an owner’s name, the reason, a map link if the person at the scene shared a location, secure links); verification attempts; line type and SMS-pumping risk of an owner’s number; call records | United States |
| Upstash Inc. | Abuse-prevention and spending-limit store | Short-lived counters and a phone-check cache, filed only under one-way hashes — hashed IP addresses, email addresses, phone numbers and area codes, device fingerprints, tags and typed tag codes (listed below) | Not yet confirmed |
| Cloudflare Inc. | Bot check (Turnstile) | The visitor’s IP address and browser signals, on the find-a-tag form and the alert form of tags not set up for a person | Worldwide network |
| Functional Software Inc. (Sentry) | Error monitoring | Technical error reports; emails, phone numbers and known medical form fields removed; unstructured medical notes not reliably matched. Never initialized in the browser on tag, find-a-tag, conversation or alert pages | United States |
| PostHog Inc. | Analytics, only if accepted | Page views and screen events tied to an account’s random ID (pseudonymous, not anonymous); never on tag, find-a-tag, conversation, secure alert or invitation pages | United States |
| Shopify Inc. | Checkout | Order, shipping and payment details (card data stays with Shopify) | Canada / United States (not yet confirmed) |
What our abuse-prevention store holds
Upstash holds only the entries below. Each is filed under a one-way hash — the first 24 characters of a SHA-256 digest — never the readable value. A hash is not encryption: for short inputs such as an area code, an IP address or a printed tag code, someone holding the list could work the input out by trying every possibility. That is why these entries are short-lived.
| Used for | Filed under | What is stored | Deleted |
|---|---|---|---|
| Limits on alerts, verification codes, test texts, contact invitations and private calls | Hashes of: the country and area code of the number being texted or called (the whole number when a code is being checked); the device fingerprint; the tag; the IP address | A count | About 30 minutes after it is created |
| Limit on page views of a tag | A hash of the IP address | A count | About 30 minutes after it is created |
| Limit of three verification codes per conversation, for private calls | A hash of the alert | A count | About 48 hours after it is created |
| One emergency-contact alert per tag per 15 minutes | A hash of the tag | A count | About 30 minutes after it is created; the 15-second in-flight lock after about 30 seconds |
| Limits on sign-in, password-reset and sign-in-link requests | Hashes of the IP address and of the email address the message goes to | A count | About 30 minutes after it is created |
| Limit on checkout requests | A hash of the IP address | A count | About 30 minutes after it is created |
| Limits on the find-a-tag form | Hashes of the IP address and of the typed tag code; one shared counter | A count | About 30 minutes after it is created |
| Limits on alert attempts before the human check runs | A hash of the IP address, and a hash of the IP address paired with the tag | A count | About 30 minutes after it is created |
| Limits on linking a tag to an account | Hashes of the typed tag code and the IP address; one shared counter | A count | About 30 minutes after it is created |
| Phone-number check cache (Twilio Lookup) | A hash of the owner’s alert number | The line type (mobile, landline, internet or unknown) and Twilio’s SMS-pumping risk score | 7 days after it is written |
| Daily spending limits | A hash of each number we text, verify or call, and the date; one daily total; one flag per kind of spending alert | A count per number per day; a running dollar total; a marker | 26 hours after its last update |
Not sub-processors, but named so the list is complete: Google receives information only if you choose to sign in with Google, or if someone opens a map link in one of our alerts.
Each provider processes data on our behalf under its own published data-processing and security terms. We update this page when the list changes, and we will not add a provider that can touch medical details without disclosing it here first.
Locations for Supabase, Vercel, Sentry and PostHog were checked against our live service on September 25, 2026. Twilio processes in its default United States region, which our service does not change. Locations marked “not yet confirmed” have not been independently checked.