Security and Trust Pages B2B Buyers Check First
Trust · 9 min read ·
Business buyers check security, privacy, uptime and compliance before committing. What to publish, how to describe it honestly and what never to claim.
Before a business buys software, someone in the organisation asks whether it is safe to use. That person may be an engineer, a security lead, a procurement officer or a founder with a long memory. They will not read your marketing. They will look for a page that tells them where the data goes, who can touch it and what happens when something breaks.
If that page does not exist, the evaluation stalls, or ends. This article describes what to publish and how to say it honestly.
What buyers are really asking
Behind every security questionnaire sit a few basic concerns.
- Confidentiality: can someone who should not see our data see it?
- Integrity: will our data be changed or lost?
- Availability: will the service be there when we need it?
- Privacy: are you handling personal data lawfully and respectfully?
- Accountability: if something goes wrong, will you tell us and fix it?
Your trust materials should answer these in plain language.
The core pages
1. Security overview
A single page that summarises your approach. Include:
- Hosting: where the service runs and, in broad terms, on what kind of infrastructure.
- Data location: regions where customer data is stored.
- Encryption: in transit and at rest, stated in general terms.
- Access control: how your staff access production, the principle of least privilege and use of multi-factor authentication.
- Customer access controls: roles, single sign-on if offered, audit logs if offered.
- Backups and recovery: how often, how tested.
- Development practices: code review, dependency management, testing.
- Vulnerability reporting: an email address or form, and what researchers can expect.
- Incident response: how you detect, communicate and learn from incidents.
Be accurate. Do not describe controls that are not in place.
2. Privacy policy
A clear statement of what personal data you collect, why, how long you keep it, who it is shared with and how people exercise their rights. Write it in plain English and keep it current. Have a qualified professional review it.
3. Terms of service
Understandable terms, including service levels if any, acceptable use, liability and termination. Link from the footer and from sign-up.
4. Data processing information
If you process personal data on behalf of customers, offer a data processing agreement and a list of subprocessors, the third parties that handle data for you, with what they do and where. Update it when it changes and tell customers how they will be notified.
5. Status and uptime
A status page showing current availability and incident history. Even a simple one builds trust. Explain how to subscribe to updates.
6. Compliance and certifications
List what you hold and what you are working towards, separately and honestly.
Describing certifications honestly
Certification claims are where trust is most often lost.
Wikipedia describes SOC 2 as an audit report for service organisations, assessing controls against five Trust Services Criteria: security, availability, confidentiality, processing integrity and privacy. It explains that only licensed CPA or audit firms certified to perform such assessments may conduct them, that a Type I report examines whether control designs align with the criteria while a Type II report evaluates operational effectiveness over a period of months, and that reports are intended for a limited audience of customers and stakeholders.
Use that precision. If you hold a Type I report, say Type I. If you hold nothing, do not say "SOC 2 compliant". Say "we have not been audited; here are the controls we operate". A buyer will respect that far more than an inflated claim that collapses under a questionnaire.
The same applies to any standard or regulation. State exactly what you hold, which scope it covers and when it was issued, and keep the evidence ready to share under confidentiality.
Be specific without being reckless
Publish enough to be credible and not so much that you hand an attacker a map. Describe controls and practices at a general level. Offer details under an agreement. A good rule is: describe what you do, not how to defeat it.
Make questionnaires easier
Large buyers will send security questionnaires. Reduce the pain.
- Keep a library of answers to common questions, reviewed regularly.
- Name an owner for questionnaires.
- Aim for a standard turnaround and tell buyers what it is.
- Offer documents on request, under a simple confidentiality agreement.
- Be consistent. Different answers on different forms signal a problem.
Incident communication
Say how you will tell customers about incidents: through a status page, by email to account owners, within what timeframe. Be careful with numbers you promise. Make commitments you can keep. After an incident, publish a short, honest summary of what happened and what you changed.
People and process
Buyers also look at who is behind the product.
- A named contact for security.
- A company page with real people.
- Evidence of maintenance: a changelog and recent updates.
- Support options and response expectations.
Google's helpful-content guidance, discussing who, how and why, makes a similar point about transparency: clearly identify authorship and be open about how content is produced. The same instinct, applied to a company, builds trust.
Format and findability
Put trust information where buyers look: a "Security" or "Trust" link in the footer and in the main navigation of the pricing page. Keep pages fast, since Google's Core Web Vitals guidance recommends an LCP within 2.5 seconds, an INP of 200 milliseconds or less and a CLS of 0.1 or less. Make documents downloadable in accessible formats. Use clear headings so people can scan.
Keep it current
Trust pages rot quickly. Add a "last reviewed" date and a quarterly reminder. When your infrastructure, subprocessors or certifications change, update the pages the same week. An out-of-date trust page is worse than a short one, because it signals carelessness.
What not to claim
- "Military-grade encryption" or other marketing phrases without meaning.
- "Unhackable" or "100 percent secure". Nothing is.
- Certifications you do not hold.
- Customer names without permission.
- Uptime promises you cannot meet.
- Compliance with a regulation without understanding it.
A starter plan for a small team
If you are tiny, start with five pieces.
- A one-page security overview, honest and specific.
- A privacy policy and terms, reviewed by a professional.
- A subprocessor list.
- A status page and incident email address.
- A security contact and vulnerability reporting route.
Then build a library of questionnaire answers and add certifications when your customers require them.
On this site
Profiles on this site link to the product's own website, where those security and privacy pages should be easy to find. The submit page starts a listing, a launch entry costs $5 and the pricing page lists every option. Our live Ahrefs DR is 60. Buyers who check trust pages also like to know who runs a site, and the Launching Pro about-the-founders page shows exactly that.
A sample structure for the overview page
To make this concrete, here is how a short security overview for an imaginary analytics product might be organised. An opening paragraph states, in two sentences, who runs the service and what kind of data it handles. A section on hosting names the type of provider and the regions used. A section on protection summarises encryption in transit and at rest, authentication options for customers and how staff access production, including the use of multi-factor sign-in and the principle that people receive only the access they need. A section on resilience explains backup frequency and that restores are tested on a schedule. A section on development describes code review, automated testing and how dependencies are monitored. A section on incidents says how customers are told and within what general timeframe. A final section lists the certifications held and, separately, those being pursued, with dates, and gives the security contact and a route for reporting vulnerabilities.
Every statement is something the team can demonstrate if asked. If a sentence cannot be defended in a questionnaire, it does not belong on the page.
When a customer finds a flaw
Eventually someone will report a weakness. Decide in advance how you will respond. Acknowledge the report promptly, investigate, fix the issue, tell the reporter what you did and, if customers were affected, tell them too. Thank the researcher publicly if they agree. How you handle the first report shapes your reputation with the security community, and a calm, professional response is itself a trust signal that buyers value.
Involving the whole company
Trust is not owned by one person. Sales needs to know what the pages say, so nobody contradicts them on a call. Support needs to know how to handle security questions and where to escalate. Engineering needs to keep the pages truthful when systems change. A short internal briefing, repeated whenever the pages change, keeps everyone aligned.
Reviewing your own pages as a buyer
Once a quarter, read your trust pages as a sceptical buyer would. Click every link, check that documents open and that dates are recent. Compare each claim with reality by asking the person responsible for the underlying system. Anything you cannot confirm should be corrected or removed the same week.
The takeaway
Publish an honest security overview, privacy and terms, subprocessors, status and a contact, and describe certifications precisely. Do not claim what you do not hold. Keep it current and easy to find. Trust pages cost little to write and save weeks in evaluation.
Questions and answers
- What is SOC 2?
- According to Wikipedia, SOC 2 is an audit report on service organisations covering Trust Services Criteria: security, availability, confidentiality, processing integrity and privacy. Only licensed audit firms can issue it. Type I examines control design and Type II examines operating effectiveness over a period.
- What should a security page include?
- Where data is hosted, how it is protected, who has access, how incidents are handled, how to report a vulnerability and an honest account of certifications held.
- Can I say I am compliant if I have not been audited?
- Do not imply a certification you do not hold. Describe the controls you have and say plainly that no audit has been completed.
- Do small startups need a trust page?
- Yes. Even a short, honest page reduces buyer risk and speeds up evaluation.