Last updated: August 29, 2026

Privacy Policy

By using Singdu, you acknowledge the practices described here. This policy should be read together with the Singdu Terms of Service.

Local app data is removed if you clear Singdu’s storage or uninstall the app. Singdu configures Android to exclude its local app data from cloud backup and device-to-device transfer, although operating-system behavior outside Singdu’s control may change.

If you choose Google sign-in, Google and Firebase provide Singdu with account information you authorize, such as your name, email address, profile photo, and a unique account identifier. Google’s handling of that information is governed by your Google settings and Google’s privacy terms.

Other Singdu users may see or search information included in your community profile, including your display name, profile photo, profile frame, membership tier, level, experience points, streak, recent practice time, vocabulary count, top genre, top artists, join date, posts, reactions, and friend connections. Do not use a display name or profile photo you do not want other learners to see.

Some preferences and cached progress are also stored locally on your device so the app can load quickly and continue to provide limited functionality offline.

Reports are used to review safety, content quality, and potential violations. They may include your account identifier, the reported user or content, selected reasons, and relevant details.

Singdu uses a Firebase Cloud Messaging installation identifier linked to your account to deliver optional community notifications. Singdu also uses Firebase Analytics to measure screen views, interaction types such as taps, long presses, and swipe directions, and product events such as onboarding, sign-in method, song selection and completion, vocabulary activity, sharing, feedback, KTV pairing and controls, and subscription-funnel actions. Analytics may use non-sensitive segments such as guest or account access, free or Pro membership, learning-language codes, song identifiers, genre, difficulty, translation language, and KTV destination type. These metrics do not include touch coordinates, pairing codes, search queries, lyric text, typed content, names, email addresses, profile fields, or other on-screen values. Advertising ID collection is disabled for Singdu's Firebase Analytics integration. Firebase may still process an app-instance identifier, masked IP-derived information, device and app information, and diagnostic information to provide aggregated usage metrics.

Singdu uses Firebase Crashlytics to identify crashes, non-fatal failures, and app-not-responding errors. Crash reports may include stack traces, app and device state, operating-system and app versions, environment, recent analytics breadcrumbs, and technical identifiers needed to group and diagnose failures. Singdu does not intentionally attach names, email addresses, lyric content, or typed input to crash reports.

The free experience also includes the Google Mobile Ads SDK and Google User Messaging Platform SDK. The Mobile Ads SDK automatically collects and shares IP address, approximate location derived from IP address, app launches, taps, video views, ad requests and interactions, diagnostic and performance information, and device or account identifiers such as the Android Advertising ID and App Set ID for advertising, analytics, attribution, and fraud prevention. Where supported and permitted, it may also use Android advertising-topic and attribution signals. This advertising processing is separate from Firebase Analytics, so disabling Advertising ID collection for Firebase Analytics does not disable identifier processing by AdMob. The information used can vary with your device, location, consent choices, and Google or Android settings.

For Google Cast, the Android sender communicates with the selected Cast receiver. Google’s Cast SDK automatically processes anonymous device-discovery, session-management, mobile-device, SDK, and client-app information to operate and improve Cast. The selected receiver’s name may be displayed in the app.

For the Singdu KTV browser receiver, the browser derives a general label such as browser and operating-system family and creates a random pairing code. The label, code, creation and expiry times, and controller and receiver messages are stored temporarily in Firebase Firestore. The browser stores the code and expiry in session storage so the session can recover after a refresh. A pairing code acts as temporary access to that KTV session, so only share it with people you want to connect. Sessions become inaccessible when they expire, each renewal is limited to no more than 20 minutes, consumed messages are normally deleted promptly, and Firestore time-to-live policies delete expired session and message records afterward.

If you scan the KTV pairing QR code, Google code scanner performs image processing on the device and Singdu receives only the decoded pairing value. Google does not store the scanned image or result. The scanner and ML Kit may process device and app information, performance and diagnostic events, and, because Singdu enables auto-zoom, a temporary scanning-session identifier, zoom changes, and predicted barcode bounding-box coordinates for diagnostics and usage analytics.

Depending on where you live, these activities may rely on performing our agreement with you, your consent, compliance with law, or legitimate interests such as operating, securing, and improving Singdu. Where processing is based on consent, you may withdraw that consent, subject to applicable law.

We may share or make information available: • to other users when you use public profile, community, reaction, or friendship features; • to service providers that host, authenticate, synchronize, secure, or deliver the Service; • to the television, browser, or other receiver you select when you start a KTV session; • to Google for advertising delivery, measurement, fraud prevention, and consent management in the free experience; • when you direct us to connect with a third-party service; • when reasonably necessary to comply with law, respond to valid legal process, prevent harm or fraud, or protect rights and safety; or • as part of a merger, financing, reorganization, acquisition, or transfer of the Service, subject to appropriate protections.

Release builds use Firebase App Check with Google Play Integrity to protect Singdu’s backend from unofficial clients, tampered apps, fraud, and abuse. Google and Firebase process an integrity token and signals used to assess whether requests come from a recognized Singdu app, a qualifying Google Play installation, and an eligible Android device. Singdu uses the resulting attestation to allow or reject backend access, not to create an advertising profile.

Singdu does not host YouTube videos or receive your Google or YouTube password. You can avoid YouTube playback data by not playing embedded videos, although this may limit karaoke functionality.

You can turn off Singdu notifications at any time in Android system settings. Signing out unregisters the current device from Singdu community notifications.

Where required, we rely on safeguards provided by our service providers and applicable law for international data transfers.

KTV browser session records and messages are short-lived as described above and are not linked to your Singdu account. Expiry prevents further session access before Firestore completes its time-to-live deletion.

When data is deleted, limited copies may remain temporarily in provider backups or logs until overwritten under standard retention processes. Public content copied or captured by other users may remain outside Singdu’s control.

You can update your display name and profile photo in the app, control playback and history preferences in Settings, revisit available advertising choices under Settings → Privacy choices, choose whether to grant notification permission, sign out, or continue with limited guest access. You can also manage advertising personalization through applicable Google account and Android settings. To ask about your information or exercise a privacy right, contact privacy@singdu.site. We may need to verify your identity before completing a request.

The in-app deletion process removes the Firebase Authentication account, the RevenueCat customer record used to manage purchase access, and associated Singdu profile, profile photo, learning progress, community posts, reports, feedback, friendships, user blocks, notifications, and push registration records. Some related information may remain temporarily in backups, security records, or material retained where required by law.

If you believe someone below the applicable minimum age has used Singdu or provided personal information, contact privacy@singdu.site so we can investigate, restrict the account, and delete the information where appropriate.