{
  "abstract": "Article 33 gives 72 hours to notify regulators after awareness; set internal escalation within 24 hours of detection to leave 48 hours for response.\n\nIndependent technical note mirroring the canonical version: https://issues.house/blog/data-breach-notice-timing-article-33-72-hour-regulator-vs-24-hour-internal-escalation.php",
  "abstract_shown": true,
  "affiliations": [],
  "article_type": null,
  "arxiv": null,
  "author_total": 1,
  "authors": [
    {
      "name": "Rachel Kim"
    }
  ],
  "bibtex": "https://research.draconitic.com/paper/cp84c0psgghtt.bib",
  "cited_by": 0,
  "doi": "10.5281/zenodo.23446770",
  "fulltext_url": null,
  "id": "cp84c0psgghtt",
  "issns": [],
  "landing_url": "https://zenodo.org/records/23446770",
  "language": null,
  "licence": "CC-BY-4.0",
  "licence_label": "CC BY 4.0",
  "licence_source": "article",
  "licence_url": "https://creativecommons.org/licenses/by/4.0/",
  "metadata_licence": null,
  "native_subjects": [],
  "openalex": null,
  "pdf_url": "https://zenodo.org/api/records/23446770/files/blog_data-breach-notice-timing-article-33-72-hour-regulator-vs-24-hour-internal-.pdf/content",
  "pmcid": null,
  "pmid": null,
  "published": "2026-10-17",
  "publisher": null,
  "ris": "https://research.draconitic.com/paper/cp84c0psgghtt.ris",
  "sources": [
    {
      "first_seen": "2026-10-31T12:21:04Z",
      "native_id": "23446770",
      "source": "zenodo",
      "url": "https://zenodo.org/records/23446770"
    }
  ],
  "subjects": [],
  "title": "Data breach notice timing: Article 33 72-hour regulator vs 24-hour internal escalation",
  "title_text": "Data breach notice timing: Article 33 72-hour regulator vs 24-hour internal escalation",
  "type": "preprint",
  "updated_at": "2026-10-31T12:21:04Z",
  "url": "https://research.draconitic.com/paper/cp84c0psgghtt",
  "venue": "Zenodo",
  "versions": []
}