Last updated: [Publication date — set when deployed]
Fuelbit is an AI-powered food and nutrition tracking application operated by a sole proprietor established in Germany.
The controller within the meaning of Article 4(7) of the General Data Protection Regulation ("GDPR") is:
[First and last name — set before publication]
trading as Fuelbit
[Street and house number — set before publication]
[Postcode — set before publication] Weimar
Germany
Email: privacy@fuelbit.app
For privacy-related requests, please use the subject line "Privacy Request".
In this Privacy Policy, "Fuelbit", "we", "us" and "our" refer to the controller identified above.
This Privacy Policy applies to the processing of personal data in connection with:
This Privacy Policy does not apply to independently operated third-party services that have their own privacy policies, including app stores and payment providers acting as independent controllers.
The personal data we process depends on how you use Fuelbit.
When you visit our website or connect to our Services, our hosting and infrastructure providers may automatically process:
We process this information to deliver the website and app, ensure technical stability, detect misuse and protect our systems.
When you register for or use a Fuelbit account, we process:
Authentication is provided through Supabase Auth.
We do not have access to your password in readable form.
Depending on the features you use, you may provide or generate:
Some of this information, individually or in combination, may constitute data concerning health within the meaning of Article 9 GDPR.
Please do not enter medical diagnoses, medication information, genetic data or other sensitive information that is not necessary to use Fuelbit.
When you use the photo-analysis feature, we process:
Fuelbit is intended to analyse photos of food. Please avoid uploading photos containing:
We do not use facial-recognition technology.
Based on an uploaded food photo, Fuelbit may generate estimates concerning:
These results are estimates and may be inaccurate. You can review and correct the generated result before or after saving it.
If you give your consent, we use PostHog Cloud EU to understand how Fuelbit is used. See PostHog's privacy policy.
The analytics data may include:
We configure PostHog so that it does not intentionally receive:
We never call an identification function that would link analytics data to your account; analytics remain tied to a random device identifier, and no person profiles are created. Session recording is disabled. IP-based location enrichment is disabled at the project level, and the app additionally strips disallowed data fields before any event is sent.
Although we do not intentionally send directly identifying information to PostHog, analytics identifiers and technical information may still constitute personal data. We therefore describe this processing as pseudonymous analytics rather than claiming that it is completely anonymous.
PostHog analytics are activated only after you have given the required consent. Declining or withdrawing consent does not prevent you from using Fuelbit's core features.
You may configure local reminders, for example for water intake, fasting or meal tracking.
Local notifications are generated on your device using the settings you select. You can disable them through the app or your device settings.
We do not use remote push notifications for these reminders.
If you purchase a paid subscription or premium feature, we may process:
Payments are processed by:
Stripe (Stripe Payments Europe, Ltd.)
Where you choose to pay using Apple Pay or Google Pay, the payment is initiated through that wallet and processed by Stripe. Apple or Google act as independent controllers for the wallet itself under their own privacy policies (Apple, Google). We receive confirmation of the payment and the limited transaction details listed above, not your full card number.
If Fuelbit is distributed via Google Play with Google Play Billing in the future, Google will be added as a payment provider.
We do not normally receive your complete payment-card number.
The relevant app store or payment provider may process payment and account information as an independent controller under its own privacy policy.
If you contact us, we process:
Please do not send passwords, complete payment-card information or unnecessary health data through email.
Where the GDPR applies, we process personal data on the following legal bases.
We process account data, meal records, goals, water logs, fasting records, photos and nutrition information to:
Legal basis: Article 6(1)(b) GDPR — performance of a contract or steps taken at your request before entering into a contract.
To the extent that weight, nutrition goals, food logs, fasting information, photos or calculated results constitute data concerning health, we process them on the basis of your explicit consent.
Additional condition: Article 9(2)(a) GDPR — explicit consent to the processing of data concerning health for the specified Fuelbit purposes.
You may withdraw your consent at any time. Because the relevant health-related information is necessary for Fuelbit's core nutrition-tracking functionality, withdrawal may mean that we can no longer provide some or all account-based features. You may still exercise your rights concerning information already processed.
Withdrawal does not affect the lawfulness of processing carried out before withdrawal.
We send a food photo to Groq Cloud to identify food and estimate nutritional information. See Groq's privacy policy.
Legal basis: Article 6(1)(b) GDPR.
To the extent that a photo or the resulting analysis constitutes or reveals health data, the additional legal basis is your explicit consent under Article 9(2)(a) GDPR.
We use PostHog analytics only after you provide consent.
Legal basis: Article 6(1)(a) GDPR.
Where the analytics technology stores information on or accesses information from your device, consent is also obtained in accordance with Section 25(1) of the German Telecommunications Digital Services Data Protection Act (TDDDG), unless a statutory exception applies.
You may withdraw analytics consent at any time. On this website, use to change or withdraw your decision. In the mobile app, use Profile → Data & Privacy → Product analytics. Withdrawal is as easy as giving consent and takes effect immediately.
We process server logs, authentication logs, IP addresses and security information to:
Legal basis: Article 6(1)(f) GDPR.
Our legitimate interests are the secure, stable and abuse-resistant operation of Fuelbit. We limit this processing to what is reasonably necessary and balance our interests against your rights and freedoms.
We process support requests to respond to you and resolve problems.
Legal basis:
We process subscription and transaction information to activate, administer and verify paid features.
Legal basis: Article 6(1)(b) GDPR.
We retain information required for tax, accounting and legal compliance.
Legal basis: Article 6(1)(c) GDPR.
We may process relevant information to comply with legal obligations or to establish, exercise or defend legal claims.
Legal bases:
Creating an online account requires an email address and authentication information.
Using nutrition-tracking features requires the relevant meal, nutrition or goal information. Using AI photo analysis requires the transmission of the selected photo.
You are not legally required to provide this information. However, without the information required for a feature, we cannot provide that feature.
Analytics consent is optional. Refusing analytics does not affect access to Fuelbit's core functionality.
Food photos linked to saved meal entries are stored in Supabase Storage in the West EU region in Ireland (eu-west-1). See Supabase's privacy policy.
A stored photo remains associated with the relevant meal until:
Deleting a meal through the app is intended to delete the associated active-storage photo.
Residual technical copies may remain temporarily in logs or caches until they are overwritten in accordance with the applicable retention cycle.
To analyse a photo, Fuelbit sends the image to Groq Cloud in the United States over an encrypted connection.
Groq processes the image on our behalf to generate an analysis. We do not authorise Groq to use your food photos or generated results to train or fine-tune AI models.
A second transmission to Groq occurs only if you use the AI buddy chat. In that case the message you write is sent together with the buddy's name and a snapshot of the current day — calories consumed and your calorie goal, protein, carbohydrates, fat, water intake against your water goal, and whether a fast is currently running — so that the reply can refer to your actual figures. This snapshot is nutrition and therefore health-related data, and it is transmitted as text rather than as an image. Your email address and your account identifier are not included. The same Zero Data Retention setting and the same transfer safeguards described below apply.
We have enabled Groq's Zero Data Retention setting for the relevant organisation and endpoints. According to Groq's applicable service documentation, customer input and output are not retained for system-reliability and abuse-monitoring purposes when Zero Data Retention is enabled. Groq may still process limited usage metadata that does not contain the submitted customer content.
We disclose personal data only where necessary to provide and secure Fuelbit, comply with the law or protect legal rights.
We use Supabase for:
Our primary Supabase project is hosted in the West EU region in Ireland (eu-west-1).
Supabase processes personal data on our behalf as a processor. Certain account, billing, security, support or operational data may be processed by Supabase and its subprocessors outside the EEA.
We use Groq Cloud for AI-based analysis of food photos.
Groq receives:
Groq acts as our processor for this processing.
To identify packaged products and look up nutrition values, our server functions query the following public reference databases. These requests contain the barcode or the food name you entered, together with our technical contact details. They do not contain your account identifier, email address or any other data that identifies you.
When you choose a password, the app checks it against the Have I Been Pwned breach database using the k-anonymity method: only the first five characters of a SHA-1 hash of the password leave your device, and the comparison is completed locally. Your password, the full hash, your email address and your account identifier are never transmitted. Privacy policy
Where a message from the contact form is forwarded to us by email, delivery is carried out by Resend (Resend, Inc., United States). Resend receives the name, email address and message text you submitted. This forwarding is only active when configured; the message is stored in our own database in either case. Privacy policy
With your consent, we use PostHog Cloud EU for product analytics.
PostHog's EU cloud infrastructure is hosted in Frankfurt, Germany.
PostHog receives only the analytics events and technical fields described in this Privacy Policy. We do not intentionally send meal content, photos, weight, goals or other health-related information to PostHog.
Apple, Google and any other payment provider used for subscriptions may receive transaction, account, device and payment information.
Depending on the processing activity, these providers may act as independent controllers or processors.
Our website hosting provider and authorised technical contractors may access limited data where necessary to:
Such access is restricted to authorised persons and is subject to confidentiality, security and data-processing obligations.
Current website hosting and content-delivery providers:
We may disclose information to:
Fuelbit is operated from Germany.
Some processing takes place outside the European Economic Area, particularly when food photos are transmitted to Groq in the United States or where a provider or subprocessor outside the EEA has authorised access to service data.
Where required, we use appropriate safeguards for international transfers, including:
For transfers connected with Groq: our contract for Groq Cloud is with Groq UK Limited, the contracting entity for EEA-domiciled customers under the Groq Services Agreement. Transfers to the United Kingdom are covered by the European Commission's UK adequacy decision. Processing involving Groq's United States infrastructure is safeguarded by the EU Standard Contractual Clauses incorporated in Groq's Data Processing Addendum, which is binding by incorporation into the Services Agreement.
For Supabase, PostHog and other processors, we use the applicable data-processing and transfer arrangements required by data-protection law.
You may contact us to request additional information about the safeguards used for an international transfer. Confidential or security-sensitive parts of contractual documents may be redacted.
We retain personal data only for as long as necessary for the relevant purpose, subject to legal and security obligations.
Your account, meal records, nutrition data, goals, water logs and fasting information are retained while your account is active.
When you delete your account, active account data is deleted without undue delay, normally within 30 days, unless retention is required by law or necessary for legal claims or security purposes.
A photo stored as part of a meal entry is retained until:
Groq's separate processing and retention are described in Section 6.3.
Fuelbit currently operates without automated database backups. Deleted data is therefore not retained in backup copies beyond the deletion process described above. Residual technical copies may persist briefly in logs or caches until they are overwritten.
PostHog analytics information is retained for:
12 months
After this period, the information is deleted or aggregated in accordance with our configuration and the provider's applicable procedures.
Withdrawal of consent prevents future analytics collection but does not necessarily require immediate deletion of lawfully collected aggregated statistics that can no longer be associated with you.
Ordinary server, sign-in and security logs are normally retained for between 7 and 30 days.
Information connected with suspected fraud, unauthorised access, abuse or a security incident may be retained longer where necessary to investigate and document the incident.
Support correspondence is normally retained for up to three years after the request has been closed, unless a shorter or longer period is necessary because of the nature of the matter or a legal obligation.
Transaction, invoice, payment and accounting records are retained for the statutory periods applicable in Germany.
Depending on the category of document, the applicable period may generally be six, eight or ten years.
Records demonstrating consent, withdrawal, legal notices, account deletion and privacy requests may be retained for the period necessary to demonstrate compliance and defend legal claims.
We implement technical and organisational measures intended to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure and unauthorised access.
These measures include, where appropriate:
Row-Level Security is designed to prevent users from accessing other users' records. It does not exclude limited access by authorised administrators, infrastructure providers or technical personnel where such access is necessary and legally permitted.
No internet-based service can guarantee absolute security.
You should use a strong, unique password and protect access to your email account and device.
Where the GDPR applies, you may have the following rights, subject to the applicable statutory conditions and exceptions.
You may request confirmation as to whether we process your personal data and obtain access to that data and related processing information under Article 15 GDPR.
You may request correction of inaccurate information and completion of incomplete information under Article 16 GDPR.
You may request deletion of your personal data under Article 17 GDPR.
This right may be limited where retention is required by law or necessary for legal claims.
You may request restriction of processing under Article 18 GDPR.
Where processing is based on consent or contract and is carried out by automated means, you may receive the personal data you provided in a structured, commonly used and machine-readable format under Article 20 GDPR.
You may also use the "Export my data" function in the Profile section of the app.
You may object, on grounds relating to your particular situation, to processing based on Article 6(1)(f) GDPR under Article 21 GDPR.
We will stop the relevant processing unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms or the processing is required for legal claims.
Where processing is based on consent, you may withdraw it at any time.
You may withdraw analytics consent through:
On this website: .
In the mobile app: Profile → Data & Privacy → Product analytics
You may withdraw consent for account-based processing of health-related information by:
Withdrawal does not affect the lawfulness of processing carried out before withdrawal.
You have the right to lodge a complaint with a data-protection supervisory authority.
The supervisory authority responsible for our establishment is:
Thüringer Landesbeauftragter für den Datenschutz und die Informationsfreiheit (TLfDI)
Häßlerstraße 8
99096 Erfurt
Germany
You may also contact the supervisory authority in the EU or EEA country of your habitual residence, place of work or place of the alleged infringement.
You can exercise certain rights through the "Export my data" and "Delete account" options in the Profile section of the app.
You may also contact:
We may request information reasonably necessary to verify your identity. If you are already authenticated in your account, we will generally use the existing account authentication rather than requesting an identity document.
We normally respond within one month. Where permitted by law, this period may be extended by up to two further months because of the complexity or number of requests.
You can delete your account through:
Profile → Data & Privacy → Delete account
Public account-deletion page:
https://fuelbit.app/delete-account
Account deletion removes or schedules for deletion:
Deleting the app from your device does not automatically delete your online account.
Information required for tax, legal or security purposes may be retained for the applicable period.
Food photos are analysed through an automated AI system to identify food and estimate nutritional values.
The process generally works as follows:
The estimates may be inaccurate and do not constitute medical, nutritional or dietary advice.
Fuelbit does not use the results to make decisions producing legal effects or similarly significant effects concerning you.
The photo analysis therefore does not constitute solely automated decision-making within the meaning of Article 22(1) GDPR.
Fuelbit may store information on your device where necessary to:
Where storage or access is strictly necessary to provide a function you requested, no separate consent is required under Section 25(2) TDDDG.
Optional analytics or other non-essential device access is used only after consent where required.
Fuelbit may request access to:
Access is used only for the function you select. You can withdraw device permissions through your operating-system settings.
Fuelbit is not directed to children under 16 years of age.
Persons under 16 may not create a Fuelbit account or provide health-related information through the app.
We do not knowingly collect personal data from children under 16.
If we learn that a child under 16 has created an account or provided personal data, we will take reasonable steps to delete the information and close the account.
A parent or guardian who believes that a child has provided personal data may contact us at privacy@fuelbit.app.
Fuelbit is operated by a controller established in Germany. We apply the protections described in this Privacy Policy to users regardless of location, subject to mandatory local law.
Depending on your place of residence, you may have additional rights, including rights to:
You may submit a request without identifying a particular privacy law.
Fuelbit does not:
Third-party processors may collect information only to provide the services described in this Privacy Policy, subject to the applicable contractual arrangements.
Some browsers offer a "Do Not Track" signal. Because there is no universally accepted standard for interpreting all Do Not Track signals, Fuelbit does not currently respond separately to general Do Not Track signals.
This does not change the fact that optional analytics are used only after the applicable consent where required.
If a legally recognised opt-out preference signal applies to Fuelbit in the future, we will process it as required by the relevant law.
We do not sell or rent personal data.
We do not disclose personal data for cross-context behavioural advertising.
We do not use food photos, nutrition data, weight, goals, water logs or fasting information for advertising.
We do not permit our processors to use Fuelbit user data for their own advertising purposes.
We may update this Privacy Policy when:
The current version will be published with a revised "Last updated" date.
If a change materially affects how we process personal data, we will provide an additional notice through the app, website or email where appropriate.
Where a new purpose or processing activity requires consent, we will request consent separately. Continued use of Fuelbit is not treated as consent where applicable law requires a specific affirmative action.
For questions, complaints or privacy requests, contact:
[First and last name — set before publication]
trading as Fuelbit
[Street and house number — set before publication]
[Postcode — set before publication] Weimar
Germany
Email: privacy@fuelbit.app
Please use the subject line "Privacy Request".