How to discuss archive access without making security promises: an eleven-sentence verification checklist that sends each claim to the system's custodian, the client's CEO or SourceX's own trust center

Short answer

Say only what you have checked yourself, and route every other claim to the party that owns it. As the IT partner you can state facts about the archive you run: which system, which years, when access ends. The client's CEO decides scope and whether to talk at all. Only SourceX's published trust center speaks for SourceX's controls, so quote it and link it instead of promising encryption, anonymity, certifications or where files will sit.

Visual briefFull-size diagram
Five tempting sentences on the left, each wired to the party that can verify it: access ends 31 March goes to the custodian, you choose the scope goes to the client's CEO, it's certified and it's anonymized are struck through and routed to SourceX's trust center, and I'll pull the export ends at a stop mark labeled not yours.
The sentences and routes come from the checklist on this page; SourceX's statements are as published on its trust center on 2026-10-27.

Archive conversations start in the middle of other work: a migration leaves the old system read-only, a vendor announces a sunset, a cost review cuts the archive tier. The client turns to the person who knows the system and asks the obvious question, "is it safe to do anything with this?" Reassurance feels helpful. It is also the moment a partner can make a promise nobody can keep.

When archive access becomes the topic

The events below put an archive on the table. Each comes with something you can verify yourself and someone else who decides.

EventWhat you can verify as custodianProof to point toWho decides what happens next
A migration leaves the old system read-onlyThe date range the old system holdsThe cutover planThe client's CEO
The archive vendor announces end of supportThe date in the noticeThe vendor's written noticeThe client's CEO
A license downgrade removes archive searchWhich features stop, per the vendor's documentsThe renewal quote and product termsThe client's CEO, often prompted by the CFO
A shorter retention rule is proposedWhich records the rule would deleteThe change requestThe client's CEO, with the records owner
An acquired company's archive is being folded inWhich entity's records these areThe integration planBefore closing the target's CEO; after closing the acquirer's CEO

Whoever owns the archive budget, usually an IT director, COO or controller, is a natural internal sponsor. The CEO authorizes any licensing discussion. A deadline is real urgency only when a dated document backs it; the archive deadline verification log shows how to check one, and the software rationalization guide covers cost reviews that switch archives off.

The access claim verification checklist

Eleven sentences a partner is tempted to say during an archive conversation. For each: who can verify it, what the published record actually supports, and what to say instead. SourceX's lines come from its trust center as read on 2026-10-27.

#Tempting sentenceWho can verify itWhat the record supportsSay this instead
1"Your archive is complete back to 2009."You, for the dates; nobody, for "complete," without a checkThe dates the system shows"The archive holds records dated from 2009; whether anything is missing would need checking."
2"Access ends on 31 March."The archive vendorA dated written notice, if one exists"The vendor's notice dated [date] says read access ends on 31 March."
3"SourceX holds the usual security certifications."SourceX's trust centerIt lists its certification work as in progress, with no report or certificate issued yet"SourceX's trust center shows where its certification work stands; here is the page."
4"Your data will be anonymized."SourceX's trust centerIt says SourceX de-identifies data through approved processing routes before use or sharing, that no method is perfect, and that the supplier agreement records that re-identification may still be possible"SourceX describes how it de-identifies data, and the limits, on its trust page."
5"Your files never leave your servers."SourceX, deal by dealIt says large datasets can stay in the supplier's own storage or ship on encrypted drives"Large datasets can stay in your storage or travel on encrypted drives; the route is agreed with SourceX."
6"You decide what goes in."SourceX's trust centerIt says the supplier decides which systems, records and date ranges are in scopeFine to say, with the link
7"Nothing moves until you sign."SourceX's trust centerIt says nothing is delivered until the supplier signs the Master agreement and the deal's Dataset Deal Confirmation and SourceX gives the go-aheadFine to say, with the link
8"I'll pull the export for you."Nobody: it is not yours to offerThe partner agreement gives a partner no authority to share a company's records or access extraction systems"I won't touch the archive for this; SourceX arranges any preparation with you directly."
9"Nobody else will ever see it."The agreement the company would signIt says SourceX authorizes its customers' access to deidentified datasets for each delivery and, at Closing, may use, sublicense and distribute the deidentified dataset as the agreement allows"Who receives what is set in the agreement you would sign; the trust center describes it."
10"If anything went wrong, you'd be covered."SourceXIt says affected access links can be revoked and affected suppliers notified, with the full incident process shared on request"Ask SourceX for its incident escalation process; it shares it on request."
11"SourceX will answer our security questionnaire."SourceXIt says questionnaire responses, a business continuity overview and a DPA where applicable are shared privately after review"SourceX shares procurement material after review; ask it directly."

