PDPL grants every data subject the right to delete their personal data. In Jadiroon, deletion comes in three sizes — deleting a single record, deleting an individual's data within a workspace, and deleting an entire workspace. All three follow the same principle: deletion is irreversible and we make sure both you and we know what we are doing before it happens.
Deleting a single record
The smallest unit of deletion is one record — a milestone on a growth plan, an assessment, an interview note. Most records cannot be deleted in v0.5; instead they are retired (marked inactive, preserved for audit). The reasoning: an audit trail with holes in it is less useful than one with retirement markers.
Records that can actively be deleted by HR or line managers in v0.5:
- Notifications in the user's own inbox.
- Pending invitations before they are accepted.
Everything else — assessments, plan milestones, interview notes — is retired rather than deleted.
Deleting an individual's data
If an employee leaves and PDPL data-subject deletion is requested, the path in v0.5 is:
- The HR Administrator marks the Person's status as
FORMER_EMPLOYEE. - The employee (or their representative) submits a deletion request via hello@jadiroon.sa with verifiable identity.
- We verify the request, scope what can be deleted (subject to legal retention requirements your organisation may have), and execute the deletion.
The execution typically completes within ten business days. Audit-trail preservation may require some retained records for a period defined by your jurisdiction's labour and tax law; we surface what is retained and why.
A self-service in-product Request my data deletion flow is on the v0.6 watch list.
Deleting an entire workspace
If your organisation no longer uses Jadiroon and wishes to terminate:
- An HR Administrator writes to hello@jadiroon.sa with the deletion request.
- We confirm and offer a final workspace export (the export flow).
- After the export is downloaded and the workspace owner confirms, the workspace is deactivated.
- The workspace is fully deleted after a 30-day grace period (during which it can be reactivated if requested).
After the grace period, the workspace is unrecoverable.
What deletion actually does
For data we do hold and have committed to delete:
- Application database records are removed.
- Object storage (CV PDFs, avatar images) is deleted.
- Backups that include the deleted data are retained for the platform's standard backup window (currently 35 days), then aged out.
- Audit logs that reference the deleted data are retained in their existing form (they reference IDs, not content) for the legal retention period and then aged out.
What deletion cannot do
- Recover deleted data later. Deletion is irreversible.
- Delete data from copies your organisation made. If you exported the workspace and the export sits in your storage, that copy is yours to manage; we cannot reach it.
- Remove records that legal requirements require us to keep. Some financial and contractual records have statutory retention periods; we honour those. The deletion notification will list any retained categories and why.
Why retire-rather-than-delete by default
Three reasons:
- Audit integrity. A growth plan with milestones that vanish is a poor audit record.
- Accidental deletion. Retirement is reversible; deletion is not.
- Operational simplicity. Most cases people imagine as needing deletion are actually well-served by retirement (the milestone is no longer active, but the history is preserved).
When deletion is genuinely required (PDPL data-subject right, organisational decommissioning), the explicit-request flow above ensures the deletion happens with the right authorisation and the right downstream cleanup.