This is what I do for the one banking app that wont work as is. And I turn it off when I am done. I also only use it on a profile design for Google Play Services--for apps that will only work with Google Play Services and apps that will be tracking me anyway (i.e. the Amazon's and Venmo's of the world). There are no Google Play apps or apps that wont work with the hardened security features on my Owner profile nor that I use on a regular basis.
Exploit Protection Compatibility Mode on GrapheneOS disables certain security protections that may interfere with specific apps, such as banking applications, which can crash or fail to launch due to the OS's strict security hardening.
When you enable this mode for your bank app, GrapheneOS relaxes some of its exploit protection features, including:
Memory hardening (e.g., hardened_malloc, which prevents memory corruption exploits).
Restricted access to system resources that apps might use in ways that trigger security blocks.
This allows the bank app to function by removing compatibility barriers caused by GrapheneOS’s enhanced security. However, it reduces the app’s security by allowing it to bypass protections that are designed to prevent exploitation.
⚠️ Important: This mode should only be enabled for apps that require it to work, and it’s recommended to keep it off for other apps to maintain maximum security.
You can find the setting at:
Settings > Apps > [Your Bank App] > Exploit protection compatibility mode
This is a known workaround—many banking apps (e.g., CapitalOne, Chase, Rabobank, HDFC) have been reported to work only with this mode enabled. If your app works with it, you’re not alone. The GrapheneOS team encourages users to report such issues to app developers to improve long-term compatibility without sacrificing security.