Who runs this

Simplytics is built and operated by one person: Nikhil, based in India. Not a team, not a company with a support rota — one person, which is the single most useful thing to know before you decide whether to depend on it.

Where that person sits is the second most useful thing, and it matters if you keep a compliance record of your own: the analytics database is in the European Union, and it is administered from India. For EU customer controllers, giving an India-based processor remote access to personal data can be an international transfer even though the database is in the EU, so the DPA covers that access with the EU Standard Contractual Clauses, publishes a transfer assessment, and states the one case the clauses were not designed for. The privacy policy says plainly what that does and does not mean.

Every email to nikhil@simplytics.dev reaches me, and I answer them myself. That is a smaller promise than a support SLA and a more honest one.

Where it came from

Simplytics was acquired in January 2026 and rebuilt. Nearly everything you can see — the tracker, the dashboard, how visitors are counted, what is stored and for how long — is work done since. The changelog starts where that work does, rather than claiming credit for what came before.

Why it exists

Most site owners want six things: how many people came, which pages they read, where they came from, roughly where in the world they are, what they clicked, and whether that is going up. Google Analytics answers all six with a setup that often includes consent tooling, a great deal of JavaScript, and a reporting model built for advertisers. Privacy-focused alternatives answer them with less tracking and charge $9–15 a month for it.

Simplytics is the third option: the same six answers, no visitor cookies, a small script, and a price low enough that a blog with four hundred readers a month can justify it.

Why it costs what it costs

Three reasons, and none of them is a launch discount:

• It stores almost nothing. Raw visit rows exist for hours and are deleted; what is kept is daily counts. Storage and query cost is what makes analytics expensive, and most of it is deliberately not incurred.
• There is no company attached. No office, no sales team, no investors expecting a return, and no headcount that has to grow.
• Yearly is the default because payment fees are per charge, not per dollar. Twelve small charges cost far more to collect than one, which is why a year is $12 — $1/month, billed yearly — while the month-to-month price is $2. Paying monthly is a perfectly reasonable choice; it just costs more to collect, so it costs more.

There is a price-lock pledge in the terms: the price you subscribe at is the price you keep renewing at.

What you should worry about

One person is a real risk and pretending otherwise would be the wrong way to start. What is in place against it:

• Your data is portable at any time. Full CSV export from the dashboard, subscribed or not, in or out of trial. Nothing is held hostage.
• Successful account deletion removes the data immediately from the live database through the Account page. When you delete your account, we first cancel your subscriptions with our billing provider, which can take more than one attempt. Any subscription already cancelled stays cancelled, even if deletion is not yet complete. We keep your account data until we confirm billing has stopped. After each deletion attempt, new checkouts and email changes are paused for up to 24 hours. If deletion does not complete, you may need to request it again. Backups take up to 90 days to age out, which the privacy policy spells out rather than glosses.
• Refunds are 30 days on any charge, no questions asked, plus a refund on a renewal for an account that recorded nothing since. See the refund policy.
• If it were ever to shut down, you would get notice and time to export, not a dead domain. That is a commitment rather than a certainty, and it is worth exactly what you think a commitment from one person is worth.

The rest of the honest list — no SOC 2, no penetration test, no second pair of eyes on a deploy — is on the security page, along with what is still unfixed.

What it will not become

No cookies, no cross-site identity, no ad-network integration, no session recording. Those are not features waiting for time; they are the things this tool exists in order not to do, and the roadmap says so in the same words.

Talk to me

Feature requests, complaints, "why is this number wrong", or just to ask whether it will still be here next year: nikhil@simplytics.dev. A fair amount of what is in the product arrived that way.