Reignat Analytics

Reignat Analytics has great potential and offers some useful features, but I encountered a few issues that could be improved. Please contact me so I can share detailed feedback and suggest the changes I'd like to see. Email: [email protected]

The hard part of this positioning isn't the tech, it's that "privacy-first" is now claimed by everyone including the people phoning home. If you're EU-hosted, name the country and the host on the pricing page. I am personally looking at self-hosted options - preferably using sqlite as the backend for simplicity.

The privacy-compliance friction here is genuinely compelling. Most site owners face a brutal decision where they need analytics to understand what's working, but traditional Google Analytics creates hesitation around GDPR compliance, user data handling, and cookie consent complexity. Reignat removes that friction entirely by putting privacy-first analytics in one dashboard. Being able to track visitor behavior, revenue attribution, and conversion funnels without worrying about complex consent flows or data residency transforms the entire analytics workflow. The lightweight tracking script and cookie-less approach means you get real insights without the compliance burden. For privacy-conscious founders especially, that confidence knowing you're respecting user privacy while still running data-driven decisions is what changes the game.

Privacy-first analytics is a crowded space (Plausible, Fathom), so the differentiator matters. What caught my eye here is the pricing/self-serve angle for small sites. I'd suggest making the cookieless attribution accuracy explicit on the landing page — that's the first objection most people switching from GA4 will raise.

W app idea, good luck on launching

privacy-first analytics is something i actually care about, im building a small saas and went with minimal tracking on purpose. curious how you handle data retention, do you keep raw events or aggregate them over time? thats usually where the real privacy tradeoff is

The feature list has both cookie-less tracking and revenue/campaign attribution, and those two pull against each other - cross-session attribution usually needs some persistent identifier. How do you stitch a purchase back to the campaign that brought the visitor in a week earlier? If it is last-touch within a single session, it is worth saying so plainly on the landing page, because anyone migrating from GA4 will compare the two numbers and assume something is broken. Same question for the funnel tracking: is a funnel scoped to one session, or can a step happen on a later visit?

This features working amazing

This features working was very amazing