Cookies, explained clearly.
This page explains the browser technologies used by PlayerCFG, why they may be used, and the controls available to you.
open --cookies READYWhat cookies are
Cookies are small text files that a website or its service providers may place in your browser. Similar technologies, including local storage, pixels and device identifiers, can perform related functions. They can be necessary for a feature to work, remember a preference, measure usage or support advertising.
Cookie and similar technology categories
Google advertising cookies
PlayerCFG uses Google AdSense code. Google and other third-party vendors may use cookies to serve and measure ads based on visits to this site or other sites. Google explains that users can manage personalised advertising through My Ad Center, and visitors may also use the relevant browser, device or industry opt-out controls.
For further detail, see Google AdSense Required Content, How Google uses cookies and Google Advertising.
Consent and regional controls
Cookie and advertising rules differ by location. For visitors in the EEA, United Kingdom and Switzerland, Google requires publishers serving personalised ads to use a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. A policy page alone does not replace a consent mechanism. Where consent is required, advertising choices must be collected and communicated before the relevant advertising technologies operate.
Managing or withdrawing your choices
Most browsers let you inspect, delete or block cookies. Blocking all cookies can affect sign-in or saved-preference features. You can remove PlayerCFG local preferences from your browser's site data controls, delete saved converter presets from your account after sign-in, and contact the publisher for questions about data connected to a correction or visual suggestion.
Updates to this notice
We may update this Cookie Policy when site features, advertising partners or legal requirements change. The effective date below identifies the current version.
Effective date: 27 August 2026. Contact: @mikelmonk on Telegram.
