this post was submitted on 11 Nov 2024
582 points (99.2% liked)

Privacy

1222 readers
196 users here now

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ValiantDust@feddit.org 132 points 4 days ago (34 children)

If anyone is in need of a more secure option in these dystopian times: drip keeps all your data on your phone. You can export the data, so you can keep the tracked data when changing phones. I only use it for tracking my cycle and sometimes symptoms though, so I can't say much about using it for birth control.

[–] disguy_ovahea@lemmy.world 25 points 4 days ago (30 children)

Apple’s Cycle Tracking app is also locally and E2E encrypted in iCloud.

When your phone is locked with a passcode, Touch ID, or Face ID, all of your health and fitness data in the Health app, other than your Medical ID, is encrypted. Any health data synced to iCloud is encrypted both in transit and on our servers. And if you have a recent version of watchOS and iOS with the default two-factor authentication and a passcode, your health and activity data will be stored in a way that Apple can’t read it.

This means that when you use the Cycle Tracking feature and have enabled two-factor authentication, your health data synced to iCloud is encrypted end-to-end and Apple does not have the key to decrypt the data and therefore cannot read it.

https://support.apple.com/en-us/120356

[–] onlinepersona@programming.dev 31 points 4 days ago* (last edited 3 days ago) (9 children)

Sure. It's encrypted. And your private data only stays on your device. Pinky swear.

With our 10 billion $ in ad revenue, you can trust that your data never makes it to a third party unencrypted 😚

Anti Commercial-AI license

[–] uis@lemm.ee 4 points 3 days ago* (last edited 3 days ago)

"If you are paying, it doesn't mean you are not the product"

- Cory Doctorow

load more comments (8 replies)
load more comments (28 replies)
load more comments (31 replies)