Privacy Policy

1. Operator, Scope and Contact

Who is responsible for this notice

1.1 Operator. MOYOTUBE TECHNOLOGIES LLC is a New Jersey domestic limited liability company, formed October 8, 2026, entity ID 0451541172. The main business address in its supplied formation certificate is 2110 E RT 70, Cherry Hill, NJ 08003, United States. “MoyoTube,” “we,” “us” and “our” refer to that company.

1.2 Scope. This notice covers processing we determine for the MoyoTube platform and associated support and commercial relationships. It applies to viewers, listeners, account holders, creators, members, buyers, sellers, advertisers, sponsors and people who contact us. Employment and unrelated affiliate services require their own notices where applicable. 1.3 Controller role. We are responsible for processing for which we decide the purposes and means. A payment provider, seller, creator or external website may independently determine its own processing; that party’s notice applies to its independent activities. We do not describe every external party as our processor simply because it interacts with the platform.

1.4 Privacy contact - complete before publication.

[CONFIRM AND INSERT monitored privacy email and working web request URL.] Postal correspondence: Privacy Requests, MOYOTUBE TECHNOLOGIES LLC, 2110 E RT 70, Cherry Hill, NJ 08003, United States. Verify the address accepts privacy correspondence before publishing it.

1.5 Regional contacts. If an EEA or UK representative or data protection officer is required, its verified identity and contact details must be inserted in the regional notice. No representative, DPO appointment or certification is asserted by this draft.

1.6 Your choices. This policy explains processing; it is not blanket consent. We will request separate consent when required, including for optional cookies or marketing. You may exercise applicable rights without accepting a waiver of legal protections.

2. Information Categories

Collection depends on the features you use Information you provide

Account and profile information: registration and sign-in details, profile name, avatar, description, preferences and contact details actually requested by the platform. Password credentials must be handled securely; do not send passwords through support messages. Content and participation: uploaded videos, audio, podcasts, images, titles, comments, chats, listings and associated metadata. A recording can include voices, faces, names and other people’s information. Public and protected content have different access conditions. Commercial and transaction information: purchases, membership periods, contributions, bids, sale records, campaign details, receipts, fees, ledger credits and payout requests. Identity, tax and payment-verification records may be required for relevant commercial features; collect only what is needed.

Support and claims: enquiry text, attachments, incident reports, appeals, copyright notices and counter-notices, correspondence and records of resolution.

Information associated with use

Technical and usage information: account or device identifiers, session and security records, browser or device information, interaction timestamps and relevant playback or engagement records. Exact production logging and third-party tracking must be audited before publication.

Recommendation information: consented content-interaction history, category and creator affinities, preference settings and coarse country context used by the documented recommendation design. Pseudonymous browser identifiers can still constitute personal information.

Sensitive information: identity documents, financial credentials, sensitive content and information revealing protected characteristics can require additional safeguards. [VERIFY which sensitive categories are actually collected, sources and uses.] This draft does not establish biometric identification, precise location tracking or collection of every sensitive category.

3. Sources and Public Visibility

Understand what others can see

3.1 Direct sources. We receive information when you register, submit content, interact with features, transact, change preferences or contact support. Avoid including unnecessary sensitive information in public descriptions, uploads or routine enquiries.

3.2 Automated sources. Available technical systems can record activity and session information when you use the platform. The recommendation design derives country context from trusted infrastructure information; it does not establish continuous GPS tracking. Cookies and similar technologies are described in section 6 and the dedicated Cookies notice.

3.3 Other parties. Where applicable, payment providers, commercial partners, sellers, rights holders or users may provide transaction confirmations, complaints, claim material and related information. [CONFIRM any social sign-in providers, verification vendors, enrichment services and imported data before including them in the live notice.] 3.4 Public material. Information you intentionally publish through public channels, comments, streams or auction listings can be visible to others and copied, shared or indexed outside MoyoTube. Your chosen profile name may identify your activity. Do not upload someone else’s private information without an appropriate basis.

