Compliance · GDPR
GDPR: where personal data is, and what happened to it.
GDPR asks where personal data is, how it is protected and what happened to it. GuardStance supports these requirements with technical controls.
Book a demoWhich articles does GuardStance support?
| Requirement | What it asks | How GuardStance supports it |
|---|---|---|
| Art. 5(1)(f) | Keep personal data secure, including against unauthorized processing and accidental loss. | One policy enforces protection across endpoints, email, web, cloud, and AI: monitor, warn, record, or block. |
| Art. 15 | Give people access to the personal data held about them. | Discovery shows where personal data sits, so a request starts from an inventory. |
| Art. 25 | Build data protection into processing, by design and by default. | Labels set by content, and policies that apply the moment data moves. |
| Art. 30 | Keep records of processing activities. | A personal-data inventory your privacy team can use for its records. |
| Art. 32 | Apply security appropriate to the risk. | Discovery, classification, enforcement and signed evidence from one agent. |
| Art. 33 and 34 | Report a personal data breach to the authority and, where required, to the people affected. | Case timelines show what moved, when and where, to support the report. |
GuardStance supports these requirements with technical controls. This is not legal advice; confirm legal questions with your counsel.