Cookie Policy
This policy describes the storage technologies visible in the current MatchSignal codebase. Cookies are small files; localStorage is browser storage that can persist without a fixed expiry. Third-party identifiers can vary, so Google advertising examples below are deliberately non-exhaustive.
Storage and cookie inventory
| Provider | Category | Identifier / example | Party | Purpose | Duration / criterion | Consent |
|---|---|---|---|---|---|---|
| MatchSignal | Necessary | matchsignal_consent (localStorage) | First party | Stores analytics choice and timestamp; fallback advertising permission stays denied | Until changed or browser data is cleared | No; necessary to remember the requested choice |
| Google Analytics 4 | Analytics | _ga; _ga_<container-id> | First-party cookies set for Google | Distinguishes browser instances and maintains session/measurement state | Commonly up to 2 years, subject to Google/configuration | Yes |
| Google AdSense / Google | Advertising | Examples may include __gads, __gpi, IDE, NID or other Google identifiers | First or third party depending on identifier | Ad delivery, frequency, fraud prevention, measurement and—only with valid consent where required—personalization | Varies by identifier, account and Google policy | Required where applicable; personalized ads require valid consent |
| Google consent services / CMP | Necessary or consent | Consent strings and vendor-defined storage, including IAB TCF data where applicable | First or third party | Records and communicates privacy choices | Varies by CMP and consent record | Used to record or transmit the choice itself |
What the code currently does
- MatchSignal does not use sessionStorage or directly write document.cookie in the application source.
- GA4 is not loaded until analytics permission is available.
- The MatchSignal fallback consent panel controls analytics only and always keeps advertising storage denied.
- AdSense and Google consent hooks are present in the root layout; their runtime UI and vendor cookie set can vary by region, configuration and Google delivery.
CMP and advertising consent
For users in the EEA, UK and Switzerland, personalized Google advertising requires a Google-certified CMP integrated with IAB TCF. MatchSignal's architecture listens for Google consent values where available and otherwise provides its own analytics-only fallback. This description does not claim that a Google dialog is currently displayed successfully on every visit. Advertising services must respect the consent signals and CMP choices that are available.
Your controls
Use Cookie Settings below to reopen the active consent control. You may also clear or block browser storage in your browser. Blocking non-essential storage may reduce measurement or advertising functionality but should not prevent access to core informational content.
Updates and contact
Google may change cookie names and lifetimes, so this inventory is not an exhaustive list of every Google advertising identifier. We update this policy when the implementation materially changes. Questions: privacy@matchsignal.pro.
Operator information
- Name
- Forray Gyöngyi
- Legal status
- Sole proprietor / individual entrepreneur
- Address
- 7633 Pécs, Esztergár Lajos utca 9/B, Hungary
- Hungarian Tax Number
- 74264166-1-22
- Sole Proprietor Registration Number
- 57756666
- Registry
- Hungarian National Tax and Customs Administration (NAV) / Hungarian Individual Entrepreneurs Registry
- Roles
- Website maintainer and technical operator; commercial and affiliate activity operator; data controller where MatchSignal determines processing purposes
- Contact
- contact@matchsignal.pro · legal@matchsignal.pro · privacy@matchsignal.pro
Last updated: 20 August 2026