ReadyComply
Menu

Frameworks · GDPR

Accountability you can point at. Not a privacy badge.

GDPR is a regulation. Supervisory authorities enforce it. ReadyComply instantiates the articles a SaaS team actually has to operate: purposes, rights, processors, security, breaches, transfers. It does not issue an adequacy decision.

ReadyComply controls table with Trust Services Criteria codes, owners, and status pills

What GDPR is

Article 5 is the test. The rest is how you prove it.

Lawful, fair, transparent, purpose-limited, minimized, accurate, storage-limited, secure, and accountable. If you cannot show the purpose for a field, you should not keep the field. The register is where that argument lives.

ReadyComply overview: control status, evidence count, and open tasks for Authio LLC

In the workspace

Starter families we instantiate.

Principles and lawfulness

Purposes and a real lawful basis. Consent is not the default for a control plane.

Transparency and rights

A versioned notice, and a path to access, erasure, portability, and the rest.

Records and processors

A dated RoPA and DPAs with anyone who processes for you.

Security, breach, transfers

Article 32 should agree with your SOC 2 and ISO technical story. Transfers need a mechanism, not a hope.

The cycle

What ReadyComply holds for GDPR readiness.

  1. 01

    Name the purposes.

    Each processing purpose on the system, with a basis.

  2. 02

    Publish a current notice.

    Version it in policies. File the live URL.

  3. 03

    Stand up rights handling.

    Who authenticates the requester, who fulfils, how long.

  4. 04

    List processors and transfers.

    Contracts and SCCs in evidence, dated.

  5. 05

    Do not wait for a DPA from us.

    ReadyComply is not your supervisory authority and does not certify you.

Write the purposes before you add another processor.

Sign in. GDPR families instantiate with the system. Fill the RoPA in.

Sign in