PDPL grants every data subject the right to data portability. In Jadiroon, this means you can export your workspace's data in machine-readable form, and individual employees can export their own data.
Workspace-level export (HR administrators)
An HR Administrator can request a full workspace export at any time:
/{slug}/app/settings/data → Request workspace export.
The request triggers a background job. When complete (typically within a business day for moderate-sized workspaces), an HR Admin receives a notification with a secure download link valid for seven days.
The export is a ZIP archive containing:
- People — every Person record as JSON, with their CV files included.
- Users — User records (with hashed passwords redacted).
- Roles — every role with required competencies.
- Hiring pipelines — every PipelineEntry with stage transitions.
- Assessments — every Assessment record with responses, scores, and narratives.
- Competency profiles — current state with version history.
- Growth plans — full content with activity logs.
- Workspace metadata — settings, taxonomy, email templates.
- Audit logs — workspace-wide audit trail for the period.
The format is JSON, with directory structure that mirrors the entity model. A README.txt in the root explains the schema.
Individual employee export
Any employee can request an export of their own data:
/{slug}/me/profile → Export my data.
The request triggers a similar background job; the employee receives a notification with a secure link to their personal export.
The personal export contains:
- The Person record.
- Assessment records and reports.
- Competency profile (current + version history).
- Growth plan (with activity log).
- Notifications history.
- Audit log entries that touched their data.
The personal export is a single ZIP archive with the same JSON-plus-README structure as the workspace export.
What is in the export, in plain language
Everything Jadiroon holds about you (or about your workspace), in a form another system or another auditor can read.
What is not in the export
- AI prompts and generated content. The narrative reports themselves are in the export; the underlying prompts and the model version that produced them are recorded in audit logs but not bundled by default. Available on request for compliance use.
- Operational logs beyond what is user-relevant (e.g., HTTP request logs).
- Cross-workspace data — even if you have accounts in multiple Jadiroon workspaces, an export from one workspace contains only that workspace's data.
Frequency
A workspace can request up to four full exports per month at no additional cost. Heavier export usage requires a written request to hello@jadiroon.sa so we can scope the work appropriately.
Individual employees can request their personal export up to once per month.
Format stability
The JSON schema for exports is versioned. The README.txt in each export records the schema version. Schema changes between versions are documented; downstream systems that consume exports should pin to a known schema version.
Verifying the export
Each export is signed with a SHA-256 hash, recorded in the notification that contains the download link. The downloaded archive's hash should match; if it does not, the file is corrupted in transit and you should request a fresh export.