Privacy policy for SoundUser

This draft covers 5 main data areas: account details, creative inputs, generated outputs, payment records, and service logs. It applies to SoundUser pages and product flows where you describe a song, paste lyrics, choose a style, and generate a track.

This page does not try to name every vendor or legal detail. Some facts depend on the final production setup and should be checked before publication. The matching rules for using the service belong in the SoundUser terms, while general product background can sit on the about SoundUser page.

If a court, regulator, or contract requires a more exact privacy notice, this draft should be updated before users rely on it.

We collect 6 practical categories of data when you use SoundUser: email, sign-in records, prompts, lyrics, generated tracks, payment status, and technical logs.

• Account data: email address and authentication records.
• Creative data: prompts, style choices, pasted lyrics, titles, and generated audio files.
• Payment data: payment status, checkout records, receipts, and provider IDs. Card numbers are handled by the payment provider and should not reach our servers.
• Support data: messages you send, bug reports, and related account details.
• Device and log data: browser type, IP address, timestamps, errors, and security events.
• Basic analytics: page views, product events, and rough usage patterns.

Do not paste private addresses, passwords, medical details, or other sensitive personal data into a song prompt.

We use this data for 5 operational reasons: account access, song generation, payment handling, service protection, and support.

Prompts and lyrics are needed so the music generation system can produce the requested track. Generated files are stored so you can access your output in the product. Payment metadata helps confirm purchases and answer billing questions, including questions related to SoundUser pricing.

Technical logs help us fix broken flows, block abuse, investigate security events, and keep basic records of system behavior. Analytics help us understand which pages and product steps need clearer copy or better error handling. We do not need your creative work to build a public profile about you.

We use 5 kinds of processors: hosting, authentication, payments, analytics, and music generation providers. These providers process data for functions we cannot run alone, such as storing files, signing users in, charging payments, measuring product events, and generating audio from prompts.

Some processors may operate in countries other than yours. That means data can be transferred, stored, or accessed internationally. Where required, the final policy should describe the transfer safeguards used for the actual vendors and regions.

We should not publish a vendor name here unless it is stable, approved, and accurate. If the stack changes, this section should change too.

Creative submissions can include 3 sensitive things: unpublished lyrics, names, and story details. Treat a prompt like studio notes written on a session sheet. If you include a real person's name, a private event, or a line from an unreleased song, that information becomes part of the request you send to SoundUser.

Worked example: Create a 92 BPM minor-key synth pop track with dry female vocal, soft kick, sidechain bass, and lyrics about Jordan leaving Chicago after the hospital call. This is meant to produce a personal breakup track. If the details are too private, change the prompt to a friend leaving a cold city after a hard phone call before generation.

We treat prompts, lyrics, and generated tracks as account content, not public posts.

You can ask for 3 core actions: access, export, or deletion of personal data linked to your account. Use the contact page to make the request and include the email address tied to the account so the team can find the right records.

Deletion may not remove every record right away. Some payment, security, backup, and legal records may need to be kept for a limited period. If the final business has statutory record duties, those periods should be added by counsel.

Retention should match the purpose. Account data lasts while the account is active. Logs should be kept only as long as needed for security, debugging, fraud prevention, and required records.

Cookies and local storage do 3 basic jobs: keep sessions working, remember product choices, and measure basic site activity. Some browser storage may be set by authentication, analytics, payment, or hosting tools. Users can adjust browser settings, but blocking storage may break sign-in, checkout, or generation flows.

SoundUser is not meant for children below the minimum age required by law, such as under 13 in some places or under 16 where a higher consent age applies. The final notice should match the markets where the service is offered.

We may update this policy when the product, vendors, or law changes. Product answers belong in the SoundUser FAQ; privacy changes should be posted on this page.