BURDEN

Privacy notice

Updated November 17, 2026

This notice covers the BURDEN fitness app, including its iPhone and web versions. BURDEN is intended for people 16 and older.

Operator and contact

Mobilis Media LLC operates BURDEN in North Carolina, United States. Contact support@burden.fit for privacy questions, access/correction requests, account deletion assistance or safety concerns. You can also use Settings → Report a problem and read replies within the app.

Account and security information

We process your name, username, email, chosen account settings, password hash when you use a password, and expiring account sessions. Optional Google sign-in supplies a provider account identifier, verified email and display name. Optional Sign in with Apple supplies an Apple account identifier and verified email, which may be an Apple private relay address; Apple may provide your name on the first authorization. Matching email addresses do not automatically merge accounts.

Apple refresh tokens are encrypted on the server for authorization management and revocation during account deletion. Google access, refresh and identity tokens are not saved. Temporary provider authorization records expire and are removed during later sign-in activity. The iPhone stores its BURDEN session in device-only Keychain storage. BURDEN does not offer a separate authenticator step. Apple and Google manage authentication for their sign-in services. Encrypted authenticator records from the former feature may remain until account deletion or maintenance removes them; they are not used for sign-in. We retain limited hashed network/account throttle identifiers and counters to prevent abuse. New accounts record the affirmed minimum age of 16 and confirmation time, without date of birth. Verified provider identities can be held briefly while the user finishes age confirmation; these pending records expire after five minutes and are removed on later signup or routine health checks.

Tracking and health records

We store the food entries, recipes, portions, calorie/macro targets, workouts, routines, calendar plans, progress records and notes that you choose to save. Optional Apple Health access is read-only for body weight and daily steps. You review the initial Health import before it is uploaded to your account; manual weigh-ins take priority. After Health is connected, automatic step sync updates daily step totals when you open the app. You can turn automatic step sync off in Health connections. Body-weight imports still require your review. You can revoke Health permissions in Apple Health. The app does not request access to your phone contacts, location or advertising identifier.

These records provide your diary, training history, progress summaries and optional personalized nutrition suggestions. Premium weekly recaps privately summarize your completed week, compare logged training over four weeks and use sufficient weigh-ins for a weight trend. Nutrition averages use food days you marked complete and your current targets. Recaps are calculated from your records, not sent to an AI service, and do not automatically change your targets. Nutrition suggestions have a separate eligibility confirmation for adults 18 and older who do not need a medically managed nutrition plan; the app-wide intended minimum age is 16. Suggestions and AI estimates are not medical advice.

Your food diary and body-weight history are private and are not automatically posted to the friend feed. You can separately choose to share a meal or recipe, as described below. Shared workouts can include exercise loads; you can omit session notes and set details. Do not put private information into a post or comment you choose to share.

Friends, comments and safety reports

We store the connections you establish inside BURDEN, friend requests, shared workouts/routines, comments, likes and notification read state. Other users can find you by name or username, including a partial name or username, or by an exact email match. Search results show your name and username, never your email. Only accepted friends can view shared workouts. Blocking removes the connection, hides social activity and prevents contact in either direction; unblocking does not restore a friendship.

Support and safety reports include your account reference, text you submit, relevant screen or content identifier, reason, time, status and replies. Safety reports include a limited snapshot of the visible profile, workout title/note or comment. Private notes, your food diary and body-weight history are not attached. A report about a recipe you chose to share can include its visible ingredients, instructions and nutrition. Authorized BURDEN support can review reports, hide content or restrict social access; moderation actions are recorded. A reported account's deletion removes its identifier but a submitted report snapshot can remain in the reporter's support history.

Shared photos and videos

You can upload one photo or a video up to 60 seconds to a friends-only update or a completed workout. Photos are resized and source location metadata removed. Videos can contain recorded audio and identifying details; review them before sharing. Cloudflare R2 stores photos and previews privately, and Cloudflare Stream processes and delivers videos. Social uploads are not sent to our AI nutrition service. Only accepted friends can access published updates; workout attachments follow the workout’s sharing setting. Authorized safety reviewers can inspect media associated with a report.

