Privacy Policy

Last updated: July 21, 2026

AskFork helps users estimate food and drink nutrition from a selected or captured photo plus optional meal context. AskFork is not a medical device, diagnosis, treatment, or substitute for a clinician, dietitian, CGM, or lab test.

Your Permission Before AI Analysis

AskFork does not send a selected photo for AI analysis until you turn on the in-app permission that names OpenAI and then tap Analyze. The permission is reset when you select a new photo. You may decline by leaving the permission off. Turning the permission off before the next analysis revokes it for future uploads.

What Is Sent and Who Receives It

When you grant permission and tap Analyze, the AskFork app sends your selected food or drink photo to AskFork's server together with the optional dish or label text, goal, meal moment, meal intent, portion setting, and glycemic preference you entered. If you separately enable profile personalization, the analysis input also includes the age, height, weight, activity, dietary style, allergens, and nutrition targets you entered. AskFork's server sends that analysis input to OpenAI, LLC through the OpenAI API so OpenAI can generate one nutrition estimate. OpenAI is AskFork's third-party AI service provider.

Your name, email address, phone number, restaurant or venue, current location, social share comment, fasting data, and on-device history are not sent to OpenAI as part of food-photo analysis. AskFork does not send raw photos or private analysis text to advertisers.

How OpenAI Handles API Data

AskFork requests that OpenAI not store response application state. OpenAI states that API data is not used to train its models by default unless the API customer opts in. OpenAI may retain API input and output in abuse-monitoring logs for up to 30 days, unless a shorter retention control applies or longer retention is required by law or needed to protect its services or others. OpenAI is required to protect this data under its API terms, privacy commitments, and security controls. AskFork requires service providers that receive user data to provide the same or equal protection described in this policy and required by applicable law.

Information AskFork Processes

AskFork processes the analysis input described above, the AI estimate returned by OpenAI, and actions you choose such as eat, modify, pass, or save. If you create an optional account, AskFork processes the email address or phone number you verify, a display name you choose, verification and security records, and any profile fields you explicitly enable for cloud sync. Production systems may store analysis metadata, estimates, flags, swaps, decision events, and support or privacy requests for product operation, abuse prevention, support, and compliance. AskFork does not intentionally store the uploaded raw photo in its SQL database.

Account Verification and Security

AskFork uses short-lived one-time codes to verify an email address or phone number. Verification codes expire, attempts and requests are rate-limited, and AskFork stores one-way hashes rather than the code or session token itself. The iOS app stores its account session in the Apple Keychain. Delivery providers receive the destination and verification message only to send the code.

On-Device History

If you log or save an analysis, the app stores the estimate and a compressed copy of its food photo locally on your device so it can appear in History. You can remove that local data with the History trash control. Deleting the app also removes its on-device data, subject to Apple's device backup behavior.

AI Estimates and Safety

Results are directional and may be wrong. Do not use AskFork for emergencies, diagnosis, treatment decisions, allergies, medication decisions, or medical nutrition therapy.

Health-Adjacent Data

AskFork may let you enter optional wellness context such as hydration, fasting, activity, cravings, reactions, or glucose readings. These fields are user-controlled and should not be treated as medical records. Sensitive health signals, medications, biomarker readings, diagnoses, exact location, and fasting details are excluded from advertising audiences by default.

Sharing, Services, and Offers

When you tap the location button in the iOS share composer, Apple Core Location and MapKit process your current location to return a human-readable locality and, when available, a nearby food venue suggestion. AskFork does not send that location to its server or to OpenAI. The suggested venue and location remain editable on your device and leave the app only if you choose a destination in Apple's share sheet. Apple's privacy terms apply to its location and maps services.

When you choose Share, AskFork creates a card on your device and opens Apple's share sheet. The photo, estimate, venue, location, or comment you choose to include is sent only to the app or person you select, and that recipient's privacy terms apply. AskFork may show clearly labeled partner, grocery, restaurant, coaching, or sponsored options. We may log contextual impressions and clicks, but we do not share raw photos or private analysis text with advertisers.

Some grocery, pantry, and supplement links are paid affiliate links. AskFork may receive a commission when you buy through an approved retailer link; this does not change the price you pay or the editorial order of products. Required program-specific disclosure appears next to an active paid link. When an approved Amazon Special Link is shown: As an Amazon Associate I earn from qualifying purchases.

Retailer links open the retailer directly. AskFork may record an anonymous first-party click containing catalog IDs, placement, and a broad editorial or contextual label, while the retailer or affiliate network handles the order under its own privacy and purchase terms. AskFork does not receive your retailer payment card, order contents, shipping address, returns, or merchant account credentials. AskFork is not the seller. Contextual product ordering happens on your device only after you enable contextual offers; raw meal text, diagnoses, medications, biomarkers, fasting details, and exact location are not sent with the catalog request or click.

Retention and Deletion

AskFork retains server-side analysis and event metadata only as long as reasonably needed for product operation, abuse prevention, support, and compliance. You can delete an optional account inside the Profile tab. If a recurring web subscription is active, AskFork requires it to be cancelled or scheduled for cancellation first so deleting the account cannot leave an orphaned charge. Account deletion removes the verified contact and synced profile, revokes all sessions, and leaves only an anonymized technical record needed to preserve database integrity and a deletion receipt. Limited billing, tax, refund, dispute, and fraud-prevention records may be retained when required by law or reasonably necessary to resolve a transaction. Local meal history remains on your device until you remove it from History or delete the app. You may also contact support to request export or deletion of other server-side data associated with information you provide.

Payments

Apple processes the paid iPhone app download and any eligible future in-app purchase. Apple provides AskFork with limited transaction and entitlement information; AskFork does not receive your full card number from Apple.

If AskFork enables an optional web subscription, AskFork uses Stripe-hosted Checkout and Stripe's customer portal. Stripe receives the contact, payment, and billing information you enter there. AskFork sends Stripe an internal account identifier, the selected server-approved plan, and transaction metadata. AskFork receives provider customer, subscription, invoice, payment-status, refund, and dispute records needed to grant access, provide support, prevent fraud, and meet legal obligations. AskFork does not send food photos, meal history, wellness profile fields, diagnoses, medications, biomarkers, fasting details, or exact location to Stripe. AskFork does not receive or store your full card number. Stripe's privacy policy applies to Stripe's processing.

Contact

For privacy or support questions, visit AskFork Support.