Privacy
Last updated
The short version
Loadcell works offline with no account. Optional sign-in via Apple or Google backs up training. Health data is read and written only with your permission and only for the features you turn on. Progress photos stay on your phone by default; encrypted backup is opt-in, and backed-up photos are deleted with your account. The AI import reader is opt-in and sends the file you choose through our backend to Azure OpenAI in our own Azure subscription. No ads, no tracking, no analytics SDKs and no sale of data.
This policy describes Loadcell, from Varvik Technologies, and the beta invitation website. Features may differ during the beta.
What we collect
Your workouts and history are local-first: you can train and keep records without an account or an internet connection. Data leaves your device for online features you choose, such as account backup or AI import. Health sync shares data with the health platform on your device. Sending us a support email also shares the information you include.
| Category | Purpose and choice |
|---|---|
| Workouts, exercises, programs and personal records | Keep your training history on your device; back it up when you sign in. |
| Bodyweight, body fat and measurements | Track changes you enter or allow a health platform to share. |
| Progress photos | Private on-device progress tracking; separate opt-in for encrypted photo backup. |
| Account identity and device identifier | Name, email address and user ID from optional Apple or Google sign-in; a random per-install device identifier separates backup histories. |
| Import files | Turn history and plans you select into records and programs. AI processing is a separate choice. |
| Beta invitation details | Send confirmation, invitations and beta updates; let you unsubscribe. |
| Support messages | Respond to your question or deletion request. |
There are no ads, tracking or analytics SDKs in Loadcell. We do not sell your personal data. Our hosting and email services necessarily process requests to operate this website and deliver messages.
The beta invitation list
When you join the list, we store your email address, selected platform, app or machine interests, signup source and optional locale and campaign fields. We record signup, confirmation, unsubscribe and invitation timestamps. The list uses double opt-in: follow the email link to confirm your place. You can unsubscribe from an email.
To limit abuse, the service uses a salted hash of your IP address, not a raw IP address in the waitlist record. The hash is deleted after 30 days. Confirmed addresses and platform preferences may be exported privately to send beta invitations for iPhone and Android. The website invitation service runs on our Azure-hosted server, stores the list in SQLite and sends email through the Gmail SMTP relay. This is separate from app account backup.
Infrastructure may process request metadata, including IP addresses, to deliver the website and protect the service. The hashed waitlist field is not a promise that every infrastructure log is anonymous.
Health data
Apple Health (HealthKit) and Android Health Connect are optional. You choose the permissions; Loadcell uses health data only for the training and body-tracking features you enable.
- Read: bodyweight, body fat, supported body measurements and workout heart rate, where the platform supports the type and you grant permission.
- Write: finished workouts and body data you choose to share, where supported and permitted.
- Conflicts: when the same body value changes in both places, the newest value wins.
You can revoke access in your phone’s health permissions at any time. See health permissions help. Revoking a permission stops future access; it does not itself erase records already saved in Loadcell or your health platform.
We do not use HealthKit or Health Connect data for advertising, marketing profiles or sale to data brokers. Loadcell’s use of information received from Health Connect adheres to the Health Connect Permissions policy, including its Limited Use requirements. Health permissions are not required to log workouts manually.
Photos
Progress photos stay on your phone by default. Choosing a photo for progress tracking does not automatically enable cloud photo backup. Encrypted photo backup is a separate opt-in setting. Backed-up photos are deleted with the account.
Keep any originals you want outside Loadcell before deleting app data. Copies you keep in your camera roll or export yourself are outside Loadcell’s account deletion process.
Photo backup uses our Azure storage and requires both sign-in and a separate opt-in. We do not describe this as end-to-end encryption.
Import files and the AI reader
You can import Strong and Hevy exports, a one-row-per-set CSV or Excel file, or a spreadsheet plan. Standard import includes a matching step you confirm for unfamiliar formats.
The AI reader is optional. Only if you choose it, the selected file is sent for one-time processing through Azure OpenAI in our own Azure subscription. The backend passes the selected file to the model service to propose an import; you review every row before saving. This is not automatic background processing of your training history. Check the proposed mapping and imported results before saving, and remove unrelated personal information from files before you upload them.
Account and backup
An account is optional. Sign in with Apple or Google if you want backup and sync across devices. Your sign-in provider processes authentication under its own policy. Signing in enables account-backed training sync; photo backup remains a separate encrypted opt-in.
Our hosted app backend runs on Azure in India. The on-device SQLite database stays the source of truth. Optional account backup stores timestamped snapshots of the full database, together with device, app and schema versions. Up to 30 snapshots are kept per device, with the oldest pruned first. The app can back up on launch when the previous snapshot is more than a day old, or when you choose Back up now. Restoring first saves a local copy of your current data.
Live account sync and timestamped backups serve different purposes: sync keeps signed-in devices current; snapshots provide restore points. Photo backup is a separate opt-in to encrypted Azure storage, not an automatic consequence of adding a photo locally.
Retention and deletion
Local records remain on your device until you remove them or clear the app’s data. Keep a separate copy of anything you need before deleting it. Removing the app is not the same as deleting a signed-in account or its cloud backup.
Use Settings → Account and backup → Delete account to request account deletion, or follow the account deletion instructions to contact us. Account deletion removes the account and its cloud-backed data, including opted-in photo backups. Copies in Apple Health, Health Connect or files you exported are managed separately in those services or storage locations.
We use your beta email to manage invitations and beta updates until you unsubscribe or request removal. Support messages are used to resolve your request. If a legal obligation requires us to retain particular records, we will explain that when responding to a deletion request. The waitlist IP hash has a 30-day retention limit.
Children
Loadcell is a training tool, not a service directed at children. If you believe a child has provided personal information without appropriate authorization, contact us so we can investigate and arrange removal where applicable.
Changes
We update this policy as the app and its data practices change. The date at the top identifies the latest revision. We will provide additional notice or ask for consent where required before making a material change to how your data is used.
Contact
For privacy questions, access requests or deletion help, email support@varviktechnologies.com. Please do not send passwords, health records or progress photos unless they are necessary for your request.