Privacy Audit: Questions to Ask Before Joining Any Dating App

Most people download a dating app, tap through the onboarding, and accept whatever permissions the app requests. Twenty minutes in, their real name, phone number, contact list, photos, location, and a facial scan are in the app's backend, and the only question they have asked is how soon they will get a match. The result is that when something goes wrong later, the cleanup is expensive, awkward, and often incomplete.

The fix is a pre-flight privacy audit. Before you install a new dating app, you run through a short checklist and get yes-or-no answers to specific questions. If the app fails too many of the questions, you walk away before any damage is done. It takes about 15 minutes per app and it has saved more than one of my clients from situations that would have cost them thousands of rupees and weeks of stress. Here is the checklist I use.

1. Does the Privacy Policy Name a Grievance Officer With a Real Email?

Every Indian intermediary must publish a grievance officer name, designation, and contact email under the Intermediary Guidelines 2021 and the DPDPA 2023. The presence of this information is a compliance floor, but its absence is a loud signal. If you cannot find a grievance officer, or if the email address is a generic free-provider address (gmail, yahoo), the app is either non-compliant or structurally incapable of responding to a data request. Do not sign up.

A 2025 audit by the Internet Freedom Foundation found that 4 of 22 Indian dating and matrimony platforms failed this check entirely, and another 6 had grievance officer emails that bounced or went unanswered within the mandated 30-day window. The check takes 30 seconds. Do it every time.

2. What Happens to My Data If I Delete My Account?

The privacy policy should specify the retention period for deleted accounts. The typical promise is deletion within 30 or 90 days, but many policies are silent on this and a few openly retain data for years "for legitimate business purposes." You want a specific period, in writing.

Ask a follow-up: does deletion apply to all data, or just the profile? Some apps delete the visible profile while retaining the underlying behavioural data, photos, and message history in a separate analytics pipeline. The correct answer is full deletion across all systems within a bounded period.

A Mozilla Privacy Not Included review in 2024, led by Jen Caltrider, found that 11 out of 25 audited dating apps had deletion policies that retained some category of data indefinitely, most often under the label of "anonymised analytics data" or "legal compliance records."

3. Does the App Require a Phone Number?

Phone number verification is the single biggest deanonymisation vector in dating app privacy. If the app makes it optional or offers email-only signup, that is a positive signal. If it is mandatory, you should treat the app as if it will eventually leak your phone number to matches, to the ad tech ecosystem, or to a breach.

If you decide to sign up anyway, use a secondary SIM or a virtual number. Never give your primary phone number.

4. Does the App Ask for Aadhaar or Any Government ID?

Some matrimony and premium dating apps ask for Aadhaar or another government ID as part of a verification feature. Under Indian law, consumer dating platforms cannot use the full UIDAI authentication API without a specific notification. They can use DigiLocker or offline XML verification with your consent.

Ask: what method does the app use? If the answer involves typing your Aadhaar number directly, or uploading a selfie with your ID card, the answer is no. A 2024 Gurugram Police report identified "selfie with ID" as the most common data collection pattern in Indian sextortion rackets. If the app asks for DigiLocker, that is the safe path.

5. What Third Parties Receive My Data?

The privacy policy's third-party sharing section should list categories of recipients: payment processors, analytics vendors, advertising networks, cloud infrastructure providers, law enforcement. A well-written policy names specific vendors. A poorly-written policy uses vague categories and says "and others."

The MediaNama 2024 report on Indian dating app data flows found that the median app shares user data with 7 third-party services, and the highest in the sample shared with 23. Every additional recipient is another place the data can leak, and every additional recipient is a place where your consent grant has to be individually respected. Long third-party lists are red flags.

6. Does the App Sell or Rent My Data?

The policy should contain an explicit statement that the app does not sell or rent user data. In the post-DPDPA environment, most Indian-operating apps have added this language, but implementations vary. Look for the word "sell" specifically. Some apps use euphemisms like "share with partners for commercial purposes," which is effectively a sale under a different label.

Bruce Schneier has written about this pattern in his essays on data brokers. His summary: "If the service is free, you are the product. If the service is paid, you may also be the product. The only way to know is to read what the company says about secondary use, and believe it or walk away."

7. Is Location Tracking On by Default?

Many dating apps use location to show nearby matches. This is a reasonable product feature. What is not reasonable is background location tracking, continuous location logging, or location history retention.

Check the privacy policy for three things: what precision the app collects (city, kilometre, metre), whether it tracks in the background, and how long the location history is retained. An app that logs precise real-time location in the background is a surveillance tool regardless of its stated purpose. A 2020 scandal involving the Grindr location API, which allowed third parties to pinpoint users to within 20 metres, is the cautionary example every dating app has been warned about and not every app has fixed.

Before you audit an app with a checklist, hear what "privacy by default" actually feels like:

8. How Are My Photos Stored and Shared?

Photos are the single highest-density piece of personal data most dating apps hold. They contain face biometrics, sometimes location metadata (EXIF), and often identifiable background details.

