Privacy Policy

Benchlight Studio LLC operates FatChance and is responsible for the data handling described in this policy. References to “we,” “us,” and “our” mean Benchlight Studio LLC.

This policy describes data handled by the FatChance mobile and web application and public marketing website. FatChance helps you review restaurant nutrition, compare choices, personalize matches, build meals, and save useful selections.

FatChance’s restaurant data currently covers U.S. locations and menus. Menu items, portions, ingredients, and nutrition information may differ in other countries. This data coverage does not limit privacy rights provided by applicable law.

The public marketing website does not currently offer account sign-in or forms. Our website hosting provider may process technical request information and set cookies. Cloudflare processes information such as an IP address, browser or device details, timestamps, requested pages, and security logs to deliver and protect the website.

The hosting platform sets a first-party cookie named __Host-appgarden-visitor, observed to expire after approximately 90 days. Cloudflare may also set security cookies to help protect the website.

If you email Support, Fastmail processes the message and related mail metadata so we can receive and respond to your request. Support mail may also be forwarded to and handled in Google’s Gmail.

Supabase and Resend process your email address and authentication email content to deliver account-verification and password-reset messages. Delivery records help us investigate email failures and keep account access working. These service messages are separate from optional marketing emails.

• Email address, authentication information handled by our sign-in provider, and an optional preferred name.
• Goals, calorie and macro targets, body and activity details used by the optional target estimator, food preferences, allergy reminders, theme, location mode, and an optional city or ZIP code.
• Saved restaurants, menu items, meals, custom presets, current-meal selections, and comparisons.
• Optional marketing-email preference and feedback or menu-correction messages you choose to submit. Feedback may include the app version, platform, page or search context, source URL, restaurant or item context, and submission time needed to investigate the request.

FatChance requests foreground location only after you choose to use it. When nearby results load or refresh while device-location mode is active, the current coordinate pair is sent to our Supabase backend to find nearby supported restaurant branches. We do not save precise coordinates to your profile, local app cache, or analytics. Your device and infrastructure providers may still process limited technical records under their own policies.

If you enter a city or ZIP code, that general location and your chosen location mode may be saved so the app can restore your preference.

Apple or Google processes subscription purchases and payment details. FatChance uses RevenueCat to obtain available offers and maintain PRO entitlement status. We send a FatChance account identifier and your account email so we can find your subscription record and help with access requests. We receive product, transaction, trial, renewal, expiration, and entitlement information needed to provide paid access. FatChance does not receive your full payment-card number.

When usage analytics is enabled, we also send limited JavaScript error reports to PostHog to diagnose app problems. Reports include error categories, severity, and limited technical details about where an error occurred in the app’s code, alongside the analytics metadata described below. We remove original error messages, function names, full URLs, local file paths, and source-code snippets before sending reports. Turning off usage analytics also stops this error reporting.

We use PostHog in the app to understand whether it works as intended: where people stop during setup, whether they use or skip the calculator, which features and restaurant results are useful, and where actions fail. The app sends limited usage events, including screen names, selected actions, app version, platform, Free or PRO status, and restaurant or item identifiers. Calculator analytics records which fields were changed, never the answers or calculated targets.

Random installation and session identifiers let us measure setup completion and return visits without linking analytics to your account. These records are pseudonymous, not completely anonymous. Analytics excludes your email, preferred name, account ID, raw search text, body measurements, nutrition targets, allergy or diet settings, precise location, and feedback text. We disable session recordings, advertising identifiers, analytics person profiles, and IP-based location enrichment. Device names, device model, operating-system version, locale, time zone, and screen dimensions are removed from event properties. As with any online request, our service providers receive connection information such as an IP address to deliver and secure the service.

Usage analytics is on by default unless you previously turned it off. You can turn it off on the in-app Privacy Policy page or in Profile → Account. The preference is saved on this device or browser, applies across accounts on it, and is separate from marketing email and required service operations. Turning it off stops new analytics collection and discards unsent queued events; it does not recall information already sent. All app features remain available. Clearing app storage or reinstalling may reset the preference to the default.

The app stores session, profile and saved-data caches, current meal and comparison state, onboarding draft, theme, catalog caches, trial-reminder metadata, account-scoped undelivered feedback, and a short deletion-recovery record, and your usage-analytics preference on your device when needed for app operation and privacy preferences. While analytics is enabled, a random identifier and an analytics queue may also be stored locally.

• Create and secure your account and sync your data.
• Personalize nutrition context, matches, filters, and saved work.
• Provide nearby search, subscription access, trial reminders, support, and menu-data review.
• Diagnose reliability problems and understand product use with privacy-limited analytics.

We use Supabase for authentication, application data, and backend functions; Resend for account-verification and password-reset email; RevenueCat and Apple or Google for subscriptions; Apple and Google for optional social sign-in; PostHog for privacy-limited analytics; OpenAI’s Sites service for website hosting and Cloudflare for public website delivery and security; Fastmail and Google’s Gmail for support email; and device operating-system services for location and local notifications. Foursquare Open Source Places is an imported branch-data source and does not receive your live location from the app.

We may disclose information when required by law, to protect users or the service, or as part of a business transaction subject to appropriate safeguards. The current app does not use personal information to serve third-party advertising.

Account-linked application data is kept while your account is active and as needed to provide the service. You can initiate permanent account deletion from Profile → Account. Deleting your account removes the Supabase account and cascading profile, save, meal, preset, preference, and submitted-feedback records. User-scoped app caches and pending local feedback are also cleared from that device.

Pseudonymous analytics cannot currently be matched back to your FatChance account. Subscription platforms and service providers may retain transaction, security, backup, or legal-compliance records under their own retention rules. Account deletion does not cancel an Apple or Google subscription.

• Turn usage analytics on or off in Profile → Account or on the in-app Privacy Policy page. This preference is separate for each device or browser.
• Update your preferred name, goals, preferences, and marketing-email choice in Profile.
• Decline location or notification permission in device settings; core browsing remains available.
• Delete your FatChance account from Account Management or follow the public account-deletion instructions linked below.

We use access controls, user-scoped database rules, secure transport, and limited client configuration intended to protect data. No storage or transmission system can be guaranteed completely secure.

FatChance is intended for a general audience and is not directed to children under 13. If we learn that a child under 13 provided personal information, we will take steps to delete it.

If you believe a child under 13 has provided personal information, contact support@fatchanceapp.com so we can investigate.

We may update this policy when the service or its providers change. The current version and update date will remain available here. Email support@fatchanceapp.com for privacy questions or requests.