Happy Songs

Acceptable Use & Community Guidelines

Controller: Happy Songs USA Corp., a Texas C-Corporation (provider, publisher, merchant of record, and data controller / responsable)
Version: v1.0 · Effective date: June 25, 2026 · Last updated: August 4, 2026 · Status: In force
Applies to: the Happy Songs mobile application (the “App”), in the United States and Mexico. A Spanish-language version governs for consumers in Mexico (§18). Incorporated by reference into, and forming part of, the Terms of Service and End User License Agreement.

Provider. Happy Songs USA Corp., a Texas C-Corporation (“Happy Songs,” “we,” “us,” “our”), which operates the Happy Songs mobile application (the “App”). Happy Songs USA Corp. is the provider, publisher, merchant of record, and data controller (in Mexico, responsable) for the App.

FieldValue
DocumentAcceptable Use & Community Guidelines (D7) — prohibited uses, anti-circumvention, name-catalog screening, moderation, DMCA and NCMEC
Versionv1.0
StatusIn force (live-operative terms)
Effective dateJune 25, 2026
Last updatedAugust 4, 2026
Jurisdictional scopeUnited States and Mexico. A Spanish-language version governs for consumers in Mexico (§18).
Relationship to the TermsIncorporated by reference into, and forms part of, the Terms of Service and End User License Agreement (the “Terms”). Where this policy and the Terms conflict, the Terms govern the contractual relationship.

This Acceptable Use & Community Guidelines document (this “Policy”) states what content and conduct are prohibited in the App, what the Customer promises about the material it provides, the license the Customer grants to Happy Songs in that material, how our safety filters and moderation operate, how to report or block content, and how we handle copyright complaints (DMCA) and apparent child sexual abuse material (reporting to NCMEC). Capitalized terms not defined here have the meaning given in the Terms.

1. Definitions

  • “the Customer” (Spanish: el Cliente) — the adult individual who registers for, operates, and pays for the account, and who is the sole party to the Terms and to this Policy. The Customer is the payee for any reward under the Referral Program (§16). All rights, responsibilities, and enforcement under this Policy run to the Customer and to the Customer's account.
  • “a child” / “a minor” — a natural person who is under the age of majority. A child does not hold an account, is not a Customer, and is not a party to the Terms or this Policy. A child may be the intended listener of, or the person named in, Generated Content, but only where the Customer provides that content on the child's behalf as the child's parent or legal guardian (§2).
  • “Your Inputs” — the information the Customer provides to create content: the first name of the person a song is for, the occasion, the theme or dedication, and creative prompts. Consistent with §3, the App stores only a first name about the person a song is for; a child's stage or age band, where indicated, is used only in the moment to browse and tailor and is not stored.
  • “Generated Content” — the songs, lyrics, and cover images produced by the App using artificial intelligence in response to Your Inputs.
  • “User Content” — Your Inputs together with the Generated Content created from them through the Customer's account.
  • “AI Providers” — the third-party artificial-intelligence services used to produce Generated Content, identified in §9 and in the Subprocessor List.
  • “Subprocessor List” — the list of AI Providers and other subprocessors maintained with, and referenced by, the Privacy Notice. The Subprocessor List is the source of truth for the identity of the AI Providers; we may add or change AI Providers by updating that list, with notice of material changes.

2. Who this Policy applies to — the Customer is an adult; children may listen but do not operate the App

2.1 Adult operator. The App is operated exclusively by the Customer, who must be an adult — at least 18 years old, or the age of majority in the Customer's place of residence — and must have full legal capacity to enter into a binding contract. By using the App, the Customer represents and warrants that it meets these requirements. A child may enjoy Generated Content, but a child may not create an account, operate the App, transact, purchase, refer, earn, or otherwise act as a party or economic operator. Any account, action, or purchase made through the App is deemed made by, and is the responsibility of, the Customer.

