> For the complete documentation index, see [llms.txt](https://docs.plumvoice.com/dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plumvoice.com/dev/plum-dev-guide/data-security/private-tags.md).

# 'Private' Tags

## Securing Your App(s)

In Plum DEV, use the logging property and set the value to ‘private’ so that app does not write any sensitive information to the call log*.* You can add the following code to your root document or at the top of each VoiceXML document to make sure no sensitive data is stored:

`<property name="logging" value="private"/>`

{% hint style="danger" %}
In order to maintain security compliance throughout your DEV application, you must ensure that the form block(s) that collect end-user input **and** the code block(s) that initiate webservices are designated as 'private'.
{% endhint %}

## Verifying 'Private' Functionality

It is **highly recommended** to perform quality assurance tests on your application(s) before deployment. To do this input test data that should remain hidden. Repeat this several times to ensure the app has an opportunity to collect data from multiple calls.&#x20;

You can check call logs to ensure that privacy settings are functioning properly and verify that no sensitive data appears anywhere in the logs.&#x20;

<div align="left"><img src="/files/-MAh7mSl6DguauvfTAgt" alt=""></div>