> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yrka.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Request a data export, restore, or account deletion

> Learn how to request a data export, account restore, or deletion in Yrka, and what to expect during the review and retention period.

Yrka supports data export, account restore, and deletion requests for organization owners and authorized business representatives. Personal data requests from individual employees are handled by the employing organization as the data controller, with Yrka supporting as the service provider. This page explains the types of requests available, how to initiate them, and what to expect during each stage of review.

<Note>
  This page explains the customer workflow. It does not replace Yrka's Privacy Policy, Data Processing Agreement, or Subprocessors list, which remain the legal source of truth for privacy obligations and commercial terms.
</Note>

## Types of requests

| Request type   | What it does                                                                                                                    |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Export**     | Delivers a copy of your organization's data to a verified owner or authorized representative                                    |
| **Restore**    | Reviews available backup or recovery evidence to assess whether a specific record or dataset can be recovered                   |
| **Correction** | Corrects data that Yrka entered incorrectly during managed setup or support — not for routine admin edits you can make yourself |
| **Deletion**   | Initiates the deletion process for your organization's data after verified owner review and operator execution                  |

## Who can submit a request

* **Organization owners** can submit account-level export, restore, correction, and deletion requests.
* **Authorized business representatives** with verified authority can submit requests on behalf of an organization owner.
* **Individual employees** seeking access to their personal data should contact their employer first. Yrka acts as the service provider for employee data — the employer (your organization) is the controller.

## What Yrka stores and what it sends to providers

Yrka stores your organization's workforce data — employee records, time entries, schedules, messages, tasks, documents, and audit history — in its own database and private storage. When you connect a provider (for example, a payroll or HR integration), Yrka sends only the data that specific integration requires based on your configuration. Provider systems maintain their own records independently.

A data export from Yrka covers data within Yrka's systems. It does not recall or replace data held by third-party providers you have connected.

## How to submit a request

<Steps>
  <Step title="Start from Account and Billing or support">
    Open **Admin > Billing** or contact Yrka support through your plan's configured support channel. Both paths accept data requests. Have the following ready:

    * Your name, email address, and organization name
    * Your role (owner or authorized representative)
    * The type of request (export, restore, correction, or deletion)
    * The affected user or employee record, if applicable
    * Your preferred delivery destination for exports
    * Any requested deadline or legal basis, if your counsel or customer agreement specifies one
  </Step>

  <Step title="Complete owner or representative verification">
    Yrka verifies that the requester has authority to act on behalf of the organization before processing any account-level data request. Export and deletion requests cannot proceed without this step.
  </Step>

  <Step title="Scope confirmation">
    Support identifies which data areas the request covers — live database records, private storage files, message and recap history, audit and security records, billing records, integration metadata, or backups. Some areas are checked separately.
  </Step>

  <Step title="Review and execution">
    Once scoped and approved, support runs the documented process for that request type. For exports, the manifest is reviewed before delivery. For deletions, the request enters a verified review state before any data is removed.
  </Step>

  <Step title="Receive the outcome">
    The final response summarizes what was completed, what was retained for audit, security, billing, or legal reasons, and where the delivered export or outcome can be found.
  </Step>
</Steps>

## Request status meanings

Your request moves through a status lifecycle. Here is what each status means:

| Status                | Meaning                                                                                                   |
| --------------------- | --------------------------------------------------------------------------------------------------------- |
| `received`            | The request was captured and is in the queue                                                              |
| `verifying requester` | Authority and identity are being confirmed                                                                |
| `scoping`             | Support is identifying the data areas and ownership involved                                              |
| `in progress`         | The approved process is running                                                                           |
| `waiting on customer` | You or your owner need to provide more information or approval                                            |
| `completed`           | The outcome was delivered or recorded                                                                     |
| `rejected`            | The request could not be verified or fulfilled                                                            |
| `export retention`    | Your paid access ended, but data remains available for export or reactivation during the retention window |
| `deletion requested`  | Deletion was requested and is awaiting reviewed operator execution                                        |

## Export retention window

When a paid subscription ends, your organization's data does not disappear immediately. A retention window keeps your data accessible for export or account reactivation during that period. To retrieve your data before the window closes, submit an export request from the **Account and Billing** path or contact support.

<Tip>
  If you canceled your subscription but want to retrieve your data, act before the retention window closes. Once the window expires, data may no longer be recoverable through a standard export request.
</Tip>

## Deletion

Submitting a deletion request does not immediately remove your data. The request enters a `deletion requested` state and requires verified operator review before execution begins.

You can cancel a deletion request before operator execution if your account state allows it. Contact support as soon as possible if you need to cancel.

<Warning>
  Database backups and storage backups follow their own retention schedules. Deleted records may persist in backups until the normal backup retention period expires, even after a deletion request is executed. This is expected behavior, not a failure of the deletion process.
</Warning>

## Restore requests

A restore request asks support to review available backup and recovery evidence. Database recovery and private storage file recovery are checked separately — evidence for one does not guarantee the other is recoverable.

Support will confirm what evidence is available and what can be recovered before any restore action is taken.

## Privacy and data boundaries

Yrka's privacy posture is governed by the Privacy Policy, Data Processing Agreement, and Subprocessors list. This page summarizes the request workflow — it does not make legal commitments about response timelines or compliance obligations. If your situation involves legal deadlines or counsel-approved requirements, include that context in your request and confirm the applicable terms with legal review before citing them as binding.