3.5 Protected access. Membership or restricted access limits ordinary playback through the relevant feature but is not an assurance that authorized viewers cannot record or disclose material. Teaser images and other deliberately public previews can be visible to non-members. Confirm audience visibility before publishing.

3.6 Transaction disclosure. A seller or buyer may need information to complete a sale, delivery or dispute, but should receive only what is necessary. [CONFIRM whether bid identity, winner identity and shipping details are displayed or transmitted, and to whom.] Bid visibility should be explained before participation, not assumed by this notice.

3.7 Third-party links. External sites and services have separate practices. This notice governs our processing, not all information a linked service independently collects.

4. Purposes and Legal Bases

Use information for defined purposes

4.1 Provide the service. Account operation, authentication, requested playback, publishing, protected access, purchase fulfilment and related communications use the information needed to perform the service. Where GDPR-type law applies, contractual necessity may support processing genuinely necessary for the requested contract, not optional advertising merely described in Terms.

4.2 Recommendations and optional tracking. The documented personalization design uses opt-in consent. Optional cookies and separately requested marketing processing need the applicable consent or other lawful basis permitted for that purpose. Consent should be specific, informed and withdrawable; refusal is not consent.

4.3 Safety, integrity and support. Fraud prevention, access security, abuse investigation, rights-claim handling and support may rely on legitimate interests where permitted and balanced against individual rights, or on legal obligations where they apply. The interests are maintaining a safe, reliable service and protecting users and rights holders.

4.4 Payments and records. We process necessary transaction information for payment administration, accounting, taxes, verification, dispute resolution and applicable reporting duties. Each identity check needs an actual legal or operational justification; “compliance” is not an unlimited purpose.

4.5 Product improvement. Relevant performance and diagnostic information can help diagnose failures and assess service use. Personal-data analytics require an appropriate basis and controls; data is not automatically anonymous because a direct name is removed. 4.6 Sensitive data. Where explicit consent or another specific condition is required, we must obtain or document it before the relevant use. We will not assume that a general content licence authorizes unrelated sensitive profiling.

4.7 Required information. Failure to supply necessary account or transaction information can prevent the relevant feature. Optional information should be identified as optional. [CONFIRM collection fields and map each purpose to its actual lawful basis before publication.] We will provide updated information and consent where legally required before materially different processing.

5. Recommendation Profiles

Documented design - verify deployed settings before adoption

5.1 Opt-in profiles. The supplied design stores personalization history only for a consenting account or browser profile. A pseudonymous browser profile uses a signed HTTP-only cookie. Signed-in profiles can persist consented history across sessions. Clearing or blocking the relevant cookie can prevent browser-history continuity; users then receive available country or global fallback discovery.

5.2 Interaction signals. With the relevant consent, clicks, watch or completion signals, shares, dislikes, likes, comments, bookmarks and bids can contribute to category or creator interests. A preference event is not proof of a unique real person, fraud-free viewing, or an entitlement to monetization.

5.3 Ranking. The design ranks suitable content using category and creator affinity and relevant context, respecting exclusions. It uses up to 3,000 recent events and a 30-day weighting decay. Those are design parameters, not immutable settings or an assertion that all production data is limited to the recommendation subsystem.

5.4 Retention and control. The documented default for recommendation events is 180 days, with daily cleanup. Feed-session snapshots expire after one hour. Turning personalization off deletes the associated profile, events and feed sessions in the documented feature. [CONFIRM actual worker operation, configuration and backup handling before adopting these statements as live practices.] 5.5 Export. Recommendation-history export is paginated and tied to the account or browser identity. It is a feature-specific export, not a complete response covering all personal information held elsewhere. A broader privacy access request must search relevant account, transaction, support and vendor records too.

5.6 Important decisions. Ordinary content ranking is distinct from automated decisions with legal or similarly significant effects. [VERIFY whether automated systems determine suspension, payout holds or other significant outcomes; disclose logic, effects and safeguards if applicable.] Do not infer the absence of such systems from recommendation code alone.

6. Cookies and Marketing Choices

Different controls address different processing

