01
Purpose limitation
Data is used only for the purpose defined in the engagement.
TRUST CENTER / DATA PROTECTION
Trust is built through concrete rules.
This page presents the operational principles used to frame an engagement. It does not claim to be a security certification.
02
Data minimisation
Only necessary data is requested and processed.
03
Secure transfer
The transfer channel is agreed before sensitive data is exchanged; email is not assumed to be the default channel.
04
Controlled access
Access is limited to the people, scope and tools required.
05
No silent reuse
No reuse for another client, marketing or model training without written authorization.
06
Processor terms
When Article 28 applies, roles, instructions, obligations and subprocessors are documented in writing.
07
Incident response
Incident handling, contacts and notification duties are defined for the engagement context.
08
Retention & deletion
Retention, return and deletion are framed around the engagement and applicable obligations.
Risk-appropriate safeguards
Depending on the data and engagement, safeguards may include encryption in transit, access control, environment separation, logging, backups and incident procedures. Applicable safeguards are documented before sensitive data is transferred.
Processing and DPA
When Pretoria BI processes personal data on behalf of a client, roles and instructions are documented in writing when required by the GDPR. CNIL guidance states that a written contract is mandatory when Article 28 applies.
Transfers and providers
External providers actually used — hosting, LLM, forms, storage or booking — must be listed before production and assessed against the data involved.
Before any sensitive transfer
Pretoria BI is designed to confirm four points with the client: purpose and data categories, transfer channel, authorized people, then retention and deletion rules. Applicable safeguards are confirmed before the exchange, not after it.