This Policy is issued by Lead Logger LLC, an Illinois limited liability company, the operator of the Cut AI iOS application. Lead Logger is the controller of personal data processed in connection with the App. It describes what we collect, why, who we share it with, and the rights you may exercise. Contact: cutai@lead-logger.com.
When you sign in with Apple, we receive an Apple-issued identifier and, at your election, your name and either your real email address or an Apple-relay email address. We retain the resulting account identifier and any display name you supply. We do not receive your Apple ID password.
You provide fitness-related information during onboarding: biological sex, age, height, current weight, goal weight, primary goal, training experience, training location, available equipment, weekly schedule, session length, target weekly rate of weight change, diet, activity level, self-reported obstacles or roadblocks to training, and, if supplied, a referral code. This is stored as a structured record associated with your account. The age value you supply is also used to enforce the eighteen-and-over age requirement described in Section 9; if the value indicates you are under eighteen, the App will not provision an account.
If you choose to scan a meal, the App asks for your express permission before opening the camera. The image is resized and JPEG-compressed on your device, then transmitted over TLS to our edge function. The edge function forwards only the meal image to Anthropic's Claude API to identify foods and estimate nutrition. We do not write the meal photograph to our database, file system, or object store. Only the nutrition result you choose to save is stored.
A meal photograph may contain identifying features, surroundings, or images of other persons. Do not include a face, body, document, or other sensitive content in a meal scan. We do not request, accept, or use body photographs to generate workouts.
Each generated workout, the date issued, and whether you marked it complete are stored on our backend under your account. A cache of recent workouts, your onboarding answers, streak count, most recent workout date, in-progress workout state, and your AI-consent acknowledgements are stored locally on your device in iOS UserDefaults. The meal photograph is held in memory only while the scan is processed and reviewed.
When you start, restore, or cancel a subscription, Apple and RevenueCat exchange transaction information with the App and our backend (product identifier, entitlement status, expiration, renewal status). We use this to verify your entitlement before granting paid features and, when our Meta integration is enabled, to measure subscription conversions and revenue.
The App uses the Meta SDK only for app activation, advertising attribution, and subscription-commerce funnel events such as viewing a subscription offer, beginning checkout, and confirming payment information. These events may include an offer product identifier, currency and value for a real offer, a Meta-generated anonymous identifier, the identifier for vendor (IDFV), and basic device and App information. RevenueCat may send subscription lifecycle events and transaction value to Meta on our behalf.
We do not send onboarding answers, meal photographs, HealthKit data, fitness profiles, exercise activity, workout activity, food-scan activity, exercise or food names, or free-form search text to Meta. If you authorize tracking through Apple's App Tracking Transparency prompt, Meta and RevenueCat may also receive or use the advertising identifier (IDFA) for attribution. If you decline, the App marks advertiser tracking as disabled and does not make the IDFA available for this purpose. You can change this permission in iOS Settings.
Our backend derives a SHA-256 HMAC of your authentication identity using a server-side secret. This pseudonymous identifier enforces a per-identity daily generation limit and records account-deletion events for fraud prevention. The HMAC is not reversible to your name or email, but it remains personal data and we treat it as such.
We do not access your location, microphone, contacts, calendars, messages, or social-graph data. We do not engage data brokers. The App does not contain Firebase, Mixpanel, Amplitude, PostHog, AppsFlyer, Adjust, Branch, Sentry, Crashlytics, Bugsnag, Datadog, OneSignal, Segment, or a third-party Google SDK. We do not deploy a browser marketing pixel inside the native App or its legal-document web views. Our use of the Meta SDK, RevenueCat attribution, device identifiers, and the App Tracking Transparency prompt is described in Sections 1, 3, and 4.
We process personal data to: provide the App's core functions (generating workouts, persisting your workout history, tracking streaks); authenticate you; verify entitlement before granting paid features; prevent fraud and abuse, including enforcing per-identity daily generation limits; diagnose errors; measure advertising performance and conversions; optimize advertising delivery; build or reach advertising audiences where permitted by your settings and applicable law; and comply with applicable legal obligations.
We do not sell personal information for money. Disclosure of app events and identifiers to Meta for advertising measurement, optimization, or audiences may be treated as “sharing,” “targeted advertising,” or cross-context behavioral advertising under some privacy laws. You can limit this processing by declining or disabling tracking in iOS Settings and by contacting us as described in Section 9. We do not engage in automated decision-making that produces legal or similarly significant effects within the meaning of Article 22 of the GDPR.
In plain language: With your permission, Cut AI sends fitness-profile text to Anthropic to create workouts. If you separately choose to scan a meal, Cut AI sends that meal photo to Anthropic to estimate nutrition. Cut AI never sends a body photograph to Anthropic.
Cut AI generates workouts by transmitting your onboarding fitness profile and recent workout history to Anthropic, PBC through Anthropic's commercial Claude API after you affirmatively agree at the point of generation. Anthropic returns a structured workout plan, which we store and present to you. For the optional meal-scanning feature, Cut AI separately asks for your permission before transmitting the meal image to Anthropic; Anthropic returns a structured nutrition estimate.
We do not transmit your name, email address, account identifier, or device identifiers to Anthropic. A meal photo may nevertheless contain information you place in its frame, so photograph only the food you want analyzed.
Our use of the Claude API is governed by Anthropic's Commercial Terms of Service and Data Processing Addendum. Under our agreement with Anthropic: Anthropic acts as our data processor; Anthropic is contractually prohibited from using API inputs or outputs to train its models; and international transfers are governed by Standard Contractual Clauses incorporated into the agreement. Anthropic's own retention, security, and transfer practices are governed by Anthropic's then-current Privacy Policy and Trust Center, available at privacy.claude.com and trust.anthropic.com. We do not adopt or guarantee any representation made by Anthropic about its own practices; consult those documents directly.
We do not use any other AI, machine-learning, computer-vision, biometric, embedding, or transcription service. The App does not perform on-device computer vision, face detection, pose estimation, or biometric template extraction.
With your express permission, the App may request the following HealthKit permissions: read access to body mass, height, active energy burned, and step count; and write access for workout sessions. HealthKit data accessed under these permissions remains on your device within Apple's HealthKit framework and is not transmitted to any server under our control. HealthKit data is not used for advertising, marketing, or data mining, is not sold, and is not disclosed to any third party except with your explicit consent or as required by law. Permissions may be revoked in iOS Settings at any time.
The App may ask for permission to deliver notifications, used to remind you to complete your daily workout and to surface session-related prompts. If you grant permission, scheduled notifications are produced locally on your device by iOS; the App does not maintain a server-side push service, does not collect a remote-notification device token for marketing, and does not engage any third-party push or messaging provider (such as OneSignal, Firebase Cloud Messaging, or Airship). You may revoke notification permission at any time in iOS Settings.
The App may render this Privacy Policy, the Terms of Service, and similar legal or informational pages inside an in-App web view (Apple's WKWebView). These web views load static documents from URLs we control and do not transmit your account identifier, meal photograph, onboarding profile, or workout history to the loaded page. We do not embed third-party trackers, advertising pixels, or session-replay scripts in these documents.
We retain your account record, onboarding profile, workout and nutrition history, and pseudonymous identifier for the duration of your account. A meal photograph is not retained by us beyond the duration of the scan request and your on-device review. The pseudonymous identifier and account-deletion ledger are retained indefinitely for fraud prevention. Operational logs are retained by our infrastructure provider as set forth in its then-current documentation and may include request identifiers and the pseudonymous identifier; they do not contain meal photographs.
Network traffic is encrypted in transit using TLS. Data at rest is encrypted by our infrastructure provider. Database access is governed by row-level security policies enforcing per-account isolation.
You may delete your account at any time within the App. Open your profile and tap "Delete Account." Upon confirmation, our backend records a deletion event (the pseudonymous identifier, the identifier of the deleted authentication record, and a timestamp) and then permanently deletes your authentication record. Deletion cascades to remove your profile, workout and nutrition history, and rate-limit record. The deletion-ledger row is retained for fraud prevention and contains no name, email address, meal photograph, or workout content.
Active App Store subscriptions are managed by Apple and must be cancelled separately through your Apple ID subscription settings. Deletion of your Cut AI account does not cancel an active App Store subscription. If you cannot complete deletion within the App, email cutai@lead-logger.com from the email address associated with your account; we will process the request within thirty (30) days.
You have the rights of access, rectification, erasure, restriction of processing, data portability, and objection; the right to withdraw consent; and the right to lodge a complaint with your supervisory authority. We rely on the following lawful bases: performance of a contract under Article 6(1)(b) (providing the App); explicit consent under Article 9(2)(a) where a fitness profile constitutes special-category data; consent under Article 6(1)(a) for third-party AI processing, HealthKit, camera, notifications, and advertising tracking or audience use where required; legitimate interests under Article 6(1)(f) (security, fraud prevention, reliability, and limited advertising measurement where permitted); and legal obligations under Article 6(1)(c). International transfers to providers in the United States are governed by the transfer mechanism applicable to the relevant provider.
You have the rights to know, access, delete, correct, opt out of sale or sharing, limit the use and disclosure of sensitive personal information, and not to be discriminated against for exercising those rights. We do not sell personal information for money. Our disclosure of identifiers and app events to Meta for advertising measurement, optimization, or audiences may constitute “sharing” under the CCPA/CPRA. You may opt out by declining or disabling tracking in iOS Settings or by emailing us. Sensitive personal information is used only as reasonably necessary to provide the App's services and as otherwise permitted by Cal. Civ. Code § 1798.121(d).
Residents of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware, Iowa, Tennessee, New Jersey, New Hampshire, Minnesota, Maryland, Indiana, Kentucky, and Rhode Island may have rights under their respective comprehensive privacy statutes, including rights to access, correct, delete, or obtain a copy of personal data and to opt out of targeted advertising, sale, or qualifying profiling. We do not sell personal information for money or engage in profiling that produces legal or similarly significant effects. You can opt out of advertising tracking or audience use by declining or disabling tracking in iOS Settings or by contacting us.
To exercise any right described above, email cutai@lead-logger.com. We will respond within thirty (30) days.
The App is intended exclusively for adults aged eighteen (18) or older. During onboarding, you are asked to confirm your date of birth or age, and the App will refuse to provision an account if the supplied age is under eighteen. By using the App you represent and warrant that you are at least eighteen years old. The App is not directed to, marketed to, or intended for use by minors. We do not knowingly collect personal data from any person under eighteen. If we become aware that we have collected personal data from a person under eighteen, we will delete the account and associated data without undue delay; a parent or guardian may also request such deletion by contacting cutai@lead-logger.com.
We may amend this Policy. Material changes will be reflected by updating the effective date above and, where appropriate, by in-App notice. Where applicable law requires renewed consent for a change in processing, we will obtain that consent before the change takes effect.
Lead Logger LLC
State of Illinois, United States
Email: cutai@lead-logger.com