Skip to main content
In most apps, at least some of the data that is sent to the application is sensitive or personally identifiable information that should not leave the network. To prevent AppSignal from storing this data the Elixir package should be configured to not send this data at all or filter out specific values. In web applications sessions can be used to store user preferences and other sensitive data without it having to be persisted in the database or sent using parameters. In Phoenix applications AppSignal automatically stores the contents of the user’s session on the AppSignal transaction. This can be disabled or specific values can be filtered out.
🔐 Do not send Personal Identifiable Information (PII) to AppSignal. Filter PII (e.g., names, emails) and use an ID, hash, or pseudonymized identifier instead.

For HIPAA-covered entities, more info on signing a Business Associate Agreement (BAA) is available in our Business Add-Ons documentation.
This feature is available since AppSignal Elixir package version 1.6.0.

​
AppSignal session data filtering

Session data filtering will filter out any values from specified keys in the filter_session_data configuration option. Any filtered out value will be replaced with [FILTERED] before it leaves your application and is sent to the AppSignal servers. This means that AppSignal never receives any of the filtered data. In the session data filtering, there’s support for nested hashes and nested hashes in arrays. Any hash we encounter in your session data will be filtered. To use this filtering, add the following to your config/appsignal.exs file in the environment group you want it to apply. The filter_session_data value is an Array of Strings.

​
Send session data

Warning: The skip_session_data option is deprecated since AppSignal Elixir package 2.2.10. Set send_session_data option to false instead to not send any session data with exception and performance traces. For more information please read about request session data filtering.