6.1 Necessary functions. Session, authentication, access-protection and security technologies may be needed for requested functions. Their purpose and lifespan must be disclosed in a current cookie inventory. A cookie is not “necessary” merely because it is commercially useful.

6.2 Optional technologies. Where applicable law requires it, optional analytics, personalization and advertising technologies will not operate before valid consent. Choices must allow refusal and later withdrawal without deceptive design. A final Cookies Policy should identify actual technologies, providers, purposes and durations.

6.3 Separate marketing consent. The recommendation patch separates personalization from marketing consent. Its authorized staff report uses category-level counts over a 30-day horizon and a minimum of 20 distinct consenting profiles per reported category. It does not produce personal contact lists. A group threshold is a privacy measure, not proof that all resulting information is irreversibly anonymous.

6.4 Advertising classification. Contextual advertising and personalization within our own service are not automatically equivalent to cross-context behavioral advertising. “Sale,” “sharing” and “targeted advertising” have legal definitions that can cover non-cash disclosures. [COMPLETE the advertising data-flow audit and state whether each legally defined activity occurs; include recipients and opt-outs if it does.] 6.5 Opt-out signals. Where applicable, we will honor recognized universal opt-out mechanisms such as Global Privacy Control for the processing covered by the law. [VERIFY and implement signal handling before making this a live commitment.] A statutory opt-out does not require consent to unrelated cookies or creation of a new account.

6.6 Messages. If optional promotional messages are offered, provide a working unsubscribe method and obtain consent where required. Necessary service, receipt, security and legal messages may continue. The supplied aggregate-report feature does not itself establish an email-marketing programme.

7. Recipients and Disclosures

Share only for a defined purpose

7.1 Service providers. Information needed for hosting, delivery, security, communications, support, payments or verification may be handled by providers performing those services. [IDENTIFY actual recipient categories and roles, locations and material processing before publication.] Providers acting on our instructions should have appropriate contracts and controls.

7.2 Creators and transaction parties. Creators can see public interactions and supported performance information. Sellers, buyers or other transaction parties may receive the details necessary for a disclosed transaction. This does not authorize unrestricted access to viewers’ private contact information, identity documents or complete financial details. 7.3 Advertisers and sponsors. The supplied recommendation design provides separately consented staff aggregates, not advertiser contact lists. [CONFIRM which campaign reports are actually released to advertisers and whether pixels, SDKs or identifiers are sent to independent advertising parties.] Do not publish a categorical “we never sell or share” claim until this audit is complete.

7.4 Legal and protective disclosures. We may disclose information where legally required or justified to respond to valid process, investigate fraud or abuse, establish or defend claims, and protect rights or safety. Requests should be assessed for authority, necessity and scope; a government request does not automatically justify unrestricted disclosure.

7.5 Rights complaints. Copyright notices and counter-notices may be provided to relevant parties as part of the legal process. A counter-notice can require contact and jurisdiction information. We will explain necessary disclosure rather than promise complete anonymity in a statutory proceeding.

7.6 Corporate events. A merger or service transfer may involve necessary information under appropriate safeguards and required notices or consent. It does not erase user rights or authorize incompatible processing.

7.7 Your direction. You can choose to disclose public content or use external sharing features. Further use by independent recipients may be outside our control. We remain responsible for our own disclosures and mandatory duties.

8. Retention, Deletion and Security

Keep information only as long as justified

8.1 Recommendation records. The documented default is 180 days for preference events and one hour for feed sessions. The recommendation feature deletes associated profiles and events on opt-out. These periods do not describe accounting, fraud, uploads, backups or all server logs; verify the deployed configuration and processing before publishing fixed claims.

8.2 Account and content records. Retention depends on the requested account or publication, an unresolved issue and lawful preservation requirements. Closing an account can remove public access without immediately deleting every record. [CONFIRM inactive-account rules, media deletion timing, cache propagation and backup-expiry criteria.] 8.3 Transactions and claims. Necessary payment, tax, identity-verification, auction, complaint and dispute records may be retained for the relevant legal or operational period. Identify the applicable requirement and retain the minimum necessary. [INSERT category-specific periods or sufficiently precise criteria after accounting, legal and vendor review.] 8.4 Legal holds. A specific legal duty or active dispute may justify limited preservation. Such records should not be reused for unrelated advertising. When the reason ends, ordinary deletion rules should resume. Explain any lawful refusal to delete information through the rights-request process.

