ReadyComply
Menu

Resources · GDPR checklist

Accountability, in order. Mapped to the workspace.

Checking a box here does not mean a supervisory authority agrees. It means the register has the record they will ask for.

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

Purposes

Before you collect another field.

  1. 01

    Each processing purpose is named.

    If you cannot name it, do not collect it.

  2. 02

    Each purpose has a lawful basis.

    Consent is not the default for a SaaS control plane.

  3. 03

    Privacy notice is versioned and live.

    File the URL as evidence against transparency.

Accountability

Inside ReadyComply.

  1. 01

    RoPA is dated.

    Article 30 is a living record, not a one-off spreadsheet.

  2. 02

    Rights path has an owner and an SLA.

    Access, erasure, portability, objection — who authenticates, who fulfils.

  3. 03

    Processors have DPAs.

    The list should match what you publish.

  4. 04

    Transfers have a mechanism.

    Adequacy, SCCs, or a real exception. File the signed SCCs.

  5. 05

    Article 32 agrees with SOC 2 and ISO.

    Do not keep three conflicting security stories.

Incidents

When it goes wrong.

  1. 01

    Breach tabletop has a date.

    Who decides on 72-hour notification. ReadyComply is not the authority.

  2. 02

    Processor breach terms are in the DPA, not assumed.

    How fast a processor tells you matters more than how fast you tell the authority, since your clock starts on their notice.

  3. 03

    The data-subject notification threshold is written down in advance.

    “High risk” is a judgment call. Make it before an incident, not during one.

Workspace

Controls · Evidence · Policies

Open the workspace. Keep the register current.

Sign in. Create the first system. Start with what you can already prove.

Sign in