What you provide
The creator asks for a recipient’s name or nickname, your relationship, a story, the song language, musical style, and lyrics you choose to edit. Provide only details you are entitled to share. Avoid private contact details, passwords, financial information, medical records, or sensitive information about another person. The current preview does not ask you to create an account, enter a payment card, or upload photos or voice recordings.
How creation works
When you submit a story, our server sends the recipient’s name, relationship, story, and selected language to Mureka to generate lyrics. When you confirm the lyrics, our server sends the lyrics and musical style to Mureka to create a song. We query Mureka for task status and receive audio links. These requests are necessary to provide the creation feature; they do not stay only in your browser. Mureka processes requests under its own terms and privacy practices. See Mureka’s API platform for its current policy links. We do not claim control over its training, retention, or international processing practices.
What is stored on this site
The current server stores song-task identifiers, recipient names, song titles, confirmed lyrics, musical styles, creation timestamps, task statuses, audio links, and a session identifier associated with usage limits. It also stores daily generation counts and session usage to manage costs and prevent abuse. On the hosted Cloudflare version, we use a keyed hash (HMAC) of the connecting IP address to enforce one lifetime free song and up to three lyric drafts per IP. The application stores this pseudonymous identifier, usage counts, and the associated task reference, not the raw IP address. These anti-abuse records do not reset daily and persist until removed by the operator. Hosting providers may separately process IP addresses in network records. Submitted story text is not separately saved in the current server task record, but details from it can appear in saved lyrics and have been sent to Mureka. Demo songs are separate, fictional examples stored as local site assets.
Cookies and browser storage
A necessary cookie named mg contains a random session identifier. It lasts up to 30 days and helps apply creation limits; it is HttpOnly and uses SameSite=Strict. Browser session storage holds your story draft and lyric draft, and local storage holds a token for your last song so this browser can restore progress. These browser records are not an account or cloud backup. Clearing site data can remove them and interrupt task recovery; it does not delete records already held by the server or Mureka. Shared-device users should clear site data when finished.
Gift links and visibility
Songs are not placed in a public gallery. A gift URL contains a random token; anyone who has that URL can read the lyrics and access the returned audio links without signing in. Treat the gift link as a private access key. It may be forwarded, saved in browser history, or captured in screenshots. We request that search engines do not index these pages, but this is not access control or a guarantee against disclosure. The current preview has no self-service link revocation or deletion control.
Other network requests
Public pages on dearchorus.net use Google Analytics (G-8TB350QYR4) to measure page visits. The tag may use analytics cookies and send technical device and visit data to Google. Our implementation excludes private gift pages and strips query strings and referrers from the page view we send. We do not send story text, lyrics or recipient names as analytics events. The site does not include advertising pixels, newsletter forms, or a contact submission form. Stylesheets and fonts are requested from Google Fonts; Google may receive technical request information such as your IP address and browser details. Playing a newly generated personal song may contact Mureka’s audio hosting provider. Homepage demo audio and the illustrative image are served by this site. Hosting, network, and service providers may process technical information required to deliver requests; their logs and retention depend on the deployment.
Retention and your choices
There is currently no automatic deletion schedule for song-task records or daily usage records on the preview server. They remain until the operator removes them. Browser storage follows the behavior described above. Mureka currently documents a 30-day validity for returned song-audio URLs; an expiring URL does not establish when the provider deletes underlying data. Save audio you wish to keep. To ask about access, correction, deletion, or a shared link, email rolelife@126.com. Include the relevant page or task context, but do not send passwords or unnecessary sensitive information. We may need to verify that a request relates to your work. Rights and any retention exceptions depend on applicable law and the providers involved.
Children and changes
This preview is intended for adults. Please do not submit a child’s sensitive details or use it to collect information from children. We may update this notice when features, providers, storage practices, or pricing change. The review date identifies this version. The DearChorus brand name is not a statement that a particular registered company operates the preview; formal operator and jurisdiction details will need to be specified before a public commercial launch.