MXTK Data ExchangeBuy dataSign in
Trust center

Trust is the product.

Operated by Mertin Industries Inc., Republic of Panama. Who you are dealing with. What data they own. What they may do with it. What was delivered.

Talk to the trust team
01Identity
02Provenance
03Permission
04Delivery
Identity

KYC / KYB

Before an organization can list or buy, the exchange needs to know who is behind it, who can sign, and whether the organization is permitted to transact.

  • 1Legal entity name, registration and jurisdiction.
  • 2Beneficial ownership and authorized signatory.
  • 3Sanctions, PEP and adverse-media screening through the NeoBank program.
  • 4Ongoing monitoring and re-verification.
Provenance

Know the data you own.

A seller must be able to show the source, the right to license, and the permission attached to the data. An attestation is recorded before upload; it is not a substitute for title.

  • 1Source and collection method.
  • 2Consent, contract or other legal basis.
  • 3De-identification method and date.
  • 4Licence restrictions, geography and term.
Permission

Know the counterparty.

Every buyer is verified as an organization, and every deal is tied to a stated permitted use. The data use agreement (DUA) turns that into a contract.

  • 1Buyer entity and authorized user.
  • 2Stated research or commercial purpose.
  • 3DUA accepted by a human, not an agent.
  • 4Licence term, territory, exclusivity and seller proceeds.
Evidence

Know what was delivered.

The buyer receives a quality report and a manifest commitment. The buyer recomputes the root and records a receipt before settlement.

  • 1Screening report and quality report.
  • 2Schema, shard and row commitments.
  • 3Manifest root verified by the buyer.
  • 4Receipt and audit trail.
Status

What is implemented today.

We separate controls that exist from controls on the roadmap. A trust page that claims everything is worse than one that shows the gap.

ControlStatusEvidence
Organization and signatory recordsimplementedOrganizations, memberships, audit events
Seller de-identification attestationimplementedAttestation text hash, actor, timestamp
Automated identifier screeningimplementedScreening report, quarantine on failure
Data use agreementimplementedTerms hash, human acceptance, signer
Manifest and receiptimplementedRoot comparison, delivery receipt
KYC/KYB and sanctionsreuseNeoBank screening program; exchange wiring pending
Independent sanctions vendornot separateWe reuse the NeoBank program rather than buy a second one
Independent security audit / SOC 2roadmapNot yet completed

Sanctions and PEP screening already run in the NeoBank. The exchange reuses that program rather than building a second vendor relationship; the connection between the exchange and the NeoBank screening service is an integration task, not a new control.

Security

Access control, private staging, audit logging, encryption in deployment and a disclosure path for vulnerabilities.

Security program

Marketplace standards

Seller listing requirements, buyer obligations, delivery evidence, disputes and enforcement.

Marketplace standards

Report a trust issue

If a listing appears to contain identifiable data, a counterparty misrepresents its authority, or a delivery does not match its manifest, stop the deal and contact the trust team.

Contact the trust team