Review UltraLocked's security model
This page is for security engineers, privacy researchers, iOS developers, and technical reviewers who want to inspect UltraLocked's architecture.
Scope
- Public .ultralocked bundle format
- Transfer bundle parser limits and tamper handling
- Documented key lifecycle and vault behavior
- Threat model and non-goals
- Disclosure handling for good-faith reports
Known limitations
- The public repository is not the full commercial iOS app.
- Public code cannot prove Apple Secure Enclave behavior or production App Store configuration.
- Unlocked-screen exposure, weak device passcodes, and operational mistakes are outside the app boundary.
- The public security core focuses on portable encrypted bundles and documentation.
Requested review areas
- Secure Enclave key lifecycle
- vault encryption and deletion semantics
- duress workflow edge cases
- encrypted transfer model
- metadata exposure
- recovery-key handling
How to report findings
Please report suspected vulnerabilities privately first. Include a concise description, affected component and version or commit, reproduction steps, impact, and any proof-of-concept files that are safe to share.
Email: security@ultralocked.com
Acknowledgement and hall-of-fame credit will be handled for good-faith reports when appropriate. Public listing is opt-in.
Reviewer Acknowledgements
Security reviewer hall of fame
Good-faith researchers who report valid issues can be credited here when they want public acknowledgement. No public acknowledgements have been published yet.
Awaiting first credited review