SWOLEMATE / Updated 17 November 2026
Your training. Your data.
This notice covers the SwoleMate website, app and optional account/access service. PRO sales remain closed until payment approval and activation testing are complete.
Who is responsible?
SwoleMate is developed by Andrii Trokoz, an independent developer in Ukraine. Contact: andrewtrokoz.me@gmail.com.
This website
There are no advertising pixels or advertising analytics on this site. Netlify hosts the website and account API, processing connection information such as IP address and technical logs for delivery, security and rate limiting. External links have their own policies.
Training data
The app processes plans, exercise names and notes, sets, reps, load, session times, history, companion selection, XP, language and settings. These are stored locally on your watch and in SwoleMate’s Zepp Settings storage on your phone, and synchronised through the Zepp/ZML bridge.
Sensors and the watchface
When available and permitted, the watch app can sample heart rate during workouts. The optional, user-started diagnostic logger can record acceleration, angular velocity, heart rate, timestamps, markers and device status. Respiratory rate is not collected. A limited companion/XP/progress/settings snapshot is shared with the separate watchface; the full workout journal and raw sensor log are not shared through that snapshot.
Sharing and exports
The account service does not receive workout journals, heart-rate traces or diagnostic recordings. Copying/exporting data or sending support logs is your choice. Zepp platform services are covered by their own policies.
Optional account and PRO
Signing in sends your email to our Netlify service and a code through Resend. The server stores sign-in challenges, hashed session credentials, account identifiers and access/payment status. It uses a keyed email identifier for entitlement records. If sales open, Creem processes checkout and sends signed purchase/refund notifications; payment-card details are not sent to the app.
Retention and your choices
Local workouts remain until you edit, remove or clear them; keep backups before uninstalling. Sign-in codes are valid for 10 minutes, sessions for 180 days and offline access for up to 30 days between checks. Expiry prevents use but is not automatic deletion of every server record. Account and payment records are kept to restore access and handle support/refunds. Contact support to request access or deletion; payment providers may retain their own required records.
Changes
We will update this notice before adding payments, a licence server or new data uses. The date at the top identifies this version.