Privacy Policy
Last Updated: March 2025
NeonPose (the "App") is committed to protecting user privacy. This Privacy Policy explains what information the App collects, its purposes, third-party disclosures, and your rights.
1. Administrator & Contact
The operator and data controller for this App is JUSTWIT WORKS (the developer).
For privacy inquiries, please contact us via the contact form (JUSTWIT WORKS website) or the developer contact in the app store.
2. Data We Collect
The App may collect and use the following data.
This App does not access device health data stores such as Apple Health (HealthKit) or Google Health Connect. We do not read or write any OS-managed health data (e.g. steps, heart rate, sleep, workouts from other apps). Health-related data is limited to the workout records and camera-based pose/form data described in the table below (each input or recorded in the App or processed on-device).
| Data Type | When Collected | Purpose |
|---|---|---|
| Auth Data (email, password, Google account info) | On login | Account creation, authentication, identity verification |
| Workout Records (exercise type, score, date/time, advice) | When logged in and performing workouts | History display, graphs, analysis |
| Camera | When using pose scoring | Pose detection (on-device processing) |
| Photo Library | When saving or sharing score cards | Image saving and sharing |
| Advertising Data (see "About Ads" below) | When ads are displayed | Ad delivery, analysis, fraud prevention |
- Pose analysis is performed on your device (Google ML Kit). Video and skeleton data are never sent to our servers. We do not store them.
- Workout records are stored in Firebase (Cloud Firestore) only when logged in. When not logged in, data is stored only on your device.
3. Purpose of Use
Collected data is used for the following purposes.
- Providing, maintaining, and improving the App (authentication, history sync, pose scoring, sharing)
- Customer support and responding to inquiries
- Preventing violations of the Terms of Service and unauthorized use
- Compliance with applicable laws
- Ad delivery, personalization, analysis, and fraud prevention (see "About Ads" below)
4. Third-Party Disclosure
The App uses the following third-party services. Data is handled according to each service's privacy policy.
- Google Firebase
Used for authentication (Firebase Authentication) and workout record storage (Cloud Firestore).
Firebase Privacy and Security - Google AdMob (Advertising)
Used for ad delivery. Data collected and purposes are described in "About Ads" below.
5. About Ads (Google AdMob)
The App uses Google AdMob (banner and interstitial ads) for ad revenue.
Services Used
- Google AdMob (delivered via Google Mobile Ads SDK)
Data Collected & Shared for Ads
The Google Mobile Ads SDK may automatically collect and share the following data.
- IP address
- Device identifiers and advertising ID
- User-ad interactions (impressions, clicks, etc.)
- Diagnostic data (crash logs, performance data, etc.)
Purpose
- Ad delivery
- Ad personalization
- Ad measurement and analysis
- Ad fraud prevention
Third Party
The above data is handled by Google LLC.
For details, see Google's advertising policy.
6. Retention Period & Deletion
- Auth Data
Retained until account deletion. Upon deletion, authentication data managed by us will be deleted (Firebase retention follows Firebase's policy). - Workout Records
Deleted upon account deletion or upon your request.
Records stored only locally will be lost when the app is deleted or data is cleared. - Advertising Data
Retention follows Google's policy.
7. Your Rights
You may have the right to request access, correction, deletion, or restriction of your personal data (depending on applicable laws). Please contact us via the contact information above. You may also request deletion of your workout records by deleting your account.
8. Policy Updates
This Privacy Policy may be revised as necessary. For significant changes, we will notify you through in-app notifications, store description updates, or by updating the "Last Updated" date on this page. Continued use after revisions constitutes agreement to the changes.
End of Privacy Policy