Essential cookies and login data
MusiBee4 uses essential WordPress cookies and session data for login, account security, creator workspaces, buyer accounts and protected tools. These are needed for the service to work.
Plain-English privacy
Privacy & Data Use
A simple explanation of how MusiBee4 uses essential site data and creator tools.
This page is a practical website notice, not a replacement for legal advice. It explains the main types of data MusiBee4 uses to run accounts, publishing records, licensing and optional creator tools.
Creator publishing records
When creators publish songs, MusiBee4 stores the song listing, creator display information, licensing settings, proof records, version history and SHA-256 evidence fingerprints needed to identify the published version.
Payments and licensing
Payments may be handled by Stripe or other configured payment services. MusiBee4 stores the platform-side licence and transaction references needed to show what was bought, licensed or requested.
Optional creator tools
If you use tools such as lyric translation or originality checking, the submitted text may be sent to the configured AI service provider so that the chosen tool can return a result. Do not submit lyrics unless you own them or have permission to process them.
Messages and enquiries
Contact forms, song enquiries and private platform messages may be stored so administrators, creators, artists or buyers can follow up inside MusiBee4.
First-party page analytics
MusiBee4 may record lightweight page activity so administrators can see which public pages are being used during launch. This uses masked IP groups and salted hashes rather than displaying full raw IP addresses.
Questions or requests
Use the contact page if you need to ask what data is connected to your account, request a correction, or ask for deletion where the platform can legally and technically remove it.