2.2 Consent on a child's behalf (parental / guardian context). Where Your Inputs reference a child — for example, the first name of a child a song is for — the Customer acts on that child's behalf and represents that it is the child's parent or legal guardian and consents, on the child's behalf, to the processing described in the Privacy Notice and to the third-party-AI consent flow. Because the content the Customer creates is likely to be enjoyed by a child, we address this proportionately: a child does not operate the App and there is no child-facing interface to design, so — rather than build a child-user product — we do not market or advertise to children, we minimize data to a first name (§3), and we apply the child-safety measures in this Policy. The parent-operated model is a lawful basis for processing a child's first name; it does not relieve us or the Customer of the child-safety obligations in §§4, 5, and 14.

Incidental, parent-supervised listening does not make the App child-directed. As with any general-audience app, an adult Customer may let a child hear a song on the adult's own device; that incidental, supervised listening is not a child using or accessing the App as a user, and it does not convert an adult-operated App into one directed to children within the meaning of COPPA, nor does it give Happy Songs actual knowledge that it has collected personal information from a child. Three affirmative facts about how the App is built hold this line: (1) we build no profile of the child — we hold only the first name the Customer provides (§3); (2) we direct no feature, screen, content, character, or message at a child — there is no child login, no child-facing mode, and nothing that invites a child to act, earn, or transact (§§2.1, 16.1); and (3) we collect no data from the child — every input is provided by, and the account is operated by, the adult Customer (§9.2). Honest boundary: a minor's first name is processed, with the Customer's parental consent, and we still do not market to, advertise to, track, or profile a child. If a future feature were to speak to a child or be operated by a child, that would change this analysis and we would re-assess before it ships.

2.3 Enforcement runs to the Customer. All responsibility and enforcement under this Policy — including removal of content, feature limits, suspension, termination, and repeat-infringer termination (§§12–13) — apply to the Customer and to the Customer's account.

3. Data minimization; sensitive-data prohibition

3.1 First name only, about the person a song is for. About the person a song is created for, the App stores only a first name. The Customer must not enter, and the App does not store, that person's surname, nickname, age, date of birth, profile, or precise location. A child's stage or age band, where the App invites it, is used only in the moment to browse and tailor content and is not stored; the App does not collect a date of birth.

3.2 No special-category or sensitive data of any person, of any age. The Customer must not submit health, medical, biometric, genetic, religious, political, sexual-orientation, precise-geolocation, government-identifier, or financial information about any person, whether an adult or a child. Your Inputs need only a first name, an occasion, and a theme.

3.3 The “Get Well” / “Mejórate Pronto” occasion is generic well-wishing only. This occasion expresses generic encouragement and good wishes. The Customer must not use it — or any prompt — to state, imply, or generate a specific illness, diagnosis, condition, symptom, or medical circumstance of any person. Because the App neither captures nor generates a specific health condition, this occasion does not produce consumer-health data.

4. Prohibited uses and conduct

The Customer agrees not to submit, generate, request, store, share, or attempt to generate any content, and not to use the App or Generated Content, in any of the following ways. This list is illustrative, not exhaustive.

4.1 Child safety (zero tolerance).

  • (a) Any content that sexualizes, sexually exploits, or endangers a child, or that constitutes child sexual abuse material (CSAM) or child sexual exploitation. This is strictly and absolutely prohibited and is not subject to any warning or “strike” tolerance (see §§5, 14).
  • (b) Any content that depicts, describes, encourages, or facilitates the abuse, grooming, trafficking, or endangerment of a child.
  • (c) Any use of a child's name, likeness, voice, or information to harass, shame, endanger, or exploit that child.

4.2 No imitation of real people (see §6).

  • (d) Content that imitates, clones, or reproduces the voice, name, likeness, image, or distinctive performing style of a real, identifiable person, including any celebrity, recording artist, musician, or public figure.
  • (e) Naming or referencing a real artist, celebrity, brand, or person — including any phrasing such as “in the style of” that names a real artist — in order to mimic that person's voice, style, or identity, or to invoke a protected mark.

4.3 Unlawful, harmful, or infringing content.

  • (f) Content that is unlawful, hateful, harassing, threatening, defamatory, deceptive, or that promotes violence, self-harm, terrorism, or discrimination.
  • (g) Sexual, sexually explicit, or sexually suggestive content of any kind.
  • (h) Content that infringes or misappropriates any third party's copyright, trademark, trade secret, right of publicity, moral rights, or privacy rights.
  • (i) Personal information about any third party (including any child) that the Customer is not authorized to provide, or any data prohibited by §3.

