sonicwater

privacy & terms

What the water keeps

Listening

There are no listener accounts, no ads, no analytics and no trackers here, and nothing is sold or shared.

  • A play is counted after 30 seconds heard. To stop one listener counting the same play over and over, the site keeps a keyed hash of the connection for a day; the key changes every day and the address itself is never stored.
  • A ripple you leave on a track is a moment and a colour, nothing that says who left it.
  • Your volume is remembered in your own browser, and stays there.
  • Listeners get no cookies. The Studio, where the artist works, uses a sign-in cookie for the artist alone.
  • The site runs on Vercel and its music and data live with Supabase; like any host, they see requests as they pass.

YouTube

The Studio uses YouTube API Services to publish the artist's own music videos and playlists to the artist's own channel, and to keep their titles, descriptions, thumbnails, schedules and the channel's branding in step with this site. Only the artist uses it; listeners never sign in to Google here, and no listener's data is sent to YouTube.

  • It asks Google for permission to upload videos and to manage the channel's videos, playlists and branding.
  • It keeps a refresh token, encrypted, so it can act without asking each time; the channel's id and name; and each video's id, status and public counts (views, likes, comments).
  • Disconnecting the channel in the Studio deletes the token and asks Google to revoke the access. It can also be revoked at any time at myaccount.google.com/permissions.
  • Using these features means agreeing to the YouTube Terms of Service; Google handles data under the Google Privacy Policy.

Updated 22 October 2026. Back to the pool.