Trusted by Design: Who is getting access to your data?
Organisations, government agencies, solution providers and everyone in between connect to DEX on the same neutral infrastructure. That’s the architecture built to answer who owns the infrastructure, whether the data can be trusted, and who controls who it’s shared with.
Key Takeaways
- DEX is a shared data exchange infrastructure, a national digital utility owned by the government through IMDA, not by any one sector, platform or commercial partner.
- Every participant’s data is checked against a shared schema, DEX’s common language, and against the specific rules of whoever it’s going to, so only validated quality data gets relied on downstream.
- Every participant controls who their data goes to: access only happens within a relationship they’ve approved.
- While owning and operating the infrastructure, DEX has no visibility into any participant’s data without the participant’s permission.
- Real customers, including Penta Ocean Construction and Teambuild Construction, report measurable gains in trust, speed and accuracy since connecting.
- Together, that’s what trusted means on DEX: a network that belongs to no single sector or participant, data that’s standardised and validated before anyone relies on it, and consent that stays with whoever shared it.
- Being a trusted data highway is one part of a shared foundation, alongside being seamless and secure, that runs across every sectoral data exchange powered by DEX, from SGTradex to SGBuildex to SGFarmdex.
DEX works differently because of how it’s structured. Ask most organisations why they’re slow to join a shared data platform, and a few hesitations come up on repeat. Can data arriving from other parties be relied on, or does it need a second check before anyone uses it? Once something is shared, who does it still belong to, who can see it, and does it stay inside the relationship it was meant for?
For a national data exchange utility connecting government agencies, large enterprises and small businesses across trade, logistics and maritime, the built environment and agri-food, those questions need answers built into the infrastructure.
One Standardised Infrastructure
DEX isn’t owned by any sector, platform or commercial partner, or any one participant within a sector. It’s shared data exchange infrastructure, a national digital utility built for everyone who connects to it, which is what makes the network neutral in the first place.
Being government-backed doesn’t mean government-accessed. The data belongs to the participant, and the participant chooses which other participant can transact with it and access it, enforced by checking every submission against a standardised schema and moving it only within a verified, consented relationship. That’s what trusted means at the ownership level, before it ever gets to day-to-day operations.
Ms Veronica Ng, Executive General Manager and Deputy Head of Civil Engineering Division at Penta Ocean Construction, has seen this first-hand on her own projects. “A neutral gateway helps establish a single source of truth,” she says. “It is not intended to eliminate all disagreements, but it can help create the conditions for earlier alignment.” The time saved shows up directly in her teams’ day: “Saving one to two hours a day, time previously lost to extracting and re-uploading data across platforms, is meaningful.”
Mr Benjamin Lee, Project Director at Teambuild Construction, makes the same point from the construction side: “SGBuildex, as a neutral data exchange platform, solves this because it provides the common language and the common highway.” As he put it, “it does not replace anyone’s system, it connects them.”
Data You Don’t Have to Double-Check
Every submission that moves through DEX gets checked against a shared schema, DEX’s common language for that sector, defined together with the agencies and stakeholders it serves. The schema sets out exactly what’s required: which fields are mandatory and what format each one must be in, so anything that doesn’t conform is rejected before it reaches anyone downstream.
DEXConnect is one way this happens: a supplier can email a test report as a PDF exactly as they always have, and DEXConnect converts it into structured data, then checks it against the agreed schema before it’s finalised.
On SGBuildex, for instance, DEXWeaver is another feature that handles it on the way out: once a contractor submits through the portal or an API, DEXWeaver reshapes that data into exactly what each receiving agency requires and validates it against that agency’s own rules, so nothing arrives in a format the next party can’t use or has to double-check. That’s what makes it trusted data you can act on, not data you have to verify yourself first.
Your Data, Your Call
Every contributor on DEX decides who their data goes to. Sharing only happens within a verified, consented relationship, not by default, and not just because another party happens to also be connected to the network. That verification isn’t just a figure of speech: DEX checks a participant’s identity through the KYC (Know Your Customer) process before any relationship between a contributor and a consumer can be set up.
Regardless of how a contributor submits data: a contributor can only route data to an authority or consumer it has an active, consented relationship with, so being on DEX never means your data can be accessed by everyone else on DEX. Access is governed by the relationship you’ve approved, not simply by being connected to the platform. For a contributor managing submissions across several government agencies, that distinction matters: each relationship is separate, each one requires its own consent, and none of them grants access to any other. DEXWeaver makes this simple when a submission has more than one recipient, reshaping it into what each one needs.
In practice, that might mean a contractor connected to SGBuildex has an active, consented relationship with BCA for productivity reporting, but not yet with HDB. Until that second relationship is set up and approved, DEXWeaver simply won’t route data there, no matter how connected the contractor already is to the rest of the network.
Built to Last, Built to Grow
One standardised data exchange infrastructure, data you don’t have to double-check, and consent that stays with the person who gave it: that’s what trusted means in practice on DEX, not a line on a slide. It’s also why more of Singapore’s data infrastructure is choosing to run through DEX, not around it, across trade, logistics and maritime, the built environment and agri-food alike. DEX also works with ecosystem partners to keep data standards aligned with the latest industry requirements, building the foundation and facilitating exchange for everyone on it.
Trusted is one part of a shared foundation, alongside seamless and secure, that runs across every sectoral data exchange from SGTradex to SGBuildex to SGFarmdex. Many dexes, one trusted foundation: the same infrastructure, the same quality bar and the same consent model travel with every new participant, whichever sector they’re in.
Want to see what connecting to a network built this way actually looks like? Get in touch with the DEX team.
