Privacy

What is stored on your device

The website and the iPhone app keep your settings, preferences and creations in local storage on your device: theme, master volume, saved mixes and sessions, favourites, visual settings, Experiments settings, experiment feedback and session history, Notched Sound profiles, your Find My Tinnitus Sound result and your sound preference profile. This local app data is not sent to us or to Google Analytics.

If you use Discover What Changes Your Tinnitus (Sound Response), your session baselines, sound-test records and Sound Response Profile — with a random identifier that only labels these records on this device and is never sent — are also kept in local storage on this device only, and can be deleted from “View experiment details” on that profile. How Sound Response works describes what is recorded. The “Clear” button on My Sound Profile removes your sound preference profile (including the sound play counts it draws on) and your latest experiment feedback and ratings. Other locally stored information — such as saved mixes and sessions, favourites, settings, Notched Sound profiles, your Find My Tinnitus Sound result and your experiment session history — stays on this device. To remove all locally stored data, clear this website’s data in your browser settings; in the iPhone app, deleting the app removes it.

On the website, your analytics choice is also stored on your device, together with two Google Analytics cookies if — and only if — you allow website analytics (see below).

Website analytics

The website findmyquietsound.com can use Google Analytics, but only if you choose Allow. Until you choose, and if you choose No thanks, Google Analytics is not loaded and nothing is sent to it. If your browser sends a Global Privacy Control signal, website analytics stays off.

If you allow it, the website sends Google Analytics basic information about each page you open: the page’s standard title and address (without app settings; campaign tags such as utm_source are kept), the page you came from, your browser and operating system, general device and screen information, your language, basic engagement such as how long the page was in use, and your country and region, which Google works out from your IP address. It does not send what you play, save, measure or type. Beyond page views it sends two kinds of events, none of which carry any detail about you. Four product-interaction events record only that something happened: a sound was started, sound has played for 30 seconds during a visit, Help Me Find My Sound was started, and Help Me Find My Sound was completed — not which sound, and nothing about the result. The Sound Response events say which step you reached: opened, welcome and safety completed, baseline completed, session started (and whether it was your first) or completed, a sound test completed, profile viewed, response sound played. No sound names, ratings, responses, tinnitus characteristics, results or preferences are ever sent.

Google Analytics then sets two first-party cookies, _ga and _ga_492Q4R9W97, holding a random identifier and visit counters. They last at most 13 months from your first visit. Google Analytics is set to keep user-level and event-level data for 2 months; its aggregated visit reports are kept longer. Google Signals and ads personalization are off, and the website is not linked to Google Ads. How Google uses information from sites that use its services.

You can change your choice here at any time. Turning website analytics off stops anything further being sent and removes the Google Analytics cookies from this site.

The iPhone app

The current iPhone app does not use Google Analytics and does not show this website analytics choice.

Other services

The website’s fonts are served from findmyquietsound.com itself; the website makes no Google Fonts requests. The currently submitted iPhone app still loads its fonts from Google Fonts until a later iPhone build, so the app requests the font files from Google.

The website is hosted on GitHub Pages; GitHub’s own server logs apply to that hosting (see GitHub Pages data collection). On the website, if you tap the microphone in Ask, your browser or device provider may process your spoken request (Google on Chrome, Edge and Android; Apple on Safari). In the iPhone app, a spoken request is turned into text by Apple’s speech recognition (Apple’s Speech framework), which may send that audio to Apple under Apple’s privacy policy; the app itself receives only the recognised text and never records, keeps or transmits your voice. iOS asks for microphone and speech-recognition permission the first time you tap the microphone, and typing always works without them. No other third-party resources load; links to research sources open other websites only when you follow them.

What we do not collect

There is no account. We don’t ask for or store your email address, hearing records or health records on our servers. Your tinnitus pitch result, experiment feedback, preferences and saved creations stay on your device, as described above; we don’t receive them.