App information & data sources
How BURDEN uses food databases and photo analysis. Updated October 14, 2026. This page describes these features; it is not a replacement for our full privacy policy or terms.
Food and barcode data
Food search uses USDA FoodData Central when connected. Its nutrition data is public domain under CC0. Barcode lookups use Open Food Facts, a community database made available under the Open Database License (ODbL), with individual database contents under the Database Contents License. Names, serving sizes, and nutrition may be incomplete, out of date, or entered incorrectly. Check the package label and serving size before saving.
USDA FoodData Central · Open Food Facts · ODbL license · Database Contents License
Search words are sent through BURDEN to the food search provider. For barcode scanning, camera frames are decoded on your device; only the barcode number is sent for lookup. Logging food saves your reviewed nutrition and serving size in your private account so you can find it again. Saved foods can remain after a diary entry is removed; deleting your BURDEN account deletes its saved foods.
AI photo analysis
When you choose AI analysis, BURDEN sends your selected meal image and optional food details to OpenAI through our server. The image is resized and re-encoded on your device first. BURDEN does not retain the photo in your account or database. The analysis request uses store:false; OpenAI may retain abuse-monitoring data for up to 30 days under its applicable data controls. API data is not used to train OpenAI models by default.
Analysis estimates dish names, ingredients, calories, and macros. A photo cannot establish exact portions, hidden ingredients, or allergen safety. Review and adjust the result before adding it. Only the nutrition you confirm is saved to your food log; no photo is attached.
Other services
Cloudflare hosts the fitness app and its database. Brevo delivers account verification and password recovery emails. Nutritionix is an optional prepared integration; it is not a source of results while unconfigured. Your private diary is not published to these food databases.
Subscriptions and payments
Subscriptions use Stripe-hosted checkout and billing management. When you open checkout, BURDEN shares your account name, email, and an internal account reference with Stripe. Card details are collected by Stripe; BURDEN does not store full card numbers. BURDEN stores Stripe customer and subscription identifiers, subscription status, and the paid-access end date to manage your membership.
The listed plans are USD $5.99 per month or USD $61.10 per year, automatically renewing until cancelled. Cancellation of renewal keeps access through the paid period. Payments are final except where applicable law requires otherwise. Premium subscriptions use live Stripe billing; the amount and renewal schedule are shown before payment. Deleting an account cancels its subscriptions and closes pending checkout sessions; payment-provider records may remain for legal and accounting purposes.
Saved foods, device recovery, and support
Favorite foods, saved meals, and progress summaries are private to your account. BURDEN can keep unfinished food forms and workout edits in storage on your current device, keyed to your account, so you can recover interrupted entries. Photo-review recovery saves nutrition and portions, not the photo. Device-only changes require a connection to reach your account; clearing browser or app storage removes those drafts.
Contact BURDEN, based in North Carolina, USA, through Settings → Report a problem in the app. Reports include what you write, your account reference, the selected app area, submission time, status, and replies. The BURDEN account owner can read and reply to reports; friends cannot. Automatic error reports include only an error category, screen, count, time, and internal account reference. Photos, tracking logs, raw error messages, and payment details are not attached automatically. Favorites, saved meals, reports, replies, and account-linked error records are removed from the active database when the account is deleted; recovery backups may retain earlier records.