Privacy policy

embeddable.music is a small, independently operated service. It is not affiliated with Spotify, Apple, Google/YouTube, Deezer, Tidal, SoundCloud, or Discord. For anything privacy-related — questions, access requests, deletion requests — contact the maintainer (see section 11).

You paste a link to a song, album, or artist (or search for one), and embeddable.music produces a shareable preview page with artwork, a short audio preview, and buttons that open the music in the recipient's own preferred streaming service. The same previews can be posted into Discord servers through the embeddable.music Discord integration. Signing in is optional and only needed for extra features (a personal dashboard, Discord server management, and Spotify "now playing" display).

If you browse or share preview pages without signing in, we process:

We do not:

• use third-party analytics, tracking pixels, or session recording of any kind;
• set any advertising or cross-site identifiers;
• build profiles of anonymous visitors, or use IP addresses for anything beyond ordinary server logs, abuse response, and the anonymous country-level counts described in section 5;
• read or record which page or app you shared a preview link from.

Fonts. The main web application loads its typefaces from Google Fonts, and the documentation site loads its typefaces from Scalar's font service (fonts.scalar.com). Your browser requests those files directly, which — like any web request — exposes your IP address and browser user agent to Google and Scalar respectively. Neither request carries any account information from us.

You can sign in with Discord or Spotify via OAuth. Sign-in happens on the provider's own pages; we never see or store your password. When you sign in, we store:

• Your basic profile from the provider — provider user ID, username, email address, and avatar URL.
• OAuth access and refresh tokens for the provider(s) you connected. These let us act on your behalf for the features below, and are presented only to the provider that issued them.
• A session cookie (em_session) — an HTTP-only, secure cookie valid for 7 days that keeps you signed in.

What connected providers are used for:

• Spotify (scopes: recently played, currently playing, top items, email, private profile): to show you your own now-playing and recently-played tracks in the app. We display this data to you; we do not maintain a listening log of our own from it. Track metadata encountered this way is cached anonymously under a generated ID so preview pages load fast — the cache records the track, not that you played it.
• Discord (scopes: identify, guilds): to show you which Discord servers you can manage and to power the server dashboard.

If you use the Discord integration in a server, we additionally store what is needed to manage those embeds: the Discord server (guild) ID, channel and message IDs of embeds created, per-server settings and playback history, your Discord account ID linked to your embeddable.music account, and — where a server admin has configured one — the Discord webhook used to post embeds.

Queue history (optional, off by default). In the Discord Activity you can choose to have embeddable.music remember the songs you queue. It is off until you turn it on, and the Activity shows you exactly what is saved before you do.

• What's saved: for each song you queue, its title, artist, artwork, the link or search it was queued with, and when you queued it; plus the fact that history is on and since when. If you choose "No thanks", only that choice is saved.
• Why: to show you the songs you've queued and suggest artists like the ones you play most. Suggestions come from asking Deezer's public API which artists are related to an artist; Deezer is never told who you are or what you queued.
• Who sees it: only you. It isn't shown to other people in a server, and it isn't part of the anonymous usage counts (section 5).
• How long: your last 500 songs or 12 months, whichever is less; older entries are deleted automatically.
• Your control: clear it at any time, or turn it off, which deletes it immediately. Deleting your account deletes it too.
• It is never sold, shared, or used for advertising. Legal basis: your consent, which you can withdraw at any time by turning it off.

Songs played in a server. For "Played here this week" in the Activity and the server's Music Feed on the dashboard, we keep the songs the bot played in each server (title, artist, artwork and link), the voice channel each one played in, and who queued it (their Discord user ID and name). The server's members see them in its Music Feed, beside the links shared in the server, and the feed names the person who queued each song; "Played here this week" shows the songs only.

• Access logs (which include IP addresses) go to our hosting platform's log stream and are kept only as long as the platform retains them; we do not ship logs to any third-party analytics or logging vendor.
• Error and diagnostic records created when something breaks may include the IP address and browser user agent of the request that triggered the error, along with the error details, so we can reproduce and fix the problem.
• Bot incident records. When something goes wrong with the bot in a server (a song that stalls or fails to start, a stream that’s refused, an error), we keep a record of it so we can find the cause: the server and voice channel, the song, the Discord user ID of whoever added it, what went wrong, and the bot’s own log lines from the minutes around it. They contain no IP addresses, stay on our own servers, are seen only by us, and are deleted automatically after 30 days.
• Live Queue events. The bot also keeps a 30-day record of what happens in Live Queue sessions (sessions starting and ending, songs starting, finishing or failing, songs added, with the Discord user ID of whoever added each one), for the same reason.
• We use no third-party crash-reporting, error-tracking, or telemetry vendors. Internal performance traces, where enabled, stay within our own infrastructure.

Anonymous usage counts. To see how much the website, the Discord bot and the Discord Activity are used, and roughly where from, we keep daily counts. They work like this:

