Privacy Policy

Last updated: 7 October 2026

1. Who we are

United History is an independent, static Manchester United history archive. It is the controller of the limited personal data described in this policy. The site has no accounts, purchases, comments, newsletter or web contact form.

Questions about this policy or requests concerning your personal data can be sent to abstractcs65@gmail.com.

2. What the site itself stores in your browser

United History's own code does not set first-party cookies and does not write to local storage, session storage or IndexedDB. Search, filters, sorting and timeline controls run in the current page. Some controls put a selection in the page URL, but the site does not persist that selection in browser storage.

Third-party advertising and consent services can use cookies, local storage, pixels, tags and similar technologies on the six advertising-enabled pages described below. Blocking or deleting those technologies may reset an advertising choice or affect ad delivery, but it does not prevent access to the archive.

3. Hosting and access logs

The site is hosted by Amazon Web Services through AWS Amplify Hosting, Amazon CloudFront and Amazon S3. When your browser requests any page or asset, AWS processes technical request data needed to deliver and secure the site. Amplify access logs can include the date and time, requested URL and query string, response status, IP address, referrer, and browser or device user-agent information.

This data is used for content delivery, reliability, troubleshooting, abuse prevention and security. AWS states that Amplify retains an app's access logs until the app is deleted. Do not put confidential or sensitive information in this site's URL or query string because those values can appear in logs. See the AWS Amplify access-log documentation and AWS Privacy Notice.

4. Google AdSense: where it loads

Google AdSense code is configured on selected editorial pages. The AdSense loader is currently present only on these six pages:

Visiting one of those pages causes the browser to request Google's advertising script. Google explains that an ad tag can call its servers and may set or read cookies even when the page does not ultimately display an ad. All other current archive pages, including the home page, directories, search, interactive tools and trust pages, omit the AdSense loader.

5. Data processed for advertising

Google and advertising partners made available through AdSense may process cookies and other online identifiers, IP address and approximate location, browser and device information, the page and referrer, consent choices, and ad impressions, clicks or other interactions. They use this data to request and deliver ads, select contextual or personalised ads where permitted, limit frequency, prevent fraud and abuse, and measure and report ad performance.

Third-party vendors, including Google, use cookies to serve ads based on a visitor's prior visits to this site or other websites. Google's use of advertising cookies enables Google and its partners to serve ads based on visits to this site and other sites on the Internet. Other third-party advertising vendors or ad networks may also use cookies where enabled in the AdSense account and allowed by the visitor's choices. The providers available for a consent decision are shown in the consent interface; Google also publishes an advertising technology provider list.

Google explains these practices in How AdSense uses cookies, How Google uses information from sites or apps that use its services, the Google Privacy Policy and its advertising technologies information.

6. Personalised and non-personalised advertising

Personalised and non-personalised advertising may appear through Google AdSense. Personalised ads may use information about prior browsing or app activity, interests, demographics or location to make ads more relevant. Non-personalised ads are selected using contextual information, such as the content of the current page and approximate location, rather than past behavior. Non-personalised ads can still use cookies or identifiers for purposes such as frequency capping, fraud prevention and aggregated ad reporting.

7. Consent and changing your choices

On advertising-enabled pages, United History is configured to use Google AdSense Privacy & messaging, Google's consent management platform. When Google delivers the message, it presents choices where required and communicates them to Google and participating advertising vendors. Depending on location and configuration, the interface can offer options to consent, not consent or manage purposes and vendors. The consent platform may store the choice in cookies or local storage so that it can be recognised later.

On pages that contain AdSense code, Google may provide a “Privacy and cookie settings” link or equivalent revocation control. You can use it to revisit or withdraw a choice. Withdrawal does not affect processing already carried out before it was withdrawn.

You can opt out of personalized advertising from Google through My Ad Center. You can also opt out of some participating third-party vendors’ personalized-ad cookies through YourAdChoices or similar regional advertising choice tools where available.

8. Analytics

United History does not deploy Google Analytics or another standalone audience-analytics service. AWS still creates the hosting access logs described above, and Google AdSense performs advertising measurement and reporting on the six ad-enabled pages. Google's consent tool may also measure interaction with its privacy messages. These operational and advertising records are not a separate site analytics installation.

9. Email correspondence

If you email abstractcs65@gmail.com, the sender address, message, attachments and related reply history are processed to review and respond to the enquiry, correction or privacy request. The mailbox is provided by Google Gmail, so Google processes and stores the correspondence under the Google Privacy Policy. The archive does not use correspondence for a marketing list.

Correspondence is kept only for as long as reasonably needed to handle the request, maintain an appropriate correction or legal record, resolve disputes or protect the site. Avoid sending information that is not needed for the request.

10. External links

The archive links to external sources such as official competition records, club pages, statistical databases and reference sites. The site does not embed those external pages. If you choose a link, your browser contacts the destination and that service's privacy policy applies.

11. Sharing, international processing and retention

Personal data is shared only as described above: with AWS for hosting and security, with Google and participating ad vendors on ad-enabled pages, and with Google Gmail for correspondence. These providers may process data in countries other than your own and describe their transfer safeguards in their privacy documentation.

Retention differs by service. AWS states that Amplify access logs remain until the hosted app is deleted. Advertising and consent data is retained by Google and participating vendors according to their disclosed settings and policies. Email is retained as described in section 9. United History does not build a separate visitor database.

12. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing of your personal data, to withdraw consent, or to complain to a data-protection authority. Contact abstractcs65@gmail.com to make a request concerning data controlled by United History. For data controlled independently by Google, AWS or an advertising vendor, use that provider's privacy controls or contact route.

13. Changes to this policy

This page will be updated before a new analytics, advertising, form, account or other data-collecting service is introduced. The date at the top records the latest review.