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

# Export, retain or delete Support data

> Handle data requests deliberately and understand what deletion affects.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Handle data requests deliberately and understand what deletion affects. Where to find it: Data controls for workspace exports and deletion; customer records for customer-specific actions; Enterprise → Security for retention policies.

## Before you start

* The required export, erasure or workspace-owner permission.
* A verified reason and scope for the request.

## Steps

<Steps>
  <Step>
    Choose the correct workspace. Data controls creates a workspace export; it is not a way to send every customer record to an individual requester.
  </Step>

  <Step>
    For a workspace export, request it, inspect completion and download it before expiry. Keep the file private and restrict it to authorized staff. For an individual data request, use the customer-specific controls available to your role or ask your administrator for assistance.
  </Step>

  <Step>
    For deletion or erasure, review the impact preview and the affected records before confirming. Keep any required legitimate records through your established process before deleting.
  </Step>

  <Step>
    Review retention settings where permitted. Retention is how long eligible content remains; shorter values can permanently remove older content or attachments.
  </Step>

  <Step>
    Track the request’s result and audit history. For data previously sent to an external provider, follow that provider’s deletion process as well.
  </Step>
</Steps>

## Example

An administrator exports the workspace for an authorized business purpose. A separate customer request is handled with customer-specific scope, never by forwarding the whole workspace archive.

## Things to know

* A preview does not itself delete data. Confirmed erasure or workspace deletion can be irreversible.
* Deleting StackShift data does not guarantee deletion from an external service that already received it.
* Data location is a separate setting from retention and backup recovery.

## What happens next

<Check>
  You know what was requested, what completed and what still needs attention outside StackShift.
</Check>

## If something goes wrong

<Warning>
  * Action unavailable: check the required role and scope.
  * Export expired: request a new one if you still have permission.
  * Deletion pending: inspect its status; do not assume every file disappears immediately.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Understand and choose your data location" href="/stackshift-support/data-location">
    Review available regional placement and follow the status of a location change.
  </Card>

  <Card title="Manage organizations, sign-in and security policies" href="/stackshift-support/organization-security">
    Group workspaces and coordinate staff access without exposing every workspace to every member.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.