@proseid v2025.01.01 EEA

GDPR Article 33 breach notification

A controller must notify the supervisory authority of a personal-data breach without undue delay and within 72 hours of becoming aware, unless the breach is unlikely to risk individuals' rights. The notification must state the nature, categories and rough number affected, likely consequences, and measures taken; a late filing must carry reasons for the delay.

Compatible with

FormGuided assessmentCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v2025.01.01
Applies in: European Economic Area
Recommended language: English
Fields: 20
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

gdpr_article_332018-05-25 → continues indefinitely

Current

Controlling sources

Legal references

Regulation (EU) 2016/679 (GDPR) Article 33

Source ↗

Schema fields

20 fields

Field

Type

Description

Req

Approx. number of personal-data records affected

Number

—

Opt

Supervisory authority notified

Boolean

—

Opt

Authority-notification date, time, and zone

String

—

Opt

Data protection officer or other contact point

String

—

Opt

Notified within 72 hours

Boolean

—

Opt

A personal-data breach under GDPR has been confirmed

Boolean

—

Req

Categories of affected data subjects

String

—

Opt

Available notification information is being supplied in phases

Boolean

—

Opt

Measures taken or proposed

String

—

Req

Approx. number of affected data subjects

Number

—

Opt

Nature of the breach

String

—

Req

Reasons for notification after 72 hours

String

—

Opt

Categories of personal-data records affected

String

—

Opt

Controller

String

—

Req

When you became aware of the breach

Date

—

Req

All information currently available was supplied without undue further delay

Boolean

—

Opt

Plan for supplying the missing notification information

String

—

Opt

Awareness time and time zone

String

—

Req

Risk to individuals' rights and freedoms

Select

Choices: Unlikely, Likely, High

Req

Likely consequences

String

—

Req

Example payload

JSON

{
  "responses": {
    "personal_data_records_affected": null,
    "authority_notified": false,
    "authority_notified_at": "",
    "dpo_or_contact_point": "",
    "notified_within_72h": false,
    "personal_data_breach_confirmed": false,
    "data_subject_categories": "",
    "notification_information_provided_in_phases": false,
    "measures_taken": "",
    "individuals_affected": null,
    "breach_nature": "",
    "delay_reasons": "",
    "personal_data_record_categories": "",
    "controller_name": "",
    "became_aware_at": "",
    "available_information_supplied_without_undue_delay": false,
    "phased_follow_up_plan": "",
    "became_aware_time_and_zone": "",
    "risk_to_individuals": "",
    "likely_consequences": ""
  },
  "effective_at": "2026-07-29"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL

curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json

200 OK

{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}

422 Invalid

{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "personal_data_records_affected",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}

A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions

Loading published versions…

Trust ledger

Crowd → credentialed

Provenance

Community publisher (unverified)

@proseid · latest v2025.01.01

Community signal

0 votes

No votes yet.

Attestations · by version

0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments

to join the discussion.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

Anmälan av allvarlig arbetsolycka eller allvarligt tillbud

FDA food-facility registration determination

EU right-of-withdrawal record

EU whistleblowing internal-report deadlines