Open the network tab on any Lotlsoft app and you won't find Google Analytics, a tag manager, a Facebook pixel, or a third-party tracker of any kind. No cookies. No stored IP addresses. That isn't a coincidence or a to-do item. It's the first decision, made before the features.
That doesn't mean we collect nothing. We'd rather tell you exactly what we do collect than hide behind "privacy-first" and let you assume it's less than it is.
Three kinds of thing, all to a small analytics service we built and run ourselves, on our own server.
Page views, so we can see which projects people open and which ones nobody does.
Feature events. This is the part a "we don't track you" line usually glosses over, so: most meaningful actions in an app send an anonymous event. Which export format you chose, which drawing tool you reached for, that you added a piece of furniture or toggled a layer, that a comment was created, and crucially whether the action worked or failed. We watch this. It's how we learn that everyone uses one export format and nobody touches another, or that a feature we were proud of gets opened once and abandoned.
Crash reports, so when something breaks we find out without waiting for an email.
They describe the action, not you. "Export, format PDF" or "furniture added, category seating", not who you are. There's no cross-site identity, nothing that follows you from one app to the next, no profile, no audience segment. We don't sell any of it, because it isn't the kind anyone would buy, and we wouldn't anyway.
We also keep things briefly. The party game forgets a game six hours after it ends. The matching app drops answer data ninety days after a match resolves. The room planner's demo clears after forty-eight hours. Error reports age out at ninety days. Collecting less, and keeping it for less time, is the cheapest privacy feature there is.
This is anonymous, but it's on by default. There's no per-event opt-out, because there's no account or profile to attach an opt-out to. If that bothers you, it's a fair thing to know going in, which is why we're writing it down plainly instead of burying it.
We see less than someone running the full marketing stack: no funnels, no session replays, no heatmaps, no idea who you are. What we get is narrower and, to us, enough: a real sense of which features earn their keep and which ones we should cut. It's a smaller picture. It's also one we can stand behind.
New posts and projects, by email. Double opt-in, unsubscribe anytime.