--- title: Around a dozen banking apps began specifically... description: Most banking apps work on GrapheneOS, according to the GrapheneOS team, though many have memory corruption bugs or incorrect anti-tampering code requiring... canonical: https://daily.dev/posts/around-a-dozen-banking-apps-began-specifically-permitting-grapheneos-pyf2v98id twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Around a dozen banking apps began specifically permitting GrapheneOS | daily.dev og:description: Most banking apps work on GrapheneOS, according to the GrapheneOS team, though many have memory corruption bugs or incorrect anti-tampering code requiring... og:url: https://daily.dev/posts/around-a-dozen-banking-apps-began-specifically-permitting-grapheneos-pyf2v98id og:image: https://api.daily.dev/og/posts/Pyf2V98Id.png og:image:alt: Around a dozen banking apps began specifically permitting GrapheneOS og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Around a dozen banking apps began specifically permitting GrapheneOS **[Hacker News](https://daily.dev/sources/hn)** · 3 min read · 0 upvotes · 0 comments ## Summary Most banking apps work on GrapheneOS, according to the GrapheneOS team, though many have memory corruption bugs or incorrect anti-tampering code requiring GrapheneOS's per-app exploit protection compatibility toggle. About 10% of banking apps are unavailable due to banning use of a non-Google-approved OS. Around a dozen banking apps began specifically permitting GrapheneOS alongside a Google-approved OS, a number that is growing. A crowd-sourced compatibility list at privsec.dev tracks which apps work. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Do banking apps work on GrapheneOS? Most banking apps work on GrapheneOS, though many have memory corruption bugs or incorrect anti-tampering code that require enabling GrapheneOS's per-app exploit protection compatibility mode toggle. About 10% of banking apps are unavailable because they detect and ban non-Google-approved operating systems. Around a dozen banking apps now explicitly support GrapheneOS alongside Google-approved OSes, a number that is growing. _Weighing a privacy-focused Android ROM against app compatibility risk? daily.dev surfaces real-world GrapheneOS reports like this._ ## Community take How the wider developer community reacted, aggregated from 1 discussion and 43 comments across hackernews (as of 2026-10-24). **TL;DR:** Commenters welcome banks starting to explicitly support GrapheneOS, seeing it as evidence of real security evaluation rather than blanket distrust, but many share stories of partial support, inconsistent app behavior, and frustration with banks that still ban non-Google-approved OSes. **Sentiment:** 35% positive · 40% mixed · 25% skeptical **The case for** - Several people report that apps explicitly supporting GrapheneOS tend to do so because security teams recognize it's more locked-down than stock Android, not less. - Some note it's easy to switch banks (at least in places like the UK) to ones that support GrapheneOS. - One commenter shares a partial list of banks/fintechs believed to support GrapheneOS by design. **The pushback** - Multiple commenters note support is inconsistent — working only in the main profile, only with certain app versions, or only with specific keyboards. - Some argue banks that ban alternative OSes do so purely to tick compliance/insurance boxes rather than for genuine security reasons. - One commenter objects to banks effectively requiring customers to run proprietary apps on their own hardware just to access their own money. - Concern that even banks who support GrapheneOS could revoke that support anytime since it's not usually guaranteed in the ToS. - Immigrants and non-citizens in some countries have far fewer banking options, making 'just switch banks' impractical. - Skepticism about whether banning alternative OSes actually correlates with reduced fraud, with no clear evidence found. **By community** - hackernews (mixed): Welcomes the trend of explicit GrapheneOS support as a sign of serious security thinking, while also detailing inconsistent real-world support and debating whether bank restrictions are driven by genuine security concern or compliance box-ticking. **Hottest debate:** Whether banks' restrictions on non-Google-approved OSes stem from genuine security/fraud concerns or just regulatory/insurance box-checking. **Open questions** - Is there actual data showing that using a non-Google/Apple-approved OS correlates with higher fraud or account compromise rates? - How stable is this support — could banks revoke GrapheneOS compatibility at any time since it's often not codified in their terms of service? - Why do some apps work only in the main profile, only with certain app versions, or only with specific keyboards on GrapheneOS? **Highlights** > In my experience with UK banks & financial institutions, GrapheneOS support can be roughly divided into four types. None. Explicitly banned. And, though I feel bad for saying it, I can't blame them. If some idiot roots their phone and downloads malware, the bank may be responsible for refunding them. I can see why they don't want that headache. Some. App works, but some functionality is unavailable. I've got a credit card app which works, but refuses to set up virtual cards or use "remember me". That's good enough for my use. Similarly, I had a merchant account which let me see my balance, but I couldn't use my phone as a credit card reader. Works, but only in main profile. I'd rather keep financial things in a locked profile. But lots of banks disallow that. Full. Everything works (although you may need to toggle some exploit protection off). Some banks are reasonably good at letting you pass on technical queries to their developers - mostly the smaller ones. The nice thing about the UK banking sector is that it is trivial to move banks. So I switched accounts to providers which worked with my phone and let the old ones know why I was moving. > — [edent on hackernews · 5 comments](https://news.ycombinator.com/item?id=50219929) > > None. Explicitly banned. ... I can't blame them. If some idiot roots their phone and downloads malware, the bank may be responsible for refunding them. I can see why they don't want that headache. I mean this is the whole reason GrapheneOS does not ship a rooted version that they attest to. I doubt they are explicitly banning GrapheneOS, what they are doing is only trusting Google attestation. The reason some banks explicitly allow GrapheneOS is because its easy for them to also trust GrapheneOS attestation, because it is not a rooted OS, and sensible security teams in banks can see that its more secure than any other Android phone including Pixels. I wish people would understand this better, its what gives GrapheneOS a fighting chance of becoming a legitimate open source mobile OS that is accepted as secure for consumer use and that is not controlled by Apple or Google. > — [justonenote on hackernews · 1 comments](https://news.ycombinator.com/item?id=50220215) > Thanks, but no thanks? I use GrapheneOS, but if you as a bank want to gate access to my money via some kind of technology, you better be including it as part of the account. For example, HSBC continues to let me manage my bank account via the web browser, and continues to offer a battery powered hardware token as the means of authentication. I let you hold my money, for whatever reason. Why do you expect me to be your distributed infrastructure provider? I am not going to let you require that I run your proprietary malware in order to access my own money. The idea where you are effectively _expected_ to constantly provide free compute for companies to run their complete garbage on hardware _you own_ just for the privilege of giving them money is one of the most absurd trend in recent times. I'd say that JS webapps are the same but at least there you run things on your terms in a sandbox that you can inspect and look at the requests, and there's no effective enclave carved out of your hardware (except for EME but that's another topic for another day and I'd be complaining if banks started to use it too). > — [Arch-TK on hackernews · 1 comments](https://news.ycombinator.com/item?id=50220325) > I found some evidence of half a dozen that there might be support 'by desogn' (all of them might pull the rug at any time again as far as I understand TOS, which however seems true for any android in theory): Swissquote, Yuh, UBS, Starling Bank, Triodos Bankieren NL, AmeriCU Credit Union. More? > — [riedel on hackernews](https://news.ycombinator.com/item?id=50220131) > Without evidence that using an OS that isn't approved by Google or Apple actually correlates with a higher rate of account compromise or fraud, I do blame them for trying to force it on users. I've done a couple casual web searches for such evidence and come up short. If somebody has good data on this, I don't think they're publishing it. > — [Zak on hackernews](https://news.ycombinator.com/item?id=50220227) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=50217495) · 167 points · 43 comments ## Similar posts on daily.dev - [GrapheneOS: "GrapheneOS is the only Android…"](https://daily.dev/posts/grapheneos-grapheneos-is-the-only-android--603x7gtcw) · Hacker News · 0 upvotes · 0 comments - [GrapheneOS Isn't Happy With Google Over Pixel's Widening Head Start](https://daily.dev/posts/grapheneos-isn-t-happy-with-google-over-pixel-s-widening-head-start-xbm7zxyim) · It's Foss · 1 upvotes · 1 comments - [GrapheneOS](https://daily.dev/posts/grapheneos-tqiuwjydb) · Hacker News · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#android](https://daily.dev/tags/android), [#privacy](https://daily.dev/tags/privacy) [View this post on daily.dev](https://daily.dev/posts/around-a-dozen-banking-apps-began-specifically-permitting-grapheneos-pyf2v98id) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Around a dozen banking apps began specifically permitting GrapheneOS","url":"https://daily.dev/posts/around-a-dozen-banking-apps-began-specifically-permitting-grapheneos-pyf2v98id","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/around-a-dozen-banking-apps-began-specifically-permitting-grapheneos-pyf2v98id"},"datePublished":"2026-10-24T10:19:25.657Z","dateModified":"2026-10-24T12:05:27.520Z","description":"Most banking apps work on GrapheneOS, according to the GrapheneOS team, though many have memory corruption bugs or incorrect anti-tampering code requiring...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/around-a-dozen-banking-apps-began-specifically-permitting-grapheneos-pyf2v98id","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,android,privacy","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Around a dozen banking apps began specifically permitting GrapheneOS"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/around-a-dozen-banking-apps-began-specifically-permitting-grapheneos-pyf2v98id#faq","mainEntity":[{"@type":"Question","name":"Do banking apps work on GrapheneOS?","acceptedAnswer":{"@type":"Answer","text":"Most banking apps work on GrapheneOS, though many have memory corruption bugs or incorrect anti-tampering code that require enabling GrapheneOS's per-app exploit protection compatibility mode toggle. About 10% of banking apps are unavailable because they detect and ban non-Google-approved operating systems. Around a dozen banking apps now explicitly support GrapheneOS alongside Google-approved OSes, a number that is growing. Weighing a privacy-focused Android ROM against app compatibility risk? daily.dev surfaces real-world GrapheneOS reports like this."}}]} ```