Loadsmith

Privacy policy

Effective 14 October 2026 · applies to the Loadsmith test version

Loadsmith is a lifting log for iPhone and Android, made by Ido Albeck in Israel. This page says what the app stores, where, who else sees it, and how you delete it. It is written to be read, not skimmed, and it describes what the app actually does today. When the app changes, this page changes with it, and the date above moves.

The short version. Your training log is yours. It is backed up to your account so it survives a lost phone. No advertising, no analytics, no selling or renting of data, ever. The only company that sees what you write is the one that has to in order to do the job you asked for: the database that stores the backup, the AI model when you ask it to write a program, the crash reporter if you leave it on, and the email service that sends your sign-in code.

Who is responsible

Ido Albeck, Israel, is the controller of this data. Write to support@loadsmith.app for anything on this page.

What the app stores

Your account

Your email address, which is how you sign in and how a sign-in code or password reset reaches you. If you sign in with Apple or Google, they also pass along the name on that account; the app does not show or use it, and it sits only in the sign-in record. Passwords are stored hashed by the authentication service, never readable.

About you

Whatever you give the app so it can plan sensibly: your date of birth or age, sex, height, bodyweight entries, and which units and effort scale you prefer. All of it is optional, and the app works without it.

Your training

Programs, training days, planned and logged sets: exercise, weight, reps, effort, rest, and any notes you type on a set, exercise or workout. Also what the app suggested mid-workout and whether you took it.

What you tell the program builder

When you talk to the AI program builder it remembers facts you tell it (“left shoulder clicks on overhead work”, “train four days a week”) so you do not have to repeat them. These facts can include injuries and other health information; the app treats them as sensitive data. You can read and delete each one under Settings → What the coach remembers. The conversation itself is kept only on your phone.

Bug reports

What you write, the screenshot you choose to attach (never one taken for you), the app version, the platform and the screen you were on. The screenshot is stored with the report, so attach one only if you are happy for the developer to see what is on it.

Crash reports (optional)

If Send crash reports is on in Settings, a crash sends the error, the screen it happened on, the app version and your account id. Never your workouts, your notes, or what you typed. The switch is honoured immediately.

Records the app keeps about itself

Which version of the in-app notice you agreed to and when; and for each AI request, the model used and the number of tokens it consumed, so the cost can be tracked. Not the content of the request.

What the app does not collect

No advertising identifier, no analytics or tracking SDK, no location, no contacts, no photos beyond the one you attach to a report, no microphone, no camera. The only device information recorded is the platform and OS version alongside a bug report or consent record.

Apple Health and Health Connect

Only if you connect it, and each part has its own switch in Settings:

A weight read from Apple Health or Health Connect goes into your training log like any other weight, is backed up to your account with the rest of your log, and is shown only to you. It is never used for advertising, never sold, never used to build a profile of you, and never passed to the AI program builder: only a weight you typed yourself can be. It is stored by the database provider below as part of your backup and goes nowhere else. Turn a switch off and nothing more is read or written; what was already written stays in the health app until you delete it there, and what was read stays in your log until you delete it here. You can also revoke the app's access from inside Apple Health or Health Connect.

Who else sees it, and why

Each of these companies processes data on the developer's instructions, for one job, and is bound by its own agreement not to use it for anything else.

CompanyJobWhat reaches it
Supabase (database hosted on AWS, Singapore)Stores your account and the backup of your log; runs the sign-in and the server functionsEverything listed above except crash reports and the AI conversation
Anthropic (United States)Runs the Claude model behind the program builder, only when you use itYour messages in that conversation, the facts it has remembered, your age, sex, height and typed bodyweight, your goals, your best recent sets per exercise, and how often you have trained lately. Not your email, not your account id, not health-app data. Anthropic keeps API inputs and outputs for up to 30 days to monitor abuse and does not use them to train its models.
Sentry (European Union)Crash reports, if the switch is onThe error, the screen, the app version, your account id. Kept 90 days.
Resend (United States)Sends emailSign-in and password-reset codes to your address. When you send a bug report, the report, your email address and the screenshot are emailed to the developer through Resend.
Apple, GoogleSign in with Apple / Google, if you choose itHandled by them under their own policies; the app receives your email and name.
Expo (United States)Delivers app updatesWhen the app checks for an update it sends the platform and the app's runtime version. No account data.
jsDelivrServes the exercise illustrationsYour IP address, as with any image on the internet. Nothing about you or your training.

Tapping “watch” on an exercise opens a YouTube search in your browser; from that point you are on YouTube under Google's policy.

Nothing is sold, rented, or shared with advertisers or data brokers. Nothing is shared for anyone else's marketing. Data would be disclosed to an authority only where the law requires it.

Where it is stored and how it moves

The backup lives in Singapore (Supabase on AWS). The AI model and the email service are in the United States, the crash reporter in the European Union. If you are in the EU or UK, that means your data leaves your region; each of these providers offers standard contractual clauses or an equivalent for the transfer. Everything travels encrypted in transit, and the sign-in session on your phone is kept in the device's secure store.

How long it is kept

Deleting and taking your data with you

In the app you can delete any workout, set, note, bodyweight or remembered fact, and sign out at any time. To remove the account and everything in it, follow Delete your account: during testing this is a request by email, completed within 30 days, and it will become a button in Settings. To receive a copy of your data, email support@loadsmith.app from the address you signed in with; an in-app export is planned.

Your rights

Under Israel's Privacy Protection Law, 5741-1981, you may inspect the information held about you and ask for it to be corrected or deleted. If you are in the European Union or United Kingdom, the GDPR additionally gives you the rights of access, rectification, erasure, restriction, portability and objection, the right to withdraw consent at any time without affecting what was done before, and the right to complain to your supervisory authority. For all of these, write to support@loadsmith.app; requests are answered within 30 days.

For EU and UK readers, the legal bases are: performance of the contract with you (your account and backup), your consent (the AI program builder, Apple Health / Health Connect, crash reports, each of which you switch on yourself and can switch off), and the developer's legitimate interest in keeping the app working (bug reports you send, the cost record of AI requests).

Age

Loadsmith is for people aged 16 and over. It does not knowingly keep an account for anyone younger; if you believe one exists, write in and it will be deleted.

Changes

This page is the current version; earlier versions are in the public history of its repository. A change that matters to you – a new recipient of your data, a new kind of data – is shown in the app before it takes effect, and you are asked to agree again.