Late one night in April 2026, I was sitting at my desk reading an investigative breakdown on consumer health apps. What I found was genuinely disturbing.

Women's most intimate biological data—exact menstrual cycle lengths, ovulation dates, physical symptoms, sexual activity logs, and pregnancy intentions—were routinely being harvested by third-party SDKs and quietly broadcast to advertising data brokers, Facebook Graph APIs, and analytics aggregators.

Think about that for a second. The exact day someone misses a cycle or logs pregnancy symptoms is packaged into an unencrypted telemetry bundle, tagged with an advertising ID, and auctioned off to targeted ad networks and insurance algorithms. And to add insult to injury, the apps doing this routinely demand mandatory email signups, bombard phones with notification spam, and lock basic cycle history behind predatory $60-a-year paywalls.

As a builder, my immediate reaction was simple:

Why does a personal health tracker need 15 tracking SDKs and a $60 paywall?

It doesn't.

So I sat down, opened an empty editor at Pixartual, and built Periodly—a cycle tracker designed from day one with an honest, modern stack: React.js on the frontend, IndexedDB for instant offline client caching, and Supabase strictly for essential data persistence. Zero ad brokers, zero telemetry auctions, and zero predatory paywalls.

Fast forward 5 months to September 17, 2026. Without spending a single dollar on paid ads, influencer sponsorships, or marketing agencies, Periodly crossed 1,500 active users.

Here is the unfiltered breakdown of how we built it, the architecture that made it scale effortlessly, and why building with dignity is the highest-leverage growth strategy in modern software.


1. The Anatomy of Mainstream Health Tech vs. The Periodly Standard

To understand why 1,500 people chose a scrappy indie web app over multi-million-dollar VC-backed cycle trackers, you have to look at what the mainstream health tech landscape has turned into.

Feature / MetricTypical Mainstream Cycle AppsThe Periodly Standard
Data Storage & SyncOpaque cloud silos vulnerable to breaches & data brokersSupabase (Core Data) + IndexedDB (Fast local caching)
Telemetry & SDKsMeta Pixel, Google Analytics, AppsFlyer, data brokers0 Bytes Sold (Zero tracking scripts or surveillance cookies)
Offline ResilienceBreak or nag when offline or travelingInstant PWA Cache (Works seamlessly offline via IndexedDB)
Pricing Model$50 – $70 / year subscriptions for basic stats100% Free Core Features (No paywalled health insights)
Platform Access200MB native app downloads with App Store lock-inReact.js PWA (Sub-second load, works on any phone or desktop)

Mainstream cycle apps don't treat users as customers; they treat them as high-margin behavioral telemetry feeds.

When you strip away the predatory ad broker SDKs, intrusive notifications, and endless upsells, health tracking is fundamentally about giving people clarity and peace of mind over their bodies.

Tip

The Principle of Honest Engineering: A database should only exist to serve the person using the software. We use Supabase strictly to persist what's yours with Row Level Security (RLS)—never to feed ad brokers or sell user telemetry.


2. The Architecture: React.js, Supabase, and IndexedDB

We didn't need a bloated microservices swarm or native app store gatekeepers. We engineered a lean, resilient stack that combines the speed of local-first storage with the convenience of secure cloud persistence.

text script
+──────────────────────────────────────────────────────────────────────────+
|                    THE PERIODLY SYSTEM ARCHITECTURE                      |
|                                                                          |
|   [ Client Device: Safari / Chrome / Mobile PWA ]                        |
|   │                                                                      |
|   ├──► 1. React.js Application Shell (Pre-compiled, Sub-Second Boot)     |
|   │                                                                      |
|   ├──► 2. Local Storage Sandbox (IndexedDB)                              |
|   │       (Instant optimistic UI updates, symptoms, & offline cache)     |
|   │                                                                      |
|   └──► 3. Client-Side Prediction Engine (Deterministic cycle math)       |
|                                                                          |
|   ────────────────────── SECURE ENCRYPTED SYNC ──────────────────────────|
|                                                                          |
|   [ Supabase Cloud (PostgreSQL + Row Level Security) ]                   |
|   └── Stores ONLY essential user records. Zero ad pixels. Zero brokers.  |
+──────────────────────────────────────────────────────────────────────────+

Here are the core technical decisions that power Periodly:

