> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/general/company-details/privacy-policy.md).

# Privacy Policy

Our order process is conducted by but not limited to online resellers like Paddle.com . When your order is processed by Paddle, Paddle is the Merchant of Record for all our orders. Legally we're obliged to say that Paddle provides all customer service inquiries and handles returns, which they do if you reach out to them directly. However, feel free to contact us directly for all said matters. It's much faster…

To make sure Hedge works as promised we need to collect data. It ensures and improves quality. Without data we would be forced to conduct pricey and less effective research, which would result in a much higher price for you, the user.

Still, to us this feels as an undesirable situation. It's creepy. It's too easy nowadays to slip into the Land Of Gimme-All-Yer-Data, and make money off *your* data. So hereby we offer you a complete insight into what we think is the bare minimum of data needed.

We do not share raw data with anyone, ever. Period. We consider the data yours, and you give us a right to use that data by using our software. Any analytics data we collect when you for instance send us a crash report is removed within a year. That period usually suffices to let us trace back issues in previous releases.

The exception to the "removed within a year"-rule is your license data - for obvious reasons, we have to store your email to know which license belongs to it, for as long as the license exists. As we cannot know when you are no longer using a particular license, we don't delete licenses unless you ask us to.

Since email is legally considered sensitive personal data, you have an explicit right of removal of that information. An execution of your right to be forgotten implies that any licenses tied to your email have to be deleted too. To invoke your right to be forgotten, simply reach out to <privacy@hedge.video> and we will reply to you with 24 business hours. Our timezone is CET.

### Policies need policing <a href="#policiesneedpolicing" id="policiesneedpolicing"></a>

If you think we use your or anyone's data in a wrongful way, or should be more stringent in how we use it, please let us know. We promise to be responsive, cooperative, and open to suggestions.

*Last changed on 20260424 by Paul Matthijs Lombert*


---

# 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.hedge.video/general/company-details/privacy-policy.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.
