# Privacy Notice — Draft **Draft version:** `draft-2026-10-13-v1` · **Effective date:** Not set · **Data controller / fiduciary:** `[LEGAL ENTITY NAME]` > This is a data-map template, not a final notice or compliance certification. Complete the actual provider list, retention periods, legal bases, transfer locations, and rights contacts before publication. Do not collect data merely because a field exists in this draft. ## 1. Who is responsible HDHub4You is operated by **[full legal name and address]**. Privacy contact: **[privacy email and postal address]**. India grievance contact, if applicable: **[designated contact]**. EU/UK representative or Data Protection Officer, if legally required: **[details]**. ## 2. Data we may process Depending on features you use, we may process account identifiers and contact details; authentication, session, and security events; profile, language, accessibility, and recommendation choices; searches, watch progress, likes, comments, reports, and interactions; uploads, metadata, ratings, moderation records, and creator-channel data; subscription, payment-token/reference, invoice, and refund records; creator identity and payout information where you request verification or earnings; advertiser organization, campaign, creative, and billing records; support messages; and technical diagnostics such as device/app version, approximate network location, and event timestamps. We do not intend to collect precise location, contacts, biometric identifiers, or government identity documents for ordinary viewing. Identity documents may be requested only for a clearly stated creator verification or payout purpose and only after the secure flow and retention basis have been approved. Do not submit Aadhaar or other national IDs unless the product explicitly requests an accepted document and the privacy notice explains the purpose and alternatives. ## 3. Purposes and legal bases We use data to create and secure accounts; deliver requested playback and creator/advertiser features; process payments and entitlements; enforce age, content, and plan rules; handle support, moderation, appeals, fraud, and abuse; maintain service reliability; measure permitted aggregate performance; comply with legal obligations; and, only where permitted and with required choice, personalize recommendations or advertising. The final notice must map each purpose to the legal basis or consent required in each market and identify any legitimate-interest balancing assessment. Recommendation settings can use selected languages and, if enabled, a user's own watch history. Users should be able to turn history-based personalization off. Do not use sensitive characteristics or covert fingerprinting for ad targeting. Do not use watch behavior to infer sensitive traits. ## 4. Sharing and processors We may share the minimum necessary data with infrastructure and storage vendors, authentication providers, payment processors, email and support vendors, moderation/security providers, analytics/advertising vendors if activated, professional advisers, and authorities where legally required. The live vendor list, processing locations, contract safeguards, and each provider's role must be published at **[vendor list URL]** before production use. We do not authorize vendors to use platform data for unrelated purposes unless disclosed and lawful. ## 5. International transfers Data may be processed in **[verified countries/regions]**. Before a transfer, the operator must identify the legal transfer mechanism, vendor safeguards, government-access risks, and local restrictions. A country selection or CDN route is not a legal transfer assessment. No complete country-by-country transfer inventory is currently confirmed by this draft. ## 6. Retention We retain data only for documented service, safety, accounting, dispute, and legal needs. The approved schedule must state a concrete retention period for each category, trigger, and deletion/anonymization method. Security logs, financial records, creator KYC records, and account profile data must not share one blanket retention period. Legal holds suspend deletion only for the relevant records. Current approved retention schedule: **[URL/version]**. ## 7. Security We use access controls and technical safeguards appropriate to the risk, including protected authentication, role restrictions, encrypted transmission, and secure storage controls where configured. No internet service can promise perfect security. Report suspected exposure to **[security/privacy contact]**. Internal incident handling and statutory reporting follow applicable law. ## 8. Your choices and rights Depending on your location, you may request access, correction, deletion, portability, restriction, objection, consent withdrawal, or review of a decision. You may change language and recommendation settings in profile, and advertising choices at **[ad choices URL]** when advertising is enabled. Submit a request to **[privacy email/form]** with the account email and request type. We may verify identity proportionately and may retain limited records where law permits or requires. Response times and appeal channels must be localized to applicable law. ## 9. Children and age-restricted content The service must not be treated as a child-safe or fully age-assured product until approved age assurance, ratings, parental controls, and enforcement are implemented and verified. Where applicable, we obtain verifiable parental consent before processing a child's personal data for a service directed to children or where required by law. Age gates must not be presented as identity verification unless they actually provide that assurance. See the Age and Child Safety policy. ## 10. Advertising and cookies Essential authentication and security storage supports requested account functions. Optional analytics or ad technologies must not be activated before the applicable consent or other lawful basis is established. The current web app must keep optional ad/analytics tags disabled until the consent manager is connected to every relevant SDK and server-side signal. A choice stored only in a browser is not a complete, auditable consent record. ## 11. Changes and contacts We will publish a new version and effective date and give notice where required. Contact **[privacy email]**. Grievance contact: **[details]**. Supervisory authority or regulator complaint options depend on your location.