1. Scope and operator
This Privacy Policy applies to the Tongue Smash mobile application, this website, and related support. Tongue Smash is operated by Muhammad Affan Naveed, an individual developer. It is a speaking-practice game, not a medical, diagnostic, or treatment service.
2. Account and profile information
The current sign-in experience supports Sign in with Apple and Google sign-in through Firebase Authentication. Depending on the provider and your settings, we may receive a provider identifier, email address, display name, and profile image URL. We do not receive your Apple or Google password.
You can use available features without signing in. Guest progress, settings, and history are stored on the device. If you later sign in, eligible app data may be associated with your Firebase user ID and synchronized to the service.
3. Practice, gameplay, and content data
Depending on the features you use, Tongue Smash may process:
- onboarding answers, goals, preferences, and reminder settings;
- words, prompts, custom content, transcripts, and tongue-twister attempts;
- scores, speech and pace metrics, duration, progress, XP, levels, streaks, achievements, saved items, and session history; and
- support messages and any information you include in them.
For signed-in users, account and gameplay records are stored in Firebase/Firestore. Leaderboard features may use a separate display profile containing a user ID, display name or initials, XP, and level.
4. Microphone, recordings, and speech recognition
Tongue Smash asks for microphone and speech-recognition permission when a voice feature needs it. Speech may be processed by Apple or Android system speech recognition, including Google's speech service when available, or by downloaded Whisper or Vosk models that run on the device. System speech services may process audio on the device or transmit it to their service depending on the device, operating system, language, settings, and service availability.
Completed drill recordings can be copied into the app's private local storage for history playback. The app does not upload those raw history recordings to Firebase Storage. The app keeps up to 30 history entries for each local user and removes app-managed audio when an entry falls outside that limit or history is cleared. It also removes unreferenced files from the dedicated history-audio folder.
Temporary app-cache recordings that survive a failed, canceled, or interrupted session are registered for cleanup. A stopped recording is eligible for deletion after a 24-hour recovery grace period when the app next becomes active; active recordings are protected. This grace period allows crash recovery and result playback and is not a promise that the file will remain available for 24 hours. Account or guest-data deletion removes abandoned temporary recordings without waiting for the grace period.
5. Transcripts and artificial-intelligence features
Transcripts and result snapshots may be stored locally for history and feedback and, for signed-in users, in Firebase-backed records. When you use optional coaching, analysis, feedback, or generation features, the app can send transcripts, prompts, onboarding context, and relevant scores or metrics through a server-side AI service. The app does not send the associated raw recording with those requests.
Voice responses may also be sent to a configured text-to-speech service and cached temporarily on the device when that feature is enabled.
6. Analytics, security, and technical information
PostHog analytics runs only when both an explicit enable flag and an API key are configured. If enabled, events can describe onboarding and feature use, sign-in outcomes, paywall and purchase interactions, durations, failure reasons, product identifiers, and gameplay metrics. After sign-in, the Firebase user ID may identify those events. The current event calls do not intentionally attach raw audio or transcript text.
PostHog is disabled in the current production configuration. Automatic PostHog screen capture and session replay are disabled. Superwall event collection is set to none, and its advertising-data and personalized-advertising consent values are denied. Tongue Smash does not include an advertising-network SDK or cross-app tracking integration.
Firebase App Check processes app and device attestation information to help reject unauthorized clients. Firebase, cloud infrastructure, the operating system, and other service providers may also process IP address, device, request, and diagnostic information needed to deliver and protect their services. No advertising-network SDK or data-sale workflow is used by Tongue Smash.
7. Subscriptions and payments
Tongue Smash uses RevenueCat for purchases and Premium entitlement checks and Superwall to present Premium upgrade screens.
Apple processes App Store purchases and payment details. RevenueCat can receive a Firebase user ID, App Store transaction and product information, entitlement status, and technical data needed to manage Premium access. Superwall can receive an app user identifier and paywall, interaction, and purchase-status information. Tongue Smash does not receive your complete payment-card details.
Purchases and subscriptions are also subject to Apple's purchase authorization requirements and any Ask to Buy, Family Sharing, parental, or device controls that apply to the Apple Account.
Apple, RevenueCat, and Superwall may retain transaction, entitlement, or operational records under applicable agreements, documented retention criteria, and legal obligations after a Tongue Smash account is deleted. No unverified fixed provider retention period is promised here.
8. How information is used
Information is used to:
- authenticate users and synchronize eligible account data;
- provide gameplay, speech recognition, history, and feedback;
- generate requested coaching, analysis, or voice responses;
- operate subscriptions, restores, and Premium access;
- secure, troubleshoot, maintain, and improve the service;
- understand product use when analytics is enabled;
- respond to support requests; and
- comply with law and protect users, the service, and others.
9. Service providers and disclosure
Relevant providers can include Apple; Google and Firebase/Google Cloud; operating-system speech services; configured AI and text-to-speech providers; RevenueCat; Superwall; and PostHog when the related feature is enabled. These providers process information under their own terms and privacy notices. If email-code sign-in is enabled in a later release, the email-delivery provider will also process the address and verification message.
Information may also be disclosed when required by law, to protect rights and safety, to investigate abuse or fraud, or in connection with a transfer of the service subject to applicable legal safeguards.
10. Storage and retention
Guest data, transcripts, settings, and history are stored locally until removed through available app controls, guest-data deletion, operating-system storage management, or app removal. Local history is capped at 30 entries per local user. App-managed history audio is removed when its entry is pruned or history is cleared; abandoned temporary recordings use the 24-hour recovery grace described above. Signed-in account and gameplay records remain in Firebase until the account is deleted or the records are no longer needed for the purposes described here.
Firebase logs and backups, support messages, operating-system speech data, Apple transaction records, and any later-enabled analytics, AI, RevenueCat, or Superwall data follow the applicable owner or provider retention settings and legal requirements. Deleting a Tongue Smash account does not necessarily delete records an independent provider must retain.
11. Account and local-data deletion
Signed-in users can request account deletion inside the app. The account-deletion process recursively deletes the user's Firebase data, the related leaderboard profile, an applicable email verification challenge, and the Firebase Authentication user. The app then attempts to clear known account-specific local recordings, transcripts, history, progress, caches, and abandoned temporary recordings. The app does not report successful account deletion or clear the local signed-in state if the remote deletion fails. If local cleanup reports an error—or if you want to remove possible residual app files—remove and reinstall the app before another person uses the device.
Account deletion does not cancel an Apple subscription and does not erase records independently retained by Apple or other providers. Read the Account Deletion guide for the current steps.
12. Children's privacy
Tongue Smash is intended for teenagers aged 13 and older and adults. It is not intended for children under 13. Children under 13 must not create an account or use the service. Users aged 13 through 17 must have any parent or guardian permission required by the law where they live.
We do not knowingly seek personal information from children under 13. If we learn that such information was collected, we will take steps to delete it. A parent or guardian who believes a child under 13 has provided information can contact tonguesmash.support@gmail.comto request deletion.
13. International processing
Firebase states that its Authentication service runs from United States data centers, and Tongue Smash configures Cloud Functions for the us-central1 region. Apple, Google, operating-system speech services, RevenueCat, Superwall, and other providers may process information outside the country where a user lives.
14. Security
Reasonable measures are used to protect information. The app uses Firebase access controls and App Check for protected operations. No storage or transmission method is completely secure, and this policy does not promise absolute security.
15. Your choices and rights
You can manage microphone and speech-recognition permissions in device settings, use guest features where available, manage Apple subscriptions through Apple, and delete a signed-in account in the app. Depending on where you live, you may also have rights to request access, correction, deletion, restriction, portability, or objection, and to complain to a regulator.
Send a privacy request to tonguesmash.support@gmail.com. Identity verification may be required before acting on a request. A parent or guardian may contact the same address about a user under 18, but the rights that person may exercise depend on applicable law and the user's circumstances.
16. Changes to this policy
This policy may be updated as the app, providers, or law changes. The effective date and last-reviewed date will be updated, and additional notice will be provided when required.
17. Contact
Tongue Smash is operated by Muhammad Affan Naveed. Privacy and support questions can be sent to tonguesmash.support@gmail.com.