What does match.com track?
match.com loaded no advertising or analytics trackers before consent.
Scanned October 2, 2026 from Germany, loading uk.match.com/?geo-redirection=match.com once and clicking nothing. How we scan
- Tracking companies
- 0
- Tracking cookies
- 0
- Third-party hosts
- 3
- Cookies in total
- 4
Consent banner
The page loaded OneTrust, a consent management platform. Everything below was recorded before anyone answered it.
Companies contacted before consent
1 of the 2 companies it contacted before consent were unclassified.
None.
Other third parties (content delivery, consent, functional, unclassified)
- arkoselabs.com2 requestsUnclassified
match-api.arkoselabs.com
- OneTrust13 requestsConsent banner
cdn.cookielaw.org, geolocation.onetrust.com
Cookies set before consent
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
| authtoken | Unclassified | uk.match.com | 12 months |
| machineid | Unclassified | uk.match.com | 12 months |
| __cf_bm | Functional | match.com | Under a day |
| OptanonConsent | Functional | uk.match.com | 12 months |
Understanding this page
- How to see which cookies and trackers a website loads
A hands-on walkthrough for checking what a site sets before you've clicked anything, using Chrome and Firefox's built-in tools, plus how CookieTosser automates the same check every month.
- What counts as valid cookie consent in the EU
The rules that actually govern cookie banners — the ePrivacy Directive, the GDPR consent standard, the Planet49 ruling, the strictly-necessary exemption, and what "reject" has to offer compared with "accept.
- Consent management platforms explained
What a CMP banner is actually doing behind the scenes, how the IAB's TCF standard and Google's Consent Mode v2 fit in, and why a banner being present is no guarantee that nothing loads before you answer it.