> ## Content Index > Fetch the complete content index at: https://akribos.tech/llms.txt > Use this file to discover other available public pages before exploring further. # A dating profile is not spare training material - URL: https://akribos.tech/dating-app-privacy-is-about-real-people/ - Published: 2026-10-30T06:08:37.000Z - Updated: 2026-10-30T12:38:25.000Z - Description: The OkCupid case is a reminder that intimate disclosures carry expectations beyond a policy document. - Author: Noah Nelson - Tags: Privacy, Commentary People disclose information to a dating service for a reason: they hope another person will understand them. That willingness to be known in one setting is not an invitation to repurpose the information in every other setting. In its [March enforcement announcement](https://www.ftc.gov/news-events/news/press-releases/2026/03/ftc-takes-action-against-match-okcupid-deceiving-users-sharing-personal-data-third-party?ref=akribos.tech), the FTC alleged that OkCupid shared users’ personal information, including photos and location information, with an unrelated third party contrary to its privacy promises. The agency announced a proposed settlement restricting misrepresentations. These are the agency’s allegations and description of its action; they should not be inflated into claims about every dating service or every later use of the data. The broader argument is about context. Information provided to find a partner should not become a general-purpose corporate resource merely because a company can export it. ## The disclosure has a purpose A product can collect technically ordinary fields that become deeply personal in combination. Their meaning comes from why someone supplied them and what the service encouraged that person to reveal. That makes purpose limitation a useful product standard. Explain the activity the information supports. Identify the parties needed to perform it. Ask separately before creating a materially different use. A vague claim that more sharing improves the service does not settle those questions. It also changes how privacy incidents should be covered. A count of records measures scale, but tells readers little about the consequences of exposure. The meaning of the information matters alongside the number of rows. ## A photo’s meaning depends on where it was offered A person may willingly show a photograph to potential partners while objecting to its use in an unrelated dataset. There is no contradiction. The audience, purpose, and expected consequences are part of the decision to disclose. That distinction becomes easy to lose when a company discusses information only as fields in a database. The technical ability to copy a field says nothing about whether its reuse fits the original relationship. A privacy system should preserve the purpose attached to the information, not treat possession as permission. The [FTC’s case record](https://www.ftc.gov/legal-library/browse/cases-proceedings/okcupidmatch?ref=akribos.tech) anchors the specific OkCupid allegations and proposed remedy. It should be read on its own terms. The case does not establish that the shared material was used in any particular AI training run, and the argument here does not depend on making that unsupported claim. ## Reuse should require a fresh decision A company may have a legitimate proposal to use data differently. It should describe that proposal directly, identify the new recipient or activity, and ask for a choice proportionate to the change. A person should not discover the new relationship only after a revised policy becomes effective. The quality of that choice also depends on the alternative. If refusing an unrelated use prevents someone from using the core service, the company should explain why the two are dependent. A business preference for a larger dataset is not a technical explanation. This is particularly important for material that is difficult to replace. A person can change an email address with effort. They cannot change the history of a disclosure or the context in which a recognizable photograph circulated. Product decisions should account for that asymmetry before information leaves the original service. ## Contracts matter, but so does enforcement A recipient’s contractual restrictions can provide meaningful protection. They can define allowed uses, require deletion, and establish consequences for noncompliance. Dismissing every contract as meaningless would ignore a practical tool for controlling relationships between companies. But the existence of a contract is only part of the evidence. The originating company should know which data was delivered, under which terms, and how it can verify that the recipient complied. If a relationship ends, there should be a process for dealing with retained copies and downstream recipients. Those are questions a customer cannot usually investigate from the outside. A company asking for trust should therefore be prepared to explain its oversight in concrete terms, without disclosing details that would expose users or compromise legitimate security controls. ## Privacy journalism should resist voyeurism Reporting on sensitive datasets does not require reproducing the intimate details that make them newsworthy. Journalists can explain the categories, access conditions, and potential consequences while minimizing the exposure of individuals. A vivid example is not automatically worth the additional disclosure it creates. The same restraint should guide product testing. Use controlled accounts and material supplied for the purpose. Do not turn a story about misuse into another occasion for circulating somebody’s profile without a sound reason. The human-interest angle is the relationship people thought they were entering. That can be examined rigorously without treating their vulnerability as raw material for the article. The standard being demanded of the platform should apply to the coverage too. ## Trust has a direction A person can choose to be vulnerable with a prospective partner while expecting restraint from the company arranging the introduction. Those expectations are compatible. Technology companies should design around that distinction. Human trust is specific to a relationship. Moving the data should not silently move the permission with it. ## Sources - [FTC: OkCupid and Match enforcement announcement, March 30, 2026](https://www.ftc.gov/news-events/news/press-releases/2026/03/ftc-takes-action-against-match-okcupid-deceiving-users-sharing-personal-data-third-party?ref=akribos.tech) - [FTC’s case record](https://www.ftc.gov/legal-library/browse/cases-proceedings/okcupidmatch?ref=akribos.tech)