Privacy Policy¶
The short version: your data stays yours¶
This policy covers the apps I publish for iOS, macOS, and other Apple platforms — including Cribsheet, GeoFill, Klicks, Photo Fling, and Rectify — unless an app ships with its own policy that says otherwise.
What I collect¶
Nothing, unless you ask me to. My apps do not collect, transmit, sell, or share your personal data. There are no accounts to create, no advertising identifiers read, and no tracking of any kind.
The one exception is the optional "Help the developer" switch described below. It is off by default, and while it is off an app sends me nothing at all.
Where your data lives¶
Anything you create or capture in one of my apps stays on your device, or in your personal iCloud account if the app offers iCloud sync. iCloud data is stored in your private storage, managed by Apple under Apple's privacy policy — I have no access to it and no way to read it.
As of this writing, three apps use that sync: Klicks keeps your goals and settings in iCloud so they follow you between devices, and GeoFill does the same with your review history — skips, applied photos, and preferences (with a toggle in its settings if you'd rather it didn't). Photo Fling syncs its lifetime stats (photos viewed, favorited, and deleted, and space recovered) between your devices the same way. In every case the data moves only between your own devices and your own iCloud account; none of it ever reaches me.
Optional crash reports and usage data ("Help the developer")¶
Some of my apps offer a "Help the developer" switch in their settings. It is off by default, it is never turned on without you flipping it, and your choice is stored only on that device. As of this writing the switch is in GeoFill, Klicks, Photo Fling and Rectify, and Cribsheet gains it in its next release (0.4.2); this section applies to each of them in the same way.
While the switch is off, nothing is sent — no usage data and no crash reports, even if the app crashes.
While the switch is on, the app sends me:
- Crash and error reports: the stack trace, the app version, the operating system version, and the kind of device (for example iPhone, iPad, Mac, or Apple TV, but not the exact model), so I can find and fix the bug.
- Session information: when the app became active and when it went to the background, how long that session lasted, and the app version.
- A random identifier that the app makes up when you turn the switch on. It is not linked to you, your Apple ID, or your device, and it is never shown to you or to me as anything but a random string. It lets me count how many installs are affected by a bug instead of how many reports arrived.
The reports never include your photos, the names or identifiers of your photos, your location or any photo's location, your name, email address, Apple ID, contacts, or the names and paths of your files. Before anything leaves the app it passes through a scrubber that removes photo identifiers, coordinates, and file paths, and the device details are cut down to the list above. A crash report does name the app's own code files, so I can read it; none of yours. The app does not attach your IP address to anything it sends; Sentry's servers see the connection as any web server does, under Sentry's own policy below.
These reports are processed by Sentry (Functional Software, Inc.) on servers in the United States, under Sentry's privacy policy. Sentry deletes them automatically at the end of its retention period, at most 90 days. I use the reports only to fix bugs and to see how many people use an app and for how long; I do not sell or share them.
Turning the switch off stops the collection at once, deletes the random identifier and the reports the app had saved but not yet sent (one final "session ended" record already in memory may still go out), and starts over with a fresh identifier if you ever turn it back on. Because the identifier is random and not tied to you, I have no way to look up or delete "your" reports on request; they expire with Sentry's retention period instead.
Crash reports through Apple¶
Separately from the switch above, if you have opted in to sharing analytics with app developers in your device settings, Apple may send me anonymised crash reports. These contain no personal information and I use them only to fix bugs.
Purchases¶
If an app offers paid features, payment is handled entirely by Apple through the App Store. I never see your payment details — Apple provides me only with anonymised, aggregate sales figures.
Children¶
My apps do not collect data from anyone, including children. The "Help the developer" switch is off by default for everyone.
Changes¶
If an app's behaviour ever changes in a way that affects this policy, I'll update this page and note the change here before the app update ships.
- November 7, 2026: added Photo Fling's iCloud sync of lifetime stats.
- October 13, 2026: the "Help the developer" switch is now also in Klicks, Photo Fling and Rectify (TestFlight builds), and Cribsheet gains it in 0.4.2. Same data, same default of off; nothing changes for anyone who leaves it off.
- October 11, 2026: added the optional "Help the developer" section ahead of the GeoFill update that introduces the switch. Nothing changes for anyone who leaves it off.
- August 6, 2026: added GeoFill's iCloud sync of review history.
Last updated: November 7, 2026.
Questions?¶
Email apps [at] mattmanuel [dot] com and I'll answer personally.