Learn how to handle Fructose Malabsorption: Fructose Malabsorption treatment, diet, medication, and tips
Fructose Scanner (“we,” “our,” or “the App”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our mobile application. The protection of your personal data is of a particularly high priority for the management of FructoHelp.
Developer: Niklas Weber
Contact: nick@fructohelp.com
Internet address: www.fructohelp.com
Core scanning and ingredient lookup features operate entirely on your device and do not transmit any data to our servers. No accounts are required to use the App, and no advertising is displayed. AI-powered features (food photo analysis, menu analysis, Ask AI) transmit food images, menu text, and questions to our backend infrastructure (Supabase) and to OpenAI for processing. When AI features are used, we log anonymous usage metadata including device identifiers, request counts, token usage, and costs for the purposes of rate limiting and abuse prevention. Data processed by OpenAI is subject to their API data usage policy, which provides that API inputs and outputs are not used to train their models and are retained for up to 30 days for abuse monitoring.
Fructose Scanner is designed with privacy as a core principle. We do not collect personal identification information such as name, email address, or phone number. We do not collect location data, advertising identifiers, or health or medical information beyond what you voluntarily provide to AI features. Scan history from core scanning is stored locally on your device and is not transmitted to our servers.
When you use AI-powered features, the following data is transmitted to our servers: Food images (base64-encoded) are sent for AI food identification. These images are forwarded to OpenAI for processing and are not stored after processing. Menu text obtained through OCR is sent for AI menu analysis, forwarded to OpenAI, and not stored after processing. Questions submitted through the Ask AI feature are sent to our backend and forwarded to OpenAI, and are not stored after processing. A device identifier, which is a randomly generated ID stored on your device, is collected for rate limiting and abuse prevention. This identifier is not linked to your real identity and cannot be used to identify you personally. Usage metadata including request type, AI model used, token counts, estimated cost, success or failure status, and timestamps is stored on our Supabase backend indefinitely. This metadata does not include the content of your images, text, or questions. Your dietary profile (severity level, avoided ingredients) is sent with each request to personalize AI responses but is not stored server-side.
The following data is stored exclusively on your device and is never transmitted to our servers: Your dietary profile, used to personalize risk assessments, is stored in a local SQLite database. Saved products, comprising your personal library of safe foods, are stored in the local SQLite database. App preferences such as color-blind mode settings are stored in SharedPreferences. Onboarding status tracking tutorial completion is stored in SharedPreferences. You retain full control over this data. You may delete it at any time by clearing app data in your device settings or by uninstalling the application.
We use Google ML Kit for on-device text recognition (OCR). All OCR processing occurs on your device. No images or text are sent to Google servers.
When you scan a barcode, we query the Open Food Facts database. Only the barcode number is transmitted. In return, we receive product name, ingredients, and brand information. Open Food Facts is a non-profit, open database.
When you use AI-powered features, food images, menu text, or questions are sent to OpenAI along with your dietary profile for processing. OpenAI’s API data usage policy provides that API inputs and outputs are not used to train their models and are retained for up to 30 days for abuse monitoring.
Our AI features use Supabase as backend infrastructure. Anonymous device identifiers, usage counts, token metrics, and cost data are stored on Supabase servers located in the EU (Frankfurt). No personally identifiable information is stored.
When you download or purchase the App through the Apple App Store or Google Play Store, your transaction is subject to their respective privacy policies.
Your data is protected through the following measures: dietary profiles, saved products, and scan history remain on your device. All communication with our backend uses HTTPS and TLS encryption. Device identifiers are randomly generated and not linked to your real identity. Server-side controls prevent abuse of AI features. No passwords or credentials are required. We collect only the minimum data necessary for rate limiting and abuse prevention.
Fructose Scanner does not knowingly collect information from children under the age of 13. The App does not require account creation or personal information input.
We may update this Privacy Policy from time to time. Changes will be posted within the App. Continued use of the App after changes constitutes acceptance of the updated policy.
Under the General Data Protection Regulation (GDPR), you have the following rights: Right to Access – all local data is visible within the App, and server-side usage data is anonymous and cannot be linked to your identity. Right to Deletion – you may clear app data or uninstall the App to delete all local data. Right to Data Portability – export features are available within the App. Right to Opt-Out – you may disable AI features in the App settings to prevent any data transmission to our servers.
If you have questions about this Privacy Policy, you may contact us at:
E-Mail: nick@fructohelp.com
Internet address: www.fructohelp.com
Niklas Weber
Dachsteinstr. 29
81825 München
Germany