LiftBlock Privacy Policy

Last updated: 14 June 2026

Who we are

LiftBlock is a strength-training app developed by Adam Zach. This policy explains what information the app collects and how it is used. If you have any questions, contact us at support.liftblock@gmail.com.

Information we collect

Account information: if you choose to create an account, we collect your email address and a password. Signing in is optional — you can use LiftBlock without an account, in which case your data stays only on your device.

Workout data: the programs you create and your progress, including the lift, the one-rep max you enter, completed sets and weeks, and the accessory weights you log.

We do not collect your name, location, contacts, or photos, and we do not use advertising or analytics trackers.

How your information is used

Your information is used only to provide the app's features: generating your training programs, saving your progress, and — if you sign in — backing it up and syncing it across your devices. We never sell your data or share it with third parties for marketing.

Where your data is stored

Your data is stored on your device. If you sign in, it is also stored in our cloud database, provided by our backend hosting provider, Supabase. Data is sent over encrypted connections and protected by access rules so that only your account can read or write your data.

Data retention and deletion

Your data is kept for as long as your account exists. Signing out removes your programs from that device; they remain safely in the cloud and return when you sign back in. To delete your account and all associated cloud data, email us at support.liftblock@gmail.com.

Children

LiftBlock is not directed at children under 13, and we do not knowingly collect personal data from them.

Your rights

Depending on where you live (including under UK and EU GDPR), you may have the right to access, correct, or delete your personal data. To exercise these rights, contact support.liftblock@gmail.com.

Changes to this policy

We may update this policy from time to time. The "last updated" date above reflects the most recent version.