Privacy-First Period Tracking: Developer Launches "Mori" to Combat Reproductive Data Surveillance Amid Post-Roe Realities
![]()
By Tech & Privacy Desk
Published: October 2023
Main Facts
In an era defined by aggressive corporate data collection, continuous user tracking, and mounting legal vulnerabilities surrounding reproductive rights, independent developer Alfred Chaos has officially launched the first public version of Mori, a privacy-centric Android period tracking application. Unlike the vast majority of health and wellness applications dominating the market—which routinely require mandatory user accounts, cloud-based data storage, and constant internet connectivity—Mori has been engineered from the ground up with a singular, uncompromising rule: no accounts, ever, for core features.
The core architecture of Mori abandons the traditional server-side data model. Instead, all sensitive personal health logs, cycle histories, and calendar markers reside exclusively within a local SQLite database stored securely on the user’s physical device. Because the application operates entirely offline by default, no reproductive health data ever leaves the smartphone.
Key facts regarding the launch of Mori include:
- Zero-Account Architecture: Core logging, tracking, and prediction tools require zero registration, email collection, or password creation.
- Local-First Processing: Cycle predictions are computed directly on the device using transparent, deterministic mathematical formulas based strictly on the user’s personal history, completely avoiding black-box machine learning algorithms or cloud analytics.
- Radical Transparency on Telemetry: The mobile application contains absolute zero in-app analytics or third-party trackers. A single Google Analytics 4 (GA4) script exists solely on the external marketing landing page to measure incoming web traffic.
- Monetization via Buy-Once Model: All core functionalities are completely free forever. An optional, one-time purchase of $3.99 unlocks encrypted cloud backups, departing from the ubiquitous subscription fatigue model.
- Current Availability: Mori is currently distributed as a side-loaded APK directly via its official website (
moricycle.com), bypassing official app stores for its initial launch phase, with an iOS version slated for future development.
Chronology
The journey toward the creation of Mori is rooted in a growing frustration with the surveillance economy that governs modern mobile software.
The Catalyst: The Post-Roe Landscape
The foundational philosophy of Mori was crystallized in the wake of the United States Supreme Court’s decision to overturn Roe v. Wade. Almost immediately, legal experts, digital rights organizations, and government agencies—including a direct warning from the White House—highlighted a terrifying vulnerability: reproductive health data stored on corporate servers could be subpoenaed by law enforcement agencies in states where abortion has been criminalized or restricted.
Mainstream period-tracking apps, many of which monetize user data through targeted advertising or routinely comply with law enforcement data requests, suddenly transformed from benign wellness utilities into potential digital paper trails for state prosecutors.
Development and Architectural Design
Confronted with this reality, independent developer Alfred Chaos spent months conceptualizing a counter-model. Rejecting the notion that cloud synchronization must be mandatory for software to function, the developer prioritized a "local-first" software engineering philosophy.
During the design phase, significant friction arose over marketing terminology—specifically spending weeks deliberating over the precise use of the word "private" on the landing page to ensure absolute honesty with users regarding the boundaries of data security.
Public Release and Current State
This week marked a major milestone with the release of the first public build of Mori. Eschewing the traditional hurdles and review processes of the Google Play Store for its initial rollout, the developer made the application available directly to early adopters as a side-loaded APK via the project’s official website. While the Android version continues to gain traction, planning for an iOS equivalent has officially begun, though development has not yet formally commenced.
Supporting Data
To understand the market disruption Mori represents, it is vital to examine the data privacy practices of legacy period-tracking applications and the technical mechanics underlying Mori’s architecture.
The Legacy Tracker Ecosystem
Industry analyses of popular free period-tracking apps reveal a troubling trend:

