> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/center/security-and-privacy/provide-a-customers-data-upon-request.md).

# Provide a Customer's Data Upon Request

A growing number of digital privacy laws grant individuals the right to access the personal data businesses collect about them. To meet these requirements, companies need a process for locating and providing that data across all the tools and applications they use.

{% hint style="info" %}
Note: This information is provided as general guidance on how Daylite can support your broader GDPR compliance strategy. It does not constitute legal advice. For tailored advice or to ensure full compliance with GDPR, we recommend consulting your legal counsel.
{% endhint %}

1. Select the Customer you're interested in
2. From the menu bar, choose **File** > **Print**
3. Choose **Contact Summary Report**
4. Click **Print**
5. Select your printer settings and choose Print.

If you choose to print as a PDF and send electronically, ensure that you are not sending via an insecure method, i.e., unsecured Email.


---

# 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.daylite.app/help/center/security-and-privacy/provide-a-customers-data-upon-request.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.