1. What cookies are
Cookies are small pieces of text stored by a website through a browser. They can help a website recognize a browser during a session, maintain authentication, remember preferences, or measure how a service is used.
A session cookie is normally removed when the browser session ends. A persistent cookie or local-storage value can remain until its expiry date or until the user or website removes it.
“Similar technologies” include browser features such as local storage and session storage. They are not always technically cookies, but they can perform similar functions.
2. Storage currently used by ZynkWatch
| Storage | Purpose | Type and duration | Status |
|---|---|---|---|
|
PHP session cookie Its exact name can depend on server configuration. |
Maintains login and connects browser requests to the correct server-side session. It may also support account security and temporary notices. | First-party session cookie. It normally ends when the browser session ends, subject to browser and server configuration. | Essential |
| CSRF and security state | Helps protect forms and sensitive actions against unauthorized requests. Tokens are generally held in the server-side session and sent in forms. | First-party session security data. It normally lasts for the active session or until replaced. | Essential |
|
Theme preference For example: ZW_THEME |
Remembers light, dark, or system appearance so pages open with the expected display. | First-party local storage. It remains until the choice is changed, site data is cleared, or ZynkWatch removes it. | Preference |
| Playback and interface preferences | May remember mute state, autoplay preference, comment sorting, language, timezone, or temporary interface state. | First-party browser storage or account settings. Duration depends on the preference and may continue until changed or cleared. | Preference |
| Temporary security and workflow state | Supports controls for login, registration, password recovery, email verification, and contact submissions. | Primarily server-side session data. It is temporary and normally removed or reset after the relevant security window. | Essential |
| Saved upload data | Upload Manager uses browser database storage (IndexedDB) to retain selected files, upload details, and progress so transfers can be resumed in the same browser and account. | First-party browser storage. Data remains until removed by the uploader, cleared by the user, or removed by the browser. Clearing site data can prevent an unfinished transfer from resuming. | Upload workflow |
| Google Ads measurement | Measures advertising conversions such as a verified registration. May use cookies and advertising identifiers; see section 5. | Google tag storage and identifiers. Exact names and retention depend on the provider configuration and browser settings. | Advertising measurement |
3. Essential storage
Essential storage is needed to provide a feature requested by the user or protect the service. This can include login sessions, authentication, form-security tokens, rate limits, and technical operations required for the website to work.
Disabling or deleting essential cookies can prevent login, log the user out, invalidate forms, interrupt password or email verification, or stop other account features from working.
4. Preference storage
Preference storage helps ZynkWatch remember choices without requiring users to set them again on every page. Examples can include theme, language, timezone, playback, mute, and comment sorting.
Some preferences may be saved both in the browser and in the account database so they can apply consistently across pages or devices.
5. Analytics, advertising, and monetization
ZynkWatch uses Google Ads conversion tracking to measure verified registrations associated with its advertising. On the email verification page, the tag is configured to send a conversion only when an account first changes from unverified to verified. Failed or repeated verification visits do not send that conversion.
Google Ads measurement can use cookies, ad-click identifiers, conversion events, and technical request information. The conversion event does not explicitly send your email or password. The page attempts to remove the verification token before loading the tag and sets the measured page address without that token.
Cookie names and lifetimes depend on Google's configuration and browser behavior. Read Google's cookie information and how Google uses information from sites using its services for provider details.
ZynkWatch also creates server logs and account records for security, troubleshooting, video views, watch activity, fraud prevention, advertising delivery, and creator earnings where those features are used. Database records are distinct from browser cookies and are covered by the Privacy Policy.
Browser privacy settings can limit cookies and tracking. Profile-visibility controls do not themselves disable Google Ads measurement, and reading this policy does not change browser settings.
6. Third-party content and services
ZynkWatch displays or connects to content and technical services operated by third parties. A third party may use its own cookies or similar technologies when its service is loaded. ZynkWatch does not control a third party’s independent storage practices.
Where appropriate, third-party content that uses non-essential storage should not be loaded until the required user permission has been obtained.
7. Managing browser storage
Most browsers allow users to view, block, or delete cookies and site data. The exact steps depend on the browser and device.
- Delete cookies and stored site data for ZynkWatch.
- Block all cookies or cookies from selected sites.
- Clear local storage through browser privacy settings.
- Use private-browsing mode to reduce persistent local storage after the private session closes.
Clearing site data may sign the user out and remove locally saved preferences or unfinished upload data. Blocking essential storage may make parts of ZynkWatch unavailable.
8. Changes to this policy
ZynkWatch may update this policy when browser-storage practices, features, service providers, legal requirements, analytics, advertising, or monetization systems change.
The updated version and effective date should be displayed on this page. Material changes may also be communicated through the website or account notices.
9. Questions and requests
Questions about cookies, browser storage, privacy, or ZynkWatch’s data practices can be submitted through the Contact and Report Abuse page.