Your information stays yours to control.

SugarCount AI privacy contact: 3230 Yonge Street #4218, Toronto, ON M4N 3P6, Canada. Send privacy questions or requests to sugarcountaibusiness@gmail.com. This policy covers the public website and connected iPhone, Android and companion features. Describing an integration does not mean it is enabled or approved for public use.

Vercel hosts this website and processes ordinary technical request information, such as IP address, browser information and request logs, for delivery and security. The website does not host your mobile account, accept card payments or read your health records. Essential browser storage remembers your privacy-notice choice. Marketing and optional website analytics are off.

The support form prepares a draft in your own email app; the website does not send or save those fields. If you send the draft, we and the mailbox provider receive the sender address and message to answer you. Avoid unnecessary health details, passwords, one-time codes and payment-card information. A support message is not marketing consent.

Information you provide may include email, display name, profile image, meal descriptions, chosen food photos, barcodes, scan results, portions, goals, dietary preferences, allergies, saved meals, SmartCart lists and app settings. These records can reveal sensitive health information. We use the records for the features you request, account recovery, saving and synchronizing information, and support. You can use manual entry without connecting a health device.

Apple or Google sign-in provides basic identity information for account access. Purchase systems provide product, entitlement, transaction, price, currency, renewal, refund and dispute information. We do not receive full payment-card numbers. Limited account, transaction, attestation and device-risk signals help verify access and prevent fraud; they are not advertising profiles.

After the in-app food-processing explanation and your affirmative permission, selected food photos or descriptions, dietary preferences and notes you choose to analyze may be sent through our server to OpenAI for nutrition estimates, meal ideas or swaps. Do not include faces, identity documents or unrelated medical information. The app resizes supported food photos and removes embedded metadata before sending the prepared image. Device health history and account details are not automatically included in food-photo analysis.

AI results are labelled as estimates and need your review. Requests use the OpenAI API with response storage disabled. This is not a promise of Zero Data Retention: OpenAI may retain abuse-monitoring information for up to 30 days under its standard policy, with exceptions for legal or safety requirements. OpenAI states API data is not used to train its models by default unless the customer opts in. We do not authorize use of Google Health information to train general AI models. Provider-specific retention exceptions still apply.

You may decline food processing or turn it off in Privacy Settings. This prevents new optional processing but does not by itself erase previously saved records or reverse processing already completed. Contact the privacy address for removal requests. A change of provider or materially different use requires an updated explanation and any required permission.

OpenAI API data controls

When enabled and permitted, chosen food-search terms go to USDA FoodData Central and scanned barcodes go to Open Food Facts through the backend. These are food-reference requests, not uploads of your account, private meal history or health-device records. Providers also receive ordinary technical request information. Coverage varies by product and country. Missing vitamins or minerals are unknown, not zero.

Food data and licences

Google sign-in does not grant access to Google Health. Connecting Fitbit uses a separate, optional Google Health authorization after an in-app explanation. The implemented read-only Google connection requests daily steps, active calories burned and dietary-sugar totals already logged in Google Health for the most recent three calendar days. These summaries appear separately beside SugarCount meals; they are not blood-glucose readings and do not add duplicate meals, grant Pro or earn referral rewards. Public Google Health approval and real-device verification remain pending.

Apple Health is available only on supported native Apple devices after you choose Connect and approve the requested data types. Optional writing of a meal you saved requires its separate sync setting and Apple permissions. Apple Watch companion summaries depend on the paired phone and permissions. Health connections are optional; denied or missing information is not treated as zero.

Approved Google Health summaries are stored privately against your SugarCount account in Supabase. OAuth credentials are encrypted on the server and are not included in the mobile bundle. Google Health information is not sent to OpenAI for food-photo analysis, sold, shared with advertising platforms, used for general AI-model training, or used for credit, insurance or employment decisions. Human access is limited to situations allowed by Google policies, such as your specific support consent, security investigations or legal requirements.

A successful Disconnect action revokes Google access and asks the backend to remove the connection credentials and imported Google Health summaries. If revocation cannot be confirmed, the app reports a failure rather than claiming success. You may also remove access in your Google account and ask us to remove previously imported data. Meal records you created separately remain until you remove them or complete account deletion. Apple permissions are managed in Apple Health or iOS Settings; turning off meal sync stops future writes, not records already written to Apple Health.

SugarCount AI handles information received from Google under the Google API Services User Data Policy and the Google Health API Developer and User Data Policy, including their Limited Use requirements. Use is limited to the visible features and choices described here.

Google API Services User Data Policy

Google Health API Developer and User Data Policy

Camera or gallery access is requested for a food photo you choose. Notifications depend on your permission and available reminder features. If you choose Detect My Location, coordinates are rounded to two decimal places before a reverse-geocoding request to BigDataCloud; this suggests city, country and timezone and is not continuous background location tracking. You can deny permission and enter location manually.

If you choose voice entry, the available device or platform speech-recognition service handles the microphone input and returns text. It may process audio off the device under its own terms. SugarCount does not implement a first-party raw-audio upload in this path; that is not a guarantee that platform speech processing stays on-device. Platform and permission behavior must be verified on the final supported devices.

Optional first-party traffic analytics require their own choice and must not include names, emails, food images, nutrition records or health history. Security and fraud-prevention information may be processed as necessary to protect the service. Owner access to named accounts, verified purchases and support requests is separate from traffic analytics and restricted to authorized duties. Cross-app advertising tracking and advertising identifiers are not enabled.

