All Collections
Compliance
Why are the GDPR consent links I send to candidates no longer working?
Why are the GDPR consent links I send to candidates no longer working?

In order to help you with your compliance workflows, eBoss has built expiry dates into all of our GDPR consent requests. Here's why:

Robin Bonass avatar
Written by Robin Bonass
Updated over a week ago

Sometimes, you may find that the GDPR consent requests you have sent to candidates are no longer working. You might see the following error:

"Unable to connect securely to this page. This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner. "

If your GDPR consent links appear to have been deactivated, it could be that the links you issued were too old, and have now expired.

GDPR consent links have a 28-day life span. It means that, if your candidates take a month or more to respond, they are likely to see this "page unavailable" error message. 

The solution is very simple: just send the candidate a new GDPR compliance request, and the fresh link will work fine for them.

When you first encounter an expired consent link, you might ask "why did we implement a time limit on consent?" The answer is: it improves security.

We learned that most of our subscribers were reviewing their compliance statuses every 30 days. By building in a 28 day expiration date, it means that all consent requests will be resolved within the same month. 

Each month, you can see who hasn't responded, and issue a new request. With the expiry time, the candidate will then not be able to reply using the previous month's request - as it has now expired. 

This way, your GDPR record-keeping is never going to fall out of sync, with consent requests sent out one month, and responded to in the next. You know where you are, and your data security reporting is kept simple and free from doubt.

Did this answer your question?