Privacy Policy — ZynkWatch

1. Scope of this Policy

This Policy applies to the ZynkWatch website, accounts, channels, videos, profiles, comments, messages, notifications, settings, reports, and other features that link to or refer to this Policy.

It does not automatically apply to websites, services, or applications operated by another organization, even when a ZynkWatch user links to them.

2. Who operates ZynkWatch

ZynkWatch is a video and social platform operated by ZynkWatch (SMC-Private) Limited in Pakistan. The operator decides how and why personal information is processed for the service.

Privacy and account questions can be submitted through the Contact and Report Abuse page. Include enough information to explain your request.

Do not include passwords or verification codes in a privacy request. ZynkWatch may need to verify account ownership before responding to a request involving private account information.

3. Information ZynkWatch collects

Category	Examples	Why it is needed
Account and identity	User ID, first and last name, email address, password hash, account status, verification status, creation date, and last-active information.	Registration, login, account ownership, verification, recovery, security, and administration.
Profile information	Profile and cover pictures, phone number, location, gender, date of birth, bio, website, relationship status, occupation, education, school, college, university, and interests.	To build a profile and display only the details selected for public visibility.
Preferences and privacy settings	Theme, language, timezone, video preferences, comment sorting, and public visibility selections.	To remember settings and provide the experience selected by the user.
Channels and uploaded content	Channel names, descriptions, genres, videos, thumbnails, titles, descriptions, upload dates, and content-management actions.	To host, process, display, moderate, and manage user-created channels and videos.
Social activity	Follows, likes, comments, replies, friend requests, friend connections, and blocks.	To provide social features, counters, relationship controls, and abuse prevention.
Messages and notifications	Direct-message threads, message content, sender and recipient IDs, timestamps, read status, and notification records.	To deliver conversations, alerts, unread counts, safety controls, and requested communications.
Viewing and engagement activity	Watched videos, view events, watch history, watch time, currently watched content, likes, comment activity, and searches.	To provide watch history, counters, recommendations, playback features, anti-fraud checks, and service improvement.
Reports and safety information	Reports, report reasons, supporting details, moderation actions, blocks, and records relevant to suspected abuse.	To review safety concerns, enforce rules, prevent repeated abuse, and comply with lawful obligations.
Technical and security data	IP address, browser and device information, request time, session identifiers, security tokens, error logs, failed requests, and diagnostic information.	To keep sessions working, prevent attacks, investigate errors, secure accounts, and maintain service reliability.
Email and support records	Email verification, password-reset and email-change records, delivery status, support requests, and account notices.	To verify account ownership, recover accounts, change login email securely, and respond to requests.

ZynkWatch does not ask users to provide more profile information than they choose to add, except information required for account creation, security, or a specific feature.

4. Where information comes from

Directly from users: information entered during registration, profile editing, channel creation, uploading, commenting, messaging, reporting, or support.
Automatically from use of the service: session information, timestamps, IP addresses, browser details, watch activity, interactions, and technical logs.
From other users: friend requests, messages, comments, reports, and content involving another user.
From service providers: hosting, email delivery, error, security, or infrastructure information needed to operate ZynkWatch.

5. How ZynkWatch uses information

ZynkWatch may use information to:

create, verify, secure, and manage accounts;
provide profiles, channels, videos, comments, friends, messages, notifications, and watch history;
apply privacy and visibility choices;
process video files and generate technical playback files or thumbnails;
deliver email verification, security, recovery, and account notices;
show content, counters, followed-channel updates, and recommendations;
detect spam, fraud, artificial engagement, abuse, security threats, and policy violations;
review reports and enforce the Terms and platform rules;
debug errors, maintain availability, test features, and improve usability;
protect users, ZynkWatch, and the public;
respond to valid legal requests and comply with applicable law;
establish, exercise, or defend legal claims.

Advertising measurement and monetization features. ZynkWatch uses Google Ads conversion tracking to measure verified registrations associated with its advertising. Where advertiser or creator features are available, account applications, ad activity, earnings, payment references, and payout records may also be processed to operate those features and investigate invalid activity.

6. Public and private areas

Information that may be public

