# Building Two Android Privacy Vaults: Encryption, Decoy PINs and App Disguise ## Itroduction: Privacy Is Not One Problem When developing privacy-focused Android applications, one important lesson became clear to me: **Protecting stored files and making access to those files discreet are related, but different, engineering problems.** An encrypted vault can protect photographs and documents from unauthorized access. A disguised application interface can reduce unwanted attention during everyday phone use. But neither mechanism replaces the other. This distinction influenced the development of two Android applications at TSI Dev Studio: - **Xsilent**, a private vault focused on access control, encrypted files and privacy-oriented sharing. - **MicutVault**, a local-first vault focused on discreet access through nine disguise modes. Both applications were built independently, but they share the same privacy-first philosophy. In this article, I'll explain the design decisions behind the two products, the security layers they emphasize and why I chose to keep them separate. ## 1\. Start With the Threat Model Before discussing encryption algorithms or interface design, it helps to consider what an application is intended to protect against. For a private Android vault, several situations matter. **Scenario A: Casual access to personal files** Someone borrows an unlocked phone and opens the gallery or file manager. The goal is to keep private content separate from ordinary browsing. **Scenario B: Someone notices a vault application** A recognizable private-vault icon attracts attention. The goal is to make access to the application less conspicuous during normal device use. **Scenario C: Sensitive information leaves the device** A photograph is shared with another person, exposing faces, background details or location metadata. The goal is to reduce unnecessary information disclosure before sharing. **Scenario D: Accidental deletion or device migration** Files are deleted or need to be restored from a backup. The goal is to support recovery without unnecessarily exposing private content. These scenarios do not all have the same solution. Encryption, authentication, disguise interfaces, image sanitization and encrypted backups address different risks. That is the foundation of the two applications. ## 2\. Xsilent: Encryption and Controlled Access [Xsilent Vault: Hide Photos](https://tsidevstudio.com/apps/xsilent) emphasizes protection and control inside the application. It supports private photos, videos, PDF documents and other files. One of its core security mechanisms is local authenticated encryption using AES-GCM. AES-GCM combines confidentiality with integrity protection, helping detect unauthorized modifications to encrypted data when implemented and used correctly. However, encryption is only one part of the user experience. Xsilent also supports a Master PIN and a separate Dynamic Decoy PIN. ### Why a Decoy PIN? Traditional vault applications commonly expose one protected storage area after successful authentication. Xsilent introduces a second, separate content space. The Master PIN accesses the primary vault, while the Decoy PIN opens an alternative gallery. This can provide a different visible experience without revealing the primary content. A Decoy PIN is not a guarantee against coercion or sophisticated forensic examination. It is an additional interface-level privacy mechanism. ### Privacy Doesn't End When a File Is Shared Xsilent also includes Clean Share functionality. Consider a photograph that needs to be shared publicly. Even when the original file is safely encrypted inside a vault, the exported image can expose information through visible content or metadata. Clean Share provides tools such as: - Face blurring. - Manual blurring of selected areas. - Removal of sensitive metadata. - Optional watermarking. These features address a different privacy boundary: the moment information leaves protected storage. Xsilent additionally includes encrypted backups, encrypted Trash, private PDF viewing and configurable locking features. Its focus is broader than simply hiding photographs. **Xsilent's design priority is controlled handling of private content throughout its lifecycle.** ## 3\. MicutVault: Disguise as an Additional Privacy Layer [MicutVault](https://tsidevstudio.com/apps/micutvault) approaches the same general problem from a different direction. Instead of centering the experience on a recognizable vault interface, it offers nine disguise modes: 1. Calculator 2. Notes 3. Books 4. Files 5. Calendar 6. Clock 7. Tasks 8. Scanner 9. Recorder The Calculator disguise is a particularly useful example. It performs ordinary mathematical calculations while also providing a PIN-based route to protected content. The goal is to create a more discreet everyday interface. Behind the protected access layer, users can manage private photos, videos, audio files and notes. MicutVault also includes: - PIN authentication. - Optional biometric unlocking. - Configurable automatic locking. - Optional intruder detection. - Temporary lockouts after repeated incorrect PIN attempts. - Encrypted Trash with a 30-day retention period. - Encrypted backup options. ### Disguise Is Not Authentication This is an important distinction. Changing the appearance of an application is not equivalent to securing its data. A calculator-like interface can make a vault less noticeable, but it does not replace encryption, authentication or device-level security. The application may also remain identifiable through Android settings or installation records. Therefore, disguise should be understood as an additional privacy layer rather than an absolute security guarantee. **MicutVault's design priority is discreet everyday access combined with protected local storage.** ## 4\. What Both Applications Have in Common Although their interfaces and priorities differ, both projects share several architectural principles. ### Local-First Storage Private vault content is intended to remain on the Android device instead of depending on a mandatory cloud account. This reduces unnecessary reliance on remote services for core functionality. However, local-first design does not eliminate the need for device protection, secure backups or careful handling of exported files. ### Authentication and Access Control Both applications provide PIN-based access and optional biometric authentication. Authentication protects access to the vault, while encryption protects stored data. These mechanisms complement each other. ### Recovery and Backup Both products include encrypted backup options and encrypted Trash functionality. Recovery is an important part of privacy software because protecting information also means reducing the risk of accidental loss. ### No Mandatory Account or Advertising Neither application requires an online account for its core vault experience, and neither relies on in-app advertising. The goal is to reduce unnecessary dependencies in software intended to handle personal content. ## 5\. Why I Didn't Combine Everything From a development perspective, combining all features into one application initially sounds attractive. One codebase. One product. One listing. But product simplicity is not determined only by the number of repositories or applications. A single application offering Decoy PIN, PDF viewing, image sanitization, audio notes and nine disguise modes could become harder to navigate and maintain as a coherent user experience. Different users also prioritize different workflows. Someone managing private documents and preparing photographs for sharing may prefer Xsilent. Someone interested in a calculator-style interface with private audio and notes may prefer MicutVault. Keeping the products separate allows each one to evolve around a more focused purpose. There is a tradeoff, of course. Two applications require additional maintenance, testing, documentation and release management. But the separation also encourages clearer design decisions. Not every useful feature belongs in every product. ## 6\. The Difference in Monetization The applications also use different pricing models. **Xsilent** offers a free version with an optional one-time Lifetime upgrade. **MicutVault** is completely free in its current public launch version. Neither uses recurring subscriptions for its current offering. For privacy software, pricing clarity matters. Users should understand what they can access and whether payment is required before deciding to rely on an application for personal content. ## 7\. Lessons From Building Privacy-Focused Android Apps Building Xsilent and MicutVault reinforced several lessons. **First, encryption is necessary but not sufficient.** A protected file can still expose information when intentionally shared. **Second, interface discretion and cryptographic security are different concepts.** A disguised application is not automatically a secure application. **Third, recovery deserves attention.** Encrypted backups and recoverable deletion can improve practical data protection. **Fourth, security claims should remain realistic.** No mobile application can guarantee absolute privacy against every threat, especially on a compromised device. **Finally, a focused product can be more useful than one containing every possible feature.** A clear problem statement helps determine what belongs in an application and what does not. ## 8\. Explore the Two Projects ### Xsilent — Private Android Vault Designed around encrypted file protection, Decoy PIN, Clean Share and private PDF support. **Official website:**\ **Google Play:**\ ### MicutVault — Disguised Android Vault Designed around nine disguise modes, calculator-style access and private storage for photos, videos, audio and notes. **Official website:**\ **Google Play:**\ ### About TSI Dev Studio TSI Dev Studio is an independent Android development studio based in Romania. We focus on privacy-conscious applications, practical tools and local-first functionality where appropriate. **Official website:**\ **Official blog:**\ **Original comparison article:**\ ## Final Thoughts Xsilent and MicutVault were developed around two different ideas. One emphasizes control over private content. The other emphasizes discreet access to that content. Both are attempts to address real privacy needs without claiming that a single technical feature can solve every security problem. For other Android developers, I think the broader question is worth discussing: **When two features solve related but distinct problems, is it better to combine them into one application or build two focused products?** I'd be interested to hear how other developers approach that tradeoff. --- *Written by TSI Dev Studio — Independent Android App Development, Romania.*