Effective: October 2, 2026
Quittin' Time is built around a simple promise: a tool that protects your time should not spend it harvesting your data. Quittin' Time tracks your active work hours on your iPhone. It has no accounts, no developer servers, and no tracking. The only place your work record can go beyond your device is your own iCloud account, which the developer cannot reach. This policy explains what that means in plain terms.
Quittin' Time is published by Tim Schindler, an individual developer. References to “we,” “us,” or “the developer” in this policy mean Tim Schindler.
None automatically. Quittin' Time does not collect, transmit, sell, or share any personal data with the developer or any third party. There is no account, no login, and no sign-up. The only information that can ever reach the developer is a diagnostic report you choose to send (see Diagnostics below).
The app does not include analytics, advertising, or third-party SDKs, and it does not track you across other apps or websites. Because it does not track you, it does not use App Tracking Transparency and never asks for permission to track.
The work shifts and settings you enter are stored locally on your device using Apple’s on-device database (SwiftData). This information stays on your iPhone and is not sent to us.
Two optional features can copy that record into your own iCloud account — iCloud sync and iCloud backup. They are separate features that work in different ways, and each is described in its own section below. Neither sends anything to the developer.
iCloud sync keeps the same work record in step across your devices. It is part of the optional Pro unlock, it is off by default, and it only starts after you turn it on in Settings.
When it is on, your Quittin' Time data is mirrored into the private database of your own iCloud account using Apple’s CloudKit. That data lives in your personal Apple account, and the developer has no access to it. Apple’s handling of iCloud data is governed by Apple’s own privacy policy.
Sync is a live mirror, not a backup: a change on one device becomes the state on your other devices. It does not keep restorable snapshots, and it is not a way to recover data you deleted. That is what the next section covers.
iCloud backup is a separate feature from iCloud sync, and it works differently. It saves point-in-time snapshots of your work history — your shifts and your day markings, such as days off — as files in your own iCloud Drive, inside the app’s own folder. It does not use CloudKit, and the snapshots do not go to the developer or to any third party.
This feature is free for everyone and is on by default. The app takes an automatic snapshot at most once a day while you are using it, keeps a limited number of recent snapshots, and removes older ones. You can also take a snapshot yourself with “Back Up Now.” You can turn automatic backup off at any time under Settings → iCloud Backup, and the app asks you about it the first time it would run.
Restoring is something only you can start. It replaces all of the Quittin' Time data on that device with the contents of the snapshot you pick, and it cannot be undone. The app warns you before it does this.
Because the snapshots sit in your iCloud Drive, you can view or delete them yourself in the Files app or through your device’s iCloud settings. If you have no iCloud account, or iCloud Drive is unavailable, the feature simply does nothing.
Quittin' Time offers a small set of shortcuts you can run from Siri, the Shortcuts app, Spotlight, or the Action button: whether you are done for the day, how long you have worked today, how much time is left against your goal, when you would reach your goal at your current pace, and one action that logs a break against the shift you have open.
The first four only read your current day’s work time and your goal settings from the app’s own on-device storage, and speak or show the answer. Logging a break writes to your open shift, subtracting the break from the time counted — the same thing the button inside the app does. None of these shortcuts require the Pro unlock, and none of them send anything to the developer.
Recognizing what you said and deciding to run a shortcut is handled by Apple’s Siri and Shortcuts system, not by the developer. Quittin' Time never receives your voice recording and cannot see what you said — it only receives the request to run one of its shortcuts, and returns an answer. Apple’s handling of Siri requests is governed by Apple’s own privacy policy.
The Apple Watch app shows the same work record as your iPhone. It collects nothing of its own: the iPhone passes the current figures to the watch using Apple’s on-device connection between your paired devices, and shared on-device storage. Nothing about the watch app involves a server or the developer.
The app can keep crash and performance reports that iOS generates on your device. They stay on your device and are never sent automatically. You can view, share, or delete them in Settings > Data > Diagnostics. If you choose to share a report with the developer, for example by email, it is used only to diagnose and fix problems. These reports are not linked to you and are not used for tracking.
You can export your shift history as a CSV file from Settings. The export uses the standard iOS share sheet, so the file goes wherever you send it — a message, a file, another app — and that is entirely your choice. The developer never receives a copy.
The optional one-time Pro unlock is processed entirely by Apple through the App Store and In-App Purchase. The developer never receives or stores your payment details or credit-card information.
Quittin' Time uses local notifications only — the nudges that remind you to stop work are generated on your device. There is no push server and no remote notifications.
Quittin' Time is not directed to children under 13 and does not knowingly collect personal information from them.
Because your data lives on your device, you control it. Deleting the app removes its local data from your iPhone. If you have used iCloud sync, you can manage or remove that data through your device’s iCloud settings. If iCloud backup has run, the snapshot files remain in your iCloud Drive until you delete them — you can do that from the Files app or your iCloud settings. The developer cannot delete any of it for you, because the developer has no access to it.
We may update this policy from time to time. Any changes will be posted on this page, and the effective date above will be updated to reflect the latest version.
If you have questions about this privacy policy, contact tim@iosharp.com.