Solutions
One person, every system, one request
Data subject rights, data residency and controls on personal data are spreading beyond Europe, and each retired HR system is another place a person's data hides. Fuse Analytics is built around the personal record, so a request to see, export or erase someone's data is answered once, across everything you have archived.
The rules keep arriving
GDPR set the pattern, and laws in US states, Brazil, China and elsewhere have followed it, with rights of access, correction, portability and erasure, and with retention limits that a system built to keep everything forever cannot meet. HR holds the most sensitive personal data a company has, for employees, contractors and applicants, and the legacy systems it retires are the ones nobody has looked at in years. How are you going to be GDPR compliant when you have an old HCM system lying around? asks the question directly.
How the archive answers a request
- Find the person across every archived system, including the ones that no longer run.
- Export their records in a portable form, or let them do it themselves through the data subject rights portal.
- Correct or erase where the law requires it, while the records that must be kept stay under retention.
- Prove it. Access logs and retention policies show a regulator what was held, who saw it and when it was deleted.
Retention and erasure are one policy
Erasure on request and deletion at the end of a retention period are two ends of the same lifecycle. Fuse applies both to the same records, so a request never conflicts silently with a retention obligation. See records retention and Data archiving and GDPR compliance.
Where to start
Compliance and security describe the controls behind the portal, and the FAQ covers the questions privacy teams ask first. Then book a demo.
Getting data subject requests for people who left years ago?
Talk to a data specialist about archiving your legacy systems so every request can be answered, and every erasure carried out, from one place.