How to write a privacy claim you can actually back up

Three nested rounded frames with a document sheet, a magnifying glass over it and a round seal alongside

The rule that catches marketers out is not about wording at all. It is about timing. Substantiation has to exist before the claim goes live, and the advertiser answers for what readers reasonably take away, including the parts nobody on the team meant to say. Privacy claims attract that second problem more than most, because the audience fills in the gaps generously.

VPN providers live at the sharp end of this, since the promise about data retention is the product rather than a feature of it. If you want to see how the claim gets worded when a company expects scrutiny, find out what PIA's no-logs policy means and pay attention to how much of the page defines scope instead of asserting a benefit. That ratio is the tell.

The same discipline applies to anything a brand publishes about handling customer data, which now includes most SaaS landing pages, a fair share of app store listings, and the trust page your sales team links to in every deal.

The claim you wrote and the claim they heard

BBB National Programs, which runs the National Advertising Division, publishes a checklist for substantiating advertising claims that is worth reading once a year even if you never touch a regulated category. Three points from it do most of the work.

Advertisers must hold substantiation for all claims before they begin advertising, not when someone challenges them. Express claims are the words on the page; implied claims are what a reader reasonably infers from those words, from the imagery, and from what the page leaves out. You are responsible for the implied version whether or not you intended it. The checklist's own example is a widget advertised as durable, which a reader may take to mean nearly indestructible.

Then there is the rule that a claim naming a level of support has to be backed by at least that level. Cite studies and you need reliable studies. Say independently verified and someone will ask who verified what. The checklist also notes plainly that reviews from satisfied customers do not count as reliable evidence, which rules out the most common shortcut in trust marketing.

Run a privacy claim through that frame and it usually widens on contact. No logs reads, to an ordinary visitor, as nothing is written down, nothing can be handed over, and nothing can be tied back to me later. If the system keeps connection timestamps for abuse handling, or crash diagnostics with device identifiers, or payment records that sit beside an account ID, the implied claim already reaches further than the express one. That gap is where the walk-back happens.

What an audit says, and what it leaves out

Independently audited is doing a lot of load-bearing work in current marketing copy, and most readers have no idea what it covers.

Scope and window

The Journal of Accountancy, the AICPA's magazine, lays out the differences between SOC reports clearly. A SOC 2 engagement looks at controls relevant to security, availability, processing integrity, confidentiality or privacy, measured against the trust services criteria, and the report includes the auditor's tests and their results. A Type 1 report addresses how the controls were designed as of a specified date. A Type 2 adds an opinion on whether those controls operated effectively throughout a specified period, with the test detail attached. SOC 2 comes in both types, and SOC 3 covers the same ground while dropping the test descriptions, which is why it is the version a company can publish freely.

So a page that says audited, with no report type, no criteria and no period, has told you almost nothing. A page that says a Type 2 report covering confidentiality and privacy across a named twelve month window has told you something you can check. Writing the second version takes one extra sentence and removes an entire category of awkward follow-up questions.

Evidence that is not an audit

Audits are one input among several, and the others are often more persuasive to a technical buyer. Published responses to legal demands show what a company actually held when someone with authority asked for it. A transparency report with consistent numbering across years shows a process rather than a gesture. Infrastructure choices that make retention difficult, rather than merely prohibited by policy, are the kind of detail that engineers repeat to each other.

Each of those carries a maintenance cost, which is the real reason thin claims survive. A sentence is cheap and a standing evidence file is not.

Before the claim goes live

A lot of the damage comes from claims that were accurate when written and that nobody revisited afterwards. A short routine prevents that:

  • write the express claim as one sentence, then list what a reasonable reader would infer from it, and treat that list as the thing you must support
  • name the data you do keep, why, and for how long, in the same place as the claim rather than four clicks away in a policy document
  • when citing an audit, give the report type, the criteria in scope and the period covered
  • date the claim and attach a trigger for review, such as a new subprocessor, a change in retention, or a product that starts collecting something new
  • keep the evidence where the next marketer can find it, because the person defending the sentence in two years will not be you
  • brief support and sales, since an answer typed into a ticket is a claim the company made

Trust signals belong to the same workstream as the rest of your visibility, not to a compliance silo. SiteTrail's rundown of SEO, PR and digital marketing tips for tech and software companies treats expertise and trust as inputs that search and buyers both weigh, which is the right framing here too. A privacy claim that survives scrutiny is a reusable asset. One that does not becomes a correction, a support thread, and in the worst case a case file.

The practical test is simple enough to apply this afternoon. Pick the strongest privacy sentence on your site, write down what a sceptical journalist would ask about it, and see whether the answer already exists somewhere you can point to. If it does not, you have a drafting problem rather than a legal one, and drafting problems are cheap to fix before publication.

Picture of Adriaan Brits

Adriaan Brits

Adriaan Brits (MSC, MBA) is the CEO of Sitetrail.com. He has over a decade of experience in consulting with clients around the world on digital marketing strategy and PR. His latest research evolves around generative engine optimization.

Accelerated PR & SEO Plan

Maximize Your Online Visibility with AI-Optimized SEO, Google News, and Digital PR—Designed to Dominate Search Engines and Fast-Growing AI Platforms.

Plugin Downloaded Congratulations Installation Guide: 

  1. In WordPress, go to Plugins → Add New Plugin.
  2. Click Upload Plugin and select the downloaded ZIP file.
  3. Click Install Now, then Activate Plugin.

 

Your free trial starts automatically. No license key is needed yet.