> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/access-and-sharing/data-privacy-and-security.md).

# Security and data handling

Review data handling for the features and deployment you actually use. Storage, request processing, diagnostic logs, and AI inputs are separate parts of that review.

## Identify where data is handled

| Area                         | What to establish                                                        |
| ---------------------------- | ------------------------------------------------------------------------ |
| Connected databases and APIs | Where the source records live and how Jet Admin requests are authorized. |
| Jet Tables                   | The hosted data stored in the Jet Tables resource.                       |
| Jet Bridge                   | Where the bridge runs and which database or API requests it handles.     |
| On-premise deployment        | Which components you operate and their network dependencies.             |
| AI features                  | Which prompts, files, and data are supplied to the selected service.     |
| Logs and exports             | What they contain, who can access them, and how long they are retained.  |

Do not assume that using an external database means no data is processed elsewhere. Review the configured request path and the applicable service documentation or agreement.

See [the architecture guide](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/cloud.md), [Jet Bridge hosting](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin.md), and [on-premise deployment](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise.md) for deployment-specific guidance.

## Credentials and network access

Use appropriately scoped credentials for each resource and keep secrets out of app code, prompts, screenshots, and shared logs. Review credential ownership and rotation with the team operating the data source.

Network restrictions such as a VPN or private network can reduce exposure. They do not replace authentication, authorization, maintenance, or monitoring.

## Recovery responsibilities

Distinguish restoring an app configuration from restoring records in a connected database. Before relying on recovery, confirm what is backed up, how restoration works, retention, and who owns the process for each system.

Test recovery in an appropriate environment. Do not assume an interface restore reverses data writes made by users, APIs, or workflows.

For access verification, use [the access test checklist](/access-and-sharing/overview/test-access.md); for operational investigation, see [Audit trail and system logs](/access-and-sharing/audit-logs-privacy-and-security.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/access-and-sharing/data-privacy-and-security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.