Cookies and Advertising
Notice for strictly necessary storage, extension state, optional advertising technologies, and consent controls.
Strictly necessary technology
- 1.1
dx Capture may use secure session cookies, browser local storage, browser extension storage, upload/share/playback state, operational logs, and audit records for security and reliability.
Advertising technologies
- 2.1
dx Capture currently renders first-party house promotions only. Google ad tags, Google ad requests, and optional advertising storage are disabled while site review, consent, and content-review controls remain incomplete.
- 2.2
If Google advertising is enabled later, third-party vendors including Google may use cookies to serve ads based on a visitor's prior visits to dx Capture or other websites. Google's advertising cookies enable Google and its partners to serve and measure personalized ads where the visitor has made an eligible choice.
Consent controls
- 3.1
Where consent is legally required, dx Capture must use an eligible consent management platform and must not request Google ads until a valid consent signal has been collected. Visitors must be able to reject optional technologies and revisit their choices.
- 3.2
For visitors in the EEA, the UK, and Switzerland, personalized Google ads require a Google-certified consent management platform integrated with the applicable IAB Transparency and Consent Framework.
Technology categories
- 4.1
Necessary technologies support authentication, security and abuse prevention, upload, share, and playback operation.
- 4.2
Advertising technologies may support third-party ad delivery, ad measurement, and personalized ads if enabled. Product analytics should be separately reviewed if added later.
Production advertising prerequisites
- 5.1
Before Google ads are enabled, the AdSense account and doxanh.dev site must be approved, placements must be configured, the required ads.txt record must be reachable from the registrable domain, and the selected Google-certified consent flow must be active where required.
- 5.2
Google ads must remain disabled on sign-in, workspace, legal, empty, error, navigation-only, and protected-access screens. User-generated share pages require a documented content-review eligibility decision before Google ads can be requested.
- 5.3
The current release does not yet store a per-share Google-ad eligibility decision, so all configured viewer inventory continues to resolve to house content.