Privacy policy

Sloe helps you log recipes, nutrition, and discover meals. This policy describes what we process, who we share it with, and your choices.

Data controller

• Controller: Sloe, LLC, a limited liability company incorporated in Delaware, United States. Full trader identity — including postal address and registration numbers — is set out under Who operates Sloe below. The registered office address will be added there once it is settled.
• Privacy contact: privacy@getsloe.com
• UK Representative (UK GDPR Art. 27): To be appointed before UK public launch. Required for non-UK controllers offering goods or services to individuals in the UK.
• EU Representative (EU GDPR Art. 27): To be appointed before EU public launch. Required for non-EU controllers offering goods or services to individuals in the EU.

Who operates Sloe

• Trading name: Sloe, at getsloe.com and in the Sloe mobile app.
• Operator: Sloe, LLC, a limited liability company incorporated in Delaware, United States, trading as Sloe. Its sole member and manager is Grace Howse.
• Company registration number: [PLACEHOLDER — Delaware file number, to be read off the Certificate of Formation].
• Postal address: [PLACEHOLDER — to be published when the operating company is registered]. Until then, write to us at the email address below and we will give you a postal address for service.
• VAT registration number: [PLACEHOLDER — UK and EU VAT registrations are in progress].
• Email: privacy@getsloe.com. We aim to respond within 14 days.

What we collect

• Account: email and profile fields you provide (e.g. display name, goals, measurements) when you create an account and sign in.
• App usage data: nutrition logs, saved recipes, and preferences you store in the application or synced to our database.
• Technical: standard server logs (e.g. IP address for rate limiting and abuse prevention), device type, and — only if you accept analytics — optional product analytics and session replay. These are off until you accept them; declining or ignoring the prompt means nothing is captured.
• Error reporting: unlike analytics, this runs regardless of your analytics choice — on iOS it is treated as part of installing the app (there is no cookie prompt on iOS), and on web we send a reduced, anonymised crash signature (crash type and location, no device identifiers, no on-screen content) even before you accept analytics, so we can tell the app is broken. Accepting analytics adds full device and session context to those reports, redacted the same way as other analytics data.

How we use data

To provide the service (logging, meal planning, barcode and recipe features), improve reliability, and comply with law. We do not sell your personal data.

Session replay

If you accept analytics, PostHog records a replay of your app or browser session — a reconstruction of what was on your screen and what you tapped or clicked. This is more than event counts, so we describe it precisely:

• Always masked: text you type into any field (passwords, email, weight entries, notes) is replaced with blocks before the recording leaves your device, and browser console output is not recorded at all. On iOS, images and system pickers are masked too.
• Masked where we render them: body weight, body-fat percentage, and your BMR / TDEE / energy figures on the profile, targets and calorie-ring surfaces on both platforms, and on the progress surfaces on web. On iOS, the Progress tab does not yet mask these figures in session replay.
• Recorded as you see it: other on-screen text. That includes the names of foods and recipes you log, meal entries and portions, calorie and macro figures outside the surfaces named above, and the rest of the interface. Because your food log is health data in a nutrition context, this means the replay can contain special-category data about you.

Replay runs under the same consent as the rest of analytics: accepting the analytics prompt is your explicit consent to this capture, and declining it, or withdrawing later in your cookie or privacy preferences, stops recording. Replays are retained by PostHog under the retention period set on our project and are viewed only to diagnose bugs and usability problems.

AI, voice, and images

If you use optional features, we send the minimum content needed to operate them to our servers and, where described below, to model providers:

• Photo meal logging: images you upload are processed to suggest food items and nutrition estimates. This processing uses third-party AI (primarily Anthropic Claude; OpenAI as a fallback).
• Voice / text meal logging: text you submit (typed or transcribed) is processed to parse foods and estimates and uses third-party AI (primarily Anthropic Claude; OpenAI as a fallback). On the web, browser-based speech recognition (Web Speech API) may run on your device or via your browser/OS vendor before text reaches us; review your browser and OS privacy settings if you use that path.
• Recipe and social import: URLs or shared links you provide may be fetched or parsed to extract recipe content. Images from imports are treated like other uploads when you choose image-based flows.

