A wallet asks for more trust than almost any software you run. Satra answers with the only honest currency: the code itself — every screen, every key-derivation path, every sync call, public under Apache 2.0.
Kotlin and Jetpack Compose, in the open. How wallets are derived, how the local database is protected, which providers get called — it’s all on the page, not in a policy.
“No analytics SDKs” is a claim you can grep. Check the dependencies, search for trackers, read the sync code. Our security and privacy pages cite the repo — not the other way around.
Apache 2.0 means you may use, modify, and redistribute Satra — build your own, audit ours, or keep a copy forever. Openness that survives us is the point.
Not just the app. The supported-asset list, the brand system, the legal documents, even this website — versioned together, so every claim has a diff and every change has a history.
When the privacy policy changes, you don’t re-read it and guess. You read the commit.
A closed wallet asks you to believe. An open one lets you — or anyone more paranoid than you — confirm. That’s the difference between marketing and evidence, and it’s why openness is a security feature, not a licensing detail.
Read how Satra is securedUse it, study it, change it, ship it. One honest caveat from our own terms: open source is transparency, not a warranty — it doesn’t make Satra a custodian, an advisor, or infallible.