Built With Care: Why Privacy Is Not an Afterthought at Heldcraft
At Heldcraft, "built with care" isn't a marketing line. It's an operating principle — and nowhere is that more visible than in how we think about the people who use our software.
Care means not taking what isn't yours
Most analytics and monitoring setups are built around a simple assumption: more data is better. Collect everything, store it indefinitely, figure out what's useful later. It's efficient for the developer. It's not a great deal for the user.
We've made a different choice. When we instrument our software, we ask a different question first: what do we actually need to know, and what's the minimum data required to know it?
That question changes everything downstream.
What "privacy-first" means in practice
It means choosing tools that are designed around data minimisation rather than data maximisation. It means configuring those tools to collect less, not more, even when collecting more is the default. It means not storing IP addresses when aggregate counts tell us everything we need. It means respecting the fact that the people using our software didn't sign up to be subjects of a data collection exercise — they signed up to use a product.
It also means being honest about the tradeoffs. Privacy-first instrumentation gives us less granular data. We can't reconstruct individual user sessions. We can't track people across devices or match behaviour to identities. We've accepted that limitation because we think the alternative — treating every user as a data point to be harvested — is incompatible with building software we'd actually want to use ourselves.
The tools we chose
We use Aptabase for in-app analytics, Umami for web analytics, and Sentry for error monitoring. All three can be configured to respect user privacy seriously. None of them require you to do so — that's a choice.
In an upcoming post, we'll walk through exactly how we've configured each one: what we collect, what we deliberately don't collect, and why.
"Built with care" as a commitment
The tagline exists because it describes something real. We build slowly and deliberately. We choose tools that reflect our values. We think about the people on the other side of our software as people, not sessions.
Privacy is part of that. Not a feature, not a compliance checkbox — a consequence of caring about what we're building and who we're building it for.
Heldcraft builds privacy-first software for users who notice. Pre-launch, building in public.