Channel information, uploaded public videos, comments, replies, likes, and profile details selected for public display may be visible to other users or visitors, depending on the feature and account settings.

Users can control public visibility for many profile fields, including email, phone, location, gender, date of birth, bio, website, occupation, education, interests, and watch history.

Information treated as private

Password hashes, login tokens, verification tokens, direct messages, non-public profile fields, private watch history, blocks, and internal security or moderation records are not intended for public display.

Private information may still be accessed by authorized administration or technical personnel when reasonably necessary for security, support, moderation, legal compliance, or investigation of abuse. Access should be limited to what is necessary for the task.

Public visibility controls reduce what other users can see. They do not make submitted information invisible to the ZynkWatch systems that must store or process it.

7. Legal grounds for processing

Where a law requires ZynkWatch to identify a legal basis, processing may rely on one or more of the following:

Performance of a contract: processing needed to provide the account and features requested under the Terms of Service.
Legitimate interests: operating, securing, moderating, preventing fraud, improving, and protecting the service, where those interests are not overridden by applicable user rights.
Legal obligations: processing needed to comply with valid laws, court orders, official requests, and recordkeeping duties.
Consent: where ZynkWatch specifically asks for optional consent, such as for a future non-essential cookie or marketing feature.
Protection of vital interests: limited processing where reasonably necessary to address an urgent threat to life or safety.

The applicable legal basis may vary by feature, country, and the circumstances of processing.

8. When information may be shared

ZynkWatch does not currently sell personal information. Information may be disclosed only in circumstances such as:

According to user choices: public profile details, channels, videos, comments, replies, and other content are displayed as selected or required by the feature.
Hosting and infrastructure providers: providers may process information to host files, databases, backups, network requests, and technical services.
Email-delivery providers: account verification, recovery, and security emails are sent through configured mail infrastructure.
Supporting content-delivery services: when a page loads a third-party technical resource, the provider may receive standard request information such as IP address, browser details, and requested file.
Video processing: Cloudflare Stream receives uploaded video files and related technical metadata for encoding and video delivery when that processing path is used.
Advertising measurement: Google receives conversion information when the Google Ads tag runs after a successful first email verification. Google may process cookie identifiers, ad-click information, and technical request information for measurement. See how Google uses information from sites using its services.
Legal and safety disclosures: information may be disclosed when reasonably necessary to comply with law, a valid order, protect rights, investigate fraud or abuse, or address a serious safety risk.
Business restructuring: if ZynkWatch is transferred, reorganized, financed, or acquired, relevant information may be transferred subject to appropriate confidentiality and legal safeguards.

Service providers should receive only information reasonably needed to perform their services and are not authorized by ZynkWatch to use it for unrelated purposes.

9. International hosting and transfers

ZynkWatch is operated from Pakistan and uses external hosting and email infrastructure. Personal information may therefore be processed in countries other than the user’s country.

The current hosting arrangement uses Hostinger infrastructure selected in the Netherlands, and hosting backups may be stored through infrastructure in Lithuania. Email traffic may pass through the locations used by the configured email and network providers.

These locations and providers may change as ZynkWatch develops. Where applicable law requires safeguards for an international transfer, ZynkWatch will use a legally recognized transfer method or another appropriate safeguard before relying on that transfer.

10. How long information is kept

ZynkWatch keeps personal information only for as long as reasonably necessary for the purposes described in this Policy, including providing the service, maintaining security, resolving disputes, and meeting legal obligations.

Active account data: generally kept while the account remains active.
Profile and content: generally kept until the user edits or deletes it, deletes the account, or ZynkWatch removes it under platform rules.
Watch history: kept until the user removes individual entries, clears history, deletes the account, or retention is otherwise required for security or legal reasons.
Messages and social records: kept while needed to provide conversations, relationships, safety functions, and account records.
Email-change requests: verification links expire after 30 minutes and are designed for one-time use. Used or expired records may be removed during cleanup.
Other verification and recovery tokens: become unusable when used, replaced, expired, or the related process ends.
Security, diagnostic, and moderation records: kept for a period reasonably needed to investigate abuse, prevent repeated violations, repair errors, defend claims, and comply with law.
Backups: deleted or changed data may remain temporarily in protected backups until those backups are overwritten under the provider’s backup cycle.

