Privacy is built through architectural decisions.
Local, connected or isolated
A local installation may have an internal network and internet connections. That is different from an air-gapped environment. If isolation is required, updates, support and file exchange must be planned accordingly.
Continuous remote telemetry and remote support are not assumed for an isolated installation. External connections made by each component need review.
Controls defined in the project
- Users, permissions and source separation.
- Networking, encryption and key management within scope.
- Retention of histories, indexes and backups.
- Authorised, documented support access.
- Validation before model or component updates.
Compliance and responsibilities
A local installation does not automatically confer GDPR compliance or ENS or ISO/IEC 27001 certification. Purposes, lawful basis, risks, rights and safeguards require assessment. Processing agreements and impact assessments must be addressed where applicable.
Return and sanitisation
The contract must identify media, copies, sanitisation methods and evidence. NIST SP 800-88 Rev. 2 is a reference; citing it does not establish a proprietary certification or prove that sanitisation has already been performed.