privacy.

the short version

sprinkle reads menstrual cycle data from apple health, read-only, and turns it into a simple translated view for the partner you pair with. we don't ask for your name or email, we don't sell your data, and we never share it with advertisers or anyone outside your pair. everything below is the long version of that.

what we collect

to work, sprinkle handles:

• derived cycle signals — your cycle phase, the day you're on in your cycle, days until your next period, and a confidence level for those estimates.
• monster content — an internally-generated "monster" text line and the character id that goes with it.
• an anonymous id — a random identifier we use to tell paired devices apart.
• a pairing code — a 6-character code used once to link two phones.

what we don't collect: your name, your email, a phone number, or any account signup. we don't ask for them and the app doesn't need them.

how apple health data is used

sprinkle's access to apple health is read-only. we read menstrual cycle data so we can estimate where you are in your cycle. we never write anything back to apple health, and we never modify or delete your health records.

the raw health records stay on your device. we do not upload your raw apple health data to our servers — only the derived signals listed above leave your phone.

what leaves your device, and where it goes

the following derived data is sent to firebase firestore (a google cloud service) so it can sync to your partner's phone:

• cycle phase
• day in cycle
• days until next period
• a confidence level
• the generated monster text line and character id

that's it. no raw apple health records, no names, no emails — because we never collect them in the first place.

who can see it

your data is shared only between the two phones in your pair, linked by the 6-character pairing code. that's the whole point of the app.

we do not sell your data. we do not share it with advertisers. we do not use it for advertising or build ad profiles. no third party gets access to it except the infrastructure providers (google firebase) that store and deliver it on our behalf.

how it's protected

• data is encrypted in transit and at rest in firebase firestore.
• accounts use anonymous firebase authentication — you're identified only by a random id, never by personal details.
• paired data is scoped to your pair, so it isn't readable by other sprinkle users.

no method of storage or transmission is ever 100% secure, but we keep the data we hold minimal and anonymous on purpose, so there's very little to expose.

keeping and deleting your data

we keep your data only while your account is active. you're in control of removing it:

• delete your account & data: in the app, go to settings → delete account. this removes your data from firestore and deletes your anonymous authentication identity.
• revoke apple health access: on your phone, go to iOS settings → health → sprinkle and turn off the permissions. sprinkle stops reading new cycle data immediately.

deleting your account removes your data from sprinkle. your partner controls and deletes their own data separately from their device.

notifications

if you allow them, sprinkle sends optional push notifications (via firebase cloud messaging) that carry the monster line. they're optional — you can turn them off in your phone's notification settings, or decline them when first asked, and the app still works.

children

sprinkle is intended for users 17 and older and is not directed at children under 17. we do not knowingly collect data from anyone under 17. if you believe a child under 17 has used the app, contact us and we'll remove the associated data.

changes to this policy

if we change how sprinkle handles data, we'll update this page and move the "last updated" date above. material changes will be reflected here before they take effect. please check back from time to time.

contact

questions about your privacy or this policy? email us at hello@sprinkle.monster.