SentraMind

Understanding

The questions we expect sovereign buyers in this region to raise

We expect residency, custody, and who operates the model to come before feature lists for buyers in Singapore, Malaysia, Indonesia, Vietnam, and Thailand.

We expect residency and custody to come before the feature list

We expect buyers in Singapore, Malaysia, Indonesia, Vietnam, and Thailand to start with where processing happens and who can open a stored record: which machines see prompt text, where the evidence keys live, and whether a public model is on the path at all. That is our expectation, not a report of buyer conversations. A feature list is easier to read after those answers have a place to sit.

The answers this POC can give are specific and bounded. The appliance is designed to run under the organisation’s control. Evidence at rest in the database is ciphertext, and the officer keys that can unwrap it are software keys in this phase. A conversation that skips the software-custody label has not answered the custody question.

Who operates the model is a separate question

A buyer who asks “where does the model run” is asking about two tiers that this design keeps apart. The verdict itself is a policy decision over a byte cap and a deterministic detector tier. A generative model is not on that path. An encoder, when one is configured, is a later tier, and in this POC that tier is a CPU stand-in whose quality on a real corpus has not been measured.

External model APIs exist in the product only as a development regime. A provider marked for that regime is refused when the deployment profile is production. Content that would be sent under the development regime is limited to synthetic fixtures, and the call goes through the model router. An air-gapped room adds a simpler fact on top: with no route out, the call has nowhere to go.

The five markets do not share one rule

Notification deadlines differ by statute and by the population the statute covers. Under Singapore’s Personal Data Protection Act, an organisation has about thirty days, by the Personal Data Protection Commission’s benchmark, to assess a personal-data breach and, if the breach is notifiable, three calendar days to notify the Commission. Malaysia’s Cyber Security Act 2024 (Act 854) requires an initial report to the National Cyber Security Agency within six hours for incidents on national critical information infrastructure. Averaging those into a single regional number produces a figure that is wrong for at least one of the duties. We last confirmed both clocks on 27 August 2026.

Permissions differ in the same way. Some market-entry licences sit on the vendor before a sale. Vietnam’s cybersecurity product business licence and import permit are the clearest case: the Ministry of Public Security issues them, and since 19 August 2026 the licensing regime is set by Decree 332/2026, as we confirmed on 27 August 2026. Duties that arise because the organisation monitors its own systems sit on the organisation after deployment. Under Malaysia’s Personal Data Protection Act, as amended by Act A1727 and administered by the Personal Data Protection Commissioner, regular and systematic monitoring can trigger the mandatory appointment of a data protection officer. We checked that duty on 12 August 2026. The act does not bind federal or state government, so a Malaysian government buyer looks to Act 854 and government directives instead. The jurisdiction pages exist so a reader can see which is which, with counsel, rather than inherit a blended rule from a regional paragraph.

The jurisdiction pages are orientation

Each instrument on those pages carries the date it was checked. The pages record what we found, including items marked for a recheck. A watch-list item says the instrument needs another look, not that it is in force, and Thailand’s draft 24-hour infrastructure clock is the example to keep in mind.

Counsel is who turns a recorded finding into advice for a particular organisation. The portal can show the finding, the population it covers, and the date its instrument was checked. The written view that someone will rely on belongs in counsel’s note. An evaluation pack that substitutes the page for that note has mixed up the two documents.

A design goal is not an approval

Local operation is a design goal of the product: the console is built without calling out for fonts or scripts, and the build can be shown to finish with no route out. Runtime egress of a running appliance has not been verified, and the private-AI surface says so. That pair of sentences is the honest form of the residency answer.

No ministry, regulator, or sector body is claimed to have approved a deployment. The POC also signs users in with local passwords rather than a directory, and it identifies machines with a software CA. Buyers who need those stronger anchors can read the labels and decide whether the evaluation is still worth running. The labels are the answer to that question.

How to read this

How to read this
Read it asWhich meansDo not read it as
Questions we expect first Where the model runs, who unwraps evidence, which clock The feature list
Jurisdiction pages Orientation; each instrument carries the date it was checked Legal advice
Five markets Different clocks and licences One averaged requirement

Product statements on this page follow the POC maturity ladder. A coming-next or roadmap item is not available for the current evaluation.