Privacy

The Privacy tab gives you direct control over how AxisSynapse handles data about you: the self-identification flags HR + DEI consume (if your workspace has HCM enabled), the data-export request to download a copy of everything we hold, and the account-erasure request that triggers the platform's five-wall safety model. It also shows the GDPR posture statement for your workspace and which processors AxisSynapse uses on its behalf.

TL;DR — Open Account → Privacy. Update self-ID flags from the Self-ID card. Request a copy of your data from the Data-export card. Request account erasure from the Erasure card — the workflow walks through cooling-off, four-eyes review, and regulatory holds before completing.

Self-identification (HCM only)

When the workspace has HCM enabled and self-ID is configured by HR, this card lets you set or change the demographic flags your workspace uses for EEO reporting + pay-equity analysis + DEI funnel work. You own the data; you can clear it at any time.

1. 1

   Open Account → Privacy → Self-identification

   The card shows your current self-ID state and the categories the workspace has enabled.

2. 2

   Update the fields you want

   Each category is independent — you can disclose gender and skip ethnicity, or vice versa. Prefer not to say is always an option.

3. 3

   Save

   Changes propagate to HCM, EEO, and DEI immediately. The audit feed records the change.

Request a copy of your data

The data-export bundle includes everything AxisSynapse holds about you: profile, audit lines, notifications, time-off records (HCM), pay history (HCM), goals + check-ins (HCM), and more — itemized by source module.

1. 1

   Open Account → Privacy → Data export

   Click Request data export.

2. 2

   Acknowledge the bundle scope

   The form shows which modules will contribute to the export. Read through to confirm; the export is asynchronous and may take minutes to hours depending on size.

3. 3

   Submit

   The request enters the queue. The audit feed records the submission.

4. 4

   Wait for the ready notification

   When the bundle is ready, you receive an in-app notification and (if enabled) an email. The bundle is available to download for 7 days.

5. 5

   Download (step-up required)

   The download itself requires a fresh step-up. The download is audited as a warning-severity action.

Request account erasure

Account erasure removes the data AxisSynapse holds about you, respecting every regulatory hold (IRS, ERISA, SOX, EEOC, FMLA, etc.) that applies. The full safety model is described at Account erasure; from your side, the flow is:

1. 1

   Click "Request account erasure"

   The drawer explains the five-wall safety model in plain language and asks for a reason.

2. 2

   Provide a reason

   Free text. Read by your admin during review.

3. 3

   Confirm + submit

   The request enters the admin queue. You receive a confirmation in your audit feed.

4. 4

   Cooling-off begins after approval

   Once an admin approves, a cooling-off window starts (default 7 days). You can Cancel at any time during the window.

5. 5

   Erasure completes after the window

   A different admin completes the erasure after the window. If regulatory holds are active, completion pauses until they expire or are explicitly overridden.

6. 6

   You receive a per-module report

   The completed erasure produces a regulator-defensible report naming every table touched, every hold honored, and the per-row outcome.

GDPR posture

The Privacy tab shows the workspace's current GDPR-relevant settings and a link to the AxisSynapse-side posture statement.

Every field, explained

What appears in the audit log

• ACCOUNT_DATA_EXPORT_REQUEST — your data-export submission.
• ACCOUNT_DATA_EXPORT_READY — bundle ready, you can download.
• ACCOUNT_DATA_EXPORT_DOWNLOADED — the download was made.
• ACCOUNT_DELETION_REQUEST / ..._APPROVED / ..._REJECTED / ..._CANCELLED / ..._COMPLETED — erasure-workflow milestones.
• ACCOUNT_DELETION_BLOCKED_BY_HOLDS — completion attempted while holds were active; the request remains in-flight until the holds resolve or an override completes.

Every row appears in your personal Account audit feed and in the workspace Security Console.

Common gotchas

• "My self-ID change didn't appear in the DEI dashboard." DEI aggregates respect k-anonymity. Your row is in the underlying dataset; the dashboard hides it until the group reaches the k-floor.
• "My data export bundle is missing my HCM payroll history." Some HCM data is held by regulatory retention regardless of export. The export includes everything we can release; the bundle's manifest names any module that contributed a partial set and why.
• "I requested erasure but my account is still here weeks later." Holds are active — check the request row. The most common holds are IRS retention on payroll (4-7 years) and EEOC retention on case data (varies). The platform fails closed until the holds resolve.
• "I want to revoke a previously disclosed self-ID." Set the field back to Prefer not to say. The platform records the change in the audit feed; downstream consumers re-evaluate immediately.
• "My admin denied my erasure request." Admins can reject for business or regulatory reasons. The audit feed records the rejection with rationale. If you disagree, escalate per your workspace's policy.

Troubleshooting

| Error code | What it means | Fix | |---|---|---| | EXPORT_QUEUE_BUSY | A previous bundle is still preparing. | Wait for it to finish. | | EXPORT_DOWNLOAD_EXPIRED | The bundle's 7-day download window elapsed. | Re-request. | | DELETION_ALREADY_PENDING | A request is already in flight. | View the active row to manage it. | | DELETION_BLOCKED_BY_HOLDS | Active retention holds prevent completion. | Wait for holds to resolve; see /platform/account-erasure. |