Should I choose open-source over closed-source for a period tracker

If you have the technical ability to read code or trust community auditors, open-source (Drip) provides the strongest verifiable privacy guarantee. If you value a polished experience and are willing to trust architecture claims verified by network monitoring, closed-source on-device apps (Floriva) are reasonable.

Is Floriva planning to become open-source

We are evaluating it. Open-sourcing the client would allow community audits of our privacy claims. The core architecture decision, on-device storage with no server component, is verifiable via network monitoring regardless of source availability.

What about browser-based period trackers

Web apps that store data in localStorage or IndexedDB are technically on-device. However, any JavaScript on the page can access this data, and browser extensions can read it. A native app with OS-level sandboxing provides stronger isolation than a browser-based tracker.

listicles

Best Privacy-First Period Trackers for Tech-Savvy Users

We compared 5 period trackers on architecture, not marketing claims. Evaluated SDK footprint, data storage, and network behavior.

How We Evaluated This is not a feature comparison. We evaluated each app's privacy architecture using four technical criteria: data storage location, third party SDK presence, account requirements, and offline functionality. We gave zero weight to privacy policy language because policy and architecture are independent variables, as Flo's FTC settlement demonstrated. For each app, we tested offline functionality (airplane mode), reviewed publicly available information about SDK inclusion, checked account requirements, and reviewed data storage documentation. For Drip, we also reviewed source code. The SDK Problem Most Reviews Ignore Most "privacy focused" period tracker reviews evaluate privacy policies. They do not check what third party code is running inside the app. A period tracker can have a perfect privacy policy while embedding Firebase Analytics (Google), Adjust (mobile attribution), or Facebook SDK. Each of these independently collects device data and usage patterns. These SDKs create data flows that bypass the app's own privacy controls. The app developer may not even fully understand what data the SDKs collect, because SDK behavior is controlled by the SDK provider and c