The Missing Comma in a Privacy Notice That Cost a Company $12 Million
Archi4 min read
Contents
The punctuation mark that rewrote a consent form#
In privacy law, the smallest detail that matters is often punctuation. A misplaced comma, a missing period, or a stray semicolon can flip the meaning of a data sharing clause. That is exactly what happened in a recent enforcement case, where a company's privacy notice contained a sentence that read, in part, "we may share your personal information with third parties for marketing purposes and analytics." The absence of a comma before "and analytics" was not a typo. It was the difference between two very different data practices.
Regulators argued that the clause, as written, bundled marketing and analytics into a single purpose. Under the state's privacy law, consent for marketing must be separate from consent for analytics. The missing comma made the two purposes indistinguishable. The company had collected data from roughly 2 million users under that notice. The settlement came to $12 million, plus a mandate to rewrite every privacy notice and obtain fresh consent.
Why a comma is not just a comma#
Legal drafting depends on syntax. In English, a comma before a coordinating conjunction can signal that the conjunction joins two independent clauses. Without it, the conjunction may be read as joining two items within a single list. In the clause above, "for marketing purposes and analytics" reads as one compound object of the preposition "for." That means the company treated marketing and analytics as a single purpose. The law required them to be separate.
The company's lawyers had reviewed the notice. They missed it. The marketing team had approved it. They missed it. The privacy office had signed off. They missed it too. The error survived three rounds of review because everyone read the sentence the way they intended it, not the way it was written. That is the trap of plain language drafting: the more natural a sentence sounds, the less likely anyone is to parse it.
The regulatory test that caught it#
The enforcement action hinged on a simple test. Regulators asked whether a reasonable user could tell, from the notice alone, that marketing and analytics were separate activities with separate consent requirements. The answer was no. The notice never used the word "separate." It never offered a toggle. It never explained that a user could opt in to analytics but out of marketing. The comma, or its absence, was the visible symptom of a deeper design flaw.
This is not an isolated case. Privacy regulators in several jurisdictions have started to treat notice design as a compliance issue, not a formatting preference. The California Privacy Protection Agency has said that dark patterns in consent flows can invalidate consent. The European Data Protection Board has issued guidance on the granularity of consent. In both cases, the question is whether the user's choice is specific, informed, and unambiguous. A missing comma can make it none of those things.
What the company changed#
The settlement required more than a new comma. The company had to rebuild its consent flow from scratch. Users now see two separate checkboxes: one for marketing, one for analytics. Neither is pre-checked. The notice uses bullet points instead of run-on sentences. The privacy office added a syntax review step to its drafting process, where a lawyer reads every clause aloud and marks the boundaries between purposes.
The company also had to delete data collected under the old notice. That meant purging marketing profiles for users who had never given separate consent. The deletion took four months and cost an estimated $3 million in engineering time. The $12 million fine was the headline. The cleanup was the real bill.
The lesson for anyone who writes a privacy notice#
The smallest detail that mattered was not the comma itself. It was the assumption that everyone shared the same reading of the sentence. Privacy notices are legal documents and user interfaces at the same time. They have to survive a literal reading by a regulator and a quick scan by a user. Those two audiences read differently. A comma that helps one can hurt the other.
The practical fix is not to add more commas. It is to shorten the distance between purposes. If marketing and analytics require separate consent, they should appear in separate sentences, separate checkboxes, and separate paragraphs. Punctuation can clarify meaning, but it cannot create granularity where the underlying design is bundled. The comma was a symptom. The consent flow was the disease.
A checklist for the next notice you review#
Read every sentence that contains the word "and" and ask whether the two items on either side require separate consent. If they do, split the sentence. Check whether your consent flow offers a separate choice for each purpose. If it does not, the notice is misrepresenting the flow. Finally, have someone who did not draft the notice read it cold and explain what they think it permits. If their explanation differs from your intent, the notice is wrong, not the reader.
The $12 million settlement will be cited in privacy training for years. The comma will be the punchline. The real lesson is that privacy compliance lives in the details of syntax and design, and the smallest detail can carry the largest liability.
More articles