The privacy-centric period tracking app, Periodical, faces an uncertain future on standard Android devices as its developers stand firm against Google’s new developer verification policy. Set to take effect in September, this policy mandates that all app developers publishing on certified Android devices submit government-issued identification directly to Google.
Developers Take a Stand
In a recent in-app notice, Periodical made it clear that they will not comply with this requirement. The developers have expressed their fundamental disagreement with the mandate, opting instead to withdraw from the official ecosystem altogether. This decision reflects a broader trend among open-source developers who are increasingly resistant to these emerging regulations. The potential loss of a vital reproductive health tool like Periodical raises significant concerns about user privacy and access to essential services.
Periodical has garnered praise from Consumer Reports for its commitment to user privacy, storing data exclusively on local device storage without employing any third-party trackers. This feature is particularly crucial for users today, as the risk of law enforcement weaponizing digital health data through subpoenas looms large in certain U.S. states, potentially placing women in precarious legal situations.
User Reactions and Future Directions
In light of the recent developments, users are now in a state of uncertainty. The in-app notice was shared across popular subreddits such as r/TwoXChromosomes and r/privacy, prompting discussions about alternative solutions. Currently, Periodical is directing users to its GitHub repository for future updates, encouraging them to bypass the official app store and install the application directly.
However, this workaround may not be sustainable in the long term. The forthcoming changes to Android’s policy will introduce significant barriers to sideloading unverified apps. Users will soon need to enable Developer Options and navigate through complex system settings to permit the installation of unverified packages. After confirming they are not being coerced, they will face a mandatory 24-hour cooling-off period before their device allows the installation.
This added complexity is likely to deter many casual smartphone users from taking the necessary steps to log their menstrual cycles. The irony of Google’s aggressive stance—removing a legitimate privacy tool from mainstream devices under the guise of user security—has not gone unnoticed. Users simply seek a secure and private method to track their health without the intrusion of corporate surveillance or the threat of legal repercussions. Now, they find themselves caught between navigating intricate Android developer settings or reverting to traditional pen and paper methods.
