> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/security-and-safety/clear-app-data-on-logout.md).

# Clear App Data on Logout

A Launcher security feature that automatically deletes application and session upon user logout to protect shared devices.

### **Overview**

Use Clear App Data on Logout to automatically clear application data once a user logs out of a device. It deletes cookies, session tokens, cached files, and running apps outside the authentication module. It is commonly used to safeguard sensitive information such as login credentials and browsing history on shared or multi-user devices.\
\
By default, this feature is disabled; however, administrators can enable it and configure which application packages are cleared or retained during the logout process.&#x20;

### **User Guide**

To configure Clear App Data on Logout, complete the following steps:

1. Enable the `clearAppDataOnLogout` setting to clear user data upon logout.
2. Define applications in the `clearAppDataIncludeList` to clear their data even if they were not actively used during the session.
3. Define applications in the `clearAppDataExcludeList` to exclude in the process and retain their user data upon logout.&#x20;

{% hint style="info" %}
Downloaded files are not automatically deleted during the default file removal process. For more information on how to explicitly remove downloaded files, refer to the Delete Files and Clear Cache sections of the Custom Intents Platform Actions page.
{% endhint %}

### **Configuration**

#### **Enabling Clear App Data on Logout**

To enable the feature, set `clearAppDataOnLogout` to `true` within the Launcher configuration.&#x20;

```json
"settings": {
  …
  "clearAppDataOnLogout": true
}
```

#### Setting Up Data Inclusion List

If `clearAppDataOnLogout` is set to true, this list specifies additional app packages that should be cleared even if they were not launched during the session. An example configuration is shown below:

```json
"settings": {
  …
  "clearAppDataOnLogout": true,
  "clearAppDataIncludeList": “com.android.chrome”
}
```

#### **Setting Up Data Exclusion List**

If `clearAppDataOnLogout` is set to true, this list specifies app packages that should be excluded from the app data clearing process. These packages will retain their app data even when the user logs out. An example configuration is shown below:

```json
"settings": {
  …
  "clearAppDataOnLogout": true,
  "clearAppDataExcludeList": “com.bluefletch.emm.epm”
}
```

{% hint style="info" %}
If `clearAppDataOnLogout` is set to false, the `clearAppDataIncludeList` and `clearAppDataExcludeList` settings are ignored. No app data will be cleared on logout.
{% endhint %}

The Clear App Data on Logout configuration consists of the following parameters:

<table><thead><tr><th width="233.44921875">Field</th><th width="295.28515625">Description</th><th>Default Value</th></tr></thead><tbody><tr><td>clearAppDataOnLogout</td><td>Enables the clearing of app data on logout for all applications launched during user session</td><td>false</td></tr><tr><td>clearAppDataIncludeList</td><td>Specifies app packages that should be cleared even if they were not launched during user session</td><td>none</td></tr><tr><td>clearAppDataExcludeList</td><td>Specifies app packages that should be excluded from the app data clearing process</td><td>none</td></tr></tbody></table>

## Putting It All Together

For the example described above, the full configuration for the Clear App Data on Logout feature is as follows:

```json
"settings": {
  …
  "clearAppDataOnLogout": true,
  "clearAppDataIncludeList": “com.android.chrome”,
  "clearAppDataExcludeList": “com.bluefletch.emm.epm”
  }
  }
```


---

# 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.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/security-and-safety/clear-app-data-on-logout.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.
