Privacy Policy — 75 Days
Last updated: 8 September 2026
The short version
75 Days has no servers. There is no account to create, nothing to sign in to, and no company database holding your habits. Your challenge lives in your own iCloud account. When you run a challenge with somebody, Apple’s own private sharing carries your day between the two of you, and nobody else can read it.
There are no analytics, no advertising, no tracking, and no third party code in the app at all.
1. Who this policy is from
75 Days is made by Damilola Payne. You can reach me at support@econtechie.com.
This policy covers the 75 Days iPhone app, bundle identifier
com.damipayne.seventyfivemedium.
2. There is no server on my side
The app has no backend of mine. It makes no network requests to any host I control, and it contains no code that talks to anybody else’s host either. Everything the app stores, it stores in two places: on your iPhone, and in the iCloud account signed in to that iPhone.
I have no ability to read your challenge, your logs, your photos or your name. Not because of a promise, but because there is nowhere for that data to reach me.
3. What is stored on your iPhone
| What | Detail |
|---|---|
| Your day logs | What you completed, the amounts you entered, the day numbers, whether a log was late and the reason you gave |
| Progress photos and step screenshots | The image files themselves, in the app’s Application Support directory, protected by iOS file encryption |
| Your challenge definitions | Name, emoji, activities, goals, miss rule, grace budget, start date, time zone |
| Reminder settings | Your blocks, times and which activities sit in which block |
| Smart timing history | The minute of the day you completed a reminder block, kept per challenge, on the device only, never synced anywhere |
Journal text is a special case. When you write an entry for a journaling activity, only the word count is saved and synced. The words themselves are held in memory for as long as the sheet is open in that session and are not written to disk or to iCloud.
4. What goes into your iCloud
The app uses Apple’s CloudKit inside your own iCloud account. Three kinds of record are written:
Your challenge — its name, emoji, start date, time zone, status, outcome, the activity definition, and the display name and profile colour of each participant.
Your days — one record per day per person, carrying which activities you completed, the values you logged (litres of water, minutes, step count, word counts, whether a tick box was ticked), whether a step count came from Apple Health or was typed in, the name of anything you recorded reading or listening to, any note you attached, the reason you gave for a late log, and the filename of a progress photo if you took one.
Your progress photos — the image bytes, in a separate record type, in the default zone of your own private iCloud database.
Apple processes and stores this data under Apple’s Privacy Policy. Data stored in your private iCloud database counts against your iCloud storage.
5. What your partner can see, and what they cannot
This is the part worth reading carefully, because the two halves are deliberately different.
Your partner CAN see your day. When you invite somebody, the challenge and every day record in it are shared with them through a CloudKit share. That is the point of the app. They see your display name, your profile colour, which activities you completed, the values you logged, your score, your streak, whether a step count was automatic or manual, and any note or content name you attached to an activity. They also receive the screenshot you attach as proof of a manual step count — that is intentional, because a step proof exists to prove something to your partner.
Your partner CANNOT see your progress photos. Progress photo images are stored in a separate record type in the default zone of your own private iCloud database. CloudKit structurally refuses to let a share target that zone, so the image bytes can never travel to your partner’s device. What crosses is the filename only, which is how your partner’s screen can show that you logged a photo without showing the photo.
A challenge holds exactly two people. There is no third participant, no public listing, no feed and no discovery. A share link works for one person only.
6. Apple Health
The app reads two things from Apple Health, and only if you allow it: your step count and your workout samples. Both are optional. Every activity in the app can be confirmed by hand, and a manually logged day scores exactly the same as an automatically detected one.
The app never writes anything to Apple Health. The HealthKit write permission is declared only because linking HealthKit requires it.
Your Health data is never transmitted anywhere by this app. What is written into your challenge is the derived number the activity needs — a step total for a day, or a count of workout minutes — which your partner sees as part of your score. The underlying Health samples are not copied, exported or sent.
You can withdraw Health access at any time in the iPhone Health app, under Sharing, Apps. The app keeps working; steps and workouts fall back to manual entry.
7. Screen Time and Family Controls
The app includes Apple’s Family Controls and DeviceActivity frameworks and ships a small system extension. If you ever grant Screen Time access, the extension can receive exactly one signal: that a usage threshold you configured has been reached. That single fact is written into a container shared between the app and its extension, on your device.
The app receives no app names, no usage totals, no browsing history and no per-app breakdown. Apple’s DeviceActivity framework does not expose that data to a third party app, and this app asks for none of it.
No activity in the current version uses this, so in practice the app does not ask for Screen Time access. The frameworks are disclosed here because they are present in the shipped binary.
8. Camera and photos
The camera is used to take progress photos and step screenshots. Choosing an existing image uses the system photo picker, which hands the app the one image you picked and gives it no other access to your library.
Photos are stripped of metadata before they are stored.
Sharing a result card goes through the standard iOS share sheet, so the app never needs permission to write to your photo library.
9. Notifications
Reminders, streak protection and partner nudges are delivered as notifications. Most are scheduled on your device. The app also registers for remote notifications so that iCloud can tell it when your partner’s data has changed. The push token that makes that work is handled by Apple.
A partner nudge carries the sender’s display name and the day number, and nothing else.
10. What is not collected
- No analytics of any kind. The app contains no analytics SDK.
- No crash reporting SDK. If you have opted in to Apple’s own crash and usage sharing at the iOS level, Apple may share aggregated crash reports with me; that is an Apple setting you control in Settings, Privacy and Security, Analytics and Improvements.
- No advertising, no ad identifier, no App Tracking Transparency prompt, because there is nothing to track.
- No third party SDKs. The app has zero external package dependencies.
- No email address, no phone number, no contacts, no location, no payment details. The app asks for none of them.
- No tracking across other apps or websites, by anybody.
11. Deleting your data
Deleting a challenge. Ending and deleting a challenge removes its day logs and its progress photos, on your device and in iCloud, including older photo files saved before the app scoped them per challenge.
Deleting the app. Removing the app deletes everything it stored on the device. Data in your private iCloud database is removed with the app’s iCloud data, which you can clear in Settings, your name, iCloud, Manage Account Storage.
Your partner’s copy. When you share a challenge, the days you logged are synced onto your partner’s device. Deleting your own copy does not reach into their device and delete theirs, in the same way that deleting a photo you sent someone does not remove it from their phone. If you want a shared challenge gone from both sides, both of you need to delete it.
One thing this policy cannot yet promise. Progress photo images written by earlier versions
of the app, before the image bytes were moved out of the shared area, may still be held in the
shared part of iCloud for challenges created back then, and may already have been downloaded onto
a partner’s device. Newer versions no longer put them there and no longer fetch them, but that
does not retrieve what is already stored. A clean-up for that older data has not shipped yet.
This affects the app’s beta testers only; the app has not been released publicly.
[OWNER: this paragraph should be deleted before submission if the pre-release data reset ships first. Tracked as issue #574.]
12. Children
75 Days is not directed at children and does not knowingly collect anything from them. It has no messaging beyond a fixed nudge, no user generated public content, and no way for a stranger to reach a user.
13. Your rights
Because I hold none of your data, there is nothing for me to hand over, correct or erase on your behalf. Everything the app holds is on your device and in your iCloud account, under your direct control, and you can inspect or delete it with the steps in section 11. If you would like help doing that, write to me at the address in section 1.
14. Changes to this policy
If this policy changes in a way that affects what the app does with your data, the updated version will be posted at this address with a new date at the top, and the change will be described in the app’s release notes.