Imported recipes from public posts

When you share a public post from Instagram, TikTok, or YouTube to Sloe, we send that post’s URL to the platform’s own public embed service (Meta, TikTok, or YouTube) to read the post’s public caption, title, creator handle, and thumbnail. We do not log in, and we only ever request what the platform publishes for a public post. Sending the URL tells that platform an anonymous request was made about that post; we send no account details with it. We store the caption text, the URL, and the creator’s public handle (when available) — so the recipe is attributed back to its source.

Creators can request removal of any recipe imported from their public post by emailing dmca@getsloe.com or by submitting the form on /dmca. We’ll remove within 7 business days.

Community food database

When you correct or add a barcode product, Sloe stores the product data with your account as the submitter so the community database can be reviewed for quality and abuse. Other users may see the product name, barcode, brand, nutrition values, verification status, and community votes; they do not see your email or profile details. You can remove products you shared from Settings → Privacy & Security → Barcode contributions on web, or Settings → Account → Barcode contributions on mobile.

Sub-processors

We use the following third-party service providers to operate Sloe. We require a data-processing agreement (or equivalent contractual terms) with each provider before it processes personal data on our behalf, and each processes your data only on our instructions. We are completing these agreements as part of our launch preparations.

Contributing food data

When you scan a barcode we can’t find and enter the product’s nutrition yourself, we offer you an optional choice to contribute that entry to Sloe’s shared food database so other people who scan the same barcode can use it too. This is strictly opt-in: it only happens if you explicitly choose “Share it” — never automatically, and never as part of logging food to your own tracker.

• What’s shared: only the food name and the nutrition values you entered (calories, protein, carbs, fat, fibre, serving size) and the barcode. Your submission is linked to your account as the submitter internally, but your identity is not shown to other users. Nothing else from your account is shared.
• Purpose: a shared lookup so the next person who scans that barcode gets nutrition info instead of a dead end.
• Visibility: your contribution is visible only to you until it is confirmed — once enough independent submissions agree on the same values, it becomes the entry everyone sees when they scan that barcode.
• Eligibility: you must be 16 or older to contribute to the shared database. Logging food privately to your own tracker has no such restriction.
• Withdrawal: you can delete your own contributions at any time from your saved items.

International transfers

Several sub-processors listed above are located in the United States (Vercel, Anthropic, OpenAI, fal.ai, Supadata, Stripe, Upstash, RevenueCat, Expo, Edamam, FatSecret, USDA, PostHog, Sentry). Where we transfer personal data of EU or UK users to a country not covered by an adequacy decision, we rely on the European Commission’s Standard Contractual Clauses (SCCs) and, for UK transfers, the UK International Data Transfer Addendum or the UK IDTA, together with supplementary technical and organisational measures (encryption in transit, access controls). A copy of the relevant transfer safeguards for any specific sub-processor is available on request by emailing the address at the foot of this page.

Legal basis (EU/UK)

• Providing the service (account, logging, planning): performance of a contract.
• AI features (photo / voice logging, recipe parsing): our legitimate interests in providing and improving those features. They are opt-in per action — nothing is sent unless you use the feature.
• Analytics and session replay: your consent. These are off by default and start only once you accept the analytics prompt; you can withdraw at any time and capture stops.
• Error reporting (crash diagnostics): our legitimate interests in keeping the app reliable. A reduced, anonymised crash signature is sent regardless of your analytics choice — installing the app (iOS) or reaching our servers (web) is the basis for that baseline signal, and you cannot opt out of it specifically. Accepting analytics adds fuller device and session context to those reports, under the same consent as the rest of analytics.
• Health & wellness data (weight, body measurements, HealthKit metrics, and food logs in a nutrition context): your explicit consent (GDPR Art. 9(2)(a)). These special-category data are processed by Supabase (weight, measurements, food logs) and Apple HealthKit (device metrics you choose to share); you can withdraw at any time by turning off the relevant sync or deleting your data. If you accept analytics, session replay can also capture these data where they appear on screen — accepting that prompt is your explicit consent for that capture, and it is described in full under Session replay.
• Contributing to the shared food database: your consent (opt-in, 16+; you can withdraw at any time by deleting your submission).
• Marketing email (if any): your consent.
• Legal and safety: compliance with legal obligations.

