← Back to Playground Forge Playground Forge trust and policy pages
Privacy | Playground Forge
This Privacy page explains what data may be processed while using Playground Forge, how browser-run tools work, and where visitors can manage cookies and consent. If Google AdSense, Google Analytics, or other Google services are enabled, cookies, local storage, advertising identifiers, IP-derived signals, web beacons, and third-party vendor processing may apply under Google policies and user consent controls.
Browser-first tools
Playground inputs are processed in the browser for the public tools covered by this site. The service does not ask visitors to create an account to use the catalog or playgrounds. Avoid entering secrets or personal data into examples because outputs may remain visible in the current browser session.
Cookies, consent, and Google services
The site can use consent-aware analytics and may use Google services such as Google Analytics or Google AdSense. If ad serving is enabled later, third-party vendors, including Google and selected ad technology partners, may use cookies or similar technologies to serve ads based on a visitor's prior visits to Playground Forge or other websites. Google's advertising cookies may allow Google and its partners to personalize or measure ads; other vendors or ad networks may also place or read cookies, use web beacons, IP addresses, device identifiers, and local storage when permitted by consent rules. Visitors can manage Google ad personalization at https://adssettings.google.com/, review partner ad settings at https://adssettings.google.com/partnerads, use industry opt-out tools such as https://www.aboutads.info/choices/ or https://www.youronlinechoices.com/, and change browser cookie settings.
Ads and where they may appear
If ads are enabled, they are handled according to user consent requirements. They should not appear on empty screens, redirect pages, error states, no-content result views, or areas without publisher content. On tool pages, the description, safe starting point, and clear limitations come first. Ads should not cover controls, output, error messages, or the first orientation area of the page.
Rules before ads can run
Advertising is enabled only after a separate operational review, not simply because Google scripts are present. The site needs a positive Google AdSense status, a published consent panel for required regions, and verified consent handling for visitors in the EEA, the UK, and Switzerland before personalized or measured advertising is allowed. Until those conditions are met, Playground Forge keeps display advertising disabled.
The content boundary matters as much as the consent boundary. Advertising is not allowed on redirect pages, error states, empty screens, search-only views, trust pages without main publisher content, or routes that have not been explicitly approved for ads. This privacy page records that rule so future advertising changes start with route quality checks instead of assuming every public URL is eligible.