Privacy Policy

1. Information you provide

• Training and preferences. Session dates, completed exercises, daily goals, streaks and streak protection, XP, achievements, challenges, league state, reminder settings, language, theme, and a display name you choose.
• Onboarding answers. The app stores selected answer identifiers for questions about your age range, training experience, goals, and performance-related concerns in local preferences. These answers may reveal sensitive health or sexual-wellness information. The current answer-storage workflow does not send the answer set to our support backend or upload it to Supabase. Analytics can record that an onboarding screen was viewed; this is separate from storing your selected answers.
• Support messages. Feedback text, timestamps, sender and recipient identifiers, and information you voluntarily include are sent to our support backend. An email address you provide in the app or use to contact us is processed with your correspondence to respond. Avoid including unnecessary medical or intimate details.
• Purchases. Google Play handles payment. The app and RevenueCat process product identifiers, purchase and subscription records, and premium entitlements. We do not receive your full payment-card number.

2. Identifiers and technical information

Our backend creates a pseudonymous numeric app-user identifier; a conventional username-and-password account is not required. Requests can contain the app identifier and version, operating-system and platform information, and premium status. Configured analytics and diagnostic providers can process installation identifiers, usage events, device information, error details, and connection information such as an IP address. A country or region may be obtained from device settings or approximate IP-based location. The current app does not request precise location, camera, or microphone access, or connect to Apple Health or Health Connect.

3. Local storage and widgets

Training history, goals, streaks, XP, achievements, challenges, onboarding answer identifiers, league state, and preferences are stored using Room and local preferences, with selected training information used by Home Screen widgets. Local training and onboarding data are not a medical record and are not automatically uploaded as a complete database by the current app workflow.

The current Android manifest disables automatic app backup. Local information can still be affected by device changes or manual data handling.

Deleting the app or clearing its local data can remove local records. This does not automatically remove support, purchase, analytics, or diagnostic records already held by providers, and it does not cancel a subscription.

4. Backend, support, and leagues

Our backend supplies app configuration, creates an app-user identifier, and handles support messages and optional email updates. Account and support request bodies use the encrypted-request workflow implemented in the app. When configured, the league feature reads league definitions, reference profiles, and leaderboard slots from Supabase. Country-based requests may include a region code from device settings. Your selected display name and league state are stored locally in the current implementation; these reads do not upload your local training history or onboarding answer set.

Connections disclose network information, including an IP address, to the receiving service.

5. Analytics, diagnostics, and remote configuration

• Firebase Analytics. Processes automatic and app-defined usage events.
• Firebase Remote Config. Provides app configuration and paywall or server-routing settings.
• Mixpanel. Processes usage events and supplied properties, including environment and premium status.
• Firebase Crashlytics. Processes crash and error information when the service is configured.

Collection depends on the app version, build, and service configuration. The Android source only initializes these SDKs when their required keys or configuration files are present; an integrated SDK is not necessarily active in a particular build. These providers may receive app and device identifiers, usage events, diagnostic details, and network information. Their practices are described by Firebase, Mixpanel.

6. Reminders and notifications

Local training reminders use your chosen times and notification settings. OneSignal, when configured, provides remote push delivery and may process push tokens, subscription or installation identifiers, permission status, device information, and notification interactions. Local reminders and push delivery are separate. Change reminder settings in the app or notification permissions in device settings. Android exact-alarm access can be used for scheduled reminders; you can manage it in system settings. See OneSignal's privacy policy.

7. Purchases and RevenueCat

RevenueCat manages offerings, purchase verification, restore operations, and premium entitlements with Google Play when configured. It may process a pseudonymous app-user identifier, product and transaction details, subscription and entitlement status, locale, and app or device metadata. Billing is handled separately by the store. See RevenueCat's privacy policy.

8. Tutorials, websites, and external links

The current pelvic-floor tutorial video is bundled with the app and plays locally; it is not an embedded YouTube player. Our websites can process normal web-request information, such as IP address, browser information, and requested pages, through their hosting provider. Google Fonts requests can disclose connection information to Google under Google's privacy policy. The existing web quiz uses browser screen state for selections; the reviewed quiz code does not submit the selected answers to a server. App stores, email services, and destinations you open or choose for sharing have their own privacy practices.

9. Purposes and disclosures

Information is used to provide training and progress features, personalize the local onboarding experience, deliver reminders, verify premium access, answer support requests, configure and improve the app, diagnose failures, and maintain security. Relevant information is processed by the providers described above for these functions. It may also be disclosed where required by law, to protect rights or safety, or during a business transfer subject to applicable protections. The reviewed app contains no advertising integration that sells your onboarding answers.

10. Retention, deletion, and your choices

Local records remain until removed using available app or device controls. Server-held support records, purchase records, analytics, and diagnostics have separate retention arrangements; we do not promise a single retention period for all categories. Uninstalling does not delete every server-held record or cancel subscriptions.

For requests about access, correction, or deletion, contact support with enough information to locate your correspondence or app-user identifier. We may need to verify a request and retain records where required by law. Depending on your location, rights may include restriction, objection, portability, or a complaint to a data-protection authority. Device permissions and store account controls provide additional choices.

11. Security and international processing

We use technical safeguards for app and service information, but no storage or transmission method is completely secure. Hosting and service providers may process data outside your country. Applicable protections and provider arrangements govern that processing.

12. Children

Kegel Go is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided information, contact support so we can investigate and address it. Higher local age requirements may apply.

13. Changes and contact

This policy may change when the app, services, or information practices change. The date above identifies this version. For questions or requests, contact Betterbase Studio, LLC at hello@kegelpt.com.