No certification claim
The site describes intended controls and does not invent achieved certifications.
Sensitive by default; controlled by design
Security and Governance
PDICON Intelligence security is designed around tenant isolation, role-based and document-level access, encryption, auditable human and model actions, explicit training consent and customer-defined deployment boundaries.
StatusArchitecture principles—not certification claims
Reviewed2026-08-20
Direct answer
PDICON Intelligence security is designed around tenant isolation, role-based and document-level access, encryption, auditable human and model actions, explicit training consent and customer-defined deployment boundaries.
Design boundary
What the system will not pretend to be.
No retrieval bypass
Vector and graph systems inherit the same access rules as source documents.
No universal training right
Customer data contribution requires a recorded policy and purpose.
01Identity and isolation
Organization membership does not imply universal access.
Every request resolves tenant, project, role and document permissions before data reaches retrieval or a model.
02Audit
Human and AI actions share one evidence trail.
Input artifacts, model version, execution policy, output, expert decision and eventual outcome remain traceable.
03Consent and residency
Customers define data use and location.
Training eligibility, retention, region and self-hosted execution follow explicit policy rather than implicit reuse.
Operating matrix
Evidence moves through explicit controls.
| Subject | Input | Intelligence operation | Human / policy control | Output |
|---|---|---|---|---|
| Owner/Admin | Organization policy | Manage identity and controls | Administrative scope | Governed tenancy |
| Engineer | Assigned technical artifacts | Review and approve | Project/document scope | Recorded decision |
| AI operator | Approved dataset and model metadata | Train and deploy | Purpose-limited role | Controlled runtime |
Questions answered
Precise answers for technical evaluation.
Does customer data automatically train shared models?
No. Training contribution is controlled by explicit customer choice and policy.
Can an engineer access every project?
No. Access is scoped by tenant, role, assigned project and document permission.