Last updated 25 August 2026
Cairnfield collects nothing about you. There is no account to create, no server of mine involved, and no analytics, advertising or crash-reporting code in the app. This is not a policy that describes careful handling of your data — there is no collection to handle.
Saved articles, highlights, notes and tags are stored on your device. If you are signed in to iCloud, they also sync through your own private iCloud database so your iPhone and iPad stay in step. That database belongs to your Apple Account. I cannot read it, and neither can anyone else — Apple documents this as the CloudKit private database. If iCloud is unavailable the app simply keeps everything locally instead.
Exactly one kind: when you save a link, the app fetches that page and the images in it, directly from the site you chose. Nothing else leaves your device. There is no call home, no telemetry ping, no remote configuration.
Those sites will see the request the way they would see any browser visiting them. That is between you and them; it does not pass through me.
There is none. The app uses only Apple's own frameworks and code written for this project. There are no SDKs, no dependencies, and therefore no vendor receiving anything about you. This is enforced mechanically: an automated check rejects any change that introduces an import outside Apple's frameworks.
Apple asks apps to declare certain APIs. Cairnfield declares one:
UserDefaults, used to share a small amount of state between the app
and its share extension so a link you save from another app arrives correctly.
The declaration is in the app's privacy manifest and is visible in the
source.
Cairnfield displays web pages you choose to save. It collects nothing from anyone, of any age.
These pages are served by GitHub Pages, which may log requests as any web host does; that logging is GitHub's, not mine, and I see no analytics from it. The site loads no third-party scripts, fonts or images. The Buy me a coffee button is an image stored on this site rather than loaded from their servers, so simply reading this page tells them nothing. If you follow that link, their own privacy policy applies from that point.
If this policy ever changes, the updated date above changes with it, and the history is public in the repository.
Questions, or something here that looks wrong: open an issue.