8.5 Backups. Backup deletion follows a documented expiry process; restricted residual copies should not return to normal use after restoration. A public deletion promise must match actual backup and provider capabilities. We do not promise instant erasure from every system or copies independently retained by other users.

8.6 Security. We will use safeguards proportionate to the information and risks, including appropriate access and provider controls. No system is perfectly secure. [VERIFY deployed safeguards before naming encryption, certifications or guarantees.] We will investigate incidents and make notifications when required by law.

8.7 Your role. Protect credentials and use available controls. Report suspected misuse through verified support channels. Do not send passwords, full payment-card numbers or unnecessary identity documents in ordinary correspondence.

9. Your Privacy Requests

How we will handle applicable rights

9.1 Available rights. Depending on applicable law, you may seek confirmation of processing, access, correction, deletion, a portable copy, restriction, objection, withdrawal of consent and specified opt-outs. Rights have lawful conditions and exceptions; we will explain relevant limitations rather than treating them as a blanket reason to refuse.

9.2 Submit a request. Use the verified privacy contact and request channel in section 1 once completed. Account settings or recommendation export can help with feature-specific requests, but are not the sole method for all statutory rights. You do not need to create a new account simply to exercise applicable rights.

9.3 Verification. We may request proportionate information to identify the requester or an authorized agent and protect others’ information. Collect only what is necessary. Do not require excessive identification for requests that law does not permit us to condition on verification. Authorized-agent requirements vary by right and jurisdiction.

9.4 Timing and charges. We will respond within the applicable legal period and explain a permitted extension in time. Requests are ordinarily free; any lawful exception must be explained and cannot be an arbitrary access fee. The regional sections describe relevant deadlines without imposing a single worldwide period.

9.5 Deletion and objections. We may preserve information where a specific legal exception applies, such as necessary transaction records or claims evidence. We will identify the reason and stop incompatible use. Consent withdrawal affects future consent-based processing, not its prior lawfulness.

9.6 Review and complaints. Where law provides an appeal, follow the same contact channel and identify the decision challenged. You can also complain to the relevant regulator. Exercising rights does not waive court or other statutory remedies.

9.7 No retaliation. We will not unlawfully discriminate for exercising privacy rights. A requested deletion or withdrawal can make a genuinely dependent feature unavailable; that consequence must be explained and must not be used to coerce unnecessary consent.

10. New Jersey and U.S. Rights

Apply the law’s actual scope and conditions

10.1 New Jersey. When the New Jersey Data Privacy Law applies to our processing and you qualify as a consumer, you may confirm processing, access, correct, delete and obtain a portable copy of covered personal data. You may opt out of covered targeted advertising, sale and profiling for decisions producing legal or similarly significant effects. Sensitive-data processing requires the applicable consent and protections.

10.2 Response. For covered, verified New Jersey requests, the ordinary response period is 45 days, with a possible additional 45 days where reasonably necessary and explained within the original period. A denial will explain the reason and how to appeal, where required. An appeal should be reviewed within the statutory period, generally 45 days, with an explanation and regulator complaint information if denied.

10.3 Signals and complaints. Where covered processing occurs, recognized universal opt-out mechanisms must be honored as required. New Jersey consumers can contact the Division of Consumer Affairs concerning suspected violations. Our location in New Jersey alone does not establish that every threshold or exemption in the law applies.

10.4 California. If the CCPA/CPRA applies, eligible consumers may know or access covered information, correct it, delete it, obtain relevant disclosures and opt out of sale or sharing, including through recognized signals. Where applicable, they may limit specified sensitive-information uses. We will not discriminate unlawfully and will provide required request methods and responses.

