{"id":1036,"date":"2026-06-19T15:25:43","date_gmt":"2026-06-19T13:25:43","guid":{"rendered":"https:\/\/blurit.io\/blog\/?p=1036"},"modified":"2026-06-19T17:36:59","modified_gmt":"2026-06-19T15:36:59","slug":"blurit-io-dsar-compliance-redacting-images-and-video","status":"publish","type":"post","link":"https:\/\/blurit.io\/blog\/en\/blurit-io-dsar-compliance-redacting-images-and-video\/","title":{"rendered":"Blurit.io & DSAR Compliance: Redacting Images and Video"},"content":{"rendered":"
<\/div>\n

A Data Subject Access Request (DSAR) gives someone the right to ask an organization for a copy of the personal data it holds about them \u2014 and footage is personal data the moment it shows an identifiable face or license plate. When that footage also includes other people, the organization responding to the request has to anonymize everyone else in the file before it can be disclosed. This is exactly where Blurit.io fits in.<\/p>\n\n\n\n

Why DSAR Requests Get Complicated with Visual Data<\/h2>\n\n\n\n

A text-based DSAR response is straightforward to redact \u2014 you can black out a name or an address in a document in seconds. Video and images are a different problem entirely. A single piece of CCTV footage, a dashcam clip, or a body-worn camera recording can contain dozens of identifiable people who aren’t the subject of the request, across hundreds or thousands of frames. Manually blurring each one isn’t just slow, it’s a real source of compliance risk if even one face is missed before disclosure.<\/p>\n\n\n\n

How Blurit.io Supports DSAR Responses<\/h2>\n\n\n\n

Blurit.io’s AI automatically detects and redacts faces and license plates across both images and video, tracking them through a full video timeline rather than requiring a frame-by-frame manual mask. That means an organization handling a DSAR can process the relevant footage, anonymize every third party who isn’t the data subject, and disclose only what’s legally required \u2014 without the bottleneck of manual editing.<\/p>\n\n\n\n

Depending on the volume and frequency of requests an organization handles, this can be done four ways:<\/p>\n\n\n\n

Through Blurit.io Studio<\/strong>, the browser-based tool, for occasional or one-off requests. Read more in What Is Blurit.io Studio?<\/a><\/p>\n\n\n\n

Through the Blurit REST API<\/a><\/strong>, for organizations that want to plug redaction directly into their existing DSAR or records-management workflow.<\/p>\n\n\n\n

Through a self-managed deployment<\/a><\/strong>, for organizations \u2014 particularly in law enforcement, healthcare, or other regulated sectors \u2014 that need to keep all processing inside their own infrastructure.<\/p>\n\n\n\n

Through Blurit.io’s dedicated DSAR solution page<\/a><\/strong>, for a tailored overview of how the platform fits specifically into a data subject access request workflow.<\/p>\n\n\n\n

Getting Started<\/h2>\n\n\n\n
    \n
  1. Go to app.blurit.io<\/a> and upload the footage or images relevant to the request.<\/li>\n\n\n\n
  2. Let the AI detect every face and license plate automatically.<\/li>\n\n\n\n
  3. Review the result and adjust any detections that need a manual fix.<\/li>\n\n\n\n
  4. Export the redacted file, ready to include in your DSAR response.<\/li>\n<\/ol>\n\n\n\n

    For higher-volume or recurring DSAR workflows, the API or self-managed options remove the need to process each request through the browser individually.<\/p>\n\n\n\n

    Related Reading<\/h2>\n\n\n\n

    This article is a general overview. For more specific guidance, see:<\/p>\n\n\n\n