4.4 Abuse of the Service.

  • (j) Removing, defeating, obscuring, or tampering with content filters, the Google SynthID watermark, provenance metadata, or AI-disclosure signals.
  • (k) Reverse-engineering, decompiling, scraping, automated bulk querying, overloading, probing, or interfering with the App, its security, or its rate limits.
  • (l) Using the App or Generated Content for commercial purposes without our prior written agreement.
  • (m) Operating the App on behalf of, or granting operational control to, a minor, or otherwise circumventing the adult-operator requirement (§2).
  • (n) Using prompt injection, jailbreaks, or other techniques to make the AI Providers produce content that violates this Policy or the AI Providers' own use policies.
  • (o) Creating or operating multiple or duplicate accounts, using false, automated, or disposable identities, or otherwise registering repeatedly, to obtain free promotional access more than once, to multiply free generations or in-app points, to evade usage limits or a prior suspension, or to abuse any promotion or the Referral Program (§16).
  • (p) Extracting, ripping, capturing, re-encoding, decrypting, re-hosting, or otherwise circumventing the in-app delivery of any song, lyric, or cover image out of the App or its on-device cache, or using any tool or service to do so (see §7).

We may refine these categories to keep the App safe; changes are handled under §17.

5. Child safety — absolute prohibition; heightened duty

Because the App is oriented to family use and children are likely to access it, our duty here is heightened. Content or conduct that sexualizes, exploits, endangers, or abuses a child is strictly prohibited, is not subject to any warning or “strike” tolerance, and will result in immediate removal, account termination, evidence preservation, and mandatory reporting as described in §14.

  • Our child-safety filters run on Your Inputs and on generated output as the first line of defense (§10).
  • We maintain an in-app mechanism to report, flag, and block content and interactions (§11).
  • We preserve evidence and report apparent CSAM to the CyberTipline of the National Center for Missing & Exploited Children (NCMEC) as required by U.S. law, and we cooperate with lawful requests from competent United States and Mexican authorities under our Law Enforcement Guidelines (§14).
  • Our public-facing child-safety commitments, age-appropriate-design standard, and best-interests-of-the-child posture are set out in our Child Safety & Trust and Safety Policy, which this Policy supports operationally.

6. No imitation of real people; name-catalog screening (Discos por Nombre)

6.1 Prohibition. The Customer may not use the App to create content that imitates, clones, or evokes the voice, name, likeness, image, or distinctive performing style of a real, identifiable person, including any celebrity, recording artist, musician, or public figure; and the Customer may not name or reference a real artist, brand, or person in order to mimic their style or voice. Genre and mood are permitted (“an upbeat pop-style song,” “a gentle lullaby”); a real person's or brand's identity is not.

6.2 Runtime filter. We apply filters — including a real-name / celebrity-name filter — to Your Inputs to block such requests, and we operate a notice-and-takedown process for right-of-publicity and impersonation complaints (§15).

6.3 Name-catalog screening (name-fill and “Discos por Nombre”). Personalization draws on a shared, reusable name-fill catalog, and the App also offers pre-generated, name-based songs (“Discos por Nombre”) keyed to popular first names. The same first name may be used across songs offered to many different Customers, and no name is exclusive to any one person. Before a name is offered from the runtime name-fill or shipped in the pre-generated “Discos por Nombre” catalog, Happy Songs screens the name pool against celebrity, public-figure, real-person, and trademark/brand references — so that, for example, the App does not ship or generate a song for a name that collides with a celebrity or protected mark (such as “Messi” or “Beyoncé”) — treating each name as a personal first name and not as a reference to a public figure or brand. This catalog-level screening is distinct from, and operates in addition to, the runtime input filter in §6.2, and it is applied before any “Disco por Nombre” is offered and on each refresh of the name catalog.

