1. What this document is, and who it is for
This is a standalone document about consumer health data. It is not a section of our Privacy Policy, and it is linked from every page of getvari.app.
It is written for residents of Washington State, whose law gives them specific rights over consumer health data. Nevada has a similar law. If you live anywhere else, you are welcome to use this document too — we will not turn down a request because of where you live.
It covers the same product as our Privacy Policy: the Vari iPhone app, the website at getvari.app, and our account emails. Where the two documents describe the same thing, they are meant to agree; where you think they do not, tell us at support@getvari.app and we will fix it.
Who is responsible. Vari is operated by Mendios Technologies (WebMobi), 10685-B Hazelhurst Dr. #42794, Houston, TX 77043, USA. We decide what is collected and what is done with it. Contact: support@getvari.app.
2. The short version
- Vari 2.0 stores your consumer health data in your Vari account, in our cloud database, so that it is backed up and stays in sync across your devices. You need an account, and you sign in with a code we email to you.
- Vari's data is kept in its own schema in a database that WebMobi's products share, and each account can reach only its own rows (§4.3).
- Apple Health readings are read on your iPhone and are not uploaded.
- If you used Vari 1, your older health data stays in your Vari account. §5 says what, and how to remove it.
- We do not sell consumer health data. Not for money, not for anything else of value.
- We do not use it for advertising, and we do not share it with advertisers or data brokers.
- Analytics and crash reports are linked to your account. Mixpanel analytics events carry your account ID and no health values. Sentry crash reports carry your account ID and email address, and are not designed to carry your health entries (§7, §9).
- You can delete your Vari records from inside the app, in Settings → Delete account. §13.3 and §13.4 list what that does not reach.
- If we say no to a request, you can appeal, and §14 says how.
3. What we mean by consumer health data
Washington's law defines consumer health data broadly: personal information that identifies your past, present or future physical or mental health status. In Vari, the following is consumer health data, and we handle it as such:
- Conditions — the health conditions you enter in onboarding;
- Targets — your fluid and sodium targets: the amount, the unit, and whether each is an "at least" target to reach or an "at most" limit to stay under. A limit set by a clinician says something about your health on its own;
- Readings from Apple Health — resting heart rate, heart-rate variability, sleep analysis and active energy, if you grant permission. They are read on your iPhone and not uploaded (§4.2);
- Fluid and sodium entries — what you drank and how much salt or sodium you took in, and the daily summaries built from them. In the context of the rest of this list, these say something about your health;
- Body measurements and activity — your weight and your activity level;
- Any health details you send us in a support message. Please don't send them (§8).
Not consumer health data: your email address on its own, your subscription status, your app version and device model, and analytics events, which carry no health values (§7). We list them so you can see where we draw the line.
4. Where it is collected from, and where it lives
4.1 The sources
| Source | What we get |
|---|---|
| You, typing in the app | Nearly all of it: fluid and sodium entries, targets, the conditions you enter in onboarding, your weight and activity level |
| Apple Health, with your permission | Resting heart rate, heart-rate variability, sleep analysis and active energy, read on your iPhone for Insights and not uploaded |
| Your earlier use of Vari 1 | Drink logs, goals, a condition field and body measurements already in our database (§5) |
| A support message you send us | Only what you choose to write (§8) |
We do not buy health data about you, and we do not receive it from data brokers, advertisers or other apps.
4.2 Where it lives: in your Vari account
Everything in §3 except the Apple Health readings is sent to Vari's cloud database and stored in your Vari account, so that it is backed up and stays in sync across your devices. When you log something, it is saved on your phone first and syncs when you are online.
The app keeps a copy of your data on your iPhone so it can show it quickly. That copy is cleared when you sign out or delete your account.
Readings from Apple Health are read on your iPhone, used there for Insights, and not uploaded. They are never used for advertising or marketing.
4.3 How it is hosted, and who can reach it
- Vari's database is a Supabase project that we operate. Several WebMobi products share that project.
- Vari's data sits in its own database schema, named
vari. Row-level security restricts every user-facing table to the signed-in person's own rows. - Your sign-in record — your email address — lives in Supabase's authentication table, which WebMobi's products share. The app may also store a device notification token with it; your reminders are scheduled on your phone.
- One person, Vari's founder, has administrative access to the production database. Server-side keys are used only by WebMobi's server functions.
- Region: Amazon Web Services region ap-northeast-2 (Seoul, South Korea). Backups: daily, kept for 7 days, so data you delete leaves our backups within 7 days.
5. If you used Vari 1
Vari 1 stored some health data of yours on our servers: your drink log, your goals, and a condition field and body measurements written into the sign-in record attached to your email address.
- That data stays in your Vari account.
- Deleting your Vari account removes it (§13.4).
- You can also ask us to delete it at any time (§13.2).
Vari 1 also sent some health-related properties — a condition field and body measurements — to Mixpanel, our product analytics provider. Vari 2.0 does not send them: its analytics events carry no health values (§7). We have asked Mixpanel to delete the historical properties.
6. Why we collect it, and what we do with it
We collect consumer health data for one purpose: so that you can keep a record of your own health and share it with whoever you choose.
Concretely, that means:
| Purpose | What happens |
|---|---|
| Show you your own data | Today's totals, how each day compares with your targets, your history |
| Do arithmetic on it | Day totals and whether a target was met |
| Describe patterns back to you | Insights (Premium): simple descriptive patterns over a stated number of days, from your entries and, with your permission, Apple Health readings read on your iPhone. They describe; they do not advise |
| Keep it backed up and in sync | Stored in your Vari account, so it appears on each device you sign in on (§4.2) |
| Let you export it | A CSV file of your fluid and sodium entries, with Premium. On any plan, you can ask us for a copy (§13.2) |
| Protect it | Row-level security in our database, so each account reaches only its own rows (§4.3) |
What we never do with it:
- We do not sell it, and we never have. Not for money, and not for anything else of value.
- We do not use it for advertising, and we do not share it with advertisers, ad networks or data brokers.
- We do not use it to profile you for marketing.
- We do not put it into analytics (§7). Crash reports (§9) are not designed to carry it.
- We do not send weekly summary emails built from it. Apart from sign-in codes, we may send you onboarding emails, and you can unsubscribe from them.
- We do not train models on it.
- We do not use it to make decisions about you — there is nothing in Vari that decides anything about you.
- We do not collect precise location, and Vari does not use geofencing of any kind. Nobody is told that you were near a clinic, a pharmacy or a hospital, because we do not know.
7. Analytics and health data
Vari 2.0 sends product analytics events to Mixpanel, our product analytics provider, and keeps analytics events in its own database schema (§4.3). Events are linked to your account ID. There is no switch in the app to turn analytics off; you can ask us to delete your analytics data (§13.2).
Events record actions — that a drink was logged, that a paywall was seen.
They carry no health values. From Vari 2.0, events carry no conditions, no amounts, no targets and no goal results.
In our database, the events are hosted for us by Supabase in Seoul, South Korea (§4.3), and our plan is to keep raw rows for 13 months. They can be reached by the one person with administrative access, the founder (§4.3). Deleting your account removes them from our database; to have them deleted from Mixpanel, ask us, and we do it within 30 days.
The website separately records page views and a few events — that the App Store link was tapped, that the salt-to-sodium converter was used. The converter's inputs are not stored.
8. Support, and WhatsApp
You can reach us at support@getvari.app or through https://getvari.app/support. We also answer on WhatsApp, because it is convenient.
Please don't send health details over WhatsApp. A WhatsApp conversation is carried by Meta under Meta's own terms, it sits on your phone and on our support phone, and it is not covered by the contracts we hold with the providers in §10. Tell us what is not working; if a health detail is genuinely needed to fix your problem, email us and we will tell you what we actually need.
If you send health details anyway, we do not copy them into our database or our analytics. We answer, and they stay in the conversation.
9. Crash reports
When the app crashes, it sends a crash report to Sentry, our crash-reporting provider: a stack trace, your device model, the app version, your account ID and your email address. Vari also keeps error records in its own database schema (§4.3).
Crash reports are not designed to carry your health entries. You can ask us to have your crash reports deleted from Sentry (§13.4).
10. Who we share it with
We do not sell consumer health data, and we do not share it with anyone for their own purposes. The list below is the complete set of parties who could hold or handle any of it on our behalf, by category and by name.
10.1 Service providers (they act on our instructions only)
| Provider | Category | What they could hold | Where |
|---|---|---|---|
| Supabase Inc. | Database and sign-in hosting (§4.3) | Everything in §3 except Apple Health readings, in Vari's own schema. Your Vari 1 health rows. Your sign-in record. Analytics events and error records | Seoul, South Korea (AWS ap-northeast-2) |
| RevenueCat Inc. | Purchases and subscription status | Your account ID and your purchase history. No health values | US |
| Mixpanel, Inc. | Product analytics (§7) | Events about how you use the app, linked to your account ID. No health values | Mixpanel's own data centres |
| Sentry (Functional Software, Inc.) | Crash reporting (§9) | Stack traces, device details, your account ID and email address. Not designed to carry your health entries | US or EU |
| Apple Inc. | App Store and StoreKit; HealthKit, which runs on your iPhone | What Apple collects under its own policy. Apple does not receive your Vari entries from us | US, global |
| Amazon Web Services (SES) | Email delivery | Your email address, your sign-in codes and the content of our account and onboarding emails. No health values | US |
Each provider is under contract to handle information only on our instructions, and not for its own purposes.
Two others, listed so the picture is complete, are not our service providers. WhatsApp (Meta Platforms, Inc.) carries any support conversation you start there, and holds whatever you write in it — which is why §8 asks you not to write health details there. Vercel Inc. hosts our website, getvari.app, and sees request logs and IP addresses for it, with no health values.
10.2 Anyone you share with yourself
When you export your entries (Premium) and send the file to someone, you choose the recipient — your clinician, or anyone else you pick. Vari does not send it anywhere on its own, and we do not receive a copy.
10.3 Legal disclosure
We may disclose information where we are legally required to, in response to a valid subpoena, warrant, court order or lawful regulatory request, or to protect the rights or security of Vari, our users or the public. Where we are legally permitted to tell you first, we will. We would resist a request that looked overbroad, and we would rather tell you about it.
10.4 If the business changes hands
If Vari is merged, acquired or sold, information could transfer as part of that. We will tell you by email or an in-app notice before your information becomes subject to a different policy.
10.5 What we never do
We do not disclose consumer health data to advertisers, ad networks, data brokers, insurers or employers. We do not sell it, and Vari has no feature that would tell anyone where you went.
11. How long we keep it
| What | How long |
|---|---|
| Your records in our database (§4.2), including Vari 1 data | Kept while your account exists. Deleted when you delete them or your account (§13.4); gone from backups within 7 days |
| The copy on your iPhone | Cleared when you sign out or delete your account |
| Apple Health readings | Not uploaded. Read from Apple Health on your iPhone |
| Analytics events (no health values) | In our database, our plan is 13 months; deleted with your account. In Mixpanel, deleted on request within 30 days |
| Crash reports | 90 days. Deleted from Sentry on request within 30 days |
| Support conversations | No fixed period. You can ask us to delete them at any time |
| Our record that we handled a request from you | Kept as a reference, without the underlying data, so we can show we did what we said |
12. Your rights
These are your rights:
- Know what consumer health data we collect, where it comes from, why we collect it, and who we share it with. That is what this document is.
- Get a copy, including a list of anyone we shared it with. Ask us (§13.2) and we send it, free, on any plan. With Premium, the app's CSV export also gives you your fluid and sodium entries straight away.
- Withdraw a consent you gave. Apple Health permission is a switch in iOS Settings, and withdrawing it does not cost you access to the rest of Vari. Your entries are stored in your account whenever you use Vari 2.0 (§4.2), so the way to withdraw consent to that storage is to delete your account (§13.4).
- Have it deleted, including from our records and from our service providers' records. §13 says how.
- Appeal if we refuse. §14 says how.
- Not be discriminated against for exercising any of these. We will not deny you the app, charge you a different price, or give you a worse experience because you made a request.
We do not sell consumer health data, so there is nothing for you to opt out of there.
13. How to exercise a right, including deletion
13.1 Do it yourself, in the app — this is the fastest route
- Export your fluid and sodium entries: a CSV file, with Premium, from Settings.
- Delete one entry: anywhere you can see it.
- Delete your Vari account and your Vari records: Settings → Delete account (§13.4).
- Withdraw Apple Health permission: iOS Settings → Health → Data Access & Devices → Vari.
- Cancel an App Store subscription: in your Apple ID settings, Settings → your name → Subscriptions. Deleting your account does not cancel it.
13.2 Ask us
Email support@getvari.app from the address on your account, and say what you want. You can also write to Mendios Technologies (WebMobi), 10685-B Hazelhurst Dr. #42794, Houston, TX 77043, USA. An authorised agent may act for you; we will ask for written proof that you authorised them, and we will still verify that you exist and that the request is yours.
We will:
- acknowledge within 3 business days;
- verify that the request is really yours — usually by confirming you can receive mail at the address on your account. If there is no account with us in your name, we may not hold anything of yours at all, and we will say so rather than ask you for more information to prove who you are;
- answer within 45 days of receiving the request. If we genuinely need longer, we will tell you why within those 45 days and take no more than a further 45;
- do it for free. If someone makes repeated, excessive requests we may charge or decline, and we will explain why.
13.3 What deletion means here
When you ask us to delete consumer health data, we delete it from our systems, and we instruct our service providers (§10.1) to delete it from theirs within 30 days. That covers your Vari records, including your Vari 1 data.
What deletion does not reach:
- Your own iPhone backup, which is yours and Apple's, not ours.
- An export file you already sent to someone. Ask them.
- Water Vari wrote to Apple Health, if you turned that on. It stays in Apple Health until you delete it there.
- Backups of our database, until they expire — within 7 days.
- Records we are required to keep by law, such as purchase and tax records. Those carry no health data.
13.4 Deleting your account, and the sign-in that survives it
Settings → Delete account deletes your Vari profile and all your Vari records: your drinks, your salt and sodium entries, your targets, your daily summaries and history, any Vari 1 data (§5), and the analytics events and error records held in Vari's database schema (§4.3). It also clears the copy of your data on the phone.
It does not delete your WebMobi sign-in record. Your sign-in record — your email address — sits in the authentication table that WebMobi's products share, and it is kept because other WebMobi apps may use it.
To delete the shared sign-in as well: email support@getvari.app from that address and ask us to delete your WebMobi sign-in. We will tell you which other products use it — deleting it ends your access to them — and once you confirm, we delete it. We aim to acknowledge within 3 business days and complete it within 30 days.
It does not cancel an App Store subscription. Cancel it in your Apple ID settings.
It does not reach Mixpanel, Sentry or RevenueCat. Ask us at support@getvari.app and we will have them delete what they hold within 30 days.
14. If we say no: how to appeal
If we refuse a request, we will tell you why, in writing, and we will tell you how to appeal. You do not need a lawyer and there is no form.
- Reply to our refusal, or email support@getvari.app with "appeal" in the subject line. Tell us what you asked for and why you think the refusal is wrong.
- A different person reviews it — not the person who refused.
- We answer within 45 days of receiving the appeal, in writing, with our reasons.
- If we still say no, we will give you a way to complain to the Washington State Attorney General, with the link, in that same reply.
We would rather grant a borderline request than win an appeal.
15. Changes, and contact
When this version applies. This document was published with the Vari 2.0 release. It applies straight away to accounts created after it was published. If your account already existed, it applies 14 days after we email you about this update.
Changes. When we change this document we update the "Last updated" date. For a change that matters — a new category of data, a new provider, a new purpose, or a change to your rights — we tell you at least 14 days before it takes effect, by email and by a notice in the app, and we say what changed. We will not apply a new purpose to data we already hold without asking you first.
Contact.
- Email: support@getvari.app
- Post: Mendios Technologies (WebMobi), 10685-B Hazelhurst Dr. #42794, Houston, TX 77043, USA
- Appeals: support@getvari.app, subject line "appeal"
A human reads these. If we are slow, write again and say we were slow.