US state privacy rights

Several US states regulate “consumer health data” specifically. A nutrition tracker collects it by definition — the food you log, your measurements, and the energy figures we derive from them — so these apply to Sloe regardless of our size.

• Washington (My Health My Data Act): your rights, the categories we collect, and who we share them with are set out in full in our separate Consumer health data privacy policy, which Washington requires us to publish as its own document.
• Nevada (SB 370): we collect the health-data categories listed under What we collect directly from you, from your device where you connect Apple Health, and from wearable services you link. We share them with the providers listed under Sub-processors — hosting and database, AI processing for photo and voice logging, and, only if you accept analytics, product analytics. You may ask us to confirm what we hold and to stop collecting and sharing it. We do not sell consumer health data.
• Connecticut (CTDPA, as amended 1 July 2026): health data is sensitive data, which we process only with your consent and never sell. You may access, correct, delete, or obtain a copy of your data, and appeal a refusal — see Your rights and choices.

To exercise any of these, email the address at the foot of this page and say which state you are writing from.

Automated processing

AI-derived nutrition matches, meal photo identification and ingredient parsing are automated but are estimates — a human (you) reviews and edits every saved entry before it enters your tracker. These features do not make decisions that produce legal or similarly significant effects about you.

Apple Health (iOS)

If you enable the Apple Health integration on iOS, Sloe reads the following data to keep your tracker in sync: steps, active energy, basal energy, workouts, weight, body fat percentage, and any dietary entries already in Apple Health (for example logs you created in other apps). Sloe writes the calories, protein, carbohydrates, fat, and fibre of the meals you log back to Apple Health so other apps on your phone can read them. Data shared with Apple Health is governed by Apple’s privacy policy and stored on your device; Sloe does not send your Health data to our servers unless you explicitly log a meal. You can revoke Sloe’s Health access at any time in iOS Settings → Privacy & Security → Health → Sloe.

Data retention

We retain your account data for as long as your account is active. If you delete your account, we will delete your personal data within 30 days, except where retention is required by law (e.g. billing records may be retained for up to 7 years for tax compliance). Anonymised, aggregated analytics data from which you cannot reasonably be re-identified may be retained indefinitely.

Analytics and error reports are the exception. Deleting your account removes your data from our own database and file storage, and cancels any Stripe subscription, but it does not automatically erase the events, session replays, or crash reports already held by PostHog and Sentry — those are removed on request, not automatically. Email the address at the foot of this page and we will erase them within 30 days. You can also stop new events being recorded at any time by turning off analytics and error reporting in your privacy settings.

Your rights and choices

• Export your data: You can export locally stored data from Settings (Download your data).
• Delete your account: You can permanently delete your account from Settings on web or mobile. Deletion is processed immediately for app data, uploads, and any Stripe subscription; billing records may be retained as required by applicable tax and accounting law (typically up to 7 years in the UK), and analytics/error-reporting records are erased on request as described under Data retention above.
• Withdraw consent: Analytics and session replay run only after you accept them. You can withdraw that consent at any time — in your cookie preferences on web, or the usage-analytics row in Settings on iOS — and capture stops from that point. Error reporting's baseline crash signature (see above) is not part of this consent and continues regardless; withdrawing analytics consent stops only the fuller device/session context added to those reports.
• Barcode contributions: You can remove products you shared with the community food database from Settings on web or mobile.
• Access and correction: You can view and update your personal data in your profile at any time, or request a copy by contacting support.
• EU/UK residents: Under GDPR / UK GDPR you have the right to access, rectify, erase, restrict processing, data portability, and to object to processing. You also have the right to complain to your national data-protection authority (in the UK, the Information Commissioner’s Office at ico.org.uk). To exercise these rights, contact the support channel below.

Contact

For questions about this policy, data requests, or to exercise your rights, email us at privacy@getsloe.com. We aim to respond within 14 days.