hungrily6100 Yeah, I personally always feel slightly frustrated when CSRs send me canned replies. On the other hand, in this case they did agree to forward it to developers (I hope that's what they meant by "team"), which is more than most CSRs usually do, in my experience. I try to keep in mind that the canned responses are usually lines (or variations of them) that they are obligated to provide, so I'll usually be receiving them anyway.
Yeah, that's verbatim the response I received from the CSR I chatted with a few days ago. However, when I kept pushing the matter the CSR agreed to forward my feedback to the development team. Here's what I wrote after receiving their first canned response. Note that I might've just got lucky in that the CSR was slightly more customer-oriented in general. And also, if someone's contacting Revolut about this, please don't use this text verbatim, as they might get suspicious that we are (or that I am) spamming them on the matter:
I am aware that GrapheneOS is not officially supported. However, it has never been officially blocked, up until now. It appears that the Android app version 10.56 is now blocking new sign-in attempts. This is not only my observation but is being observed by all GrapheneOS users I have talked with who have attempted to sign in. They have been locked out of your service.
For background: GrapheneOS is not an
operating system that's certified by Google but is still closely based on Android. The Revolut app works fine on GrapheneOS when already signed in, and has always worked fine for me, except that the app is now blocking new sign-in attempts. I use GrapheneOS because it focuses extensively on users' privacy and security, and builds on Android's own security and privacy features while also strengthening them. I very much care about the security of my device and I'll be unable to use your product if you block GrapheneOS.Your developers can allow GrapheneOS specifically by following this guide:
https://grapheneos.org/articles/attestation-compatibility-guideTo summarise: GrapheneOS is keeping fully up to date with the latest Android patches and versions, and has pioneered security features that Apple has now integrated into iOS, such as auto-reboot and contact scopes. There's no reason that the app should allow users to run it on Android 7 - which has not received security updates for years - but block an OS that's recognized for its security features and implements the full Android security patches each month.
Kindly asking that my feedback be forwarded to the
development team for consideration.