1. Who is responsible
This Privacy Policy describes how harmuno (also styled Harmuno), the service at harmuno.com, handles personal data in connection with music, lyric, image, voice, editing, sharing and account features. The operator is responsible as controller for the purposes it determines. For privacy questions, email [email protected].
This policy describes the data handling of the service and the choices available for its features. It is not a claim of GDPR, UK GDPR, CCPA or other regulatory certification. A privacy notice does not replace an appropriate legal basis, a processor agreement, a transfer safeguard or a working rights-request process.
2. Google sign-in and Google user data
harmuno (also styled Harmuno) is the AI song and lyric-video creation service at harmuno.com. You can read our public homepage, browse templates and pricing, and read this policy without an account. If you choose Sign in with Google, Google authenticates you and Clerk, our authentication provider, links that identity to your Harmuno account. Harmuno does not receive your Google password.
The Google identity information used for this sign-in feature is your Google account identifier and, when Google provides them, your email address and verification status, name and profile picture. These are basic sign-in/profile information associated with OpenID Connect, email and profile permissions. Harmuno does not offer Gmail, Google Drive, Google Photos, Contacts, Calendar or YouTube account-content import or reading features.
We use your sign-in identifier to recognize your account, associate your private projects with you, secure access and handle account support. Clerk displays available profile information in account controls. When you explicitly start a purchase, our server obtains your verified account email from Clerk and passes it to Paddle to identify the billing customer, prefill checkout and deliver billing communications. Signing in alone does not start a purchase, publish your work or grant a third party access to your projects.
Google and Clerk process authentication and identity records to provide sign-in. Harmuno uses Clerk user IDs and session tokens for application access; it does not use Google authorization to read the account content listed above. Google identity/profile data is not sold, used by Harmuno for advertising, or sent by Harmuno to music, image or language models as model input or training data. A story, name or photo you separately choose to enter or upload is creation content and is processed for the feature you request, as described below.
Harmuno handles information received through Google sign-in in accordance with the Google API Services User Data Policy, including its Limited Use requirements where applicable. Access and transfers are limited to providing the sign-in/account features you request, necessary security and support, and lawful obligations. We do not use Google sign-in information to develop, improve or train generalized AI or machine-learning models.
Clerk stores the linked authentication profile, while Harmuno stores the user identifier and the account/project associations needed to provide your workspace. A verified email may also remain in billing/customer records when you use checkout. We retain account identity information while the account is used to provide the service; records needed for billing, legal claims, security or mandatory retention are handled separately. Deletion is not triggered just by signing out or revoking a connection.
You can review or revoke the Google connection in your Google Account third-party connections settings. You may also sign out of Harmuno and request access, correction or deletion of your Harmuno account and Google-derived profile data by emailing [email protected]. Tell us which account and data the request concerns; do not send a password or authentication token. Requests are reviewed after proportionate identity checks. Removing a Google connection does not automatically delete your Harmuno creations, erase legally retained billing records or cancel a Paddle subscription.
3. Data involved in the service
| Category | Examples and source | Why it is used |
|---|---|---|
| Account and identifiers | Account ID, name, email address and authentication records supplied by you or the sign-in provider. | Account access, session security and customer support. |
| Inputs and generated work | Prompts, chat, lyrics, titles, photos, reference audio, videos, generated audio, images, timestamps and editing choices. Inputs may contain people’s names, likenesses or personal stories. | Deliver requested writing, generation, editing, preview, storage and export features. |
| Optional voice data | Your voice samples, recorded verification phrase, verification status and voice-model or persona identifiers. Voice-related templates may be sensitive or biometric data depending on the processing and applicable law. | Optional voice verification and voice-based creation requested by you. |
| Purchase information | Order, plan, credit, transaction, invoice and refund records from you or the checkout provider. Payment-card handling depends on the verified payment integration. | Fulfill purchases, prevent fraud and meet financial record obligations. |
| Technical and preference data | Session and service logs, errors, network or browser information exposed to service infrastructure, chosen language and workspace/design preferences. | Operate and secure the service, diagnose failures and remember settings. |
| Support and published material | Messages you send to support and information you explicitly choose to share or publish. | Resolve requests and enable the chosen publication or sharing feature. |
4. Purposes and EEA/UK legal bases
We do not assume that agreeing to these terms supplies consent for all processing. Where we rely on legitimate interests, you may object as provided by law. Where consent is required, refusing an optional feature must not prevent access to unrelated service features.
We do not use generated musical choices to make decisions producing legal or similarly significant effects about you. A new high-impact use would require a separate assessment and notice.
| Purpose | Potential legal basis, subject to the actual deployment |
|---|---|
| Account access, requested generation, storage, export and purchase fulfillment | Performance of a contract or steps requested before entering a contract, where processing is objectively necessary. |
| Service security, proportionate abuse prevention and limited diagnostics | Legitimate interests, after necessity and balancing assessments; or legal obligation where applicable. |
| Invoices, tax records and binding legal requests | Compliance with applicable legal obligations. |
| Optional sensitive voice/biometric processing and optional cookies or marketing | Specific, informed and freely given consent, including explicit or written consent where required. Consent must be separate from general terms and withdrawable. |
| Legal claims and dispute handling | Applicable legitimate interests or legal obligations, and an appropriate additional condition if special-category data is involved. |
5. AI services and other recipients
The current integration includes Clerk for authentication; DeepSeek for writing and lyric correction; Suno for music generation, reference audio and optional voice processing; and OpenRouter for transcription and image-model routing. Depending on the selected feature, routed image models may include OpenAI or Black Forest Labs. Some cover-generation paths use Pollinations. The live website is hosted on Hetzner and uses Cloudflare for content delivery and network protection. These infrastructure providers can process request and service metadata needed to deliver and secure the website. Creem provides pre-generation text-prompt moderation. Paddle provides checkout, subscription billing and customer self-service and acts as merchant of record for purchases processed through Paddle. Moderation requests send relevant user-controlled visual directions and song data used for images, plus pseudonymous request identifiers.
If you choose to connect TikTok, Clerk processes the sign-in authorization and basic profile information to link your account. If you separately authorize video uploads and confirm sharing a video, Harmuno sends the selected video to TikTok and checks its processing status. TikTok receives the content under its own terms and privacy policy. Uploading does not automatically publish the video: you continue editing and choose whether to publish in TikTok. You can revoke the connection through your account or TikTok settings.
The writing provider can receive relevant prompts, chat context, lyrics, musical direction and generation metadata. Transcription can send song audio to the selected model through OpenRouter. AI scene and cover generation can send the song concept, lyrics and visual direction; scene continuation can use previously AI-generated scenes as continuity references. Uploaded personal photos are used for photo layouts and filters; new AI person-fusion requests are disabled. Music and voice processing can transmit lyrics, reference recordings, verification recordings and necessary voice identifiers to the relevant provider.
Safety records contain request identifiers, timestamps, moderation decisions, provider result identifiers and a hash of the screened text. These operational audit records do not store the prompt text or uploaded photos; the moderation provider receives the text necessary to evaluate the request. Contact [email protected] to report a screening error or ask about these records.
Provider retention, model-improvement use and access depend on the applicable account, endpoint and contractual settings. We have not established a universal zero-retention or no-training guarantee across these integrations. Do not assume that paying Harmuno or deleting an item in Harmuno automatically changes a provider’s retention or training practices. You can contact us about the provider and processing path used for your request; each provider’s own policy also describes its practices.
Data may also be disclosed to professional advisers, authorities or transaction counterparties where necessary and lawful, with appropriate confidentiality and safeguards. Disclosure for advertising or an unrelated purpose requires its own legal assessment and notice. Public sharing occurs only when you expressly choose it; a download or private workspace edit is not a public-sharing instruction.
6. Voice, photos and sensitive information
Ordinary photos or audio are personal data when they relate to an identifiable person. A voiceprint or other template used to identify or verify a person may be biometric information; some processing may be special-category data under EEA/UK law or subject to US state biometric laws.
The current optional voice flow requests an adult’s own sample and a separate verification recording. Do not upload another person’s voice to create a voice model. Photos of others require the permissions appropriate to the feature and your jurisdiction.
Before sensitive or biometric collection, the feature-specific notice must state the purpose, recipients, retention and destruction criteria, and a working method to withdraw consent and request deletion. Where Illinois biometric law applies, the required public retention/destruction policy and informed written release are additional requirements; ordinary terms acceptance is not a substitute.
A complete biometric retention and deletion workflow is not yet established. The operator must complete that workflow and confirm provider-side deletion, or restrict the feature where those requirements cannot be met. Avoid uploading health records, government IDs, payment-card details or other sensitive information that is not needed to create your work.
8. International processing
Your data may be processed outside your country, including in the United States, China and locations used by the selected AI, hosting and payment providers. Provider names alone do not establish where every copy is stored or accessed.
Before restricted transfers of EEA, UK or Swiss data, the operator must identify the exporter/importer roles, destination countries and applicable safeguards. Depending on the transfer, these may include a valid adequacy decision, applicable standard contractual clauses, a UK addendum or IDTA and supplementary measures. Membership in a framework must be verified for the particular recipient and processing; it must not be assumed.
The transfer arrangements and a method to obtain information about safeguards are not yet finalized. This policy does not assert that those agreements are already executed. Contract acceptance is not blanket consent to unrestricted international transfers.
9. Retention and deletion
Active account and creation records are retained to provide the requested workspace and service. Moving an item to Trash is reversible. The current permanent-delete action removes relevant project records and their interface references; it does not yet establish timed erasure of every stored media file, backup or third-party copy.
The current application does not implement a complete account-wide erasure request process, a verified provider-wide deletion process or a finalized automated retention schedule. We therefore do not promise that data is erased immediately, within 30 days, or from every backup merely because a button is clicked.
Account identifiers and private creation records are kept to operate your account and make saved work available. We review erasure requests by data category: account/profile records and creations, payment records needed for accounting or disputes, security records needed to investigate abuse, and backup or provider copies. The purpose, applicable legal retention duty and any unresolved claim determine what may still be retained. Current backup and provider deletion limitations are described above; this policy does not promise a fixed universal erasure deadline that the service cannot enforce.
For biometric information subject to Illinois law, the policy must provide for destruction when the initial collection purpose is satisfied or within three years of the person’s last interaction, whichever occurs first, unless an applicable legal exception governs. Other laws or consent conditions may require earlier deletion. A provider’s technical default is not, by itself, justification for indefinite retention.
10. Your privacy rights
Depending on your location and applicable law, you may request access, correction, erasure, restriction, portability or information about processing, object to processing based on legitimate interests, or withdraw consent without affecting prior lawful processing. You may complain to a competent data-protection authority, including one in your EEA/UK place of residence where applicable.
US state laws, including the CCPA/CPRA when applicable, can provide rights to know/access, correct and delete personal information; obtain information about categories, sources, purposes and recipients; opt out of sale, sharing or targeted advertising; limit certain sensitive-data uses; and receive non-discriminatory treatment for exercising rights. Authorized-agent requests and appeals must be handled where required.
Harmuno does not operate an advertising-data marketplace or a targeted-advertising feature. Whether onward disclosures constitute a “sale” or “sharing” under a particular law must nevertheless be assessed against the actual provider contracts and uses. This policy does not claim that such activities are legally absent or that a Global Privacy Control handler has already been implemented.
Send privacy requests to [email protected]. Include only information reasonably needed to identify your account and request; never send a password or full payment-card number. Requests will require proportionate identity verification and responses within applicable legal deadlines, normally one month under the GDPR and 45 days for covered CCPA requests, subject to lawful extensions and exceptions.
Requests and appeals are handled through [email protected] rather than a complete self-service erasure or export portal. Automated account-wide and provider-wide erasure are not available; contact us so the request and any retention exceptions can be reviewed.
11. Security and children
Harmuno uses account-based access controls and service-side checks intended to prevent unauthorized access to projects. No networked service can promise absolute security. Private project access requires authentication and ownership checks. The public website uses HTTPS in transit. These measures are not a guarantee against every security risk or a claim of an independent security certification.
Harmuno is intended only for adults aged 18 or older and is not directed to children. Do not submit a child’s voice for cloning or provide unnecessary personal data about children. If you believe a child has supplied personal data, use the privacy contact so the operator can investigate and take the legally required action. An age statement alone does not replace appropriate enforcement.
12. Updates and contact
This version is updated October 22, 2026. Material processing changes will be explained before they take effect where required, and new consent will be requested when needed. A new privacy policy does not retroactively authorize unrelated use of previously collected data.
For support and privacy requests, email [email protected].
Provider information
These links identify current integrations for transparency. They do not replace Harmuno’s own obligations or establish permission for resale, commercial use, training or international transfers.