Opt-out of FLEDGE
For developers and users who want to opt-out of FLEDGE.
FLEDGE will eventually require sites to set a Permissions Policy to allow FLEDGE functionality to be available. This will help ensure that arbitrary third parties can't use the API without a site's knowledge. However, to facilitate testing during the first origin trial, this requirement is waived by default.
Sites that would like to explicitly disable FLEDGE functionality during the testing period can use the relevant Permissions Policy to block access. There are two FLEDGE permissions policies that can be set independently:
join-ad-interest-groupenables/disables functionality to add a browser to interest groups
run-ad-auctionenables/disables functionality to run an on-device auction
Access to FLEDGE APIs can be disabled completely in first-party contexts by specifying the following permissions policy in an HTTP response header:
Permissions-Policy: join-ad-interest-group=(), run-ad-auction=()
You can disable usage of the APIs in an iframe by adding the following
allow attribute to an iframe element:
<iframe src="https://example.com" allow="join-ad-interest-group 'none'; run-ad-auction 'none'"></iframe>
The Proposed First FLEDGE Origin Trial Permissions-Policy section provides more detail.
A user can block access to the FLEDGE API and other Privacy Sandbox features by using any of the following mechanisms:
- Disable the Privacy Sandbox trials in Chrome Settings: Settings > Security and privacy > Privacy Sandbox. This is also accessible at
- Disable third-party cookies in Chrome Settings: Settings > Security and privacy.
- Set Cookies and other site data to either "Block third-party cookies" or "Block all cookies" from
- Use Incognito mode.