Privacy Policy

Last updated: [DATE — fill in at launch]

HearingScout (“we,” “us”) operates this website to help visitors compare over-the-counter hearing aids. This policy describes what information we collect and how we use it.

Information you provide directly

If you join our email list, we collect your email address and nothing else at signup. If you later respond to a follow-up about your experience with a device, we keep whatever you tell us in that response.

Answers you give in the matching tool itself (budget, hearing needs, lifestyle preferences) are used to generate your results in your browser session. [Founder note: confirm and update this section once the matching engine’s actual data handling is built — e.g., whether answers are also sent to a server or stored anywhere, versus staying entirely client-side.]

Information collected automatically

We use privacy-respecting, cookie-free analytics (currently [Plausible/Fathom — confirm which]) to understand aggregate traffic patterns. This does not track you individually across other websites and does not build an advertising profile.

Affiliate tracking

When you click a link to a retailer or manufacturer, that company’s affiliate network (for example, Awin) may set a tracking cookie or use a referral parameter to confirm that the visit came from HearingScout, so that we can be credited for a resulting sale. We do not control what those third-party networks or retailers do with data once you’ve left our site — see their own privacy policies for that.

What we don’t do

We do not sell your personal information. We do not share your email list with the brands we compare.

Your choices

You can unsubscribe from any email we send using the link in that email, or by contacting us directly at hello@hearingscout.com.

Contact

Questions about this policy: hello@hearingscout.com.

This page is a working draft, not legal advice. Have it reviewed by an actual lawyer, or generated/reviewed via a service like Termly, before relying on it in production — particularly once the matching tool’s real data flow (client-side only vs. server-processed) is finalized.