Rows 6 and 7 are the only SourceX sentences safe to say in your own voice, and even those go out with the link. Rows 3, 4 and 9 cause the most trouble. Row 3 because a certification is easy to assume, and SourceX states plainly that none of the three it is working toward has been issued. Row 4 because "anonymized" sounds absolute, and neither SourceX nor NIST treats it that way: NIST's report on de-identifying personal information says the technique can reduce privacy risk and that de-identified data can sometimes be re-identified (paraphrase of its abstract). Row 9 because the honest answer depends on a contract the client has not seen yet. Certification questions get a fuller treatment in discussing audit status without overstating certifications, and security questions raised before anyone is introduced in when security questions arrive first.

Method. The eleven sentences are the claims that come up when a client asks an IT partner about archive security. Each was checked on 2026-10-27 against the page that can verify it: SourceX's trust center for SourceX's controls, the partner agreement for what a partner may do, and NIST's de-identification report for the general point about re-identification. The checklist reports what SourceX publishes; it does not test or rate those controls. The trust center lists dedicated data rooms, independent security assessments and direct connectors as planned, so never describe them as current.

Three voices in one archive conversation

An archive conversation needs three voices, and a partner who speaks in all three has overstepped.

VoiceSpeaks aboutWhere its authority comes fromNever speaks about
The custodian (you, if you run the system)What the system holds, its dates, its access deadlinesThe service agreement, and the client's agreement to share the factsSourceX's controls, or whether to license
The owner (the client's CEO)Whether to talk to SourceX, what is in scope, who acts for the companyOwning the company and its recordsSourceX's controls
SourceXIts own process, controls and termsIts published pages and, later, its signed agreements with the companyThe client's systems before the client describes them

The partner agreement backs the line between the first and third rows. A partner is not SourceX's agent and cannot commit it to prices, licenses, payouts or other obligations (7.1), and a promise about SourceX's security is exactly that kind of commitment. The same agreement gives a partner no authority to share a company's records or reach into extraction systems (4.2), and bars collecting or keeping dataset copies through the program without separate written authorization (4.4). For the client's side of an export, should the company go ahead, the live guide on MSP client data licensing security covers the questions to settle, and the encrypted drive versus cloud transfer comparison covers delivery routes.

A script for the archive meeting, and an introduction with no attachments

In the meeting, three sentences carry the whole position: "I can tell you what the archive holds and when access ends, because I run it. Whether any of it is licensed is your call, and SourceX publishes how it handles data on its own trust page; I won't speak for it. If you'd like a conversation, I'll introduce you and step out."

If the CEO says yes, the introduction email holds four things:

  1. Who you are: the company's IT partner for the archive system, with a note that you may receive a referral reward if the company goes ahead.
  2. What the CEO said: the records she wants to discuss, in her own words.
  3. The dated event, if one exists, and the document behind it.
  4. A link, not an attachment: SourceX's trust center, so the CEO reads SourceX's claims from SourceX.

Then step back. SourceX may deal with the company directly without affecting valid attribution, and it answers security questions itself; the trust center gives hello@sourcex.si as its security contact and says requests are answered within two business days. Before you introduce anyone, check the basics on who qualifies: 50 or more full-time employees at peak with contractors left out, records the company created itself, rights to license them and a CEO who agrees.

Walking back a promise you should not have made

If one of the tempting sentences already slipped out, correct it before the client relies on it.

  1. Write to the CEO the same day. Quote the trust center line that replaces what you said, and give the link.
  2. Tell SourceX in the introduction. One sentence on what was said, so SourceX can answer the point directly.
  3. Do not soften it with a new promise. "I'm sure it's fine" is the same mistake twice.

The list of privacy promises partners should never make covers the wider set beyond archives.

Before you quote anything

  • The trust center changes. Re-read it before each conversation and quote the date you read it. A line accurate in October may not be in March.
  • Planned is not done. Items the trust center lists as planned are not controls in place.
  • Your service agreement comes first. It may limit what you may say about a client's systems, and to whom.
  • Rights are not yours to judge. Whether the archive holds material that belongs to the company's clients, which SourceX's screening guidance treats as usually not a fit, is settled in SourceX's review.
  • The archive's own facts can be wrong. A system that shows records from 2009 may have gaps; say "dated from," not "complete."

What happens to custody and access when a company closes altogether is covered on the main site in who controls company data after a shutdown.

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.

When a client's archive is about to go dark and its CEO wants to talk, send the trust center link instead of reassurance and make a four-line introduction; register as a partner before you do, confirm the company against who qualifies and read the program terms. The managed service provider overview and the guides hub carry the rest of the partner playbook.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can I tell a client that SourceX is certified?

No. On 2026-10-27 SourceX's trust center listed its certification work as in progress, with no report or certificate issued yet. Send the client the trust center link and let it read the current status for itself.

The client wants me to describe how SourceX protects its data. What do I say?

Say that SourceX publishes its controls on its trust center, quote the line that answers the question, and give the link. Anything the page does not cover goes to SourceX's security contact, which the trust center says answers within two business days.

What can I say about the archive itself?

Facts you can see because you run it, with the client's agreement: the system, the date range it holds, and any dated notice about access ending. Say nothing about completeness you have not checked, and never open the archive to size an opportunity.

Sources

  1. sourcex.si/trust
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. csrc.nist.gov/pubs/ir/8053/final
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment