Skip to content

The record, in detail.

What CX3 captures, how it seals, what the seal proves and what it does not. Written for the person who has to sign off the vendor.

Download a sample minute (PDF)

This is a real sealed record from our demo firm. Its chain position and SHA-256 hash are printed at the foot. The people and firm are fictional.

Attendance note - SRA Code of Conduct, MLR 2017

Who was met
Priya Nair, Harlow Freight Ltd
Who met them
James Okafor, Partner, Corporate
Where
Fenwick & Holt, London
When
3 September 2026, 15:20 BST
Who approached whom
Harlow Freight Ltd approached Fenwick & Holt
Identified by
Card tap

What was discussed

Freight and logistics dispute - contested demurrage claim, counterparty in Rotterdam. She approached us. Sending the charterparty and the correspondence over. Scoping an early view. No advice given.

Consent wording shown

Chain position
1,284
Previous hash
e41fbbb510…bbb0af6384
This record
5a08f0c7b2…9f7571ea66
Sealed
10 September 2026
Sealed - verifies

From tap to contact.

TriggerNFC tap, or QR code where a phone won’t tap.
Visitor softwareNone; the profile opens in the browser.
LeaversCard reassigned from the dashboard with immediate effect.
FinishesPVC; brushed stainless steel; black brushed stainless steel.

From the box to the pocket.

Wallet passApple Wallet and Google Wallet. The QR code encodes the profile URL. The pass updates when the profile changes.
vCardOn every profile, and in every card email.
ClaimingOn the first tap: to the work email on file, or any address at one of the firm’s verified domains. A link by email, then one confirmation.
Card lifecycleRequested, ordered, shipped, unclaimed, active. A leaver’s card returns to unclaimed and locked.
RegistrationsFCA, SRA, Companies House, ICO, VAT, ISO 27001, Cyber Essentials and professional memberships. Each is verified by CX3 before it is shown, and links to its register where there is a public one.

By reply.

MethodReply to an email.
ContentsWhat was discussed; who approached whom; where.
ReminderDay 6 if no write-up.
DigestEvery Friday, for conversations with no card tap.

Hashed and chained.

Timing7 days after the conversation.
HashSHA-256.
ChainingEach record’s hash incorporates the hash of the record before it.
Sealed fields21, including the consent wording shown and whether the visitor identified themselves by tap.
IdentificationRecorded either as the visitor identifying themselves by tap, or as asserted by the colleague.
ModelAppend-only. Each record prints as a standalone minute carrying its chain position and hash.

Detection, not prevention.

ProvesThat a record has not changed since it sealed, and its position in the sequence.
Does not proveThat the write-up is accurate; it is the colleague’s account.
Does not preventAlteration by someone with direct database access; it makes that alteration detectable, because the record and every later record stop verifying.[1]

Your schedule, enforced.

RetentionSet per firm, separately for contacts and meeting records.
EnforcementNightly.
ErasureReaches every copy, including meeting records.
Chain integrityOne person’s erasure does not break verification for other records.

Signed, with retries.

MethodSigned outbound webhook.
SystemsHubSpot, Salesforce, Microsoft Dynamics, Clio, through Zapier or Make.[5]
EventsThe contact as soon as it is captured; the write-up when your colleague replies, marked as unsealed; the sealed record on day seven.
PayloadContact, write-up, consent wording, seal hash.
FailureDurable retry queue.

Who can see what.

DashboardPeople, cards, leads, meetings, conflicts, audit log, settings.
Two-factorRequired for every admin, after a 14-day grace period from their first sign-in. Always required for CX3 staff.
Audit logEvery change to a profile, setting or card, and every admin action: who, what and when. Kept separately from the chain.
Corrections and voidsA correction is an addendum linked to the sealed record and sealed in turn. A record can be voided with a reason before it seals, never after.
Export fieldsEvery sealed field, the chain position, the previous hash and the record’s own: enough to recompute each hash.
Conflicts searchBy name, email or company domain, across all captured contacts.
ProfilesFCA (SYSC 10A.1.16R, retained under SYSC 10A.1.14R); legal (SRA Code of Conduct, MLR 2017); general (no citation, by design).
13Conversations (30d)
92%With a note12 of 13
85%Who started it recorded11 of 13
85%Sealed11 of 13

Export evidence

WhenWho they metWho hereRecord
19 SepPriya NairHarlow Freight LtdTapped a cardJames OkaforOpenSealed #1,2851 missing
17 SepTom AshworthHarlow Freight LtdLogged by rep - not verifiedRuth CastellanSealed #12
13 SepNadia HaddadHaddad RetailTapped a cardAma BoatengSealed #11
04 SepGrace KimKim AdvisoryTapped a cardPriya OseiSealed #9
31 AugOliver MarshMarsh PartnersTapped a cardJames OkaforSealed #7

We make the record. You make the judgement.

CX3 does not make a firm compliant, and no software can. We build records designed to hold up as evidence: dated, attributed, sealed and chained. Whether those records satisfy your firm’s obligations is your firm’s judgement, not our claim. CX3 Digital Ltd is registered with the ICO. It is not regulated by the FCA or the SRA.

See it on your own cards.

Half an hour. Bring your head of BD and your compliance lead to the same call if you can. It is the same product for both.

Your role

By submitting, you agree that CX3 may use these details to contact you about a demo and about the product. We don't share them with anyone else, we won't add you to a marketing list, and we delete them after 24 months. You can ask us to delete them sooner at any time by replying to our first email.

The wording above is stored with your request, word for word. It is what our product does for your contacts. Privacy