Can I trust Tinder Dating App: Chat & Date?
This app did not meet two or more trust checks, has a critical issue in one, or has a red flag.
- Avoid if
- Users avoiding data broker integrations
- What it means for you
- Dating profile data, messages, and auth credentials are excluded from Google cloud backup and device transfers. Facial recognition processing occurs entirely on the device, and the build includes no code to pass raw biometric photos to third-party services. The app includes code to pass usage and behavioral data to advertising and attribution networks including Google Ad Manager, AppsFlyer, and LiveRamp, though seven tracking integrations are individually consent-gated.
- Main concern
- The app includes code to upload government ID images (passports, licenses) to Tinder servers via FaceTec
- The developer's description
- Tinder is a dating app that connects people based on location and interests. Features include profile matching, real-time messaging, optional biometric age verification, and optional government ID verification.
- Third-party services
- 22
- Findings rated low or higher
- 13
Open on Google PlayOpens the app's listing on Google Play in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
One criterion not metSecurity gaps detected
Why this result
This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.
Data Minimization
StrongTracking done right
Why this result
The check looks at analytics and attribution code for companies other than the developer: the data it reads, the companies named in code as recipients, and whether a consent step runs before that code. In this build, either no such code was recorded, or a consent step runs before it and the app's own disclosures describe the collection.
The install attribution SDK registers and initializes before any user consent decision is made, a step that may involve capturing device and install-referrer signals in memory, even though no data is transmitted to the attribution provider until after consent is explicitly granted. Seven tracking and advertising SDKs are individually gated behind the app's consent management system, Firebase Analytics is disabled at launch and activates only after the user consents, and the app implements the IAB Transparency and Consent Framework. The pre-consent SDK initialization creates a compliance gap under strict interpretations, while the transmission-level gating and comprehensive per-SDK consent architecture represent genuine positives, producing genuinely mixed signals.
Manifest Mismatch
One criterion not metDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
User Control
StrongNo lock-in
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.
No proprietary data formats trapping user content, no artificial barriers to account deletion, and no mechanisms preventing users from switching services were identified in the decompiled code.
Strengths
- Dating profile data, messages, and auth tokens are fully excluded from Google cloud backup and device-to-device transfers
- Firebase Analytics starts disabled and only activates after explicit user consent is granted
- Facial recognition and ML processing run entirely on-device, and the build includes no code to send raw biometric photos to third-party ML services
- Screenshots and screen recordings of other users' profiles are blocked in the profile swipe view
- Seven tracking SDKs are individually consent-gated through a granular per-SDK consent management system with TCF 2.x support
- All first-party API traffic uses HTTPS with no cleartext HTTP on Tinder's own endpoints
- Auth tokens are encrypted with AES-256-GCM backed by Android Keystore hardware
What the app contains
22 services
Third-party services the scan names in the build:
- AppsFlyer
- Branch.io
- Google Ad Manager
- AdMob
- Nimbus SSP
- Google Privacy Sandbox
- LiveRamp
- Firebase FCM
- Firebase Analytics
- FaceTec
- WorldCoin IDKit
- Bugsnag
- Sentry
- Google ML Kit
- TensorFlow Lite
- Arkose Labs
- hCaptcha
- Google Sign-In
- Line SDK
- Spotify Auth
- Noonlight
- Braintree
Libraries
| Library | Version | Advisory |
|---|---|---|
| ExoPlayer / media3 | not recorded | none confirmed |
| Room | not recorded | none confirmed |
| Lottie | not recorded | none confirmed |
| Google Play Billing | not recorded | none confirmed |
| AppsFlyer | not recorded | none confirmed |
| Bugsnag | not recorded | none confirmed |
| Shimmer | not recorded | none confirmed |
| Jackson | not recorded | none confirmed |
| Glide | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
Show all 37 librariesShow fewer
Changes since the previous scan
- Version 17.10.0 (versionCode: 17100007), score 74.
- Score 38 before, 74 after.
- Version 17.2.4 (Build 17020439) before, 17.10.0 (versionCode: 17100007) after.
- Score change since version 17.2.4 (Build 17020439): +36 points.
- Since the previous scan: 15 findings added, 8 removed.
- Version 17.2.4 (Build 17020439), score 38.
- First public scan of this app.
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Build SHA-256
- 2c670d4353cba803bf8744d98cb75a95f06b652c4df296d8e3ad972a905015af
- Rule pack
- citt-ruleset-2026-08-v1
- Files decompiled
- 100,491
- Scan date
- 13 August 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.