SexNov 16, 20266 min read

A Dating Profile Is Not Location-Broker Data

The FTC's OkCupid case is a reminder that proximity is part of the product, but intimate location data cannot become a side channel for somebody else's business.

Dating apps need a sense of place. That is part of their premise.

The person across town is a different proposition from the person across the country. Distance can help people decide whether to start a conversation, meet for coffee, or stay home. It can also expose routines, neighborhoods, identities, and vulnerabilities that a person never meant to sell.

In March, the Federal Trade Commission took action against OkCupid and Match Group Americas. The FTC alleged that OkCupid gave an unrelated third party access to personal data from millions of users. The data included photos, demographic information, and location information. The agency said the companies’ privacy promises did not match that sharing. The proposed settlement would bar misleading claims about how personal data is collected, used, disclosed, deleted, or protected.

This is not a story about a missing privacy toggle. It is a reminder that a dating profile is not a bag of neutral signals. Photo, age, orientation, desire, timing, and proximity can combine into a map of a private life.

Proximity Is Intimate Context

Location information does not need an exact street address to become sensitive.

A pattern of nearby profiles can reveal where someone sleeps, works, spends weekends, or travels. It can reveal a queer social scene in a hostile place. It can reveal that a person is using a dating app while away from home. It can connect a profile to a photo, a device, and other data that make a supposedly partial picture much clearer.

The FTC complaint says that the outside recipient received location information with user photos and demographic details. That combination matters. A coordinate by itself is abstract. A coordinate beside a face and a profile becomes social context.

This is why the usual defense is too thin: the app needs location to work.

Maybe it does need some location data to show nearby people. That does not answer who gets that data, how long they keep it, whether they can link it to other records, or whether people receive a clear account of the trade. Collection for a narrow feature is not permission for a wider data economy.

A Hidden Distance Is Not Always Hidden

The product design can complicate the promise even before data leaves the company.

Grindr’s current help materials make the limitation plain. A user can turn off the displayed distance. The user’s profile can still appear in a grid ordered by proximity. Grindr says other people may therefore estimate a general distance. Its safety guidance also says people can limit or remove precise location at the device level.

That is a more honest warning than many interfaces give. It also shows why a single switch is not a complete privacy model.

Bumble’s privacy policy says it may collect device coordinates when location access is enabled. It says it uses location to support nearby connections and related app features. The policy also directs users to device settings if they want to turn off geolocation.

Neither statement means these companies are doing what the FTC alleged against OkCupid. The point is simpler. Location features have layers: an operating system permission, an app’s collection, another person’s view, ranking logic, company retention, and any disclosure to another party. Each layer can change the risk.

The interface often compresses all of that into one cheerful word: nearby.

Privacy Is More Than A Promise Page

The OkCupid matter should make every dating platform ask harder questions.

  • What exact location precision does the feature need?
  • Which people can see a proximity signal?
  • Can a profile be ordered by distance after the distance number disappears?
  • Which vendors receive photos, demographic data, or location data?
  • What contract limits those vendors’ use and retention?
  • How long do logs remain after a person deletes an account?
  • Can the company explain these answers without sending users through a legal maze?

Those are not exotic compliance questions. They are product questions.

The difference between a safety feature and a surveillance feature is often in the details: precision, default settings, retention, access, and the quiet ability to join data from different systems. Private browsing does not erase those joins. Nor does a polished privacy page.

Dating platforms should not ask people to become privacy engineers before they can flirt. They should use the least precise location that supports the promised feature. They should make the trade clear at the moment it matters. They should keep third-party access narrow, documented, and auditable. They should delete what they no longer need.

Most of all, they should stop treating intimate context as ordinary audience inventory.

The Risk Is Not The Same For Everyone

Location privacy is not one abstract consumer preference.

For a person in a hostile household, workplace, or legal climate, a visible pattern of proximity can carry real consequences. For a survivor of stalking or abuse, location clues can make an already difficult safety problem worse. For queer people in places with discrimination or criminal penalties, the question may be whether an app can reveal a community that needs discretion to exist.

That does not mean people should leave dating apps. It means platforms should not make a narrow social choice carry an invisible data burden.

The same standard belongs in sex-tech cloud design and in the wider fight over identity systems at adult gates. Intimate technology works with unusually revealing material. It needs unusually strict restraint.

What The FTC Case Changes

The FTC action does not decide every question about dating-app location. It does something more basic. It puts a regulator’s line under the idea that privacy claims have consequences.

The agency alleges that OkCupid’s data-sharing conduct conflicted with its privacy promises. Its proposed order would prohibit the companies from misrepresenting how personal information is handled. The settlement process does not make every claim in the complaint a final finding. It does make the enforcement theory clear: companies cannot promise one thing about sensitive data and provide another thing in practice.

That principle should feel obvious. It often gets lost when the data comes wrapped in growth metrics, matching quality, analytics, or vendor jargon.

People use dating apps to look for connection. They should not need to wonder whether a profile and a nearby signal are becoming a durable file for someone they never agreed to meet.

Bottom Line

Dating apps can use location to help people find one another. That does not make intimate location data ordinary.

The FTC’s OkCupid case is a warning about a wider product culture. Proximity is not only a feature. In the wrong hands, it is a record of where a private life happens.

The better dating product is not the one that knows the most. It is the one that needs the least.

Sources

Comments

Useful additions, field notes, thoughtful disagreements, and reader questions. Everything is moderated before it goes public.

Loading
Loading comments

Checking the public thread for this article.

Join the Backchannel

A private dispatch for sharper experiments, taboo-adjacent research notes, field reports, and the links too weird to leave in polite company.

Private list. Signups are saved now; welcome emails are queued for human review until outbound sending is enabled.