# Privacy and recovery

Forge holds personal, commercial and operational information, so treat requests to see, delete or recover data carefully: for example, a customer asking what data you hold on them, or a team member trying to restore a deleted job record.

## Before you start

"Get it back" is not enough on its own. Before you touch anything, know exactly what's missing, where it belonged, and who is responsible for the decision.

## Protect access

Use individual accounts and workspace roles rather than a shared password, reset link or privileged session. If a request involves someone else's information, keep it narrow: identify the exact workspace, task, file or record before you look at or change anything.

## Recover something safely

1. Work out what's missing, where it belonged, and what result you actually need.
2. Review a recovered copy before you replace anything that's currently in use.
3. For a table record, recovery needs administrator access and a complete snapshot. Forge won't do a partial restore, because that could break the record of who has access to what. This is deliberate.

If a deletion, access problem or possible data exposure has unclear scope, stop and bring in the responsible administrator. Keep whatever evidence exists about what happened.

## Prompts to try

```
For [workspace], identify the exact file or record named [target], its current location and the safest read-only checks before any recovery action. Do not change anything.
```

```
Draft a recovery plan for [target]. Include the owner, source snapshot, checks before restore, and how we will avoid overwriting current work. Wait for my confirmation before acting.
```

## Next steps

If you only need the original file, start with [Files and storage](/help/files). If it's access itself that's changing, use [Add a teammate](/help/add-teammates).

See [Add a teammate](/help/add-teammates) and [Files and storage](/help/files).