Cookies and browser storage on PicRemedy

Image and analytics storage

The image workflow does not write a source or generated image to local storage, session storage, IndexedDB, cookies or a service-worker image cache. The audience integration is cookieless, sends only property-free work_started and work_completed events and honours Do Not Track.

Advertising choices

The current advertising unit id is empty, so the reserved surface is hidden and does not request the Google ad library. If advertising is configured later, Google may use cookies or similar storage according to the visitor's region and consent choice.

Personalised advertising in the EEA, United Kingdom or Switzerland requires a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. Declining that choice must leave both local image tools usable. Applicable US state opt-out controls must be available before targeted advertising is activated.

Image-workflow separation

PicRemedy does not add a source file, file name, thumbnail, decoded pixel, selected mode, dimensions or generated result to audience or advertising event properties.