LOG_REF: 2026.02.10

Subpoena-Proof by Design | Locikit Technical Bulletin

SOURCE: Locikit System 2 MIN READ
Subpoena-Proof by Design | Locikit Technical Bulletin
![Subpoena-Proof by Design](../../assets/blog/subpoena-proof-cover.svg)

In the current legal landscape, the privacy of reproductive health data is no longer a theoretical concern—it's a matter of safety. For users of period and pregnancy trackers, the threat of digital surveillance and data subpoenas is real. At Locikit, we engineered Luna to be fundamentally subpoena-proof.

What You Don't Have, You Can't Give

The simplest way to protect user data from legal overreach is to never possess it. Most health apps store your data on their servers, making them a target for law enforcement requests. If a company receives a subpoena for your records, they are legally compelled to comply.

Locikit takes a different approach: We have nothing to give. Because Luna operates 100% offline, your health metrics, journals, and predictions never touch our infrastructure. There is no database for us to search, no server for us to hand over.

The Legal Void

In a subpoena-proof architecture, the developer is legally and technically decoupled from the user's data. This creates a "Legal Void"—a space where surveillance cannot penetrate because there is no intermediary to intercept. By removing the central point of data aggregation, we eliminate the primary vector used for digital dragnets and broad discovery requests.

Hardware-Level Security

Even if a device is physically seized, your data in Luna remains protected through multi-layered defense. We utilize the Apple Secure Enclave and Android StrongBox to ensure that encryption keys never leave the hardware security module (HSM).

// Hardware Security Integration KeyStore.getInstance("AndroidKeyStore").apply { generateKey( KeyGenParameterSpec.Builder( "luna_root_key", PURPOSE_ENCRYPT | PURPOSE_DECRYPT ).setUserAuthenticationRequired(true) .setIsStrongBoxBacked(true) .build() ) }

By requiring biometric authentication for every decryption event, we ensure that even a compromised device cannot reveal its secrets without the user's active presence.

  • Secure Enclave Integration: Encryption keys are isolated from the main application processor.
  • AES-256-GCM Encryption: All local databases are encrypted with per-record nonces to prevent pattern analysis.
  • Zero-Metadata Logging: Luna does not generate internal logs that contain sensitive identifiers, ensuring no "digital breadcrumbs" are left behind.

The Responsibility of the Developer

As developers in 2026, our responsibility has shifted. We are no longer just building tools; we are building shields. By prioritizing local-first architecture and hardware-backed security, we ensure that your most intimate data remains exactly where it belongs: under your absolute control, protected by the very silicon it lives on.