The fine print,
in plain English.

Resona keeps the playlist, not the music.

Your player config — track titles, artists, the src_url for each track, cover URLs, optional LRC lyrics, and your skin/accent choices — lives in your Resona account. The audio files themselves stay wherever you host them.

When a visitor loads your page, the player fetches your config and streams audio directly from your URLs in the listener's browser. We're the jukebox interface, not the record shelf.

We build it well — but no guarantees.

Resona is provided on an “as-is” and “as-available” basis. We work hard to keep the player fast, themed, and online, but we can't promise uninterrupted, error-free, or perfectly compatible service across every browser, device, or network.

If one of your linked audio URLs goes dead, moves, or rate-limits, the player can't stream it — that's outside our control. To the fullest extent allowed by law, we're not liable for indirect or consequential losses arising from your use of the service. Always keep your own backup of anything important.

Be a good citizen of the web.

Use Resona for what it's built for: embedding music players you have the right to share. Please don't:

• Abuse the API or play-beacon endpoints, scrape at scale, or try to overload our infrastructure.
• Reverse-engineer, resell, or wrap the service as your own competing product.
• Use the player to distribute malware, spam, hateful, or unlawful content.
• Inflate play counts or otherwise game analytics.

We may suspend players or accounts that break these rules, usually after a heads-up where we reasonably can.

Counts only — no listener profiles.

When a track plays, the player sends a lightweight beacon (POST /api/player/:id/play) so you can see how popular your music is. This is deliberately minimal:

• We record play counts — how many times tracks and players were played.
• We do not build listener profiles, sell data, or track people across the web.
• No names, emails, or accounts are collected from your visitors — they just listen.
• The public player config (GET /api/player/:id) is read-only; owner routes need a Firebase token managed in your dashboard.

Account and billing data (your email, subscription status) is handled by the CC All-Access system — see the next clause.

Handled by CC All-Access.

Resona is part of the CC platform family. Sign-in, your account, and payments all run through the shared CC All-Access system rather than a separate Resona-only login.

The free plan (1 player) needs no card. Pro features — unlimited players, custom skins & accent overrides, synced LRC lyrics, advanced analytics & API, and removing Resona branding — are included in CC All-Access at £6.99/mo or £59/yr (save 30%), which also unlocks every other CC platform. Manage or cancel anytime at /shop/subscribe.html — no contracts.

One snippet, running on your pages.

The player loads via a single script tag you place on your own site:

<!-- drop where you want the player -->
<script src="https://cil101101.com/shop/resona/embed/p.js"
        data-player="PLAYER_ID"></script>

You're responsible for where you embed it and for complying with your own site's privacy and cookie obligations. On the free plan a small Resona credit appears in the player; CC All-Access removes it.