Zashi is a privacy-first pockets, and we take that significantly. Meaning gaining access to as little knowledge as potential, and being clear concerning the knowledge we’ve entry to, why it issues, and how one can management it. Right here’s what you’ll want to know:
What Knowledge We Accumulate
Zashi doesn’t acquire any knowledge. Like most software program apps, it makes use of crash experiences, enabled and generated on the working system degree, to assist our staff detect and repair bugs. However in contrast to most apps—even those who declare to prioritize privateness—Zashi doesn’t see or acquire another knowledge. Crash experiences are the one knowledge we will see, which is uncommon amongst app builders.
Crash experiences present restricted anonymized technical knowledge the only real goal of which is to observe the wholesome perform of the app. They assist make the pockets extra secure and usable, nothing extra.
Vital:
ECC and the Zashi builders don’t observe, view, or acquire your pockets exercise. When a crash report is generated, it affords restricted knowledge wanted to determine what triggered the crash. We don’t see or acquire names, emails, telephone numbers, contact lists, user-generated content material, or transaction particulars.
What Crash Report Instruments We Use
Crash experiences are saved and processed by Google (on Android) and Apple (on iOS), and like all apps on their platforms, we should observe strict guidelines about what knowledge is collected and the way it’s dealt with. Violating these guidelines would result in removing from their shops.
What Crash Reviews Do Not Include
Crash experiences are anonymized and solely embody technical diagnostics like machine kind, app model, time of the crash, stack hint (which a part of the code crashed), error logs, and working system model.
These experiences do not comprise:
Your transaction IDs or historical past
Pockets addresses
ZEC balances
Private info like identify, e-mail, or telephone
Consumer IDs tied to Zashi
Something that might hyperlink a transaction to a particular consumer
Crash experiences inform us how and when the app broke, not who it occurred to.
Can You Choose Out?
Sure, in a number of methods:
iOS customers:
Apple permits customers to choose out of diagnostic knowledge sharing throughout all apps. You are able to do this in your iPhone settings. iOS doesn’t permit customers to choose out for particular person apps.
Android customers:
Google doesn’t permit builders or customers to opt-out from the default Google Play Providers knowledge assortment for Android Vitals.
To choose out, Android customers can obtain Zashi by way of F-Droid. The F-Droid model of Zashi is basically totally different from the Play Retailer model: it’s fully freed from proprietary analytics and crash reporting instruments.
Enhancements:
We already entry far much less knowledge than most apps, however we’ve taken extra steps to restrict knowledge assortment even additional:
For iOS, we’ve eliminated Firebase Crashlytics fully (Zashi iOS v1.5.2).
We’ve carried out a risk to opt-out of Firebase Crashlytics for Android. Customers can choose out of sharing crash experiences in Zashi’s Superior Settings. (Zashi Android v1.5.2)
For Android, we’ve set Firebase Crashlytics to be “Off” by default. Customers can select to choose in by means of Zashi’s Superior Settings or the pockets’s standing widget. (Zashi Android v2.0)
We’ve up to date the F-Droid model, eradicating the inaccurate safety warning, which falsely implied that the F-droid model collects crash experiences. That was by no means the case.
F-Droid & GitHub: Full Transparency
Zashi is out there on F-Droid, an impartial app retailer that prioritizes open-source, privacy-respecting software program. In contrast to conventional app shops, F-Droid doesn’t observe or profile customers, and it permits for fully nameless downloads. The F-Droid model of Zashi is totally open-source and consists of no crash reporting instruments in anyway.
The F-Droid Zashi construct is totally reproducible, and we encourage our group to construct it and confirm our work. This helps establish and mitigate potential threats to our infrastructure, processes, and the third-party providers we rely on.
You can even construct the app your self from supply.
Zashi code is totally open supply and out there on GitHub:
Learn extra about alternative routes to obtain Zashi pockets.
Philosophy: Privateness by Design
Many wallets declare to prioritize privateness, whereas quietly gathering analytics and consumer conduct. Zashi doesn’t simply declare it—we dwell it.
We don’t see or acquire consumer and app knowledge. We don’t profile customers. We don’t observe their exercise. And we exit of our option to reduce metadata leakage. Zashi is constructed by the identical staff that created and maintains the Zcash protocol—probably the most superior privateness tech within the blockchain trade. We apply the identical requirements to app improvement that we do to protocol-level privateness.
We welcome scrutiny—particularly in privateness tech. However conversations about privateness and consumer security have to be grounded in details, not worry or hypothesis. We encourage customers to use the identical excessive requirements to all of the apps and wallets they use, and to demand transparency and alter when these instruments fall brief.
Our dedication to Zashi customers is unwavering.
Shields up.