1
Fast React.js PWA Shell
The application is built with React.js and configured as an installable Progressive Web App. Users simply tap "Add to Home Screen" to get an app experience that loads in under 350 milliseconds without the bloat of native 200MB app store downloads.
2
IndexedDB for Instant Local Experience
When you log a cycle day, pain symptom, or flow level, it writes immediately to browser `IndexedDB` with optimistic UI updates. You never wait on a loading spinner or bad network connection. If you're on a subway or flight, Periodly works uninterrupted.
3
Supabase for Secure Main Data
We use Supabase solely for storing essential user records with strict Row Level Security (RLS) policies. Users own their data, and it is accessible only by them. There are no secondary pipelines pumping analytics into ad servers.
4
Zero Surveillance SDKs
Open your browser's Developer Tools network tab on Periodly. You will find zero requests to `graph.facebook.com`, `google-analytics.com`, or anonymous broker endpoints. When you use the app, your activity is strictly between you and your database.
Why combine IndexedDB with Supabase instead of pure cloud sync?

Traditional cloud-only apps force a round-trip network request every time a user taps a button, resulting in sluggish UI, spinning indicators, and broken screens when offline. By pairing IndexedDB for instant client-side reads and optimistic writes with Supabase for secure cloud synchronization, users get sub-millisecond tactile responsiveness and continuous offline reliability.


3. The 5-Month Benchmark: 1,500 Users with $0 Ad Spend

Here is the part people find hardest to believe: we spent exactly $0.00 acquiring our first 1,500 users.

No Meta ads. No Google search PPC. No sponsored TikTok or Instagram creator posts. No SEO link-buying schemes.

text script
5-Month Performance Metrics (April – September 2026):
────────────────────────────────────────────────────
• Total Active Users:         1,500+
• Total Marketing Capital:    $0.00
• Cost Per Acquisition (CAC): $0.00
• User Data Leaked or Sold:   0 Bytes
• Server Cloud Bills:         <$5/month (Static Edge Hosting)
• Average Page Load Time:     < 350ms

How do you get 1,500 people to use a health tool without marketing?

The answer is simple: people shared it because they were genuinely relieved it existed.

When someone discovers an app that solves their everyday problem, respects their private boundaries, doesn't ask for their email address, and doesn't interrupt their day with $60 paywalls, they don't just use it—they tell their closest friends, post about it in Discord servers, and recommend it on privacy forums.


4. Three Truths Learned from 1,500 Sovereign Users

Building Periodly in public over the past five months taught me three core lessons that run completely counter to standard Silicon Valley playbook advice:

I. Privacy is a Value Proposition, Not a Compliance Checkbox

Most software companies treat privacy as a legal obstacle—a 40-page Terms of Service written by corporate lawyers to indemnify the company while continuing to monetize user data.

When you flip that equation and engineer uncompromised privacy as the primary feature, users notice immediately. In a world where every app feels like a surveillance device in your pocket, dignity is an unmatched differentiator.

II. The Anti-Bloat Advantage

Mainstream apps suffer from terminal feature creep. They start as a simple cycle log, and three years later they have added community forums, AI dating quizzes, sponsored vitamin promotions, and daily push notification alarms trying to boost their daily active user (DAU) vanity metrics.

Speed, clarity, and minimalism are superpowers. When an app does one thing exceptionally well and gets out of your way in 5 seconds, you win the long game.

III. Dignity Compounds

Growth achieved through aggressive marketing burns cash and creates high churn. Growth achieved through craft and ethical engineering compounds organically.

The 1,500 users using Periodly today are sovereign users. They aren't locked in through forced account credentials or hostage data; they use it because they trust the product.

Important

The Founder's Rule: If your business model requires keeping your users in the dark about what your software does with their data, you don't have a product—you have a surveillance operation.


5. Frequently Asked Questions

Frequently Asked Questions

Where is my cycle data actually stored?
Main data is securely synchronized to Supabase with strict Row Level Security (RLS) under your control, while instant daily cycle states and offline logs are cached right inside your device browser memory via IndexedDB.

Frequently Asked Questions

Can I use Periodly offline?
Yes. Periodly is a fully compliant Progressive Web App (PWA). Once loaded, the IndexedDB cache allows you to log cycles and view history completely without internet connectivity.

Frequently Asked Questions

Does Periodly sell data to ad brokers?
Never. Periodly contains zero tracking SDKs, zero Meta pixels, and zero telemetry brokers. We use Supabase strictly for your personal data, never for advertising.

What Comes Next

Reaching 1,500 users is just the beginning of the journey. Periodly proved that there is a massive, underserved global audience waiting for ethical, local-first software.

At Pixartual and Sagarithm, our goal remains unchanged: build software that solves real human problems with uncompromised engineering craft, exceptional design, and radical privacy.

Thank you to every single person who tested early builds, shared the app with friends, and believed in this standard. We are just getting started.

Tags:PeriodlyBuild In PublicLocal-FirstPrivacyIndie Hacking