Financial AI must be permissioned, logged, and bounded
FDE.HK emphasises secure deployment methods, data permission design, auditability, NDA workflow, and clear compliance-support boundaries. It does not claim to replace regulated professional judgement.
Security design before production deployment
These controls are part of the implementation scope and should be adapted to each client’s internal policy.
Role-based access for users, departments, AI employees, and knowledge bases.
Non-sensitive samples first; sensitive materials after NDA and access scoping.
Separate indexes, access policies, and retrieval boundaries for different business units.
Record usage events and review paths for operational visibility.
Policy templates for allowed use, prohibited data, review flow, and escalation.
FDE.HK provides AI deployment and workflow enablement. It does not replace licensed professionals, lawyers, compliance officers, or internal accountable owners.
Compliance support does not replace licensed judgement
FDE.HK provides AI deployment and workflow enablement. It does not replace licensed professionals, lawyers, compliance officers, or internal accountable owners.
No licence claim
FDE.HK does not claim to hold financial licences unless separately verified and published with evidence.
No replacement of counsel
AI outputs must be reviewed by authorised internal and professional reviewers.
No sensitive upload by default
Initial forms request business context only; sensitive documents wait for NDA and access design.
Audit-ready workflow
Usage records, source references, and escalation paths are considered during deployment.
Security questions
A concise FAQ for procurement, compliance, and technology teams.
Can FDE.HK sign an NDA?
Yes. The request flow supports an NDA preference, and sensitive data should wait until NDA and access rules are confirmed.
Can AI outputs be used directly for regulated decisions?
No. AI output is supporting material and requires review by the client’s authorised professionals.
How are permissions handled?
Permissions are scoped by department, role, knowledge base, AI employee, and task.
Start with a secure diagnosis
Clarify data boundaries and risk controls before choosing tools or building workflows.