Consumer health data privacy policy
Required by Washington's My Health My Data Act.
Who this applies to
This policy describes how Sloe handles consumer health data as that term is defined in Washington’s My Health My Data Act (chapter 19.373 RCW). It applies to Washington residents and to anyone whose consumer health data we collect in Washington.
What we collect, and why
We collect the following categories of consumer health data. In every case the purpose is to provide the tracking, planning and recipe features you asked us for, and to keep them working correctly.
- Food and drink you log — item names, portions, and the calorie, macro and micronutrient figures attached to them. Used to render your diary, your daily totals and your progress over time.
- Body measurements — weight, body-fat percentage, height and any other measurements you enter. Used to calculate your energy targets and to chart change.
- Derived energy figures — your BMR, TDEE and calorie and macro targets, which we calculate from the above. Used to set and display your targets.
- Dietary preferences and restrictions — allergens, intolerances, exclusions and diet type. Used to filter recipes and to warn you about ingredients you have told us to avoid.
- Apple Health data you choose to sync — steps, active and basal energy, workouts, weight, body-fat percentage, and dietary entries already in Apple Health. Used to keep your tracker in step with your device.
- Wearable data from services you connect — if you link Oura or Whoop, the activity and energy figures those services provide. Used to inform your daily energy picture.
- Meal photos and descriptions you submit — images you upload and text you type or dictate when logging a meal. Used to identify foods and estimate nutrition.
Where it comes from
- Directly from you, when you log, enter or upload something.
- From your device, through Apple Health, and only after you grant that permission in iOS.
- From third-party services you connect, such as Oura or Whoop, and only after you authorise the connection.
- Derived by Sloe from the above — for example your energy targets, calculated from your measurements, or nutrition estimates produced from a meal photo.
What we share
We share the categories listed above with service providers only to the extent needed to run the features you use. Specifically:
- All of it is stored with our database and hosting provider so that your account works across your devices.
- Meal photos and meal descriptions are sent to AI providers when you use photo or voice logging, so those features can identify foods. They are sent without your account details attached.
- Food and recipe names, and on-screen figures may appear in product analytics and session replay — but only if you accept analytics. If you decline, or ignore the prompt, nothing is captured. You can withdraw at any time and capture stops.
- Crash diagnostics are sent to our error-reporting provider. These contain stack traces and device type, not the contents of your screen or your diary.
Who we share it with
Affiliates: none. Sloe is operated by Sloe, LLC, which has no parent, subsidiary or affiliated entities.
Categories of third parties, with the specific providers in each:
| Category | Provider | Consumer health data received | Region |
|---|---|---|---|
| Database, authentication and file storage | Supabase | All categories listed above | EU (Frankfurt) |
| AI processing for photo and voice logging | Anthropic; OpenAI (fallback only) | Meal photos and meal descriptions, without account details | US |
| Product analytics and session replay | PostHog | Food and recipe names and on-screen figures — only if you accept analytics | US |
| Error reporting | Sentry | Stack traces and device type; not diary contents | US |
| Device health platform | Apple (HealthKit) | The metrics you choose to sync, and the nutrition figures we write back | Global |
We do not sell it
Sloe does not sell consumer health data, and has never sold it. If that ever changes we will obtain your signed, written authorisation first, separately from any other consent, exactly as RCW 19.373.030(2) requires.
Your rights
Under RCW 19.373.040 you have the right to:
- Confirm and access — ask whether we are collecting, sharing or selling your consumer health data, and get a copy of it, including a list of everyone we have shared it with.
- Withdraw consent — withdraw your consent to our collection and sharing of your consumer health data.
- Delete — have your consumer health data deleted. This removes it from our own database and file storage. Events and session replays already held by our analytics and error-reporting providers are erased on request rather than automatically — ask us and we will erase them within 30 days.
Exercising any of these rights will not cause us to charge you a different price or give you a worse service.
How to exercise them
Email privacy@getsloe.com and tell us which right you want to exercise. We aim to respond within 14 days, matching the commitment in our privacy policy, and in no case later than the 45 days RCW 19.373.040(3) allows. If we do need longer than 45 days we will tell you why within that first 45 days, and may take one further 45 days.
If we refuse. We will tell you why, and how to appeal. To appeal, reply to our decision at the same address with the word “appeal” and we will review it and write back within 45 days. If we deny the appeal, we will give you a link to submit a complaint to the Washington State Attorney General.