Cookies &
local storage.
IDFlow uses browser storage for a media preference and referral attribution, plus measurement tags that help understand site traffic and campaign performance.
Current browser storage
When you enable or disable sound on the homepage video, IDFlow stores that preference locally in your browser under the key idflow-video-sound. This avoids asking for the same preference on every visit.
If you arrive through a recognised partner referral link, we remember its campaign code in your tab’s session storage under idflow-referral. This keeps attribution while you browse and refresh. It contains no contact details, is not used for cross-device tracking, and is normally cleared when the tab’s session ends. Browser session restoration may retain it. Blocking storage does not prevent signup but may prevent attribution after navigation or a refresh.
Cookies and analytics
The website header loads Google Tag Manager and the Meta Pixel so IDFlow can measure visits, referrals and campaign performance. Google Analytics 4 is delivered through Tag Manager. These services may set their own cookies or similar identifiers. Google Search Console verification is a static ownership tag and does not measure visitors.
Your controls
You can remove local site data, restrict storage or block cookies through browser settings. Restricting essential site storage may cause preferences to reset but should not prevent access to public website content.
For information submitted through forms, read the privacy notice.
Control stays with you.
You can clear IDFlow site data or block third-party cookies through your browser settings at any time.