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

# Data Governance

## Data Localization

Couchdrop normally routes your domain to the closest available server region for performance.

If your organization requires Couchdrop traffic to be restricted to a specific geographic region, your Couchdrop URLs can be bound to a particular **Point of Presence (POP)**.

Geographic binding can be useful where you have:

* Data residency or localization requirements
* Network policies requiring traffic to remain within a particular region
* Performance requirements for users or systems in a specific location

{% hint style="info" %}
Geographic binding is configured by Couchdrop. Contact <support@couchdrop.io> if you need your account mapped to a specific region.
{% endhint %}

## Reporting Event Retention

Couchdrop retains reporting events for a defined period based on your plan.

| Plan           | Default retention |
| -------------- | ----------------- |
| **Link**       | 30 days           |
| **Essentials** | 90 days           |
| **Business**   | 6 months          |
| **Enterprise** | Customizable      |

If you need a different reporting event retention period, contact <support@couchdrop.io>.

## Related data governance controls

Couchdrop also provides controls that affect how file data is handled as it moves through the platform.

### Zero-custody transfers

When you use your own connected storage, Couchdrop transfers files directly to or from that storage rather than becoming another permanent location where those files are stored.

This allows you to retain control over the storage platform, residency, retention, and access policies applied to your file data.

{% hint style="info" %}
For example, if an SFTP user uploads a file to a Couchdrop folder connected to SharePoint, Couchdrop transfers the file into SharePoint and SharePoint remains the system storing the file.
{% endhint %}

### Transfer Shield DLP

[**Transfer Shield**](/security-and-governance/transfer-shield-dlp.md) allows you define what content can cross your organizational boundary.

Using [**Content Rule Groups**](/security-and-governance/transfer-shield-dlp/content-rule-groups.md), you can apply controls to inbound and outbound transfers before files enter or leave your custody.

Depending on the policy, Couchdrop can:

* Detect sensitive or unexpected content
* Block a transfer
* Require manual approval
* Record matched content for review

Transfer Shield policies apply only to files transferred through Couchdrop. Files added directly to connected storage, such as SharePoint or AWS S3, do not pass through Transfer Shield.


---

# 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.couchdrop.io/security-and-governance/data-governance.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.