10.5 California disclosures - completion required. [INSERT an accurate prior-12-month category, purpose, source and recipient disclosure; state whether information was sold or shared, and identify relevant categories.] Attach a notice at collection and any required “Do Not Sell or Share My Personal Information” and sensitive-use controls. Do not replace actual disclosures with a generic statement that they “may” occur.

10.6 Other U.S. states. Additional rights, appeal processes and opt-outs may apply where eligibility and scope requirements are met. This notice does not limit those protections. [COMPLETE the state applicability review and publish specific additional disclosures where required.]

11. EEA, UK and International Use

Additional protections where regional law applies

11.1 Rights and bases. Where GDPR or comparable UK protections apply, you may have access, rectification, erasure, restriction, portability and objection rights, and rights concerning solely automated significant decisions. Portability generally concerns data provided and processed automatically on consent or contract. The actual legal basis and purpose determine available rights; section 4 must be verified for each use.

11.2 Direct marketing and consent. You may object to processing for direct marketing, including related profiling. We will stop that processing as required. You may withdraw consent at any time without affecting its prior lawfulness. Legitimate-interest objections require the applicable assessment and cannot be dismissed automatically.

11.3 Timing. GDPR requests are ordinarily answered without undue delay and within one month, subject to lawful identification and extension rules. A permitted extension of up to two further months requires timely explanation. We will use the rule applicable to your request, including any current UK-specific provisions.

11.4 Complaints. You may complain to a competent EEA supervisory authority, including one in your habitual residence, workplace or place of the alleged infringement as applicable. UK users may contact the Information Commissioner’s Office. We encourage contacting us first but do not require it as a condition of regulator access.

11.5 International processing. MoyoTube is based in the United States; its services may involve access or storage across borders. [INSERT actual processing and recipient countries and the applicable transfer mechanisms before publication.] A worldwide service description does not itself provide a lawful transfer basis.

11.6 Transfer safeguards. For restricted transfers, identify an applicable adequacy route or implemented safeguards and explain how a copy can be obtained. Standard contractual clauses or UK instruments must actually be adopted where relied upon. No Data Privacy Framework certification, representative appointment or transfer assessment is claimed in this draft.

11.7 Other regions. Mandatory local rights remain available. We will publish further location-specific information where required by the actual markets served. This notice does not claim a complete worldwide legal assessment.

12. Children, Updates and Contact

Maintain an accurate, usable notice

12.1 Proposed eligibility model. The companion Terms propose use by adults aged 18 or over. That policy choice is awaiting adoption; confirm it and the actual audience before publication. We do not offer a minor account or parental-consent process through this draft. 12.2 Children’s information. An adult-only notice does not remove child-privacy obligations if actual use or collection triggers them. If we learn we collected information from a child contrary to applicable requirements, we will assess it promptly and take appropriate deletion, restriction, consent or safeguarding steps. [INSERT a monitored child-privacy reporting route and confirm operational handling.] 12.3 Content involving children. Uploaded material can depict a child even when the account holder is an adult. Creators must respect privacy, consent and safety requirements. We must assess our own collection and disclosure obligations; responsibility cannot simply be transferred to uploaders by a general statement.

12.4 Updates. We will keep the policy accurate as practices change. Material changes will be communicated as required, and new consent obtained where necessary before introducing a new consent-based purpose. A revised date does not retroactively authorize an undisclosed use.

12.5 Contact. [INSERT verified privacy email, working request URL, and any legally required telephone method.] Postal correspondence, subject to verification: Privacy Requests, MOYOTUBE TECHNOLOGIES LLC, 2110 E RT 70, Cherry Hill, NJ 08003, United States.

Required DPO or regional-representative details should be added only after appointment. 12.6 Effect. This notice explains handling of personal information and choices. It does not waive mandatory rights, grant content ownership, create unlimited consent or substitute for separate cookie choices. Content and payment conditions remain in the relevant terms, subject to applicable law.

End of proposed public Privacy Policy. Do not publish the following internal appendices. Resolve every bracketed practice and contact field before adoption.