How-to

Handling duplicate requests

What to do when the same person submits twice, and how merging keeps one clean record.

1 min readLast updated 17 July 2026
Jump to section

Handling duplicate requests

People submit twice. They forget they already asked, they don't get the confirmation email, or they try again from another device. Blankitt Privacy flags likely duplicates so you can deal with them in one click.

How duplicates are flagged

When a new request arrives that closely matches an open one (same person, same kind of request), the detail page shows a possible-duplicate notice linking the two.

Merging

If it really is the same ask, use Merge on the newer request. Merging:

  • Closes the duplicate and records which request it was merged into.
  • Adds a case note to the surviving request so the history is visible.
  • Emails the requester so they know which reference is live.

Both requests keep a link to each other, so an auditor can always follow what happened.

When not to merge

If the second submission is actually a different right (say, an access request followed by an erasure request), keep both open. Each has its own deadline and its own work. Merging is only for true duplicates.

Still stuck? Email support or open the support widget in the bottom-right.