Personal information deserves clear choices.
Your period dates and personal notes deserve an explanation you can read without a glossary. This page describes Veya’s confirmed product design and separates it from features still planned for release.
Veya is pre-launch. This is product information, not the formal privacy policy; that policy will be published before launch.
What we’ve built so far
Local storage is the foundation of the app: what you log is stored in a local database on your phone. That includes the entries you choose to make, such as period days, symptoms, test results or personal notes.
This is the current storage design. The app is still in development, and the features described below aren’t available yet.
What’s still planned
Optional cloud backup, partner sharing and an anonymous community are planned for launch. They will run only if you turn them on. The community uses an anonymous ID, and partner sharing uses a private code. Cloud backup, which is how you move your record to a new phone, uses a Google account (Android) or Sign in with Apple (iOS) that you choose to link. You don’t need an account for anything else.
Downloading and deleting your data are planned too: a full JSON export, with your entries, notes, medicines, reminders and settings, that you can restore into Veya on another phone without an account, a CSV copy for spreadsheets, and an option to delete everything.
App lock and reminders you choose are also planned. We’ll publish the settings and their explanations before launch so you can see what each option does.
What is stored where
| Information | Confirmed design | Availability |
|---|---|---|
| The health entries and notes you log, including medicines, care contacts and your care region | A local database on your phone | Local storage is the current foundation; the app is pre-launch. |
| Community posts | An optional cloud feature, enabled by you | Planned for launch. |
| A short summary shared with a partner | An optional cloud feature, enabled by you | Planned for launch. |
| Cloud backup | An optional copy held through a cloud feature, enabled by you | Planned for launch. |
| Browser-demo entries | Fictional sample data, with edits held only in page memory | A website preview, separate from the app. |
The optional cloud features involve information leaving the phone. Local storage doesn’t mean that information shared through those features stays on your device.
Optional cloud features
Community
An optional anonymous community is planned. It uses an anonymous ID, but an ID cannot make identifying details in something you write anonymous; a name, workplace or personal story may still identify you.
Partner sharing
Optional sharing is planned for a short summary, through a private code you give to the person you choose. You decide what the summary includes, and stopping sharing deletes the shared copy. It’s a separate choice from keeping your own record, and you don’t need to enable it to log personal entries.
Cloud backup
Optional cloud backup is planned for people who choose to use it, mainly to move a record to a new phone. To use it, you link a Google account on Android or use Sign in with Apple on iOS. Veya receives only the email address, to recognise the account; your cycle data isn’t shared with Google or Apple. Details of what is backed up and how copies are managed will be explained before the feature is released.
A lock and a reminder are different choices
App lock is a planned control for access to the app interface. It shouldn’t be read as a guarantee about the security of the underlying database or any cloud copy.
Reminders are planned as something you choose. Notifications on a locked screen are designed to use neutral wording, and a medicine reminder can show a name you pick instead of the medicine. The final notification options will be explained before launch.
What we don’t do
Veya has no ads, no analytics and doesn’t sell data. Every feature is planned to be free, so there’s no premium tier that depends on your information. You don’t need an account to use Veya; the only time an email address reaches us is if you link a Google or Apple account for cloud backup.
The full details of data protection, retention and deletion are still to be published. Before launch, we’ll explain how long information is kept and how removal requests work, including what happens to cloud copies.
The website demo
The interactive preview uses sample data. Don’t enter your real health information into it.
Demo changes stay in page memory, are cleared on reset or reload, and aren’t sent to a backend, analytics or browser storage. This describes the demo’s behavior, not the app’s storage arrangements or a claim that all website infrastructure is local.
The waitlist
The waitlist is separate from health logging. When available, it asks for an email address and, optionally, your preferred platform; it doesn’t ask about your health or reproductive plans.
If the page says Waitlist preview, signup isn’t available. The preview doesn’t submit or retain an email, and it doesn’t reserve a place on a list.
Before a real signup service is enabled, this section must be updated with its approved data-handling information, including who receives submissions and how to manage them. Waitlist email addresses must be kept out of analytics payloads and error logs.
Before launch
The formal privacy policy will explain the responsible organisation, service providers, retention and deletion arrangements, and how to contact us about your information. Those details aren’t supplied yet, so we haven’t filled them in with assumptions.
If you’re comparing cycle tracking apps, our guide to what to check in a period tracker’s privacy settings and policy lists the questions worth asking, and they apply to Veya too.
Approved privacy information and terms are required before launch. You can find the current product information on the app page and contact availability on Support.