Here is exactly what Petal Chan handles.

Petal Chan can process information you choose to record, including period dates and flow, cycle settings, symptoms and severity, moods, energy, notes, period-product timers, basal body temperature (BBT), LH test results, cervical-fluid observations, optional profile details, and app preferences.

This health and cycle information is used inside the app to show your calendar and history, calculate estimates, create visualizations, and provide features you select.

The current Petal Chan app stores health and cycle records locally as JSON using AsyncStorage. Petal Chan does not operate a health-data cloud backend that receives those records, and core tracking does not require an account, online sync, or a Petal Chan health-data server.

Health records are not separately encrypted at rest by Petal Chan. Your device passcode, operating-system security, physical access controls, and backup settings therefore remain important. SQLite or SQLCipher code may exist in development materials, but it is not the current live health-data store.

Petal Chan does not require a Petal Chan account, email address, or login for core tracking. The app does not upload or sync your health and cycle records to a Petal Chan health-data server.

Data can leave the app when you choose to import, export, share, back up, or otherwise move it using your device or another service. Those actions are described below.

Petal Chan calculates estimates locally using the cycle history and optional signals you record. Added information can update an estimate, but BBT, LH test results, cervical-fluid observations, and other logs do not make ovulation or fertility predictions certain.

Petal Chan is not a medical device, does not provide medical advice, and is not intended to diagnose a condition. It must not be relied on as contraception, to determine safe days, or as guaranteed conception guidance.

PIN lock helps control access through the Petal Chan interface. PIN verification and related attempt state use the device’s secure storage. If you enable biometric unlock, Face ID, Touch ID, fingerprint, or device face authentication is performed by the operating system; Petal Chan does not receive or store your biometric template.

Chan+ can also obscure the app preview in the app switcher. These controls protect access through the app, but they do not separately encrypt the health-record storage and do not change the privacy of exported files or device backups.

Android Auto Backup is disabled for Petal Chan. Petal Chan does not currently implement an explicit iOS iCloud-backup exclusion for the health-data storage, so iOS backup behavior depends on your Apple device, operating system, and account settings.

A device or cloud backup is controlled by the relevant operating-system or backup provider. Review those settings if you do not want app data included in a backup.

Imports are processed so the selected information can be added to Petal Chan’s local records. Full CSV export is available so you can take your data with you.

CSV exports are plaintext, ordinary files. On native apps, Petal Chan creates the CSV in app cache and opens the system share sheet. The file is not encrypted by Petal Chan, and the app does not explicitly delete that cached file after the share flow. On the web, the CSV downloads as a normal browser file.

Once you save or share an exported copy outside Petal Chan, that copy is outside the app’s sandbox and its privacy depends on the destination you choose.

Chan+ is a one-time in-app purchase. Apple or Google processes the storefront payment under its own terms and privacy practices. Petal Chan also uses RevenueCat to retrieve offerings, coordinate purchase handling and validation, check Chan+ entitlements, and restore purchases.

RevenueCat may process purchase, storefront, device, and entitlement information needed for those functions. Petal Chan does not send your menstrual-cycle history, BBT logs, symptoms, moods, notes, or other health and cycle records to RevenueCat for purchase handling. Petal Chan’s developer does not receive your full payment-card details.

Production Petal Chan builds do not use PostHog analytics and do not send Petal Chan production analytics events to PostHog. Code associated with development or tooling is not active in final App Store or Google Play builds.

Petal Chan does not include an advertising network. Purchase and storefront systems may still process the non-health information required to provide purchases and restores, as described above.

You can delete health and cycle records by using Reset all data in Petal Chan’s settings. Uninstalling the app removes its local app data subject to your operating system and any backups it maintains.

Resetting or uninstalling Petal Chan does not delete copies you previously exported, shared, downloaded, or stored elsewhere. Those copies must be deleted from their destinations separately.

Questions about this policy or Petal Chan’s privacy practices can be sent to [email protected].