Privacy Policy

1. Introduction

Kindly Robotics, Inc., which operates Nommie (“Nommie,” “we,” “us,” or “our”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, share, and protect your personal information when you use our mobile application, website, and related services (collectively, the “Service”).

By using the Service, you agree to the collection and use of information as described in this policy. If you do not agree, you should not use the Service.

2. Information We Collect

2.1 Information You Provide

• Account information: name, email address, and password when you register
• Nommie Ring waitlist: if you join the waitlist, the email address you give (on our website) or your account (in the app), your consent, the date, and any campaign tags in the link you used. We use it only to tell you about the Nommie ring, and you can leave the waitlist at any time
• Profile data: age, height, weight, gender, activity level, and dietary goals
• Food data: photos of meals, text descriptions of food, barcode scans, and manual food log entries
• Health data: weight measurements, nutritional intake history, and calorie goals
• Communications: messages you send to our support team or through the AI chat feature
• Social media handles: if you tell us in the app that you post on TikTok or Instagram, the handles you enter and any note you add. We use them only to contact you about featuring your posts or joining our creator program, and we keep them in BrandBeacon, the service we use to run that program. You can ask us to delete them at any time

2.2 Information Collected Automatically

• Device information: device type, operating system, unique device identifiers, and app version
• Usage data: features used, pages visited, actions taken, timestamps, and session duration
• Log and diagnostic data: error reports, crash logs, and performance metrics
• Session recordings: to understand where the app confuses or fails people, we may record how the app's screens are used during a session (screen layout, taps, and navigation), processed by PostHog. These recordings are aggressively masked before anything leaves your device: all text you type, all images (including your food photos), and all system photo/contact pickers are replaced with placeholders, and no app logs are captured. What we receive shows the shape of your journey through the app, not your content. Recordings are throttled snapshots, not continuous video, and are used solely for product improvement
• Install source: if you install the app from a creator's link (an install that AppsFlyer attributes to that link, not an organic one), we record the AppsFlyer install ID, the creator's code, and the install time, even before you create an account. To limit abuse, we also keep a one-way coded version of your network address (never the address itself) for about 2 days. If you then sign in or start a guest session, we link that record to your account.

2.3 Information from Third Parties

If you sign in with Apple, Google, or another authentication provider, we receive your name, email, and profile identifier as permitted by your settings with that provider.

If you install the app from an ad or a creator's link, AppsFlyer tells us which link or campaign the install came from.

3. How We Use Your Information

We use your information to:

• Provide, maintain, and improve the Service
• Analyze food photos and descriptions to estimate nutritional content
• Generate personalized nutrition insights and recommendations
• Process subscriptions and payments
• Send you service-related notifications and updates
• Respond to your support requests and communicate with you
• Improve our AI models using de-identified, aggregated data
• Detect, prevent, and address technical issues and security threats
• Comply with legal obligations

4. How We Share Your Information

We do not sell your personal information. We may share your information in the following limited circumstances:

• Service providers: We share data with trusted third-party providers including cloud hosting (Supabase), payment processing (Stripe for web checkout; Apple and Google for in-app purchases), AI food analysis (Google Gemini), and analytics (PostHog).
• Install attribution (AppsFlyer): shortly after launch (on iPhone, after the app asks for tracking permission), the app starts AppsFlyer, which tells us whether an install came from an ad or a link. We send AppsFlyer three in-app events: your first food scan, creating an account, and starting a free trial or a paid subscription (order ID, product, price, and currency). On iPhone, AppsFlyer can use your device's advertising identifier only if you allow tracking.
• Ad measurement (Meta): the app includes Meta's SDK with its automatic app events turned on, which report events such as app installs and app opens to Meta so we can measure our Facebook and Instagram ads. On iPhone, the app tells Meta that ad tracking is allowed only if you allowed tracking in the iPhone prompt. On Android, Meta may use your device's advertising ID, which you can reset or delete in your Android settings.
• Subscriptions (RevenueCat): in-app subscriptions are managed through RevenueCat. We identify you to RevenueCat by your account ID and email address, and RevenueCat receives your App Store or Google Play purchase and subscription status. We also give RevenueCat your AppsFlyer install ID, so we can tell which ad, link or post a subscription came from. We do not send your device's advertising identifier with it.
• Crash and error reporting (Sentry): crash reports, error reports, and a small sample of performance data are sent to Sentry, tagged with your account ID and the app version.
• Creator program (BrandBeacon): when someone clicks a creator's link, installs the app from it, or signs up or subscribes with a creator's code, we share the creator's code, the time, and an event identifier with BrandBeacon, the service we use to run our creator program. For an install, the identifier includes the AppsFlyer install ID; for a subscription, we also share the amount paid. We do not share your name or email with it.
• Legal requirements: We may disclose information if required by law or governmental request.
• Business transfers: In the event of a merger or acquisition, your information may be transferred as part of the transaction.
• With your consent: We may share information for other purposes when you give explicit permission.

4.1 Third-Party AI Processing: Google Gemini

Some features send parts of your profile to Google's Gemini so the model can respond to your situation. Meal planning and meal suggestions send your allergens, dietary preferences, and whether you have enabled GLP-1 mode, because a plan that does not know your allergies is not safe. The AI chat additionally sends your medication name, your display name, and, if you have turned on pregnancy mode, your pregnancy status and due date, so the coach can answer in context. It also sends your fasting status, so the coach knows whether you are mid-fast. Your GLP-1 dose and injection schedule are never sent. We use Google's paid Gemini tier, under which Google does not use what we send to train or improve its models.

Four more features send data to Gemini. Voice logging sends a text transcript of what you said, and it is the most used way of logging in the app. Pantry scan sends every photo of your fridge or pantry. Supplement scan sends the photo of the label. Your weekly nutrition summary sends your first name, your goal, your calorie and macro averages, the foods you log most often, and, if Pregnancy Mode is on, that you are pregnant and which trimester, though not your due date.

Food photo analysis sends only the photo and meal context, and no account identity. That applies to the photo scan specifically: the weekly summary sends your first name and the chat sends your display name. Our fuller Consumer Health Data Privacy Policy sets all of this out, including how we established it.

You must consent before any photos are sent, and you can withdraw consent at any time in Settings. If you are a Washington State consumer, see our Consumer Health Data Privacy Policy.

5. Data Storage and Security

Your data is stored on secure servers in the United States using Supabase (SOC 2 Type II). We implement encryption in transit (TLS 1.3), encryption at rest (AES-256), row-level security policies, and access controls limiting employee access to personal data.

6. Data Retention

We retain your personal information for as long as your account is active. If you delete your account, we will delete or de-identify your personal data within 30 days, except where required for legal purposes.

7. Your Rights

Depending on your location, you may have rights to access, correct, delete, export, or restrict processing of your personal data. To exercise any of these rights, contact us at privacy@nommie.ai. We will respond within 30 days.

8. Cookies and Tracking

Our web application uses essential cookies required for authentication and session management, and PostHog for product analytics. On our website, we do not use third-party advertising cookies or trackers.

9. Children's Privacy

The Service is not intended for children under 13. We do not knowingly collect personal information from children under 13. Contact us at privacy@nommie.ai if you believe a child under 13 has provided us with personal information.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy and updating the “Last updated” date.

11. Contact Us