# Security wording without certification claims | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-describe-security-work-without-claiming-certification
Last updated: 2026-11-05

Describe security work as work: in its owner's own words, with a status and a date. For SourceX, quote its trust center, which on 28 October 2026 listed a SOC 2 Type II report and ISO/IEC 27001 and 27701 certifications as in progress, none issued, beside the controls it says are in place today. On your own pages, posts, graphics and FAQs, remove any badge, seal, icon or adjective that implies a certificate, and keep your firm's own security claims visibly apart from SourceX's.

This page is for the compliance or communications lead at a partner firm, such as an IT services provider, a consultancy, an accounting practice or an agency, who signs off what the firm publishes about SourceX's referral program. A founder asking "are they certified?" across a table is a different moment, and [discussing audit status without overstating certifications](/guides/how-to-discuss-audit-status-without-overstating-certifications) covers it. Here the subject is what stays published: a website section, a LinkedIn post, an explainer graphic, an FAQ answer, an agency's landing copy, even an image's alt text.

## Whose security a published line is describing

Every security line in partner material describes one of three parties, and each has a different source.

- **SourceX's security.** Only SourceX's own trust center states it. A partner can quote it, date it and link it; a partner cannot add to it.
- **Your firm's own security.** Your evidence, your scope and your sign-off. It describes your systems, not the referral process, in which your firm handles no company records: SourceX's sample partner agreement gives a partner no authority to share a supplier's records, raw data or personal information.
- **A referred company's security.** Never yours to publish, and the company itself is not named publicly without its permission.

Most problems come from lines that blend two owners, saying something about both and supported for neither.

The commercial connection matters too: a partner may be paid a referral reward, and readers may weigh its words accordingly. In the United States, the FTC's Endorsement Guides say endorsers may be liable for statements they make in the course of an endorsement, that an advertiser may be liable for a deceptive endorsement even when the endorser is not, and that ad agencies, public relations firms and similar intermediaries may be liable for their part in creating or spreading endorsements they know or should know are deceptive (a paraphrase of 16 CFR 255.1). The FTC's policy on advertising substantiation expects a reasonable basis for objective claims, express or implied and however conveyed, before they run (a paraphrase of the policy statement). Whether a given page is an endorsement and what it must disclose is for your own counsel.

SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04) contain no section on partner marketing or on use of SourceX's name. The rule that does exist sits in section 4.5 of the sample Channel Partner Agreement: "No data license, trademark license or right to train models is granted. Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." Section 8 of the terms says the signed agreement governs confidentiality, so the version your firm signed is the one to read. Badges and titles beyond security are covered in [program membership versus endorsement](/guides/the-difference-between-program-membership-and-endorsement).

## SourceX's security work in its own status words

SourceX's trust center sorts its security work into groups, and each group supports a different kind of sentence. Its own summary of the certification work is the line to quote: "All three initiatives are in progress. SourceX has not yet received a SOC 2 Type II report, ISO/IEC 27001 certification, or ISO/IEC 27701 certification."

The same page shows the discipline to copy: under its list of business systems, it says the names are "shown for reference only and do not imply a partnership or endorsement." A name near a claim is read as part of it.

| Group on the trust center (28 Oct 2026) | What it lists, in its words or close to them | A published line may say | A published line may not imply |
|---|---|---|---|
| Compliance status: in progress | SOC 2 Type II, "Report not yet issued"; ISO/IEC 27001 and ISO/IEC 27701, "Certification not yet issued" | That SourceX lists all three as in progress and none as issued, with the date checked | Certified, audited or compliant, or any badge or seal for those standards |
| Controls in place today | "Companies only see their own records."; private storage shared through links that expire within minutes; nothing delivered before the supplier signs its agreements and SourceX gives the go-ahead; a full audit trail | The specific control, quoted and linked | That an outside party has assessed them: independent security assessments are listed as planned |
| Planned | Dedicated secure data rooms for Acquisition Partner review, assisted data-preparation tooling, independent security assessments, direct connectors | That SourceX lists the item as planned | That the item exists today |
| De-identification | "No method is perfect: the supplier agreement records that re-identification may still be possible and that SourceX is not liable for it." | The quoted sentence, caveat included | Anonymous, untraceable or risk-free |

## The status evidence review sheet

Run every security element in a piece through ten fields before it is published, and keep the completed sheet with the approval record. An element is any word, phrase or visual that a reader could take as saying something about security.

| Field | What to record | The element fails when |
|---|---|---|
| 1. Element | The exact words, or the visual described: badge, shield, seal, padlock, color band | A visual is left off the sheet because it "isn't copy" |
| 2. Where it appears | Page, post, slide, FAQ, alt text, social preview, metadata, email signature | The alt text or preview says more than the visible page |
| 3. Whose security | SourceX, your firm or a company | One line or one row of icons blends two owners |
| 4. Source sentence | The owner's exact published sentence and its URL | No sentence exists, or the line strengthens one |
| 5. Status word | In place, in progress, planned or issued, as the owner uses it | The line upgrades the status, as in "in progress" becoming "certified" |
| 6. Date checked | The day you read the source | There is no date, or it is older than your re-check interval |
| 7. Scope | Which entity, system or process the source covers | The line reaches wider than its source |
| 8. Permission | SourceX's written authorization for its name or mark; your firm's sign-off for its own claims | SourceX's name or mark appears without written authorization |
| 9. Drafted and approved by | In-house writer or agency, and the approver's name | An agency draft went live without the sheet |
| 10. Verdict and next check | Keep, rewrite or remove; the re-check date | No re-check date is set |

