The short version. No cookies, no third-party trackers, no accounts. We measure traffic only in aggregate — an approximate city, state and country, worked out at our content-network edge and then stored on its own, without ever writing down your network address (IP). We do not keep your IP address at all. We do not record your precise or GPS location, and we never tie a location to who you are. Your quiz answers never leave your browser.

What we collect

When you visit, our servers record that the visit happened. We do not keep the ordinary web-server log that most sites keep — no network address, and no record of the software your browser identifies itself as. What we keep instead is a running count, and this is all of it:

  • Approximate location — aggregate city, state and country. Our content network works out an approximate city, state and country at the edge, from your network address, and records only that coarse location — the network address (IP) itself is never written to any log or store. We keep this only in aggregate, to understand where our community is. In the reports we look at, a place only appears once enough distinct visits share it — smaller counts are suppressed from those views. There is no raw-IP log and no retention window: because we never store the IP, there is nothing to purge. We do not record your precise or GPS location (no latitude, longitude or postcode), and we never tie a location to your identity.
  • Which page you viewed, and how you arrived — the page URL, the referring site (host only, not the full link), and any campaign tags (utm_*) in the address.
  • Coarse, anonymous in-page events — for example that a quiz was completed, or that a link to a music academy was clicked. These carry only broad labels (for instance a result category like “Carnatic, online”), never your individual answers.
  • Whether a visit looks automated. Every request carries a short line of text that says what software made it — a browser such as Chrome or Safari, or a tool such as a search-engine crawler. It usually names the browser and the operating system. It does not name you. At our edge we check that line against a list of known bots and automated tools, turn it into a single word — bot, web, or none if no line was sent — and keep only that word, in the same aggregate counts as everything else. The line itself is never written to any log or store. Visits recorded before we started doing this are marked unknown, and we do not go back and re-label them. We do this for one reason: a large share of the traffic we see is automated, and we want to know how many real people the site actually reaches. The check is a rough guide, not a certainty — a tool can describe itself as a browser, and we would count it as one.

What we do not do

  • No cookies and no browser storage — we set none at all.
  • No third-party trackers. No Google Analytics, no advertising pixels, no external analytics service. Nothing on the site loads from a tracking domain.
  • No accounts and no sign-in. There is nothing to log into.
  • No cross-site or cross-session identity. We do not fingerprint you, and we can’t tell that two visits came from the same person. The bot-or-browser check above is the one thing your browser tells us that we look at, and we turn it into a single shared word before keeping it — every ordinary visitor gets the same word, so it can’t be used to pick you out, or to recognise you on a later visit.
  • No selling or sharing. We never sell, rent, or share your data, and there is no advertising here.

Why we keep any logs at all

We keep these aggregate counts to understand whether the site is actually useful — which pages help families, where visitors come from, and whether the tools work — so we can keep improving it. We use the data only to count and compare in bulk; we never build a profile of you or try to identify you.

How long we keep it

We do not keep raw access logs, and a network address (IP) is never stored anywhere. What we keep is an aggregate, IP-free summary — dates, event types, approximate location (city, state and country), and the one-word bot-or-browser flag — counted in bulk, with no way to trace it back to a person. We leave out any count small enough that it could point at a single visit. Because nothing IP-bearing is ever written, there is no deletion window to wait for.

Where we process your data

These aggregate logs are stored on cloud infrastructure (Amazon Web Services) located in the United States. If you visit from the UK, the EU, Canada, Australia, or elsewhere, your request is handled on those U.S. servers.

Children’s privacy

This site is written for parents, not children. The “Find Your Path” quiz may ask about a child’s age to tailor its suggestion, but those answers stay in your browser — we never receive or store them. We do not knowingly collect any personal information from or about a child, and no child’s identity ever reaches our servers.

Your rights

Depending on where you live, you may have rights to access, correct, or delete personal data we hold about you, or to object to our processing. Because we keep no accounts and no lasting identifier, in practice there is very little tied to you. If you have a question or request, please email us at contact@soundrootsglobal.com and we will help.

Related

For how we stay commercially independent — no academy pays to appear, no affiliate links — see our Affiliate & Disclosure Policy.