[show ih] i built a privacy-first psychometric tool that performs all calculations locally. how do you balance utility vs. data sensitivity?

Self Promotion

hey everyone,

i recently launched srquiz.com, an assessment tool based on multiple validated psychometric scales (like the sis/ses dual control model) to help people explore their sexual well-being and psychological characteristics.

since the subject matter is highly sensitive, i made a core architectural decision early on: the entire assessment process happens 100% locally on the user's browser. no data—not even the results—is ever uploaded to a server or stored in a database. the site is served as a static frontend, and everything is processed in-memory and then wiped when the session ends.

i hit a few interesting challenges while building this that i thought might be useful for other indie hackers:

  1. the "privacy vs. analytics" conflict: since i don't store any data, i have zero insight into how users actually perform or where they drop off. it makes iterating on the UX feel a bit like shooting in the dark.
  2. localization friction:** my traffic is split between english and chinese users. it’s not just about translating strings—i had to ensure the psychometric validation holds up across cultures. maintaining parity in next.js while keeping the UX clean is a balancing act.
  3. the monetization trap: currently, the site is ad-supported to keep the infrastructure running, but the cpm for different regions varies wildly. i’m debating if i should pivot to a "pay-what-you-want" model or keep the utility free and figure out better ad-partners that respect the privacy-first nature.

i’m looking for some feedback from the group:

  • for those of you in the "niche quiz/utility" space: how do you balance the need for user insights (analytics) with a strictly privacy-first, zero-data-storage policy?
  • have you found effective ways to monetize a project where the "value" is an anonymous, one-off diagnostic result?

i’m not here to spam—i’m genuinely trying to bridge the gap between "science-based utility" and a sustainable project. would love to hear your thoughts.

Posted Jun 3, 2026, 1:14 PM UTC

313
Loading comments…