Compatibility/Feature request: Default disable filtering (not VPN) for ASB Mobile banking app #18
Description
This is a follow-up to #15, which was closed, but I don’t think the specific request was addressed.
I am asking for ASB Mobile (nz.co.asb.mobile) to be excluded from filtering by default, while still being routed through AdGuard.
In AdGuard for Android this corresponds to:
- Route traffic through AdGuard = ON
- Filter traffic = OFF
This keeps the app inside the VPN (DNS, routing, leak protection) while preventing AdGuard from blocking or modifying the app’s network traffic with filter rules.
Rationale
ASB Mobile is a banking application and communicates with multiple backend, security and fraud-detection endpoints. Some of these are covered by common filter lists, which can cause the app to behave differently compared to a normal, unfiltered connection even if it does not fully break.
On non-rooted Android devices, HTTPS filtering is not active for ASB anyway, so this request is not about TLS interception. It is specifically about DNS/IP/SNI-level filtering interfering with a banking app’s normal operation.
In addition, for a banking app it is generally desirable that traffic is not inspected, modified, or pattern-matched by a content-filtering layer, even when routed through a VPN.
AdGuard already treats banking apps as special cases for HTTPS interception on rooted devices. I am requesting the same principle be applied to normal filtering on non-rooted devices: ASB should remain routed through the VPN, but not have its traffic blocked or modified by filter rules.
Accordingly, ASB Mobile should be placed on the default filtering exclusions list.