6.4 Legal basis. These restrictions reflect right-of-publicity and anti-impersonation laws, including U.S. state right-of-publicity statutes (for example, the ELVIS Act in Tennessee), emerging federal proposals, and Mexico's reforms on the protection of voice and image under the Ley Federal del Derecho de Autor. This section is coordinated with the AI Disclosure & Policy; both prohibit the same conduct.

7. In-app access only; anti-circumvention and no extraction (closed ecosystem)

7.1 What the Customer receives. The Generated Content created through the Customer's account is provided under a personal, non-exclusive, non-transferable, and revocable license to access and play it solely inside the App, for personal and family, non-commercial enjoyment. This is a license of access — not a transfer of ownership, not a sale, not an exclusive or unique right, and not the delivery of a downloadable or exportable file. Because personalization inserts a reused, shared name, the same or substantially similar content may be offered to other Customers, including others whose child shares the same first name; no song is unique, one-of-a-kind, or exclusive to the Customer. For offline convenience, the App may store an internal, App-managed copy of the Customer's songs on the device; that cache is not a user-accessible file, cannot be exported, and is purged when the Customer's access ends, on deletion, or in the ordinary course.

7.2 Anti-circumvention obligations. The Customer will not, and will not permit or assist any person or tool to:

  • (a) extract, rip, capture, screen- or audio-record in order to remove, re-encode, decrypt, or otherwise remove any song, lyric, or cover image from the App or its on-device cache;
  • (b) circumvent, disable, bypass, or defeat any encryption, access control, cache protection, or the closed-ecosystem delivery mechanism that controls access to Generated Content;
  • (c) re-host, distribute, publicly perform, upload, or share any extracted or circumvented copy anywhere, including on social media, messaging, or any file-sharing or third-party platform; or
  • (d) use, reproduce, adapt, or commercialize any copy obtained through such extraction or circumvention.

7.3 Consequences. Extraction or circumvention is a material breach of this Policy and the Terms and a ground for immediate suspension or termination (§12). Independently, circumventing a technological measure that controls access to a work may violate the anti-circumvention provisions of the U.S. Digital Millennium Copyright Act, 17 U.S.C. § 1201, to the extent an effective technological protection measure controls access to a work protected by copyright. The availability of the § 1201 remedy is conditioned on the App's in-app delivery and on-device cache being protected by an effective technological protection measure, and its application to AI-assisted Generated Content that may not itself be registrable for copyright is a question reserved for counsel. For the avoidance of doubt, Happy Songs does not assert that the Generated Content is protected by a Happy Songs copyright, and this section is not a claim of copyright infringement in the content; it addresses breach of contract, unauthorized use, and the circumvention of a technological access-control measure. We reserve all remedies available in contract and under those provisions.

7.4 Remove-all-copies obligation. If the Customer has obtained any extracted or circumvented copy, the Customer must immediately cease all use and delete or destroy every copy in its possession or control — including any copy posted, shared, or re-hosted on social media or elsewhere and, where those platforms permit, take it down — and may not keep, use, or distribute it. This obligation survives termination (§12).

8. The Customer's representations and warranties about Your Inputs

By submitting Your Inputs or generating content, the Customer represents and warrants, each time, that:

  • 8.1 Authority. The Customer has all rights, licenses, consents, and authority necessary to submit Your Inputs and to have the content generated, and doing so does not infringe or violate any third party's rights or any law.
  • 8.2 Authorization for named persons, including any minor. The first name the Customer provides may reference a child or another member of the Customer's household. The Customer is authorized to provide that person's first name and to have content personalized for them; and, where the named person is a minor, the Customer is that child's parent or legal guardian and consents on the child's behalf to the processing described in the Privacy Notice and the AI consent flow. The child-specific protections in §§4, 5, and 14 apply whenever the named person is a minor.
  • 8.3 No prohibited content or data. Your Inputs do not contain, and are not intended to generate, any content prohibited by §§3, 4, or 6.
  • 8.4 Adult status. The Customer is an adult with full legal capacity and is the account holder (§2).

