Why Your Cycle Tracker Should Be Local-First
Local-first apps store your data on your device, not in the cloud. Here's why that matters for a period tracker — and what to look for.
What “Local-First” Actually Means for Health Apps
When an app says it’s “local-first,” it means your data stays on your device. Not on a server. Not in someone else’s cloud. Your cycle data, symptoms, predictions — everything lives in a database on your phone.
This matters more than it sounds like.
Most popular period trackers (Flo, Clue, Ovia) operate on a “cloud-first” model. Your data travels to their servers, gets processed, gets stored, and gets used to improve their algorithms — or, in some cases, sold to advertisers. You create an account, you trust them with intimate health information, and you hope they’re being honest about what they do with it.
Local-first apps flip this. Your data never leaves your phone unless you explicitly choose to sync it. And if you do choose cloud backup, it’s encrypted before it ever leaves your device — so even the company that hosts your backup can’t read your health information.
The Architecture of Vela: SQLite on Your Device, Not in the Cloud
Vela stores all tracking data in a SQLite database on your iPhone. This isn’t an afterthought — it’s the foundation of the privacy model.
When you log a period, record a symptom, or track your mood, the data goes into a local database. Predictions are calculated on-device using algorithms that run entirely in your phone’s memory. No API calls. No cloud compute. No data leaving the device.
When you open the app offline — on a subway, in a basement, in a country with restricted internet — everything still works. Your cycle data, your predictions, your garden gamification. All of it.
Offline Capabilities: Tracking When You Have No Signal
One of the most practical benefits of local-first architecture: Vela works perfectly offline. No signal required.
This isn’t just a privacy feature — it’s a usability feature. Your period doesn’t wait for WiFi. You might be traveling, hiking, or simply in an area with poor connectivity. With a cloud-first app, you’re stuck. With Vela, you track normally and your data syncs when you’re back online.
If you enable cloud backup, all your data is encrypted client-side before it ever leaves your device. Your backup provider — and anyone who might intercept the data in transit — sees only encrypted blobs. Only you have the keys.
What Local-First Doesn’t Mean
Local-first doesn’t mean your data is locked in one device forever. With Vela’s encrypted cloud backup, you can sync across devices while maintaining end-to-end encryption. Your partner can share data with you through the same encrypted channel. The privacy model doesn’t require sacrificing convenience.
It also doesn’t mean the app is primitive. Vela still offers cycle predictions, fertility insights, symptom analysis, and a garden that grows with you. All of that works offline.
The Privacy Tradeoff You’re Making When You Choose a Cloud-First App
When you use Flo, Clue, or Ovia, you’re placing enormous trust in a company’s servers. You’re trusting them to keep your health data safe from breaches. You’re trusting them not to sell it to advertisers. You’re trusting them not to hand it over to law enforcement without a fight.
That trust might be warranted — or it might not. But why make that tradeoff for an app that tracks something as personal as your menstrual cycle?
With Vela, the trust model is different. Your data is encrypted on your device. Even if Vela’s servers were breached, your health data would be unreadable. There’s nothing to sell because there’s nothing to access.
Your cycle. Your device. Your rules.