arkhangelpilot

Mobile Application Developer — Secretly, Secure Messenger

Secretly • Self-employed

Feb 2026 - Present • 6 mos

Secretly is an end-to-end encrypted messenger. I designed, built and published it to the App Store and Google Play as sole developer, owning the product from architecture through store release and maintenance. SECURITY ARCHITECTURE End-to-end encryption with client-side key generation and storage, so message content is never readable server-side. Key material handled through the iOS Keychain and Android Keystore rather than application storage. Encrypted local message database. Data model designed to collect as little as the product can function on. STORE COMPLIANCE An encrypted messenger is one of the hardest categories to get through review, and most of that difficulty sits outside the code: - Encryption export compliance declarations, which most developers meet for the first time when their build is held - User-generated content safety requirements Apple applies to any messaging product - iOS privacy manifest and App Privacy nutrition labels that had to match real behaviour precisely, on a product whose entire premise is privacy - Google Play Data safety declarations covering the same ground - Permission purpose strings written so a reviewer understands why each one is requested - In-app account deletion, now required by both stores - Third-party SDK disclosure - the item most teams miss, because the collection happens inside dependencies rather than their own code RELEASE Signing, provisioning and versioning on both platforms, store listings and screenshots, submission, and handling reviewer questions through to approval on iOS and Android. Stack: Secretly is a cross-platform end-to-end encrypted messenger built with Flutter and Dart for Android, iOS, macOS and Windows, backed by a Rust server stack. The client runs to roughly 300,000 lines of Dart across five platforms and includes SQLCipher-encrypted local storage, a pluggable cryptography layer with both a pure-Dart and a Rust FFI implementation (X25519, HKDF, HMAC, ChaCha20-Poly1305), WebRTC a