LifterFlow Privacy Policy
Effective date: November 9, 2026
1. Who we are and what this policy covers
LifterFlow is software for running powerlifting meets. It is operated by Daniel Kim, an individual based in Honolulu, Hawaii, United States ("LifterFlow", "we", "us").
This policy covers:
- the website at lifterflow.com, including meet pages, online registration, results, scoreboards and displays ("Cloud");
- the LifterFlow desktop app for Mac and Windows ("Local Hub"); and
- the pages that phones, tablets and screens open from a Local Hub over a venue's own network, such as referee and display screens ("LAN pages").
It explains what we collect, why, who we share it with, how long we keep it, and the choices you have. It does not cover sites we link to, such as YouTube or OpenPowerlifting, or what a meet director does with information outside LifterFlow. Using LifterFlow is also governed by our Terms of Service.
2. Two kinds of users
- Meet directors and their staff create accounts, set up meets and run them.
- Lifters usually have no account. They register online for a meet, or a director enters or imports their details.
A meet director decides what to collect about their lifters and how to use it. For lifter information, LifterFlow stores and processes it on the director's behalf. For directors' own account information, LifterFlow decides how it is used. Section 6 explains what this means if you are a lifter.
3. What we collect
From meet directors and staff
- Account details: name, email address and sign-in records, handled by our sign-in provider, Clerk. A Local Hub signed in to Cloud keeps a record of that device's sign-in.
- Meet setup: meet name, dates, venue, divisions, fees, logos, schedules and settings.
- Staff Chat messages sent during a meet.
- Payment account details: if a director accepts online payments, they set up a payment account through Stripe's own forms (business details, bank account, identity checks). Stripe collects these. We keep the account's name and status, not bank or identity documents.
- Problem reports a director chooses to send us from the app.
About lifters
These come from the lifter's own online registration, or from the meet director, who may type them in or import them from a file:
- Identity and contact: full name, birth date, gender, email address, phone number, street address, city, state or province, postal code and country.
- Emergency contact: name and phone number.
- Federation details: membership number, team, drug-tested status and the result of any membership check.
- Competition details: divisions, weight class, bodyweight, lot number, rack heights, attempts, referee decisions, results, placings and records.
- Optional profile: photo, Instagram handle, occupation, quote, personal bests and a walkout song link. The director chooses which of these to ask for.
- Weigh-in confirmations: when a lifter, coach or parent signs at weigh-in, we store the drawn signature, who signed (lifter, coach or parent), the weigh-in official's name, the time, and the weigh-in values they confirmed, such as bodyweight, weight class, openers and rack heights. Confirmations stay private. They are kept, copied and backed up with the rest of the meet.
- Registration extras: answers to the director's own questions, items bought (such as a T-shirt), director notes, and whether the entry is paid.
Card details go directly to Stripe. LifterFlow never sees or stores card numbers.
Collected automatically
- Technical and security logs: IP address, browser and device type, pages requested, time and errors. We use these to keep the service running, stop abuse and fix problems.
- Error and performance reports from the website, the app and LAN pages, such as "this screen took 6 seconds to load in Safari on iOS". These reports are designed to leave out passwords and sign-in tokens.
- Cookies and browser storage, described in section 8.
LifterFlow itself shows no ads and uses no ad tracking or third-party analytics. Embedded YouTube playback is the exception described in section 7.
4. How we use information
- To run meets: registration, check-in, weigh-in, flights, judging, results, scoreboards, displays and printouts.
- To handle registration and payments: confirm entries, apply fees, and pass payments to the director's Stripe account.
- To send email: verification codes, registration confirmations, and messages the director sends to their lifters.
- To check federation memberships when the director asks. For USA Powerlifting meets, we send the lifter's membership number to USA Powerlifting and receive their membership record back.
- To publish results of meets the director makes public (section 5).
- To keep LifterFlow secure: detect and block abuse, investigate problems, and keep a record of administrator actions.
- To support directors and to fix and improve LifterFlow.
- To meet legal obligations.
We do not sell personal information. We do not share it for advertising.
5. What is public
Some meet information is meant for audiences. We call it public information:
- the meet's name, dates, venue and schedule;
- lifters' names, gender, age (worked out from the birth date), state or province, country, team, divisions, weight class, bodyweight, lot and flight;
- attempts, referee decisions, results, placings and records; and
- profile details the meet collects: photo, Instagram handle, quote, occupation and personal bests.
Who can see public information depends on where it is shown:
- On the website: anyone, once the director makes the meet Public. A Private meet's website pages are not shown to the public.
- At the venue: when the director turns on venue network (LAN) access, the desktop app shows public information on screens and live-stream graphics to anyone on that network, with no sign-in, even if the meet is Private on the website. Anything on a venue screen or a live stream can be seen and recorded by the audience.
- Profile photos are stored at web addresses that are very hard to guess. Anyone who has a photo's address can open it, even for a Private meet.
We never put these on public pages: birth date, email address, phone number, street address, city, postal code, emergency contact, membership number, walkout song, weigh-in signatures, registration answers, director notes, purchases or payment details. The walkout song is used only by the meet's Music Player.
Results are shared widely in powerlifting. A director may download a meet's results in OpenPowerlifting's format and send them to OpenPowerlifting, which publishes them permanently. LifterFlow does not send results there on its own. Federations may also publish results and records.
A lifter can ask the meet director, or us, to remove their optional profile details (photo, Instagram handle, quote, occupation and personal bests) from public pages. A Public meet's names and results stay public, because they are the meet's official competition record, as they are for federations and OpenPowerlifting.
6. Meet directors are responsible for their lifters' information
The meet director decides what to collect from lifters, what to show publicly and how long to keep a meet. Directors must have the right to collect and use their lifters' information, and must get any consent the law requires, including a parent's or guardian's consent for any lifter under 18 (section 13). Our Terms of Service set out how we handle lifter information on directors' behalf.
If you are a lifter and want to see, correct or delete your information, ask the meet director first. You can also contact us (section 15), and we will work with the director.
7. Who we share information with
We share information only as this policy describes. These companies handle it for us:
| Company | What it does for LifterFlow | Information it handles |
|---|---|---|
| Clerk | Sign-in and accounts | Directors' names, email addresses and sign-in records |
| Stripe | Registration payments and directors' payment accounts | Payment details, registration amounts, lifter email for receipts, director payment-account details |
| Resend | Sends email | Recipient email addresses and email content |
| Cloudflare | Network delivery, security, desktop app downloads and updates, and storage of photos, logos and backups | All website and download traffic, including IP addresses; stored files and backup copies |
| Our hosting provider | Runs our servers in the United States | All Cloud information |
| USA Powerlifting | Membership checks for USA Powerlifting meets | Membership numbers sent; membership records returned |
| YouTube (Google) | Looks up song titles from walkout song links, and plays music in the Music Player | Song link video IDs; during playback, whatever YouTube's player collects from the playing device |
Embedded YouTube. The Music Player plays songs through YouTube's own player inside LifterFlow. That player is run by Google, not LifterFlow. It loads only on a device where the Music Player is open, normally the computer that plays music at the venue. It can collect information from that device, store cookies or similar data on it, and show ads, under Google's Privacy Policy. Using the Music Player means agreeing to YouTube's Terms of Service.
We also share information:
- with the meet director and the staff they invite, for that director's meets;
- when the law requires it, or to protect people's safety or LifterFlow's rights; and
- if LifterFlow is sold or reorganized, with the new owner, under this policy.
8. Cookies and browser storage
LifterFlow uses only cookies and browser storage it needs to work:
- sign-in cookies that keep directors and staff signed in;
- join cookies that keep a referee or display screen connected to its meet; and
- browser storage that saves a copy of meet data on the device, so pages load fast and keep working through short internet drops.
LifterFlow sets no advertising or tracking cookies. YouTube's player may set its own cookies on a device where the Music Player is open (section 7). Blocking cookies will stop sign-in and referee screens from working.
9. The desktop app keeps data on your computer
The Local Hub app stores its meets in a data folder on the director's computer. Linking a meet to Cloud copies it to our servers. Unlinked meets are not copied there. Running a meet needs no internet: referee, display and other LAN pages get meet data from the Local Hub over the venue's own network.
Some optional features use the internet, even for an unlinked meet:
- looking up a walkout song's title sends its YouTube video ID to YouTube;
- the Music Player loads YouTube's player through our servers, and its music from YouTube; and
- signing in to Cloud and sending a problem report contact our servers.
Live USA Powerlifting membership checks work only for a meet linked to Cloud, and go through our servers. Checking lifters against an uploaded national membership list happens on the computer.
The app checks for updates on its own, when it starts and every hour. Each check asks our download server, downloads.lifterflow.com, for the newest version, and new versions download from there. The check sends no meet data. Like any web request, it shows Cloudflare, which runs that server for us, the computer's IP address. When the app is signed in to Cloud, Cloud also records its app version and update channel with that computer's sign-in, so the director and our administrators can see which version each computer runs.
The app stores its Cloud sign-in in the computer's secure credential store, such as the Mac Keychain. Uninstalling the app keeps the meets folder; the director can delete it to remove them. The director is responsible for securing that computer.
10. How long we keep information
| Information | How long |
|---|---|
| Director accounts | Until the account is deleted |
| Meets, including their lifters | Until the director or we delete the meet; finished meets kept in Cloud Archives stay until deleted |
| Profile photos on Cloud | Until the photo or its meet is deleted, or the meet becomes a Cloud Archive. That starts removal of the file and its cached copies; a copy can stay reachable at its address until cleanup finishes |
| Staff Chat | As the director chooses, per chat room: about the latest 50 messages (older ones are removed in batches once a room passes 60), or until deleted |
| Security records with raw IP addresses | 30 days; a blocked address is kept while the block lasts |
| Web server logs with IP addresses | Usually up to 14 days. The logs are kept in files that rotate as they fill, so on quiet days entries can stay longer |
| Administrator action records | 1 year |
| Website error and performance summaries | Up to 90 days |
| Backups | The four newest backup copies, usually a few days; longer if new backups fail |
| Payment records | Stripe keeps them under its own rules |
Deleting an account removes its sign-in, its Local Hub device sign-ins and its problem reports. An account can be deleted only after:
- each of its meets is handed to another director or deleted;
- no remaining meet still uses that director's Stripe payment account; and
- unfinished registration payments are settled.
Handing a meet to another director does not move the original director's Stripe account to them. Deleted information can remain in backup copies until those copies are replaced.
11. Your choices and rights
You can ask us to:
- see the personal information we hold about you;
- correct it;
- delete it;
- get a copy of it; and
- stop or limit how we use it.
Email [email protected]. We answer within 30 days, or within 10 days for requests from Korea. We may need to confirm your identity first. For a lifter's information, we work with the meet director, who decides about their meet's records.
Some places give extra rights:
- Korea: you may ask to see, correct, delete or suspend processing of your information. Our privacy officer is Daniel Kim, [email protected].
- Europe and the United Kingdom: we rely on performing our agreement with you, our legitimate interest in running and securing LifterFlow, consent for optional profile details, and legal obligations. You may complain to your local data protection authority.
- California: we do not sell or share personal information for advertising.
12. Security
- All website and app traffic to Cloud is encrypted.
- Private meet data and public results live in separate databases. Public pages read only the public one.
- Card details stay with Stripe.
- Administrator access is limited, and every administrator action is recorded.
- The Mac and Windows apps are signed, so those systems can confirm they came from us. On every system, the app checks each update against its published fingerprint before installing it.
No system is perfectly secure. If a breach affects your information, we will tell you as the law requires.
13. Children and young lifters
LifterFlow is not made for children to use on their own, and accounts are for adults only. Meets may include young lifters, for example in youth or sub-junior divisions. A meet director must have a parent's or guardian's consent before entering or collecting information about a lifter under 18. Parents and guardians can ask us to delete a child's information (section 15).
14. Where information is stored
Our servers are in the United States. Our service providers may process information in the United States and other countries. If you are in Korea, Europe or elsewhere, your information is moved to and stored in those countries. Where the law requires safeguards for these transfers, we rely on our providers' data processing terms, including the European Commission's Standard Contractual Clauses.
15. Changes and contact
We will post any change to this policy here with a new effective date. For a significant change, we will also email account holders before it takes effect.
Questions or requests: [email protected]. LifterFlow is based in Honolulu, Hawaii, United States.