Information We Collect
SonicLife may collect account details such as name or DJ name, email address, account role and approval status; event and request information; and song metadata selected through supported music-search features.
TikTok and Social Connections
When a DJ chooses to connect TikTok or another supported social account, SonicLife may receive information the DJ authorizes through that platform, such as a public profile name, profile image, account identifier, and public video information. SonicLife uses this information to connect the DJ account and display authorized public content. SonicLife does not ask DJs to provide their TikTok password directly to SonicLife.
Spotify Search
SonicLife may use Spotify to help users find songs. Search results can include track names, artists, albums, artwork, Spotify track IDs, URIs, and links. Selected track metadata may be stored with a song request.
How We Use Information
- Operate registration, authentication, DJ approvals, events, party codes, song requests and voting.
- Display connected DJ social content when authorized by the DJ.
- Maintain security, diagnose errors and improve the service.
- Comply with applicable requirements and enforce SonicLife policies.
Third-Party Services
SonicLife uses third-party services that may process information under their own policies, including Firebase and Google Cloud, Spotify, TikTok, and other services added to SonicLife integrations.
Public Information
DJ names, public DJ request links, event details, request information, votes, and connected public social videos may be visible to other SonicLife users where those features are designed to be shared.
Data Retention and Choices
Information is retained as reasonably needed to provide SonicLife and maintain service records. DJs may choose not to connect social accounts and may revoke access through the applicable platform. Users may request account or data deletion through the contact method provided by SonicLife.
Security
SonicLife uses reasonable technical measures intended to protect information. Authentication is handled through Firebase, and sensitive service credentials are intended to remain on secure server-side systems rather than in public website code.
Changes
This policy may be updated as SonicLife adds features or integrations. The effective date above will be updated when the policy changes.
Contact
Questions about this policy can be directed to the SonicLife site administrator through the contact method provided by the SonicLife service.