app-guides

How to Export Your Data From Floriva (and Why That Matters)

How to export your Floriva cycle data, what the export contains, and how to store it safely. Data portability explained for on-device apps.

Why data export matters for an on device app When a period tracker stores data on a server, the company has a copy regardless of what you do. Your data exists in their infrastructure, under their retention policies, subject to their legal obligations. If you want a copy, you submit a request. If you want it deleted, you submit a different request and wait. Floriva's on device storage flips this. Your data exists only on your phone. The export function is not a way to get your data from a company. It is a way to package your own data into a portable file that you can move, store, or delete on your own terms. This matters for two practical reasons: data portability (moving to another app without losing history) and data security (protecting against device loss or damage). What the export contains Floriva's export includes the data you have logged: cycle start and end dates, flow intensity, symptom entries, and any notes. Because Floriva only stores what you enter on your device, the export reflects exactly what you put in. There is no behavioral metadata, no inferred data from usage patterns, and no third party data appended. This is different from data exports from cloud based apps,