Data policy

Version 1.0 · Last updated 4 October 2026

What this covers

This page explains the data behind the partner register: where it comes from, how it is stored and dated, how it gets corrected, and how it can be accessed. It covers public research data. Personal data — your account, your briefs, anything you send through a form — is covered by the privacy page, which also lists the retention periods for it.

Public data sources

Partner profiles are compiled from public sources: the Salesforce AppExchange public listings, partners’ own websites, public professional profiles, and published materials. We do not use leaked, purchased, or private datasets. Where a claim comes from the partner itself rather than an independent source, it is labelled as partner-supplied and shown as such — displayed, not endorsed.

How claims are stored

Every claim on a profile is stored as a structured record with its value, its source, and the date we checked it. Claims are not free-text blurbs: the value, the citation, and the check date travel together, so anything we publish can be traced back to where it came from and when.

Retrieval dates

Each claim shows when we last checked it against its source. If we don’t know something, the profile says so rather than guessing — an absent fact is labelled as absent, never filled in. Facts that couldn’t be confirmed are labelled as not confirmed, never presented as verified.

Corrections

Anyone can report an error through the corrections process. Partners can claim their listing and correct it directly through the register interest form. A person reads every submission; corrections that pass the source check go live with a new check date.

Retention

Register data is kept while the listing is published. When a claim is corrected, the superseded value is replaced — the profile shows the current sourced value, not a running log. Retention periods for personal data (accounts, briefs, form submissions) are published on the privacy page and are not restated here, so there is exactly one copy that can go stale.

Licensing and reuse

The register — the compiled profiles, the research behind them, and the matching data — is ours. You are welcome to link to it, cite it with attribution, and use it to make procurement decisions. Bulk copying, republishing the register, or reselling its data is not permitted (see the terms of use). Facts about third parties (for example, a partner’s own certification names, or Salesforce marks) belong to their owners and are referenced for identification. AppExchange-derived values are shown as cited references to the public listing while their licensing posture is under review; the machine channel withholds them in the meantime (see below).

Machine access

The register is readable by machines by design: a sitemap at /sitemap.xml, a site summary at /llms.txt with a full register summary at /llms-full.txt, and a documented read-only MCP connector you can set up yourself on the connect page. Automated access beyond those published channels — including bulk scraping — is not supported (see the terms of use).

Questions

Questions about this policy, or a correction to anything published, go through the site forms — see corrections or the contact page.