Four rules settle most visual and adjective questions before the sheet is even needed:

- A seal, shield or badge carrying a standard's name reads as a certificate. If no certificate was issued to the party pictured, remove it.
- A padlock or "secure" icon beside SourceX's name is a security claim about SourceX. It needs a trust center sentence behind it, or it goes.
- Adjectives such as "bank-grade", "enterprise-grade", "fully secure" and "compliant" have no owner's sentence behind them. Replace each with the specific control, quoted.
- If your firm holds its own certificate, it lives on your firm's own page with a statement of what it covers, never in the same visual group as SourceX's name.

**Method note.** The sheet was built on 28 October 2026 from SourceX's trust center, section 4.5 of the unsigned sample Channel Partner Agreement (version 2026-10-19), the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the FTC's advertising substantiation policy and 16 CFR 255.1. It tests whether a published element matches its owner's published words; it does not test whether any control works, and no data on how readers interpret security badges in partner content has been published.

## One banner audited line by line (Illustrative)

Illustrative: the firm, its agency and its certificate are invented, and nothing here describes a real page.

A 60-person IT consultancy asks its agency for a "Data partnerships" section. The draft contains five security elements. The compliance lead runs each through the sheet:

| Element in the draft | Whose security | What the source says | Verdict |
|---|---|---|---|
| Headline: "Certified-secure AI data partnerships" | Blends the firm and SourceX | No certificate issued to SourceX; the firm's own certificate covers its own systems | Remove |
| A shield labeled with an audit standard, beside SourceX's name | SourceX | Trust center: in progress, report not yet issued | Remove |
| "Our certified team handles your data end to end" | The firm | In a referral the firm handles no company records at all | Remove: false in scope, whatever the certificate covers |
| "Your data stays anonymous" | SourceX | "No method is perfect" on re-identification | Rewrite with the quoted sentence |
| An "Official SourceX partner" badge | SourceX's name and mark | Sample section 4.5: no trademark license; public identification needs written authorization | Remove until SourceX authorizes it in writing |

The approved section, after the review:

> We can introduce clients to SourceX, which licenses business records from companies for AI training. We never handle a client's records in that process. SourceX's trust center lists the security controls it has in place today and, as of 28 October 2026, shows a SOC 2 Type II report and two ISO/IEC certifications as in progress, none issued. If an introduction leads to a qualifying deal, SourceX may pay us a referral reward, which does not come out of what the client is paid.

The last sentence rests on section 4 of the terms: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Whether even the plain first sentence counts as publicly identifying SourceX as a partner under the firm's signed agreement is a question the firm settles with SourceX in writing before the section goes live.

## Before it goes live, and after it already has

**Before.** Give the agency the review sheet with the brief; agency copy is still the firm's publication. Date and link every SourceX status line. Place any disclosure of the firm's possible reward where a reader meets the claim, in wording your counsel approves. Set a re-check interval for pages that stay live, because statuses move.

**After.** If a page already claimed certification for SourceX, correct it where it appeared and as visibly as the original: the page itself, its social preview, any PDF version, partner directories that copied it and pinned posts. Keep a dated note of what changed and why. [Correcting an overenthusiastic message before it spreads](/guides/how-to-correct-an-overenthusiastic-message-before-it-spreads) covers channel-by-channel placement, and firms with many partners can sample what is already published with the [partner network claims audit](/guides/how-to-audit-the-claims-used-across-a-large-partner-network).

When a reader writes back with a real security question, do not answer it from your page. [Handing off security questions without interpreting the answers](/guides/how-to-hand-off-security-questions-without-interpreting-the-answers) routes it to the party who will sign the reply, and [security questions that arrive before an introduction](/guides/when-security-questions-arrive-before-the-introduction) sorts what SourceX publishes from what it shares after review. Promises about anything beyond security are the subject of [the referral promise a partner must never make on SourceX's behalf](/guides/the-referral-promise-a-partner-must-never-make-on-sourcex-s-behalf).

## What the review sheet cannot do

- **Test controls.** It checks words against published words. Whether SourceX's controls or your firm's work as described is outside its reach.
- **Keep up on its own.** The sheet is only as current as its last re-check date.
- **Make wording lawful.** Matching a source does not settle what advertising, endorsement or disclosure rules require of your firm. That is for your counsel.
- **Settle permission.** Only SourceX's written authorization does, under the agreement your firm signed.

More guides for partner teams sit in the [guides hub](/guides).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

With every security line traced to its owner's sentence and dated, your firm can [register as a partner](/register), point clients to [SourceX's published screening criteria](/who-qualifies) rather than describing them from memory, and keep the [program terms](/terms) open beside the review sheet when it approves anything that mentions the program.

## Sources

- https://sourcex.si/trust
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/terms
- https://www.ftc.gov/legal-library/browse/ftc-policy-statement-regarding-advertising-substantiation
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.1
