Effective 13 September 2026
Built Log is a workout tracker built by Evan Thomas. The short version: your training data lives on your phone. It leaves the phone only when you turn on cloud sync, use AI conversion, or buy a subscription, and each of those is something you choose. We show no ads, we sell no data, and we run no behavioural tracking or product analytics.
| Data | Collected | Leaves your phone | Who receives it | Tied to your account | Why |
|---|---|---|---|---|---|
| Email address | Only if you sign in | Yes, at sign-in | Us, through Supabase. Apple or Google if you use their sign-in | Yes | Running your account |
| Account identifiers: your Built Log user id, and the identifier your sign-in provider gives us | Only if you sign in | Yes, at sign-in | Us, through Supabase; your sign-in provider | Yes | Running your account |
| Name and profile photo from a sign-in provider | Only if you sign in with Google | Only if the provider sends it | Us, through Supabase | Yes | Nothing. We do not use it |
| Strength training: workouts, exercises, sessions, sets, reps, load, personal records | Only if you turn on sync | Only with sync | Us, through Supabase | Yes | Backing up and syncing your data |
| Cardio: runs, distance, duration, run kind, surface, perceived effort, races, goals, training availability | Only if you turn on sync | Only with sync | Us, through Supabase | Yes | Backing up and syncing your data |
| Health entries you type: nutrition and macros, bodyweight, sleep, daily targets, and the prior-injury flag on a running goal | Only if you turn on sync | Only with sync | Us, through Supabase | Yes | Backing up and syncing your data |
| Your own words: workout, exercise, category and location names, equipment, custom macro labels, and any notes you write | Only if you turn on sync | Only with sync | Us, through Supabase | Yes | Backing up and syncing your data |
| Text you paste into AI conversion | Only when you use that feature and agree to it | Yes, when you convert | Us, through Supabase, then Anthropic | See the AI section | Turning your text into a workout |
| Coach report excerpt | Only when you preview it and press Send | Yes, on Send | Us, through Supabase, then Anthropic | Yes or linkable | Explaining an existing finding or recap |
| Preferences and weekly schedule | Only if you turn on sync | Only with sync | Us, through Supabase | Yes | Backing up and syncing your data |
| Purchase and subscription state | Only if you buy or restore something | Yes | Apple or Google, RevenueCat, and us | Yes once you sign in | Unlocking what you paid for |
| Feature counters: AI requests used today, subscription checks | Only when you use those features | Yes | Us, through Supabase | Yes | Enforcing the daily AI limit and keeping Pro accurate |
| Server error records | When a server request fails | Yes | Us, through Supabase | Yes or linkable | Diagnosing failures |
| Sync diagnostics on your phone | Always, locally | Only if you export and share them | Whoever you send the file to | Yes, the file names your email | Helping you or us debug sync |
| Backup files you export | Only when you export one | Only where you send it | Whoever you send it to | Depends on where you send it | Your own backup |
| Rest and personal-record notifications | Always, locally | No | Nobody | Device only | Timing your rest and flagging records |
| Everything else you record | Always, on the device | No | Nobody | Device only | Running the app |
The sections below explain each row.
Everything you record in Built Log is stored on your device: workouts, exercises, logged sets, personal records, runs, races and running goals, nutrition entries, bodyweight, sleep hours, targets, schedules, preferences, equipment, workout locations, and coach reports. If you never sign in and never use optional AI requests, this data never leaves your phone and we have no copy of it.
One thing can still happen before you sign in. If the app was built with purchases enabled, the purchase service creates an anonymous customer record for the installation when the app first runs, before you buy anything and before we know who you are. That is described below.
Coach reports deserve a specific mention because they touch health-adjacent data. They are computed entirely on your phone by a deterministic engine reading your own logs. Generating a report makes no network request. You can separately choose to send a previewed excerpt for an AI explanation, as described below.
"Workout locations" are names you type, like "home garage" or "the gym on 4th". Built Log has no access to your GPS or any location service, and no location permission. A location in Built Log is a label, not a place on a map.
If you subscribe to Pro and sign in, Built Log syncs your training data so you can back it up and use it across devices. Sync covers your exercises, workouts, sessions, categories, runs, races and running goals, workout locations, nutrition days, bodyweight entries, sleep entries, daily targets, custom macros, preferences, and weekly schedule, along with everything inside them: sets, reps, loads, distances, durations, perceived effort, the prior-injury flag on a running goal, and any notes and names you wrote. All of it is tied to your account.
We use Supabase to store this data and to run sign-in. Data travels between your phone and Supabase over encrypted connections. Supabase hosts the data on our behalf and does not use it for its own purposes.
Synced data is used for one thing: making sync work. We do not use it for advertising, profiling, or marketing, and we do not sell it. It is handled by the companies listed under "Companies that handle your data", each doing a specific job for us. Nobody else receives it.
Built Log offers two optional AI features through Anthropic. Both require a signed-in Pro account and share a limit of 20 requests per rolling 24 hours.
Workout conversion: paste text, choose Convert with AI and agree to the conversion disclosure. Built Log sends the pasted text through its Supabase server function to Anthropic. You review the returned workout before importing it. Built Log does not attach your account, email or saved records to the provider request. Names or health details you paste are sent as part of the text.
Coach explanations: open Explain or the quick recap on an existing report. The app previews the selected finding, or the summary and up to three findings. Nothing is sent until you press Send. That excerpt goes through Supabase to Anthropic and may include training or health details and custom names. The reply explains the report; it does not change your plan, targets or logs.
Supabase authenticates both requests and checks Pro access. Our application code stores a shared request counter linked to your account, not the text you send or the response. Coach replies stay in app memory until you clear them, change accounts, turn AI requests off or close the app. Workouts you choose to import become ordinary saved workout data.
What Anthropic does with it. Anthropic handles the text under its commercial terms, which state that Anthropic may not train models on the inputs and outputs sent through the service. Under the data-retention setting on our Anthropic account, the text and the response are retained by Anthropic for 30 days, and may be accessed by Anthropic during that period for safety and security purposes. After that period they are not retained.
Turn AI requests off in Settings to hide its buttons and prompts and stop new AI requests. Local Coach reports, session tips and ordinary workout logging still work. The setting stays off after restarting the app. You can re-enable it in Settings; explicit conversion consent and Coach Send still apply. Turning it off or withdrawing conversion consent does not recall text already sent or delete workouts you already imported.
You can create an account with an email address and password, with Sign in with Apple, or with Google. We receive your email address (or Apple's private relay address if you choose to hide yours) and an account identifier from the provider you pick.
If you sign in with Google, Google also passes along your display name and a link to your profile photo, which are stored with your account record. We do not use them anywhere in the app.
Sign in with Apple asks for your name and email at the prompt. Built Log does not read or store the name Apple returns; only the identity token reaches our server.
Your sign-in session is stored on your phone in the operating system's secure storage, not in ordinary app files.
Pro subscriptions and tips are processed by Apple's App Store or Google Play. Your payment details go to Apple or Google, never to us and never to RevenueCat.
We use RevenueCat to track which subscription an installation holds. Before you sign in, RevenueCat identifies your installation by an anonymous id it generates itself. When you sign in, we tell RevenueCat your Built Log account id so your purchase follows your account, and the earlier anonymous id stays attached to the same customer record. RevenueCat therefore holds your purchase and subscription history, those identifiers, and service details such as platform and when it last saw you. RevenueCat also runs its own subscription analytics on that data as part of the service it provides us.
Our server keeps a record of your entitlement: whether Pro is active, when that was last confirmed, and why it changed, for example a renewal, a cancellation, or a refund. That record is tied to your account and exists so the app can trust what you are entitled to without asking the store every time.
Built Log does not send crash reports. No crash-reporting service is enabled in the app.
When a request to our server fails, our server records what happened: a status code, a size, a request id, and your account id on some paths. These records exist to diagnose failures. We do not put the contents of your workouts, your pasted text, or the AI's response into them.
Built Log also keeps a sync diagnostic log on your phone. It records what synced, whether it worked, and any error, identified by record id rather than content. It stays on the device and uploads nowhere. If you export it to send us for support, the exported file includes your email address and an installation identifier that Built Log generates for itself, and you choose where the file goes.
You can export a backup file at any time and send it wherever you like. The backup covers your saved data: exercises, workouts, sessions, categories, nutrition, bodyweight, sleep, targets, custom macros, preferences, schedule, scheduled sessions, runs, races and running goals, training plans, and workout locations. It does not cover a session you are part-way through, your coach reports and coach settings, sync diagnostics, or your sign-in and subscription state. When you import a file, Built Log reads only the file you picked.
You can also export your schedule or a run plan as a calendar file, which carries the dates and names of the sessions in it.
Exported and imported files are written to the app's temporary storage while your phone hands them around. They are not uploaded anywhere by us.
Rest-timer and personal-record notifications are scheduled locally on your phone. Built Log does not use push notifications and never registers your device with a notification server. Personal-record notifications name the exercise and the weight, so if your phone shows notification content on the lock screen, that text can be visible without unlocking. Your phone's notification settings control that.
Each of these does one job for us and is not permitted to use your data for its own purposes.
| Company | What it does | What it receives |
|---|---|---|
| Supabase | Hosts our database, sign-in, and server functions | Your account, everything you sync, entitlement and counter records, server logs |
| Anthropic | Converts pasted workouts and explains selected Coach text | Pasted text after conversion consent, or a previewed Coach excerpt after Send |
| RevenueCat | Manages subscriptions and entitlements | Purchase and subscription history, your account id and its anonymous id, service details |
| Apple, Google | Sell the subscription and process payment; provide sign-in if you choose it | Payment details, purchase records, and the sign-in details described above |
You can delete your account from inside the app: Settings, then Cloud Sync, then Delete account. Built Log asks whether to delete the cloud account only, keeping your workouts on this phone, or to delete the account and erase this phone's data too. Both paths confirm twice before anything happens.
Deleting the account removes your synced records and your account identity from our servers, along with the entitlement and AI-counter records attached to it.
If you cannot use the in-app path, or you no longer have the app installed, write to support@builtlog.app and we will delete the account for you. The full procedure, including what survives deletion and for how long, is at https://builtlog.app/delete-account.
Three things do not disappear when you delete your account, and it is better to say so:
Data we hold in our own database is kept only while your account exists.
Built Log is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe a child has created an account, contact us and we will delete it.
If the app starts handling data differently, this policy changes with it and the effective date above moves. Meaningful changes will be called out in the app's release notes. If a change affects AI conversion, Built Log asks for your agreement again the next time you use it.