Lesson 04 · Data protection principles
Security starts with data and permissions
The account plan is one element. Assess the entire process: what you share, with whom, why and under which terms.
Training and processing
Check the particular product’s terms and workspace settings. Disabling training does not mean data are not processed, stored or shared through integrations.
Encryption and secrets
Encryption protects particular transfer and storage stages. Do not paste passwords or API keys into prompts. Check customer-managed key options in the current offer.
Access and recipients
Grant minimum permissions. Check users, shared links, integrations and access revocation when staff leave. SSO and SCIM serve different purposes; availability depends on product and plan.
Retention and activity records
Establish storage duration and who can delete data. Check logs and copies. Do not assume deleting a chat immediately removes every copy.
Location and transfers
EU data location alone does not ensure GDPR compliance. Assess remote access, subprocessors and transfers. Check which data categories a residency option covers.
Purpose, agreement and responsibility
Define purpose, processing basis, roles and required agreements. For personal data, consult the controller or privacy officer. Purchasing a plan does not replace this assessment.
Exercise: decide before uploading a file
Prepare a fictional complaint. Mark the information needed to identify its subject, remove the rest and name the person approving the process. Acceptance result: a minimal dataset and a list of access and storage requirements.
Sources to check for a particular rollout: OpenAI Enterprise Privacy · RODO / GDPR. Current features and terms need verification; this material helps prepare an assessment rather than determine organisational compliance.