Deleting an update, attachment or account removes its app access and queues provider storage for deletion. Failed provider deletions are retried by scheduled cleanup. Unpublished uploads expire from the app after 24 hours and are removed by subsequent cleanup. Previously issued video playback links can remain valid for up to five minutes. Copies made by viewers and provider backups cannot always be recalled.

When you choose to share a meal or recipe, accepted friends receive its ingredients, portions, instructions, nutrition and source link. Personal recipe notes and diary dates are excluded. Direct shares appear in the recipient’s recipe inbox; recipe feed posts can include an optional photo or video under the existing friends-only media rules. Friends can save an independent copy. Removing a friendship, blocking or deleting a feed post prevents further access to the original share; copies already saved by a recipient remain in their account until they delete them.

Optional AI and food-data services

When you choose or take a photo in Photo AI, analysis starts automatically. The app resizes/re-encodes the photo, removes source EXIF metadata and sends the image with your optional food/portion description through BURDEN to OpenAI. BURDEN does not save the image in its application database. We keep temporary account-scoped allowance counters and aggregate AI request/token counts and estimated service costs. Aggregate cost records do not contain photos, recipe text or account identifiers. Only the nutrition entry you review and save becomes part of your food diary. The request does not include your account profile, food history or HealthKit imports. The image and description may contain personal information you choose to include.

Recipe AI import sends the pasted recipe or extracted public recipe content to OpenAI. Saved recipe ingredients, instructions, source link and nutrition remain in your account until deleted. The app asks OpenAI not to store the response as application state. This does not eliminate provider abuse-monitoring retention: OpenAI's default API controls may retain content for up to 30 days, with stated legal and safety exceptions. See OpenAI API data controls.

Food searches and barcodes go through BURDEN's server to Open Food Facts, USDA FoodData Central and, when configured, Nutritionix. These services receive the search terms or product/food identifiers needed to return results, not your BURDEN account profile or complete diary. Public recipe sites receive a server request when you choose to import their URL. Food-search results can be cached on the server by search text without account or device identifiers. Results are reusable for five minutes; cached entries can remain until replaced, the cache is cleared or the server process restarts. External services have their own privacy and retention practices. See the Open Food Facts privacy policy, USDA privacy information and Nutritionix privacy policy. Open Food Facts describes retaining visitor request logs for three years; our requests use BURDEN’s server address, rather than your device’s address. Its policy does not separately specify retention for API search terms.

BURDEN may retain the public product information returned by a barcode lookup in an internal food-quality review queue. That record does not include who scanned it, their diary, logged amount or profile. Custom foods stay private unless you choose “Suggest this food for BURDEN.” Food details you submit are available to the owner for verification and, if approved, to other users in the shared food catalog without your account identity. Pending account-linked suggestions are deleted with your account. Approved generic food records and owner quality-review history may remain independently of your account so other users’ food records remain usable. Contact support@burden.fit about a submitted food.

Premium AI allowances

Premium includes 250 successful meal-photo analyses and 50 successful recipe imports per BURDEN account per calendar month. Allowances reset on the first day of each month at 00:00 UTC, not on your payment anniversary, and unused allowances do not roll over. Photo analysis also has a 20-attempt daily safeguard. Retry-rate and app-wide safety budgets can temporarily limit access before the monthly allowance is exhausted. Failed analyses release their monthly slot; generating a successful estimate or draft uses one even if you choose not to log or save it. Reviewing or editing a result does not use another analysis. Manual food logging and manual recipe creation remain available.

Purchases, emails, notifications and hosting

Cloudflare hosts the API, database, operational monitoring and backups and processes network/request information needed to deliver and protect the service. Brevo receives recipient email addresses and message content for requested verification, recovery and service communications. Apple and Google process their respective sign-in interactions under their own policies.