Ask: does the app strip EXIF metadata on upload? Does it serve photos from a public CDN URL or through an authenticated endpoint? Are photos shared with facial recognition vendors for training purposes? A 2023 audit by the University of Chicago's Security Lab found that 5 out of 12 tested dating apps served profile photos from public URLs that were guessable or enumerable, meaning anyone with the URL pattern could scrape the entire photo database. This is a catastrophic flaw and you should test it by looking at the URL structure of any photo in the app.

9. Does the App Use End-to-End Encryption for Messages?

In-app messages on most dating apps are not end-to-end encrypted. They are encrypted in transit (HTTPS) and at rest in the database, but the app operator can read them and so can anyone who gains access to the database. A few apps have implemented true end-to-end encryption; most have not.

If the app claims end-to-end encryption, verify it by searching for the phrase in the privacy policy and checking whether the app publishes a security whitepaper. Signal-level encryption is a non-trivial engineering commitment, and the apps that have done it usually advertise it prominently.

If the app does not have end-to-end encryption, treat every message you send as if the app's employees could read it, because they can.

10. What Is the App's Breach History?

Check Have I Been Pwned and search for the app's domain. Check news archives for "(app name) data breach" or "(app name) leak." A history of breaches is not automatically disqualifying, but unresolved breaches, lack of notification, and slow remediation are all strong negative signals.

The Ashley Madison 2015 breach, the Heyyo 2019 breach, the MobiFriends 2020 breach, and the Muslim Match 2023 breach all involved Indian or Indian-adjacent user data. Apps with a clean breach record are not necessarily more secure; apps with a messy breach record are almost certainly less secure.

11. Does the App Have a Transparent Security Practice?

Look for a security policy, a vulnerability disclosure program, and a bug bounty. Apps that publish a security.txt file and participate in bug bounty platforms like HackerOne or Bugcrowd are generally more mature in their security practice. Apps that have no visible security surface are either very small or very opaque, neither of which is comforting.

Check the company behind the app: who owns it, how long has it operated, where is it headquartered, and how does it handle data breach notifications. A parent company with a track record of transparency is a signal of competence.

12. Can I Use the App Without Linking to Social Media?

Some apps require Facebook, Google, or Instagram sign-in. Others offer email as an alternative. The best apps also accept sign-in methods that minimise linkage, like Apple Sign In or email without social graph access.

Social sign-in creates a cross-platform graph that is difficult to unwind. If the app requires Facebook sign-in and does not offer an email alternative, the app has access to your Facebook friend list, your name, your profile photo, and anything else your Facebook privacy settings expose. This is a structural privacy loss even if the app does nothing malicious with the data.

Scoring Your Audit

Run through all 12 questions and give each one a yes, no, or unclear. The interpretation is simple.

• 10 or more clean answers (yes where yes is good, no where no is good): The app is within the acceptable range for most users. Proceed with standard privacy hygiene.
• 7 to 9 clean answers: The app has notable gaps. Use it only with a pseudonymous identity, a virtual phone number, and a dedicated email alias. Do not share identifying information.
• Fewer than 7 clean answers: The app fails the audit. Do not sign up. Look for alternatives.

The Two Principles Behind the Audit

Two principles do most of the work in this checklist, and it is worth naming them explicitly so you can apply them to questions I have not listed.

Principle 1: Data you do not share cannot be leaked. Every question is some form of "what does the app ask for." The less it asks for, the less it can leak. Apps built around anonymity by design, like Hidnn, exist precisely because the minimisation principle is so powerful that it justifies building the whole product around it.

Principle 2: Promises without enforcement are decoration. A privacy policy that says the right things is only as strong as the grievance process, the regulatory environment, and the track record behind it. A well-phrased policy from a company with a history of breaches is worse than a plain policy from a company with a clean record.

Frequently Asked Questions

How often should I re-run this audit?

Once at signup, and then every time the app sends a "we have updated our privacy policy" email. Policy updates are often the moment when data sharing expands. A 2024 Princeton CITP study found that 63 percent of privacy policy updates on consumer apps introduced new third-party sharing without reducing any existing sharing.

What if the app does not respond to my privacy questions?

If you email the grievance officer and get no response within 30 days, you can escalate to the Data Protection Board of India under DPDPA. Keep records of the original email and the timestamp. This is the primary enforcement mechanism available to Indian users in 2026.

Is it realistic to audit every app before signing up?

Yes. The first audit takes about 15 minutes and subsequent audits are faster because you develop a sense for where to look in a privacy policy. Compare that to the weeks or months of cleanup required after a privacy failure, and the cost-benefit is clear.

Should I avoid all dating apps that fail any question?

No. The scoring framework acknowledges that almost no app is perfect. Use the score to calibrate how much personal information you share, not as a binary accept-or-reject decision. An app that fails on third-party sharing can still be used safely if you share less data with it.

What if I already use an app that fails the audit?

Exercise your DPDPA right to erasure, delete the account, and rebuild your presence on an app that passes the audit. If the account holds valuable conversation history or matches, export what you can first, but do not let sunk cost keep you on a platform that is leaking your data.

Do This Now

• Pick the dating app you use most
• Run through all 12 questions this week
• Count your clean answers and decide what to do with the score
• Save the audit result somewhere you can reference later
• Repeat for each new app before you install it

The 15 minutes you spend on this checklist are the highest-leverage 15 minutes you will ever spend on dating app privacy. Use them.