Privacy and analytics Updated 4 May 2026

What we collect, what we do not collect, and why

What Grammar School Hub collects, what it does not collect, and how site usage is measured at a high level.

No accounts

Grammar School Hub does not currently offer user accounts or saved family dashboards.

Limited analytics

We use analytics to understand which pages and tools are useful.

No ad focus

The aim is to improve the site, not to build advertising profiles.

Quick answer

Grammar School Hub is a research site. We use limited analytics to understand which pages and tools are useful, and we try to keep data collection proportionate to that purpose.

  • Parent accounts can save a shortlist and basic planning details so the dashboard can show useful signals.
  • We do not collect payment information.
  • Analytics is kept to coarse product events rather than raw account, password, postcode, or town text.

What we collect

Site analytics

What it covers
General information about how pages, search, rankings, tools, sign-in, and shortlist actions are used.
Why it is used
To understand what is helpful, what is unclear, and what needs improving.
How to think about it
Used to improve the site, not to create advertising-style profiles.

Parent account details

What it covers
Email address, saved schools, child school year, target entry year, location input, and school preferences for signed-in accounts.
Why it is used
To power the parent shortlist dashboard and keep saved schools available across visits.
How to think about it
Used for the account feature; analytics avoids raw emails, passwords, and exact location text.

Technical information

What it covers
Basic device or browser information needed for site performance and reliability.
Why it is used
To spot issues with pages, tools, and user journeys.
How to think about it
Used at a broad operational level rather than as a personal record.

Public school information

What it covers
School facts and published admissions information shown across the site.
Why it is used
To power school profiles, guides, rankings, and comparisons.
How to think about it
This is public-source information, not private user-submitted data.
Category
What it covers
Why it is used
How to think about it
Site analytics
General information about how pages, search, rankings, tools, sign-in, and shortlist actions are used.
To understand what is helpful, what is unclear, and what needs improving.
Used to improve the site, not to create advertising-style profiles.
Parent account details
Email address, saved schools, child school year, target entry year, location input, and school preferences for signed-in accounts.
To power the parent shortlist dashboard and keep saved schools available across visits.
Used for the account feature; analytics avoids raw emails, passwords, and exact location text.
Technical information
Basic device or browser information needed for site performance and reliability.
To spot issues with pages, tools, and user journeys.
Used at a broad operational level rather than as a personal record.
Public school information
School facts and published admissions information shown across the site.
To power school profiles, guides, rankings, and comparisons.
This is public-source information, not private user-submitted data.

What we do not collect

  • No payment information

    The site does not currently process payments or subscriptions.

  • No account credentials in analytics

    We do not send email addresses, passwords, raw postcodes, or town text to analytics events.

  • No detailed child records for analytics

    Analytics may use broad values such as school year or entry year, not a child's name or detailed educational history.

Search and analytics

If you use search on the site, that search may be processed so relevant results can be shown. We may also measure search usage at a general level so we can improve the experience over time.

For parent accounts, analytics may record broad events such as sign-in method, whether a shortlist action succeeded, saved-school counts, the school slug involved, and coarse dashboard setup choices. It should not include passwords, email addresses, raw postcodes, or town text.

Changes and questions

If you want to raise a concern or point out a factual issue, keeping it specific is the quickest way to help.

  1. Send the page route

    Include the page where you saw the issue.

  2. Say what the concern is

    A short explanation is usually enough.

  3. Include the better source if relevant

    If the issue is factual, it helps to include the school or admissions page that supports the correction.