The Customer is solely responsible for Your Inputs and for content generated from them, and indemnifies Happy Songs against claims arising from Your Inputs or the Customer's breach of this Policy, as set out in the Terms. This indemnity covers the Customer's own inputs and conduct; it does not shift to the Customer the third-party intellectual-property risk of AI output, which is allocated in the Terms and the AI Disclosure & Policy. If any of these representations proves untrue, that is a material breach and a basis for enforcement under §12.

9. License to Happy Songs in User Content; AI Providers and data minimization

9.1 License grant. The Customer grants Happy Songs a non-exclusive, worldwide, royalty-free, sublicensable (only to our subprocessors and AI Providers for the purposes below) license to host, store, reproduce, process, transmit, adapt (for formatting and technical purposes), and display User Content solely as needed to: (a) operate, provide, secure, and maintain the App and deliver the content the Customer requests; (b) run safety filtering, moderation, and abuse prevention (§§3, 4, 10, 14); (c) comply with law and respond to lawful requests; and (d) maintain the provenance record for each generation. This license does not transfer ownership of anything to us and does not enlarge or reduce the Customer's rights in Generated Content, which are governed by the Terms (a revocable, in-app access license — §7).

9.2 Purpose limits; no child profiling. This license is limited to the purposes in §9.1. We do not sell User Content, and we do not use a child's first name — or any information about a child — for behavioral advertising, profiling, or cross-context behavioral advertising. Usage and analytics processing is consent-gated to the adult Customer; because a child does not operate the App, hold an account, or interact with it, there is no child user to track and no child-facing surface to profile.

9.3 AI Providers. To generate content, User Content is transmitted to the AI Providers named in the Terms, the Privacy Notice, and the in-app consent screen — currently:

