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

# Data Policy

Data policies are essential guidelines and rules that help manage and safeguard application data. They provide a framework to:

* **Classify Data**: Categorize data based on sensitivity and relevance, ensuring appropriate handling.
* **Validate Access**: Confirm that modules and users have the appropriate level of access and permissions, tailored to their role.
* **Support Security Measures**: Serve as a reference for app policies to ensure application security and prevent unauthorized access or excessive rights.

These policies are crucial for maintaining data integrity, confidentiality, and compliance with regulatory standards.

Data policies are automatically generated the first time an app is processed by AppControl. When a data policy is first created it has the following statuses:

* **Data Classification: INCOMPLETE.** You need to classify all data in your domain model according to its access and sensitivity, and flag personal data stored in your app.
* **Module Role Access: REQUIRES VALIDATION.** You need to validate the module and entity access that has been granted to each module role.
* **User Role Access: REQUIRES VALIDATION.** You need to validate the module roles that have been granted to your user roles, which users they can manage, what level of data they can access, and  categorize your user roles.

There are two configuration modes for a data policy:

* **Manual (default).** When manual configuration mode is selected, you must classify data attributes and validate roles manually. You can use UI tools to bulk classify and validate, and enable auto-classification to help with this manual management process. Each time your app domain model changes or access rules are modified, you may need to take action to keep your data policy complete. To manually complete your data policy so that it is classified and validated, perform the following steps: [Classify Data](/administration/policies/data/classify-data.md), [Validate Module Roles](/administration/policies/data/module-roles.md), [Validate User Roles](/administration/policies/data/user-roles.md).
* **Automatic.** When automatic mode is selected, AI will be used to automatically classify your data and validate your user roles. Data classification records created by the system can still be viewed and changed if needed. No further action is necessary. When automatic configuration mode is selected you will see an overview of all data classification records that have been created by the system (or by you) in the 'Classify Data' tab. The 'Validate User Roles' tab shows how your app user roles have been classified by the system. You can change these the automatically selected settings if necessary.

{% hint style="info" %}
**AI-powered Feature**

Automatic data policy configuration is an AI-powered feature and requires the AI service to be enabled in [feature settings](/administration/system/system-configuration.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://docs.bluestorm.io/administration/policies/data.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.