The code is public

Today I'm making the Pikos codebase publicly available. You can read every line of code that runs on your machine, build the app from source, and verify for yourself that it does what I say it does.

Why

Pikos makes a specific promise: your content stays on your device. No accounts, no telemetry, no analytics inside the app. That's a strong claim, and there's no reason you should take my word for it.

Now you can check. Pikos makes exactly two kinds of network call, and you can go and find both: the update check, and calendar sync once you've connected a calendar. There are no tracking scripts, and that's a thing you can search for rather than a thing I can assert. Even if you never read a line of it yourself, the fact that anyone can is the point.

Public to read, not to resell

You can read the code, and you can build the app yourself and run it. You can't take it and sell it. That's why I say the code is public rather than calling this open source: the words mean different things, and I'd rather use the accurate one.

Trust through transparency

Privacy claims from closed-source apps are marketing copy. You're trusting the company, not the code. That trust can break at any point: a new feature, a quiet SDK addition, an acquisition. You'd never know.

With a public codebase, the privacy promise is verifiable. If I ever added tracking or phoned home, it would be visible in the diff. That constraint is the point. It keeps me honest, and it should give you confidence that the app respects your data. Not because I said so, but because you can check.