- Data Sharing: Numerous widely downloaded trackers have historically integrated software development kits (SDKs) designed to share device identifiers, IP addresses, and specific app usage behaviors with third-party data brokers and social media platforms.
- Mandatory Cloud Storage: Most applications require users to create an account tied to an email address or social login before viewing even a basic calendar interface. This architecture inherently pulls local bodily data into centralized cloud servers controlled by corporate entities.
- Subpoena Vulnerability: Server-side data is subject to legal discovery. If law enforcement serves a warrant or subpoena for user logs during a criminal investigation into suspected illegal medical procedures, companies holding that data on remote servers have historically complied.
Mori’s Technical Architecture
Mori addresses these vulnerabilities through a bifurcated structural design:
-
The Free, Local Tier:
- Database: SQLite on-device storage.
- Analytics: 0% in-app tracking.
- Predictive Logic: Deterministic math. Rather than utilizing opaque AI or machine learning models that harvest aggregate data to predict user behaviors, Mori calculates upcoming cycles using transparent averages of past entries. Every prediction is paired with an explicit confidence label and a plain-language explanation of how the estimate was derived.
-
The Optional Paid Tier ($3.99 One-Time):
- Cloud Sync: For users who fear losing their phone or wish to transfer data between devices, Mori offers an optional backup feature.
- Encryption Protocol: Snapshots are encrypted directly on the device using a Data Encryption Key (DEK) before any data is uploaded to the backend server (built on a robust Go and Postgres stack).
- Honest Limitations: Crucially, the developer explicitly refrains from calling this architecture "end-to-end encrypted" in technical documentation. Because the server retains the ability to unwrap the DEK during account recovery processes, absolute zero-knowledge encryption cannot be claimed. This candid transparency is a deliberate pushback against the "security theater" frequently utilized by major tech companies.
Official Responses and Developer Insights
The launch of Mori has sparked significant discussions within developer communities and privacy advocacy spaces regarding ethical software design, data minimization, and user trust.
When questioned about the decision to avoid Google Play for the initial release, the developer pointed to the friction and gatekeeping often associated with traditional app store bureaucracies, choosing instead to establish a direct relationship with users through direct-download APK distribution.
Furthermore, the developer’s approach to the optional cloud backup feature has drawn praise from security purists. In software engineering, claiming "end-to-end encryption" has become a marketing buzzword often abused to imply absolute security where backdoors or recovery keys exist. By openly admitting that the backend server can unwrap the DEK during account recovery, Alfred Chaos has set a refreshing benchmark for professional accountability.
Privacy advocates have consistently argued that software creators must shoulder the moral burden of protecting vulnerable populations. By designing an application that treats reproductive data not as an asset to be monetized or analyzed, but as private personal property that should never leave the physical possession of its owner, Mori serves as a case study in ethical product design.
Implications
The introduction of Mori carries profound implications for the future of health-tech app development, digital privacy activism, and user expectations.
1. A Blueprint for Data Minimization
Mori proves that modern applications do not need to harvest user telemetry, maintain persistent cloud databases, or demand mandatory user accounts to deliver functional, high-quality software. By demonstrating that local-first architecture is both viable and economically sustainable via a simple buy-once monetization model, Mori challenges the extractive business models of venture-backed startups that view user data as the primary product.
2. Legal Resilience for Reproductive Rights
As legislative attacks on bodily autonomy persist across various jurisdictions, tools like Mori provide a vital shield. By ensuring that cycle data physically cannot be subpoenaed because it exists nowhere outside the user’s pocket, the application offers tangible legal protection to individuals navigating hostile legal landscapes. It transforms a smartphone from a potential surveillance device back into a private personal tool.
3. Rebuilding Trust Through Radical Honesty
The tech industry is plagued by pervasive distrust, driven by complex privacy policies, hidden trackers, and misleading security claims. Mori’s commitment to radical honesty—from declining to use buzzwords like "zero-knowledge" when recovery keys exist, to maintaining absolute transparency regarding web-only analytics—demonstrates that honesty can be a powerful competitive advantage for independent developers.
Looking Ahead
While Mori currently serves Android users via direct downloads and faces the ongoing challenge of expanding to iOS and mainstream app stores, its underlying philosophy is already making waves. As users grow increasingly weary of subscription fatigue, data breaches, and corporate surveillance, Mori offers a compelling glimpse into a more ethical, user-respecting technological future.