LayerAI ProviderLocation
Song / audioGoogle Lyria via Google Vertex AI (applies the Google SynthID watermark)United States
Lyrics / textAnthropic and OpenAI (both active)United States
Cover imageNano Banana (Google's Gemini image-generation model)United States

The Subprocessor List is the source of truth; we may add or change AI Providers and give notice of material changes.

9.4 Data minimization to the AI Providers. We minimize what is sent. The real first name is transmitted only to the music provider (Google Lyria via Vertex AI), because it is sung. The lyric providers (Anthropic and OpenAI) receive a placeholder name, and the real first name is inserted locally; the cover-image provider receives only an image prompt derived from Your Inputs. The Customer's phone number is not sent to the AI Providers as part of a creation prompt.

9.5 Explicit consent before sending PII. Before any information is sent to the AI Providers, the App presents an explicit, affirmative in-app consent screen that names the providers. Generation requires this consent; if the Customer declines, the App cannot generate content.

9.6 Risk allocation, stated honestly. The music provider does not indemnify Happy Songs for the intellectual-property content of the music output, and no AI Provider indemnifies Happy Songs for a data breach. Happy Songs therefore carries the residual output-IP and breach risk, which it mitigates through the measures in this Policy, its information-security program, and the cyber/breach and media-liability insurance coverage it maintains or intends to maintain — measures that reduce and bound the risk but do not eliminate it. We make no warranty that Generated Content is original, unique, exclusive, or non-infringing (see the Terms and the AI Disclosure & Policy).

9.7 Non-exclusivity and shared name-fill. Personalization draws on a shared, reusable name-fill (§6.3); the same first name may appear in songs offered to many Customers, and no name, song, or output is exclusive to any one person. Nothing in this Policy or the Terms promises that a song is the Customer's property or is unique or exclusive; what the Customer receives is personalized in-app access.

9.8 Survival and deletion. The license in §9.1 ends when the relevant User Content is deleted in the ordinary course, except to the extent we must retain limited copies for legal, safety, security, dispute-resolution, or backup purposes, or as required by our Data Retention Policy and applicable law. Deletion follows the Account Deletion / DSAR flow; because Generated Content is provided by in-app access only, deletion also purges the on-device cache, and no exported copy exists.

10. Content moderation and child-safety filters; payments and refund/retry

10.1 First line of protection. Every creation request runs through automated child-safety and content filters — including the safety filters of the AI Providers (for example, Google Vertex AI / Lyria) and our own moderation layer — applied to Your Inputs and to the generated output. Keeping the AI Providers' safety filters active is a condition of our agreements with those providers and supports our good-faith, reasonable-care posture. (For the music output, the AI provider does not indemnify Happy Songs; keeping filters active is a good-faith and terms-of-service condition, not an indemnity condition.)

10.2 Filters can reject a request. Because AI systems and safety filters are probabilistic, we cannot and do not guarantee that every request will produce a finished song, lyric set, or cover image, or that the filters will catch all unwanted content in every case. A filter rejection is an automated decision; the Customer may request human review where applicable law provides that right, as described in the AI Disclosure & Policy and the Privacy Notice.

10.3 Payments; how card data is handled. Happy Songs is a paid subscription service, currently offered with free promotional access — during the promotional period no payment card is collected and no charge or auto-renewal is made. Happy Songs does not store card numbers: subscription charges are processed by the app stores — Apple In-App Purchase and Google Play Billing — which process the card, and Happy Songs receives only subscription status and receipts (through RevenueCat). There is no separate web or card payment processor. Happy Songs stores transaction, subscription, and tax records. Changes to plans, features, and pricing are governed by §17 and the Terms.

10.4 Refund or retry on rejected generations. No charge applies to a rejected request during the promotional period. When continued access requires a subscription, or a paid generation is otherwise offered, and a request is rejected by a filter or not delivered, the Customer is entitled to a retry at no additional charge or, at the Customer's election, a refund of the amount paid for that generation, disclosed before the Customer pays and subject to applicable app-store rules. Content created during free promotional access does not retroactively acquire paid-plan rights.

10.5 If unsafe content reaches the Customer. If content that should have been blocked reaches the Customer, or the Customer encounters content it believes violates this Policy, the Customer should stop using it and use the in-app report / flag control (§11) or contact us (§19).

11. In-app reporting, flagging, and blocking

The App provides, and Happy Songs maintains, an in-app mechanism (required for user-generated-content apps by Apple Guideline 1.2 and the Google Play UGC policy) that lets the Customer:

  • 11.1 Report / flag content it believes is objectionable, unsafe, infringing, or otherwise in violation of this Policy, directly from the content or creation screen.
  • 11.2 Block abusive content or interactions and prevent them from recurring.
  • 11.3 Reach a published contact for content concerns (§19).

11.4 After a report. We review reports and take appropriate action — which may include no action, removal of content, a warning, feature limits, or suspension or termination (§12). Reports about apparent CSAM are escalated immediately under §14. We aim to acknowledge and act on reports promptly, and treat child-safety reports as the highest priority.

11.5 Good-faith reports. We do not penalize good-faith reports. Knowingly false or abusive reporting may itself be a violation of this Policy.

12. Enforcement — removal, suspension, termination

12.1 Our actions. Consistent with the Terms and applicable law, we may remove or disable content, limit features, and suspend or terminate access or an account, with or without prior notice, for any actual or suspected violation of this Policy or the Terms, for legal or safety reasons, or to protect our Customers, the children for whom content is created, or the App.

12.2 Immediate action for severe violations. For child-safety violations (§5), threats of harm, or unlawful content, we act immediately and without prior warning, including evidence preservation and reporting (§14).

12.3 Notice where practicable. Where practicable and lawful — and not for CSAM or where notice would impede an investigation or safety — we will give the Customer notice of a material enforcement action and a brief statement of the reason.

12.4 Effect and survival. Termination ends the access license, stops in-app playback, and purges the on-device cache; because no downloadable file is ever delivered, no copy survives outside the App. The sections that by their nature should survive — including §§3, 7, 8, 9.7–9.8, and 13–15 — survive termination. On any breach involving extraction or circumvention (§7), and on termination, the remove-all-copies obligation in §7.4 applies, including any copy posted or shared on social media, and survives termination.

13. Copyright — DMCA notice-and-takedown, designated agent, counter-notice, repeat infringers

Happy Songs respects intellectual-property rights and complies with the Digital Millennium Copyright Act (DMCA), 17 U.S.C. § 512. This section governs copyright complaints and preserves our safe-harbor posture.

13.1 Designated agent (U.S. Copyright Office)

We have designated an agent to receive notifications of claimed copyright infringement, registered in the U.S. Copyright Office's DMCA Designated Agent Directory (electronic registration; renewable every three years to remain valid).

FieldValue
Designated Agent[agent name / title]
CompanyHappy Songs USA Corp.
Address[designated-agent address]
Email[dmca@happysongs.ai — to be created]
Phone[agent phone]

13.2 Filing a takedown notice (§ 512(c)(3))

If you are a copyright owner (or authorized to act for one) and believe content available through the App infringes your copyright, send a written notice to the designated agent (§13.1) that includes:

  1. a physical or electronic signature of the owner or authorized agent;
  2. identification of the copyrighted work claimed to be infringed (or a representative list);
  3. identification of the allegedly infringing material and information reasonably sufficient to locate it in the App;
  4. your contact information (name, address, phone, email);
  5. a statement that you have a good-faith belief the use is not authorized by the owner, its agent, or the law; and
  6. a statement, under penalty of perjury, that the information is accurate and that you are the owner or authorized to act on the owner's behalf.

Misrepresentation liability. Under § 512(f), a person who knowingly materially misrepresents that material is infringing (or was removed by mistake) may be liable for damages.

13.3 Our response

On receiving a compliant notice, we will expeditiously remove or disable access to the identified material and, where appropriate and where the Customer is identifiable, take reasonable steps to notify the affected Customer and provide a copy of the notice.

13.4 Counter-notification (§ 512(g))

If your content was removed and you believe it was removed by mistake or misidentification, you may send a counter-notification to the designated agent that includes: (1) your signature; (2) identification of the removed material and its former location; (3) a statement, under penalty of perjury, that you have a good-faith belief the material was removed by mistake or misidentification; and (4) your name, address, and phone, plus consent to the jurisdiction of the applicable federal district court and to accept service from the complaining party. Where the DMCA requires, we may restore the material in 10–14 business days unless the complaining party notifies us that it has filed suit seeking to restrain the activity.

13.5 Repeat-infringer policy (§ 512(i))

Happy Songs maintains, and reasonably implements, a policy to terminate, in appropriate circumstances, the accounts of Customers who are repeat infringers. Because a child is not an account holder (§2), any repeat-infringer determination and termination apply to the Customer's account. We may also terminate for a single egregious or unlawful infringement. We track infringement notices for this purpose consistent with the Data Retention Policy.

14. Apparent child sexual abuse material — reporting to NCMEC; cooperation with authorities

Happy Songs has a zero-tolerance policy for child sexual abuse and exploitation and complies with U.S. mandatory-reporting law for electronic service providers, 18 U.S.C. § 2258A.

14.1 Mandatory reporting. When Happy Songs obtains actual knowledge of an apparent violation involving CSAM or child sexual exploitation — whether detected by our filters (§10), reported through the in-app mechanism (§11), or otherwise identified — we will report it to NCMEC's CyberTipline as required by law, including the information the statute requires.

14.2 Evidence preservation. We will preserve the reported content and related records as required by § 2258A(h) (preservation for at least 90 days, extendable), in a secure and access-restricted manner, to support NCMEC and law-enforcement handling.

14.3 No further distribution; restricted access. Apparent CSAM is removed from user-facing surfaces immediately, access is restricted to the minimum personnel required to handle the report, and it is not further distributed except to NCMEC and law enforcement as the law permits or requires.

14.4 Account action and cooperation. We will terminate the associated Customer (§12.2), and we cooperate with lawful requests from competent United States and Mexican authorities under our Law Enforcement Guidelines.

14.5 No general monitoring obligation created. Nothing in this section creates, or should be read to create, an affirmative duty to search or monitor for CSAM beyond what the law requires; § 2258A obligations attach on knowledge. Our filters and reporting mechanism are safety measures, not a warranty that all such content will be detected.

15. Right-of-publicity and other (non-copyright) complaints

For complaints that are not copyright — for example, right of publicity, voice-and-likeness impersonation (§6), trademark, privacy, or defamation — you may contact us (§19) with: a description of the content and where to find it in the App, the right you assert and your basis, your contact information, and a good-faith statement. We review such complaints and may remove content and take enforcement action under §12. This channel is separate from the DMCA process in §13.

16. Referral Program — permitted use and anti-abuse

16.1 Adult Customer only; the child is never a participant or payee. Happy Songs operates a single-tier Referral Program (presented in the App as “Familia Emprendedora”). It is a reward/cashback program, not a commission and not a multi-level or pyramid scheme, and it is operated solely by the adult Customer, who is the only participant and the only payee. Any financial-literacy narrative is motivational and educational only; a child is never a participant, is never paid, and is never a payee. There is no payment to minors.

16.2 No abuse. The Customer must not manipulate the Referral Program through self-referral, fake or duplicate accounts, false or automated identities, circular referrals, or any other conduct that games the reward mechanics (see §4.4). A reward is deposited only when the referred party pays and the referring Customer has reached its goal; a claim window applies; and a refunded or charged-back referral is clawed back from a later payout. Rewards are paid to the adult Customer through a regulated cross-border payout provider (currently Wise) that runs its own identity verification (KYC) and whose availability is limited to the countries and banks it supports. Abuse of the Referral Program is a material breach and a ground for withholding rewards and for enforcement under §12. Full Referral Program mechanics, eligibility, financial-incentive notices where required by law, and tax reporting to the adult payee are set out in the separate Referral Program terms.

17. Changes to this Policy, the App, and pricing

17.1 We may update this Policy, and may change, add, or discontinue plans, features, pricing, content libraries, and the Referral Program, as our features, providers, safety practices, or legal obligations evolve.

17.2 Any such change is prospective only and does not retroactively deprive the Customer of what the Customer has already paid for or of non-waivable consumer rights. Where the law requires notice — including for a subscription price increase — we will give it, and the Customer may cancel. Material changes to this Policy will be notified through the App and/or by the contact the Customer provided, and the “Last updated” date will change. Continued use after an update constitutes acceptance to the extent permitted by law and by the Terms.

18. Governing law; jurisdictional scope; non-waivable consumer rights

18.1 Scope. This Policy applies to the United States and Mexico. It is governed as provided in the Terms (Texas law and applicable U.S. federal law), subject to the non-waivable-rights carve-out below.

18.2 Mexico. A Spanish-language version of this Policy governs for consumers in Mexico, aligned with the Mexican Aviso de Privacidad and the Ley Federal de Protección de Datos Personales en Posesión de los Particulares (2025); in Mexico the competent data-protection authority is the Secretaría de Anticorrupción y Buen Gobierno. Mandatory, non-waivable provisions of Mexican consumer-protection law (LFPC / PROFECO) apply notwithstanding any conflicting provision of this Policy or the Terms.

18.3 United States. This Policy is designed to operate consistently with COPPA and the amended COPPA Rule (2025), the Texas Data Privacy and Security Act, the CCPA/CPRA, and other applicable U.S. federal and state law.

18.4 Non-waivable rights control. Nothing in this Policy waives, limits, or overrides any right or remedy that applicable consumer-protection or data-protection law makes non-waivable. Where any provision conflicts with such a non-waivable right, the non-waivable right controls and the remainder of this Policy remains in effect.

19. Contact

PurposeContact
Safety / report content; abuse / Policy violationssupport@happysongs.ai
Privacyprivacy@happysongs.ai — Happy Songs USA Corp.
Copyright / DMCA designated agent[dmca@happysongs.ai — to be created]; [agent name], Happy Songs USA Corp., [designated-agent address]
Right of publicity / other non-copyright complaintssupport@happysongs.ai
Law-enforcement requestsper the Law Enforcement Guidelines

Happy Songs USA Corp.
United States (registered): 8350 Ashlane Way, Suite 103, The Woodlands, TX 77382, United States.
Mexico (operating): Calle Tijuana 22-1, Col. Del Valle, C.P. 03100, Benito Juárez, Ciudad de México, México.
Domain: happysongs.ai.