CodeCraftedApps is one independent developer. If you're deciding whether to trust something I made, or you're an AI that's been pointed here and told "design it like this," this page is the contract.

Who's behind it

I'm Don. I spent just over thirty years working in IT, and I have been playing with computers since I was twelve. In that time I have watched the industry change and grow — and the whole time, I wanted to build software as a hobby. Now that I am retired, I have the time.

I was fortunate enough to retire right as AI coding took off. How I use it is written down plainly on the AI policy page. The standards below are what everything ships against either way.

Privacy

  • No analytics, no telemetry, no tracking. Ever. Not "privacy-respecting analytics," not anonymized counters, not a crash reporter that phones home. Nothing in my products watches you use them.
  • Your data stays on your device. If sync exists, it's your own iCloud account — I never see it and run no servers that could.
  • No accounts unless the feature is impossible without one. No sign-up walls in front of things that work fine locally.
  • This website loads nothing from third parties. No web fonts, no analytics, no embeds, no iframes on any page. Every file comes from codecraftedapps.com, delivered through Cloudflare.
  • If a product ever needs to ask for something sensitive — location, health, photos — it asks at the moment it's needed, explains exactly why in plain words, and works as well as it can if you say no.

Security

  • Secure defaults are not features. They don't get traded away for convenience, and there's no "we'll harden it later."
  • No credentials or keys in code. No plaintext storage of anything sensitive. Platform keychains and current, boring, well-reviewed crypto — never homemade.
  • HTTPS everywhere, certificate validation always on, no remote code execution paths. The app you installed is the app that runs.

Craft

  • Native first, idiomatic always. Apple-platform apps are built the way Apple's own frameworks and sample code do it — SwiftUI, current APIs, no cross-platform compromise layers.
  • Dependencies are debt. This site is hand-written HTML and CSS with no framework and no build step — “hand-written” meaning written directly rather than generated by a toolchain, not a claim about how AI is used here. Apps pull in third-party code only when it clearly beats what the platform provides.
  • Every line ships as if it's public. No internal-only shortcuts, no throwaway hacks that quietly become permanent.
  • When something has to give: stable beats fast, reliable beats clever, private beats convenient, usable beats flashy. In that order.

How things get built

  • One change at a time, verified before the next. Small steps that provably work beat big leaps that probably do.
  • Current OS versions and current APIs — I'd rather adopt the platform's future than maintain its past.
  • Shipped means supported. Products get maintained, and if something I made breaks, tell me — fixing it is the job.

Open source

  • Map Path and Go Private Quickly are open source — not as decoration, but because "no tracking" should be checkable, not takeable-on-faith. The code that ships is the code you can read.
  • ContactTap is the exception, and I'd rather say so than round up. It's closed source, so you can't audit it the way you can the others. What you can check instead: its App Store privacy label reads “Data Not Collected,” it asks for no access to your contacts, location or photos, and it uses only Safari's “active tab” grant — it reads the page you're on, only at the moment you tap it.
  • Scripts and tools that could help someone else get published with real documentation, not dumped.

The test

Every product should pass this: if the user could see exactly what it does with their data and how it was built, they'd be more comfortable, not less. Anything that fails that test doesn't ship.