Period Privacy

The post-Roe landscape changed the floor on period-tracker privacy. Several mainstream apps in 2022–2023 were caught sharing cycle data with ad networks; one settled with the FTC for $1M+ over Meta and Google sharing. Soulwise was designed after those events; the privacy posture is the moat, not a marketing line.

What Soulwise stores, where

The cycle data — the part that matters — never leaves your device unencrypted.

What is not in the app

• Meta SDK
• Google Analytics tag (in the cycle flow)
• Facebook pixel
• TikTok pixel
• AppsFlyer / Adjust / similar growth-attribution SDKs (in the cycle flow)
• Any third-party SDK that reads, decrypts, or derives signal from your cycle entries

Marketing/install attribution lives in a separate auth/onboarding scope that never touches cycle data. The anti-claim lint covers content; the SDK isolation covers data.

Jurisdiction-aware defaults

Soulwise auto-detects your locale and sets the safer default for your jurisdiction. See jurisdiction-aware-privacy for the full mapping. Examples:

• US trigger-law states (Texas, Idaho, Oklahoma, Tennessee, Missouri, Arizona): cloud sync is off by default. Any sync requires explicit opt-in and a second password layer.
• EU (Germany, France, Spain, Italy, etc.): GDPR-aligned data subject rights surfaced in the privacy screen.
• UK: ICO-aligned defaults; equivalent rights.
• Other: strictest default.

One-tap rights

• Export: full archive in JSON, encrypted with a passphrase you choose. Decrypts on any device.
• Erase: local key and cloud blob deleted. Confirmation modal, not a permanent on-screen button.

What changes at premium

Premium adds optional encrypted cloud sync (same key derivation, end-to-end). The default remains local. Premium does not add any ad-tech.

Where to learn more

• The /soulwise/privacy page has the in-app walkthrough.
• The non-medical-cycle-tracking glossary entry covers the regulatory posture.
• Jurisdiction-aware privacy explains why defaults differ by region.