STZ Gym is a workout, nutrition and gamified progression app made by STZ LABS. This page explains what data the app uses, why, where it is kept and how you can delete it.
Last updated October 19, 2026
Data that stays on your device
Most of the app works locally. These are kept in the database on your device:
Your body profile: birth date, height, weight, sex (optional) and goal.
Training plan, completed workouts, sets, loads, reps and logged runs.
Nutrition: meal routine, checked meals, water and food preferences.
App preferences: theme, language, reminders and settings.
Data sent to our servers
When you use online features, some data leaves your device:
Account: when you sign in with Google, Firebase Authentication gives us an account identifier, your email and your name. Without signing in, the app creates an anonymous identifier.
Cloud backup (Google Cloud Firestore): when signed in, a copy of your profile (name, weight and height), preferences, current plan, goals, progress (level, XP and streak) and nutrition (profile, routine and daily log), so you can restore it on another device.
Competitive progression (Supabase): completed workouts (exercises, sets and times) are sent so the server, which validates progress, can compute power, rank, league, coins and gems.
Public profile: display name, @username, level, title, rank, avatar border and league position are visible to other users in the league, the friends list and the player card.
Friends: friend requests, friendships and blocks.
Health Connect (runs)
If you allow it, the app reads from Health Connect on Android your running exercise sessions and their data: distance, steps, speed, calories burned, elevation gained and the route. The app only reads; it never writes to Health Connect.
This data is only used to show your runs in the app and to build the share card you choose to create. Each run summary (distance, duration and pace) stays on the device; the route is loaded on demand and kept only in memory, and you can hide the parts near places you mark as sensitive (such as home and work), which also stay on the device. None of it is sent to our servers, used for advertising or shared with third parties. You can revoke access at any time in the Health Connect settings.
Diagnostics and usage statistics
We use Firebase Crashlytics to receive crash reports (technical device and error data) and Google Analytics for Firebase for app usage statistics (events such as a completed workout or an unlocked achievement, with an installation identifier). This data is used to fix bugs and improve the app.
Device permissions
Camera: only to read QR codes from friends and shared workouts. Images are not saved or sent.
Photos: only when you pick an image for the run share card. The image is not sent to our servers.
Notifications: workout, water and meal reminders, scheduled on the device itself.
What we do not do
We do not sell your data.
We do not show ads.
We do not use your workout or health data for advertising.
Who processes the data
Online data is processed by Google (Firebase Authentication, Cloud Firestore, Crashlytics and Analytics) and by Supabase, which host the app infrastructure. They only handle the data to run these services.
Retention and deletion
Server data is kept while your account exists. When you delete your account, we delete the account, the cloud backup and all your progression, league, friends and purchase data. Local data is erased from the device.
Crash reports and usage statistics are not linked to your email and are kept by Google according to Firebase retention.