Apple processes iPhone purchases. BURDEN stores product and transaction references, subscription state, expiry and account-bound entitlement information. Existing web subscriptions use Stripe; Stripe receives account references and checkout details, and BURDEN receives customer/subscription identifiers and status. BURDEN does not receive your full payment card or bank information from Apple or Stripe. Deleting BURDEN does not cancel Apple subscription renewal; cancel it in your Apple subscription settings.

Optional notifications store device/installation identifiers, APNs tokens or browser push endpoints and keys, preferences, time zone, quiet hours and delivery records. Apple or your browser's push service delivers messages. A social notification can show a sender's display name and action; sensitive diary content is not included. On iPhone, BURDEN requests Apple’s notification permission after account setup. When permission is granted, it reconnects notification delivery on app launch or return without resetting your alert categories. Existing users whose iPhone permission is off can receive one dismissible notice linking to device settings. Disable or pause notifications in BURDEN and/or device settings. Already-delivered notifications cannot always be recalled.

Diagnostics and local storage

Account-linked automatic error records contain category, screen, count and time, not raw stack traces, photos, credentials or tracking logs. Separate operational counters contain aggregate categories and minute buckets. Reliability samples contain only operation categories (such as saving or importing), outcome categories, coarse duration bands, platform and counts. They exclude recipe links, searches, food/workout details, photos, credentials, stack traces and account/device identifiers, and are retained for up to seven days. Monitoring uses these records to keep the service working; BURDEN does not use your information for advertising or cross-company tracking.

Hydration drink logs stay on the current device; hydration targets and units are saved with your account. Local device storage holds preferences, drafts, recent account data and changes waiting to sync, plus account-scoped markers for dismissed update notes and notification notices. These markers are not advertising identifiers and ordinary app updates preserve them; deleting app data can remove them. Recent offline caches expire after up to seven days; unsynchronized changes remain until sent or explicitly removed. Offline records are isolated by session but are not encrypted by BURDEN. Protect your device. Successfully signing out clears that session's local caches after pending entries are handled.

Retention, deletion and choices

Account records generally remain until you remove them or delete the account in Settings. Deletion removes associated records from the active app database, clears the current session and revokes a linked Apple authorization. Other devices, already delivered messages, service-provider records and recovery backups may retain earlier copies. Contact support if you need help with access, correction, export or deletion.

Optional streak reminders use your time zone, latest app-open time and logged activity dates to avoid sending reminders after you have been active or after a streak lapses. We retain only the latest app-open timestamp and prune reminder delivery records after eight days. Nutrition coaching uses your completed food logs and weigh-ins; accepted target adjustments are recorded in your account.

Deleted food entries can have a recovery copy for up to ten minutes; cleanup runs on later activity and health checks. Notification jobs are pruned after seven days, food reminder metadata after two days past its due time, aggregate server-failure counters after seven days, and monitoring history/delivered-alert records after 30 days. Cleanup depends on scheduled or subsequent app activity. Routine daily SQL backups expire after 30 days through a storage lifecycle rule and cleanup process; Cloudflare's database recovery retention is separate. Apple, Stripe and other providers may retain records under their own service and legal requirements.

BURDEN is intended for people 16 and older. We do not intend to create accounts for younger children. Contact support if you believe a younger person has provided personal information. New accounts must confirm they are at least 16. This is a self-confirmation and does not independently verify age.

Service providers may process information outside your country. We use HTTPS, access controls, password hashing and protected credential storage; no service can guarantee absolute security. Depending on your location, you may have rights to access, correct, delete or receive a copy of your information, object to or restrict processing, withdraw consent where applicable, or complain to your local privacy authority. Email support@burden.fit to make a request. We may need to verify account ownership before acting; we will explain any limits that apply. Withdrawing optional permissions does not undo processing already completed. We will update the published notice when practices materially change.