1. About This Policy
This Policy explains how Trero obtains, uses, stores, and deletes user information. Please review it before using the app.
2. Information Collected
| Category | Main items | Purpose |
|---|---|---|
| Account data | UID, email address, display name, auth provider data, creation timestamp | Sign-in, account management, public profile sync |
| Workout logs | Exercise ID, exercise name, muscle group, date, set number, weight, reps, memo, logged timestamp | History, analytics, goal progress calculation, and CSV export features |
| Body composition data | Weight, body fat %, muscle %, waist, memo, recorded timestamp | Body composition history, charts, derived metrics such as BMI |
| Social data | Public profile, friend requests, accepted relationships, blocks, reports, reactions | Providing friend and reaction features |
| Local settings and on-device data | Unit system, height, goal weight, rest timer sound, completion counts used for in-app prompts, onboarding state, locally saved profile image | Preferences, calculations, and on-device user experience |
| Usage analytics data | Event information such as sign-in type, onboarding completion, workout start/finish, goal creation/update, body-record save, paywall exposure, and share actions, plus usage-state properties such as sign-in state and plan type. | App improvement, usage understanding, and feature-flow evaluation |
| Biometric sign-in credentials | Saved email-login credentials in Keychain | Face ID / Touch ID sign-in |
Collected information is used for account features, history display, analytics features, friend features, usage measurement, and support. Stored data and usage analytics data are handled separately for different purposes.
3. Optional Access
- HealthKit: Used to write weight and body fat percentage when saving, and to manually import the latest values from the body-record screen. Core app functions remain available if permission is not granted.
- Notifications: Used for rest-timer completion, a same-day 20:00 reminder when no workout has been logged, and a weekly summary every Monday at 09:00.
- Camera: Used to scan QR codes for adding friends.
- Face ID / Touch ID: Used for biometric sign-in when saved credentials are available.
4. Third-Party Services
| Service | Provider | Purpose |
|---|---|---|
| Firebase Authentication | Google LLC | Email / Apple authentication |
| Cloud Firestore | Google LLC | Storage of user, workout, body composition, and social data |
| Cloud Functions | Google LLC | Server-side processing for some features |
| Firebase Analytics | Google LLC | Usage measurement, app improvement, and feature-flow evaluation |
| StoreKit / App Store | Apple Inc. | Purchase, restore, and entitlement checks for Trero Pro |
| Apple Health | Apple Inc. | Write on save and manual import for weight and body fat percentage |
5. Storage Locations
- Cloud storage: Account, workout, body composition, and friend-related data are stored on Firebase / Google Cloud.
- Usage analytics: Event information and usage-state properties may be processed on Google infrastructure through Firebase Analytics.
- On-device storage: Settings values, onboarding state, completion counts used for guidance display, profile images, workout caches, and Keychain credentials are stored locally.
- HealthKit-linked data: Read and written within the scope of Apple Health permissions.
6. Data Deletion
You can delete your account from the in-app Settings screen. Email accounts and Apple accounts may require re-authentication before deletion. After account deletion, related cloud-stored data and authentication information are removed in sequence.
7. Children's Privacy
The app is not intended for children under 13, and it is not designed to intentionally collect personal information from children under 13.
8. Contact
Email: freetokyo2020@yahoo.co.jp