Skip to content
VooHr Support Contact Sign in

Privacy and security

Data access, export and deletion

VooHr has specific employee export and deletion operations, but those operations do not establish a universal data-subject request process or full deletion from every system.

Available exports #

The employee directory offers CSV export of employee records in the caller's allowed scope. The bulk export is audit-logged. There are also employee-level export paths and other product screens that display session, survey, meeting, or memory information, but do not assume those screens form a complete account-wide archive.

Handle downloaded data as sensitive, share it only through approved channels, and check that you selected the intended organization, scope, and filters.

  • Employee CSV export is limited to the caller's permitted scope.
  • Bulk employee exports are audit-logged.
  • Available export screens do not establish a complete account-wide archive.

Available deletion actions #

An administrator can delete an employee record through the directory API. That operation also deletes sessions and notifications attached to the employee before deleting the employee record. Sessions can be deleted through their own endpoint; conversation-memory and survey records have their own operations.

These are separate application records and endpoints. The employee-delete code does not establish deletion from backups, logs, third-party providers, email, WhatsApp, or all related collections. Do not promise complete erasure based only on one delete action.

  1. Identify the records and person covered by the request.
  2. Follow your organization's approved privacy request process.
  3. Ask an administrator to use the applicable export or deletion operation.
  4. Verify the operation's scope and consult the privacy contact about backups and providers.

Requests and retention #

The code reviewed for this guide does not define a universal user-facing data-access request form, deletion-request workflow, retention schedule, or response deadline. Follow your organization's approved privacy process and consult the existing Privacy Policy.

Customer request process, retention and backup deletion timelines: [CONFIRM: data request and retention policy]

Use this guidance thoughtfully

This page describes the current product workflow; it is not an HR policy or a promise about every deployment. Before acting on information about an employee, verify the source record, consider context the system cannot see, and use your organization's process. If a control behaves differently from this guide, check the current workspace UI and confirm the saved result rather than assuming an action completed.