> For the complete documentation index, see [llms.txt](https://help.screena.ai/resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.screena.ai/resources/faq/hosting-and-deployment/how-do-you-segregate-the-data-and-configuration-between-customers.md).

# How do you segregate the data and configuration between customers?

There is no data segregation as we don’t store or keep customers’ personal data sent through [Screena search endpoint](https://developer.screena.ai/#integrating-search-engines). We only log and count the **number of API requests** executed monthly for billing purposes.

Configuration is segregated per organization based on API keys.

{% hint style="info" %}
To learn how Screena's configurable components are managed per organization and tied to distinct API keys, check the answer to this question: [What options do I have to optimize my screening results?](/resources/faq/personalization/what-options-do-i-have-to-optimize-my-screening-results.md)
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.screena.ai/resources/faq/hosting-and-deployment/how-do-you-segregate-the-data-and-configuration-between-customers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.