Cookie Notice
This notice explains how watchFIWN uses cookies and browser storage across the public website and private app.
Last updated: July 1, 2026
What we use
watchFIWN uses cookies, localStorage, and similar browser storage to run login, remember app state, protect sessions, keep drafts responsive, measure traffic, and support billing or OAuth flows.
Some cookies are set by watchFIWN. Others may be set by third-party services such as Google, Razorpay, PayPal, or infrastructure providers when you use those features.
Local app storage
The app may store profile cache, project cache, draft project data, dev flags, admin control preview values, brand settings, and marketing media settings in localStorage so the interface stays fast and resilient.
Signing out clears the main user and project caches. You can also clear browser site data if you want to remove local copies from your device.
Analytics and operations
Traffic and operational data may include domain, page path, browser, device, country-level location, timestamp, referrer, and basic request details. We use this to understand usage, reliability, security, and abuse patterns.
We do not use this notice to claim consent for unrelated advertising tracking. If advertising or retargeting cookies are added later, this notice should be updated before launch.
Your choices
You can block or delete cookies and localStorage through your browser settings. Blocking essential storage may prevent Google login, dashboard access, uploads, exports, billing, or admin actions from working.
For questions about cookies or local data, contact info@watchfiwn.cc.