Exact retention may vary where a longer period is required by law, a valid legal request, a dispute, fraud prevention, safety, or technical recovery needs.

11. Security

ZynkWatch uses technical and organizational measures intended to protect information, including password hashing, sessions, CSRF protection, access controls, verification tokens, rate limits for sensitive actions, encrypted website connections, and restricted database operations.

No internet service can guarantee absolute security. Users should use a unique password, keep access to their email account secure, avoid sharing tokens, and sign out from shared devices.

If ZynkWatch identifies a security incident that creates a legally reportable risk, affected users and relevant authorities will be notified where required by applicable law.

12. User choices and controls

Depending on the feature, users can:

edit profile details;
choose which supported profile fields are public;
make watch history public or private;
remove individual watch-history entries or clear history;
follow or unfollow channels;
accept, decline, or remove friend connections;
block users;
delete eligible comments, messages, videos, channels, or other content;
change password and securely request an email change;
choose language, timezone, theme, and supported playback preferences;
request account deletion or anonymization through the available account process.

13. Privacy rights

Privacy rights differ by country. Where applicable law provides them, a user may have rights to:

receive information about processing;
request access to personal information;
correct inaccurate or incomplete information;
request deletion of eligible information;
request restriction of certain processing;
object to certain processing;
receive eligible information in a portable format;
withdraw consent where processing is based on consent;
complain to an applicable privacy or data-protection authority.

ZynkWatch may need to verify the requester’s identity before fulfilling a request. A request may be limited or refused where the law permits or requires it, including to protect another person’s rights, preserve security, prevent fraud, comply with law, or maintain information needed for a legal claim.

Deleting an account may anonymize the account rather than erase the numeric user ID. This helps preserve database integrity, prevent reuse or impersonation, and keep remaining content correctly attributed to a deleted user. The deletion screen should explain the available deletion mode before the user confirms it.

14. Children and minimum age

ZynkWatch accounts are intended only for people who are at least 16 years old. ZynkWatch does not knowingly permit children under 16 to create accounts.

If ZynkWatch learns that an underage account has been created, it may restrict or remove the account and related information, subject to security, safety, and legal retention needs.

15. Cookies and local storage

ZynkWatch uses browser storage that is necessary or useful for the service, including:

session cookies used to keep a user signed in;
security values used to protect requests;
theme and appearance selections;
language, timezone, and playback preferences;
temporary interface state, such as the last selected tab.

Google Ads conversion tracking can use cookies and similar identifiers to measure advertising results. The verification page is configured to send a conversion only when an account changes from unverified to verified; failed and repeated verification visits do not send that conversion. Before loading the tag, the page attempts to remove the verification token from its address and sets the measured page address without the token. The conversion event does not explicitly include your email address or password.

Browser privacy settings can limit cookies and tracking. ZynkWatch profile-visibility settings do not themselves disable third-party advertising measurement. For information about Google's storage, see Google's cookie information.

Blocking necessary session storage may prevent login or other essential features from working.

16. Recommendations and automated decisions

ZynkWatch may use viewing activity, follows, engagement, or simple ranking signals to select or order videos, channels, suggestions, and counters.

ZynkWatch does not currently use solely automated decision-making that is intended to produce legal or similarly significant effects on a user. Safety, moderation, fraud, or eligibility signals may assist human review, but important enforcement or monetization decisions should include appropriate review and safeguards.

17. Changes to this Policy

ZynkWatch may update this Policy when features, providers, legal requirements, or data practices change. The page will show the current version and effective date.

Material changes may be announced through the website, account notifications, email, or another reasonable method. Where applicable law requires consent for a new type of processing, ZynkWatch will request that consent before beginning the processing.

18. Privacy contact

Use the Contact and Report Abuse page to request access, correction, deletion, or other privacy assistance.

Privacy requests and questions can be submitted through the Contact and Report Abuse page. State that your message is a privacy request and identify the account or issue concerned without including passwords or secret verification links.

Do not send a password, complete password-reset link, verification token, government identity document, or other highly sensitive information through an ordinary message unless ZynkWatch provides a secure method and specifically requests it.