Security review · November 17, 2026
A review you can
read for yourself.
An initial AI-assisted review examined selected parts of Hirasa’s security code and test evidence. Here is what it covered—and what remains unresolved.
AI-assisted source review. Two findings remain open.
Hirasa has not yet had an independent security audit. This review is not a certification or an approval by ChatGPT or OpenAI.
What was checked
The review examined selected code paths for vault encryption, unlocking and recovery, duress wipe, backups, file transfers, temporary files, app locking, managed sharing and purchase validation.
It was performed with ChatGPT as part of Hirasa’s development work, not by an independent auditor. It covered source version 0.6.2+11, at this exact commit:
411abd75b1f43dca45da0951767f86aa9e2b5b13
It does not automatically apply to later builds.
What the tests show
- 7 server tests passed when run locally using synthetic data and a temporary database.
- 123 app tests passed in existing GitHub CI for the reviewed commit. Those results were inspected; the app tests were not independently rerun during this review.
- An additional local check confirmed a sharing-limit issue that the existing tests did not cover.
Passing these tests is evidence about the cases tested, not proof that the app is secure.
What remains open
- Camera temporary-file cleanup. Source inspection identified a failure path that needs stronger cleanup. Physical-device verification remains outstanding.
- Managed-sharing limits. A publishing-limit weakness was reproduced with disposable local data. It still needs remediation and retesting.
Both findings were open at the end of this review. Detailed reproduction steps are held in the private engineering report while the issues are addressed.
Where this review stops
No physical Android or iPhone security testing, production infrastructure assessment, full dependency vulnerability review, or independent human audit was completed as part of this review. It does not establish protection against every attack or guarantee forensic erasure.
The next steps are to fix and retest the findings against a named new build, complete device and release checks, and obtain an independent assessment before making an independent-audit claim.
If you lose both your pattern or passphrase and your recovery key, that vault is gone for good.