
Data Protection and Privacy Engineering
Collecting less, holding it properly, and being able to answer what you hold about a person.
Collecting less, holding it properly, and being able to answer what you hold about a person.
How this is bought: Bought as an assessment first, then a project priced from what the assessment finds. Build an estimate for your case.
Sorting information into levels - public, internal, confidential, regulated - so protection matches sensitivity.
Collecting only what the purpose requires and deleting it on a written schedule.
TLS 1.2 or above on the wire; AES-256 or equivalent on disk, with keys held separately.
Replacing identifying values with tokens so working copies carry less risk.
Watching for regulated data leaving by email, upload or removable media.
Privacy decided when the system is designed, with the protective setting as the starting point.
A written assessment before high-risk processing, recording risks and mitigations.
A working process for access, correction, deletion and portability requests within the legal window.
Evidence of why each category of data may be processed, and what the person agreed to.
Contractual and technical measures when data moves between jurisdictions.
We follow the structure and controls these standards describe. We do not claim to be certified against them - where you need a formal certificate, we prepare the evidence and an accredited body performs the audit.
These are the areas clients most often ask us to improve. Your project sets its own targets, measured and agreed with you.