Trust Centre
What exists in this build. What comes when a firm goes live.
How VeriFount talks about security, privacy, and production-readiness — AI agent prepared, human verified. The agent prepares the draft; a named human verifies. The agent never verifies, certifies, or files. This page does not pretend the product is already certified.
VeriFount is not SOC 2 certified, not ISO 27001 certified, not GDPR- or PDPA-audited, and not a licensed financial institution. This page describes how the product is shaped so those programmes can be met. It is not an attestation and not legal advice. This page is a product description, not legal advice, not an attestation, and not a certificate.
- GDPR · Designed toward
- Singapore PDPA · Designed toward
- SOC 2 Type II · In programme
- ISO 27001 · When required
Controls, as they stand
Each tile states what the demo walks today, and what production still has to earn. GDPR, Singapore PDPA, and SOC 2 CC families sit on the feature — not as fake control IDs on a badge.
01
In the demo todaySecurity
- In this demo
- Four seats on the desk, an append-only session log, and secrets kept out of git. No WAF, no pen test, and no real login in this prototype.
- Production when required
- IdP SSO, independent penetration test before live files, and the technical measures named in the DPA.
GDPR Art. 32 · SOC 2 CC6 · PDPA
Control mapping02
In the demo todayPrivacy
- In this demo
- For a compliance desk processing client KYC and source-of-wealth files, the modelled lawful bases are performance of a contract with the firm and the firm’s legitimate interests in meeting AML / CDD duties. That is a design assumption for this desk — not legal advice, not a determination for any firm, and not consent-washing. Each firm still records its own basis with counsel.
- Production when required
- A privacy notice and processor terms in the signed DPA. A DPIA for KYC / SoW processing when the firm requires it.
GDPR Art. 6 · PDPA notice · SOC 2 privacy
Lawful basis note03
Prototype · sampleData residency
- In this demo
- Sovereign or local data residency. The firm chooses the region. Client files stay in-country or in-region. The model does not train on client files. Settings walks a firm-chosen picker. Hosting can be deployed in-region. This prototype keeps state in the browser — no database, no outbound API.
- Production when required
- Hosting in the region the firm chooses. No silent cross-border send. Transfer assessments live in the DPA, not as a cloud-vendor headline.
GDPR Art. 44 · PDPA transfer · SOC 2 confidentiality
Residency picker04
Production when requiredEncryption
- In this demo
- Production deploys are expected to serve the app over TLS (encryption in transit). This local prototype may run on http://localhost. Encryption at rest, key management, and a secret manager are on the production path — they are not implemented in this tree.
- Production when required
- TLS in transit, encryption at rest, and a secret manager. Keys never in git.
GDPR Art. 32 · SOC 2 CC6 · ISO 27001 overlap
Processor terms05
In the demo todayAccess control
- In this demo
- Analyst drafts. Head of Compliance reviews the memo. Managing Director records senior-management relationship approval where required. MLRO receives escalations. The agent cannot approve a memo or dismiss a flag. The header role switcher impersonates those seats — it is not a login.
- Production when required
- IdP SSO (SAML / OIDC) maps firm groups onto the same four seats. MFA at the identity provider. Least privilege.
SOC 2 CC6 · GDPR Art. 32 · PDPA
Roles on the desk06
In the demo todayAudit logging
- In this demo
- Every material act stamps actor, action, model version, inputs, and evidence used, in Singapore time. The trail is append-only for this session. Shaped around SOC 2 access and logging (CC6 / CC7) — this log is not a Type II report.
- Production when required
- A durable, exportable log a later examiner can follow. Operating effectiveness over a period is the Type II work — that work has not started.
SOC 2 CC7 · GDPR Art. 32 · ISO 27001 logging
Open the audit trail07
Production when requiredSubprocessors
- In this demo
- Categories only: hosting, and logging / observability. This prototype has neither — state stays in the browser. Named vendors belong in a signed DPA, not as invented names on a marketing page.
- Production when required
- The DPA names processors. Changes follow whatever notice that DPA requires.
Hosting
Run the app and store client files in the region the firm chooses.
This prototype: None. Session state in the browser.
Logging / observability
Operational logs and the append-only audit trail in production.
This prototype: In-session audit array. No log vendor.
GDPR Art. 28 · PDPA · SOC 2
Categories08
Production when requiredData Processing Addendum
- In this demo
- A data processing agreement (DPA) is available on request when a firm is in diligence. This prototype is not a DPA.
- Production when required
- Signed processor terms before live client files. GDPR Art. 28 and PDPA processor obligations live there, not in this clickable desk.
GDPR Art. 28 · PDPA processor
Request in diligence09
Production when requiredCertifications path
- In this demo
- SOC 2 Type II and ISO 27001 are in programme / when required. VeriFount is not certified today. Badges and certificate numbers will appear only after an examination or an audit — not before.
- Production when required
- SOC 2 Type II over an operating period. ISO 27001 if a firm’s procurement requires it. Reports are shared then — never invented here.
SOC 2 Type II · ISO 27001
Programmes10
Production when requiredIncident response
- In this demo
- No live incident process. This prototype holds no customer files. There is nothing here to notify a regulator about.
- Production when required
- A documented playbook. Notice within 72 hours where GDPR — or the firm’s PDPA policy — requires it.
GDPR Arts. 33–34 · SOC 2 CC7 · PDPA
Control mapping11
Prototype · sampleData subject rights
- In this demo
- Settings walks a practice export pack and erase on a synthetic practice file. Names are fictional. No NRIC or passport numbers are stored. Erase is session-only; refresh restores seeds.
- Production when required
- The firm remains controller. VeriFount assists access, correction, and erasure on live files under the DPA. Certified deletion if that DPA requires it.
GDPR Arts. 15–17 · PDPA access / correction · SOC 2 privacy
Open the practice DSR12
Production when requiredUptime / status
- In this demo
- No public status page and no invented availability percentage on this site.
- Production when required
- Hosting availability is a DPA topic. A status page only if the firm requires one. No invented percentage on this site.
SOC 2 availability
13
In the demo todayModel policy
- In this demo
- The model does not train on customer files. Client packs are inputs to a draft, not training data.
- Production when required
- The same rule in the DPA. Client packs are inputs to a draft. They are not training data.
SOC 2 confidentiality · GDPR Art. 5 · PDPA purpose
Model toggle (fixed)14
In the demo todayHuman-in-the-loop
- In this demo
- A person still decides. VeriFount never assigns the final ML/TF risk rating, never files a suspicious transaction report (STR) with STRO, never onboards a client, and never contacts the client or the relationship manager. It may flag a file for the MLRO / CO; filing stays human and outside the AI. AI agent prepared, human verified. The agent prepares the draft; a named human verifies. Drafts only.
- Production when required
- The same hard limits. Human verification remains a named reviewer's act. The agent still does not verify, onboard, file an STR, or contact a client.
SOC 2 CC6 · AML hard limits
Programmes this build is shaped around
Designed so GDPR, Singapore PDPA, and SOC 2 can be met as part of the build. Certificates, audits, and licences come later. ISO 27001-aligned controls and MAS TRM appear where they overlap — access, logging, residency. None of that is a certificate, an audit report, or a licence.
01
GDPR
Designed toward
Articles that this codebase already sketches: Art. 6 (lawful basis modelled as contract / legitimate interest for a KYC desk), Arts. 15–17 (access, rectification, erasure — practice DSR on a synthetic file), Art. 28 (processor terms — DPA on request), Art. 32 (security of processing — access, logging, TLS-in-transit note), Art. 44 (transfers — residency picker, no silent cross-border send).
02
Singapore PDPA
Designed toward
Consent / notification (the firm is the controller of its client files; VeriFount is modelled as a processor), access and correction, retention, and transfer. The practice DSR pack is the access/erase walk. Retention is a settings control. Residency is firm-chosen, in-country or in-region.
03
SOC 2 (Type II path)
Type II path — not certified
Trust Services Criteria this prototype is shaped around: security, availability, confidentiality, and privacy. Access (CC6 family) and logging (CC7 family) are walked in the demo as roles plus an SGT-stamped audit trail. There are no fake control IDs on the marketing hero. A Type II report would cover operating effectiveness over a period — that work has not started.
04
ISO 27001-aligned controls
Aligned controls — not certified
Where ISO 27001 overlaps this desk: access control, operations logging, and information-transfer / residency. The mapping is in docs/compliance.md. VeriFount is not ISO 27001 certified.
05
MAS TRM (overlap only)
Overlap — not a licence
Monetary Authority of Singapore Technology Risk Management guidelines, where they overlap this product: access, logging, and data residency / localisation. VeriFount is not a MAS-licensed institution and does not claim TRM attestation.
Control mapping
Regime → feature in this codebase. Engineering table: demo settings and docs/compliance.md.
| Regime | Ref | In this tree | Status |
|---|---|---|---|
| GDPR | Art. 6 | Trust page models contract / legitimate interest for a compliance desk processing client KYC. Not legal advice. | In the demo today |
| GDPR | Arts. 15–17 | Settings → practice data-subject request: export pack / erase on a synthetic practice file. | Prototype · sample |
| GDPR | Art. 28 | DPA on request. This prototype is not a DPA. | Production when required |
| GDPR | Art. 32 | RBAC seats, append-only audit log, TLS-in-transit note, secrets not in git. | In the demo today |
| GDPR | Art. 44 | Sovereign / local residency picker. No silent cross-border send. No live backend. | Prototype · sample |
| PDPA | Consent / notification | Firm is modelled as controller of client KYC; VeriFount as processor. Trust page + DPA-on-request path. | In the demo today |
| PDPA | Access | DSR export pack on a synthetic file (no NRIC / passport numbers). | Prototype · sample |
| PDPA | Correction | Analyst edits stay on the practice file; production would bind correction to the same audit trail. | In the demo today |
| PDPA | Retention | Settings retention picker (5 / 7 / 10 years), floor five years to match MAS Notice 626 para. 12.3 / SFA04-N02 para. 11.3. Same span as /audit. Session-only in this demo. | Prototype · sample |
| PDPA | Transfer | Residency picker — in-country or in-region, firm-chosen. Not a cloud-vendor headline. | Prototype · sample |
| SOC 2 | Security (CC series) | Four seats (analyst, Head of Compliance, Managing Director / senior-management approver, MLRO). Agent cannot approve a memo. Demo role switcher is not a login. | In the demo today |
| SOC 2 | CC6 family | RBAC on the desk. Production path: IdP SSO mapping groups to these seats. Audit page copy ties the log to CC6 without fake IDs on the marketing hero. | In the demo today |
| SOC 2 | CC7 family | /audit — SGT-stamped actor, model version, inputs, evidence used. Append-only in the session. | In the demo today |
| SOC 2 | Availability | Not implemented. Production path: hosting SLA in the DPA, not a prototype toggle. | Production when required |
| SOC 2 | Confidentiality | No training on customer files. Practice data only in this tree. Encryption at rest is a production-path item. | In the demo today |
| SOC 2 | Privacy | Practice DSR export / erase. DPIA and incident 72h notice are production-path. | Prototype · sample |
| ISO 27001 / MAS TRM overlap | Access | Role-based seats on the KYC desk. Header impersonation is labelled prototype. | In the demo today |
| ISO 27001 / MAS TRM overlap | Logging | Immutable-in-session SGT timeline with actor, model, inputs, evidence. | In the demo today |
| ISO 27001 / MAS TRM overlap | Residency | Sovereign or local residency picker. Hosting can be deployed in-region. Not a cloud-vendor headline. | Prototype · sample |
Documents and walks
Nothing here is a downloadable certificate. A DPA is a request in diligence. The practice DSR and the audit trail are walks on practice data.
- Request
Data Processing Addendum
On request in diligence · this prototype is not a DPA
- Read
Programme mapping
GDPR, Singapore PDPA, SOC 2 Type II path, ISO 27001-aligned, MAS TRM overlap
- Walk the practice file
Data subject request (practice)
Synthetic practice file · no NRIC or passport numbers
- Open
Audit trail
SGT-stamped actor, model, inputs, evidence · session-only
Trust Centre
Walk the desk, or request a DPA.
GDPR, PDPA, and SOC 2 rows sit on this page. Demo settings walk residency, retention, RBAC, and a sample data-subject request. VeriFount drafts; a named human verifies. The agent never verifies.