Last updated: October 2026
This page explains what data these smartlink pages collect, in plain language.
Each time a smartlink page loads, one record is added: which smartlink it was and when. When you tap a platform button (Spotify, Apple Music, and so on), one more record is added: which smartlink, which platform, and when.
Because nothing is tied to an individual visitor, this data generally isn't "personal data" under the GDPR at all. It exists only so Joshua Rupley can see how many people viewed or clicked through to a release — a straightforward, legitimate interest in understanding how their own music is performing (GDPR Article 6(1)(f)).
Individual view/click records are automatically deleted after 400 days. Aggregate totals shown on the dashboard reflect whatever history is currently retained.
The only cookies this application itself sets for visitors of a smartlink page are described below (if any) — the login session cookie used when the site owner manages their smartlinks is separate and only ever applies to them.
When you're shown the Meta consent prompt on a smartlink page, your
choice (accept or decline) is remembered in a first-party cookie called
capi_consent for about 6 months, so you're not asked again
on your next visit. This cookie only stores your choice — it isn't used
for tracking by itself.
This site is set up to help Joshua Rupley measure how their Meta (Facebook/Instagram) ad campaigns perform. If you accept the on-page prompt, this happens:
_fbp) to help Meta match your visit
to an ad campaign.If you decline, or don't respond to the prompt, neither of the above
happens — the Meta script never loads and no server-side event is sent.
This is processed on the legal basis of your consent (GDPR Article
6(1)(a)), which you can withdraw at any time by clearing the
capi_consent and _fbp cookies in your
browser's site settings and declining next time you're asked.
This site is hosted with a provider based in the EU. Standard web server logs (kept by the hosting provider for security and operation of the server itself, not by this application) may briefly include IP addresses, as is normal for any web server — that's outside this application's control. Check your hosting provider's own privacy documentation for details on those logs.
The anonymous analytics this app keeps for itself aren't tied to any identifier, so there's typically nothing to look up, export, or delete for a specific person. If you accepted Meta tracking, Meta is a separate data controller for what it does with that data on its end — see Meta's own privacy policy for how to exercise rights there. For anything specific to this site, you can reach out below.