Recover deleted DSRs and automatically block third-party scripts

By Sypher | Published in Resources


Recover deleted Data Subject Requests

Deleting a data subject request in Sypher isn't final right away. Deleted DSRs are kept for 30 days, and during that time you can restore any of them with a single click, whatever the reason it was deleted.

Go to Project Settings → Deleted Items and open the Data subject requests tab. You'll see every deleted request with its reference number and the date and time it was deleted. From there you can:

  • Review before you restore - click the reference number to open the deleted request in read-only mode and check its contents.
  • Restore in one click - press Restore next to the request, or use the Restore option in the request's own actions menu. The request returns to your DSR list.
  • Keep the audit trail - the restore is recorded in the request's history, so you can always show who brought it back and when.

After 30 days, deleted requests are permanently removed, in line with data minimisation. Restoring is available to users who have the right to manage and assign DSRs.

Deleted Items has two more tabs, Mapping and Security incidents, which work the same way.


Your cookie scanner now catalogues and blocks third-party scripts

Until now, a scan could find a tracking script on your website and show it in the report, but the script was only blocked if someone had added it to your list by hand. A tracker nobody remembered to add could keep running without consent.

The scanner and script blocking now work together.

Known scripts are handled automatically. After each scan, third-party scripts are compared with the Sypher script library, which our team maintains. When a script is recognised, it's added to your script list in the right category and blocked until the visitor consents. You don't need to do anything.

Unknown scripts are flagged, then blocked. We don't guess. If a script can't be identified, we let you know by email and on the scanner page, and you have 30 days to review it. If it's still not categorised after that, it's blocked for all visitors until you decide what it is.

The Scripts tab now shows what to do next. Each detected script has a status, such as catalogued, pending, blocked or ignored. You can categorise an unrecognised script in a few clicks using a pre-filled form, or ignore it if you're happy to leave it running. A warning on the scanner page shows how many scripts need review and when the first one will be blocked.

You stay in control:

  • The feature is on by default for new websites.
  • For existing websites, nothing changes until you turn on Auto cataloguing of scanned scripts in the website's advanced settings. It works together with Auto block third party scripts, so turning it on enables that option too.
  • You can edit or delete anything added automatically. Automatically added scripts are marked with a wand icon. 
  • Your website's own scripts are never blocked.

Good to know: blocking applies to external script files. Inline scripts, tracking pixels, iframes and anything that loads before the consent widget can't be blocked this way.