Because the current service does not track you across other companies for advertising or share information with a data broker, Apple’s App Tracking Transparency prompt is not shown. If that practice changes, the required notice and permission must be reviewed before tracking starts.

Supabase provides authentication, database, private file storage and server functions; the connected project is in the United States. OpenAI processes selected AI inputs as described above. Apple, Google and RevenueCat handle applicable purchases and entitlements. Resend delivers enabled account/security messages and reports delivery, bounce and complaint status. Vercel hosts the website; our mailbox provider processes support messages. USDA, Open Food Facts and BigDataCloud receive the limited requests described here.

Instacart is the only grocery-checkout provider where enabled. Shopping-list information and handoff information needed for that action go to Instacart; Instacart and retailers control their checkout, payment, availability, fulfilment and privacy practices. We do not send health-device history to grocery checkout. Provider relationships do not remove our responsibility for the disclosures and choices we control.

Where European or UK data-protection law applies, account and requested service processing relies on performing our agreement with you where appropriate; essential security, fraud prevention and service protection may rely on legitimate interests; legally required records rely on legal obligations. Optional AI, health and other sensitive processing uses your consent or explicit consent where required. We assess an additional legal condition before processing health information. Consent is not inferred from merely using the website, accepting Terms or signing in with Google.

Under applicable Canadian law we seek meaningful consent for the relevant collection, use and disclosure, with express consent where required for sensitive information. Optional processing may be declined without agreeing to marketing. We do not use nutrition outputs to make solely automated decisions with legal or similarly significant effects about you.

We retain account, meal, scan, preference, shopping and imported health records while needed for the account and requested features, then remove or de-identify them when no longer necessary, subject to a verified deletion request and limited lawful exceptions. A shorter visible history window on a Free plan does not mean the underlying records were erased. Hiding scan history is not permanent erasure because saved meals and duplicate-request prevention can still reference the result.

Exports have a limited availability period shown in the app; the implemented export-file expiry is one day after completion. Expired files are queued for cleanup, whose completion must be confirmed rather than assumed from link expiry. Support, diagnostic and security records are kept only while needed to handle the matter, protect the service or meet an applicable obligation. Provider backups and logs have separate retention cycles; deleting active records does not instantly erase every backup.

Limited purchase, accounting, tax, fraud or dispute evidence may require longer retention under applicable law. Any exception must be specific and limited; it is not a reason to keep meal photos or health history as financial records. A final financial-record retention period has not yet been approved for public launch. No universal multi-year period or immediate-erasure guarantee is promised here.

Automatic account-deletion processing is not enabled in the current prelaunch release. Contact sugarcountaibusiness@gmail.com from your account email to request deletion or help without the app. Do not send a password or verification code. We verify ownership, explain the applicable completion period and any lawful exception, and confirm completion separately. Opening an email draft, hiding a scan or uninstalling the app does not erase an account.

Deleting an account does not cancel an Apple or Google subscription. Cancel it separately through the store. We will explain any refusal, permitted extension or retained category when responding to your request.

Depending on your location, you may request access, correction, deletion, a portable copy, restriction, objection, withdrawal of optional consent, and information about collection and sharing. Applicable US rights may include an appeal of a denied request and non-discrimination for exercising rights. We do not sell personal information or share health records for targeted advertising. Where a legally applicable opt-out signal is received, we honor it for the covered processing; there is no advertising-sale activity on this website to opt out of.

Use available Profile → Data & Privacy controls or email sugarcountaibusiness@gmail.com. We verify identity proportionately and never ask for your password or verification code. Rights have legal exceptions; we explain the result and applicable review or appeal route. We respond within the deadlines that apply to the request, and notify you if a permitted extension is needed. EU/UK requests normally receive a response within one month.

You may complain to the Office of the Privacy Commissioner of Canada, the relevant provincial privacy authority, your EU/EEA supervisory authority, the UK Information Commissioner, or an applicable US regulator. Contacting us first is welcome but does not remove your right to contact a regulator. A separate Consumer Health Data Privacy Policy explains covered US health-data processing.

Consumer Health Data Privacy Policy

Information may be processed in Canada, the United States and other countries where disclosed providers operate, whose laws may differ from yours. Where required, transfers must be supported by a recognized adequacy decision, applicable contractual safeguards or another lawful mechanism. You may ask about the safeguards relevant to your information. Availability in an app store is not evidence that every country requirement has been completed.

We use access controls, private storage, encrypted transport and restricted owner access to reduce risk. These measures do not make the service unbreachable. We assess suspected incidents and make legally required notifications. We do not claim HIPAA, medical-device, SOC 2 or ISO certification merely because a provider offers a related service or certification.

The service is not intended for children under 13. Higher local age-of-consent requirements and valid parent or guardian authorization may apply to minors. A statement that someone is 13 or older does not replace required parental consent or age safeguards. Do not provide a child’s health information through another person’s account. Contact the privacy address if a child has provided information inappropriately.

Age-appropriate signup and any required parental-authorization process remain public-launch requirements; these policy words do not certify that those controls are complete. We will not silently change the service’s age eligibility through a policy update.

Marketing sending remains off. Signup, a purchase, a referral or a support request does not enrol you in marketing. Any future marketing programme needs its own applicable permission, sender identification and unsubscribe process; health information must not be used for advertising.

We show the policy version and update date. Material changes receive appropriate notice, and a new purpose needing consent requires a new affirmative choice. Continued use or silence is not treated as consent to a new optional or sensitive-data use.