• Visitors are counted, not recorded. To tell visitors apart within a day, your IP address (website and API) or Discord account ID (bot and Activity) is turned into a one-way code using a random key that changes every day. The address or ID itself is never stored. At the end of each day the codes are reduced to a single number and deleted along with that day's key, so nothing links you to the count or connects one day to the next.
• Place is a country or a language setting. For the website and API, your IP address is looked up in a country database kept on our own servers (IP geolocation by DB-IP.com), and only the country is counted. Discord hides IP addresses from the Activity and the bot, so for those we count the language setting Discord reports (for example, “pt-BR”) instead.
• Volume is a count, not content. We count requests, Activity sessions, queue actions (add, remove, reorder, skip, pause), bot commands by name, songs played and minutes listened. We do not record which songs, searches or links were involved.
• Only the maintainer can see these counts. They are never shared or sold.

Servers using the bot. To see how the bot grows, we keep, for each Discord server it is in, the server’s ID, name and member count, when the bot was added or removed, and per day how many songs it played there, minutes listened, commands and queue actions, and how many music cards it posted. These are counts about the server, never about the people in it: no user is recorded. Only the maintainer can see them. We also count, per server and day, songs that failed to start and the broad reason (no matching upload, refused, timed out), never which song.

People who sign in. To know how many people use embeddable.music signed in, and how many are new, each person who uses a signed-in session (the website or the Activity) is kept as a one-way code made from their Discord account ID with a secret key that stays on our servers, together with two dates: the first and the last day they used it. Your ID itself is not stored in this count, and nothing in it records what you did on those days. Only the maintainer can see the totals.

We share personal data only with the infrastructure providers that run the service, and only as needed to run it:

• Fly.io hosts the API, content cache, video renderer, and database (region: San Jose, California, USA). Fly's servers see standard request data to deliver the service — see Fly.io's privacy policy.
• Netlify hosts the web application and the documentation site — see Netlify's privacy policy.
• Cloud object storage (Cloudflare R2 / Amazon S3) may hold encrypted-in-transit database backups (see retention, section 8).

Music metadata, artwork, and audio previews are fetched from the streaming platforms and music databases we support — Spotify, Apple Music, YouTube / YouTube Music, Deezer, Tidal, SoundCloud, MusicBrainz, and Wikipedia/Wikidata. These lookups are made by our servers, not by your browser, so those providers do not see your IP address when you view a preview page. Your browser contacts a streaming provider only when you click through to open the music there (or have auto-open enabled), at which point that provider's own privacy policy governs; and it contacts Discord's CDN when the dashboard displays your Discord avatar or server icons.

We do not sell personal data, share it for advertising, or disclose it to anyone except the processors above or where the law requires.

The service is operated from the United States. If you use it from elsewhere, your data is processed in the US, which may have different data-protection laws than your jurisdiction. Connections to the service are encrypted with HTTPS (TLS); still, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.

No third-party cookies are set. The documentation site sets no cookies; it uses localStorage only for reader-interface preferences such as color mode.

• Content caches (metadata, artwork, audio previews) expire on rolling TTLs — typically 24 hours for metadata and about 7 days for artwork and audio in the API cache — or are evicted when space is needed. This is licensed third-party content, not personal data.
• Sessions expire after 7 days; signing out ends the session immediately.
• Inactive Discord webhooks are deactivated on expiry and deleted after 90 days.
• Database backups are kept on a short rolling window (approximately 7 days).
• Queue history (only if you turned it on): your last 500 queued songs or 12 months, whichever is less; deleted immediately when you turn it off or delete your account.
• Songs played in a server: kept with the server's shared links, with no set time limit (the Activity's "Played here this week" shows only the last 7 days).
• Bot incident records and Live Queue events: 30 days, then deleted automatically.
• Servers using the bot: daily counts for about 13 months; a server’s details for about 13 months after the bot is removed from it.
• Anonymous usage counts: the per-day visitor codes and their key are deleted at the end of each day (UTC); the resulting daily totals are kept for about 13 months.
• Sign-in counts: a person’s code and its two dates are deleted about 13 months after the last day they used a signed-in session, or sooner with account deletion.
• Account deletion: contact us (section 11) and we will delete your account and everything linked to it — profile, OAuth tokens, sessions, Discord account link, per-user usage and diagnostic records, your sign-in count record, Discord embed records tied to your account, and your name and Discord ID on the songs you queued in servers. Revoking embeddable.music's access from your Spotify or Discord account settings invalidates our stored tokens on their side as well.

Where the GDPR, UK GDPR, or similar laws apply: we process anonymous-use data (server logs, caching, anonymous usage counts) under legitimate interest; queue history under your consent in operating and securing the service; account and provider data under performance of the service you signed up for (consent given at the OAuth screen, withdrawable by disconnecting the provider or deleting your account). You have the right to access, correct, export, and delete the personal data we hold about you, and to object to processing — contact us (section 11). For data held by Spotify, Apple, Google, Deezer, Tidal, SoundCloud, or Discord themselves, exercise your rights with those services directly. You also have the right to lodge a complaint with your local data-protection authority. Under the CCPA: we do not sell or share personal information as those terms are defined there.

embeddable.music is not directed at children, and we do not knowingly collect personal data from children under 13; if we learn that we have, we will delete it. Sign-in requires a Discord or Spotify account, each subject to that provider's own age requirements.

Email privacy@embeddable.music for any privacy question or request.

Changes take effect when published on this page, with the effective date updated above. Material changes — meaning changes in what the service actually does with data — will be called out in release notes or in-app.