Quilore Request your data

Why trust this

Specific complaints.
Specific answers.

Three services tried this before us. Each one made a different version of the same mistake. Here is what they got wrong, and what this does instead.

The incumbents

What went wrong

  1. 01

    Last.fm

    It only knew what happened after you connected it.

    Last.fm counts scrobbles from the moment you install the plugin. Anything played before that date never existed. A decade of listening before you signed up leaves no trace, so the lifetime total is not a lifetime total.

    Before you
    signed up

    History simply missing

    Quilore reads the export, which begins when your account was created.

  2. 02

    stats.fm

    The number you wanted was behind a paywall.

    Lifetime listening time is a paid feature. The data already existed and the price did not feel justified for something Spotify had already handed over.

    Paywalled

    Your own data, for a fee

    Quilore is free. Every statistic, all of them, no tier.

  3. 03

    Spotify Wrapped

    It arrives once a year and covers only that year.

    Wrapped is a marketing campaign. It covers roughly January to October, not twelve months, and it has no memory of previous years. It is a snapshot Spotify chose to publish, not a record of your listening life.

    ~10 months

    Not a full year, never cumulative

    Quilore reads every month you have ever used the account.

  4. 04

    Receiptify and similar tools

    They sent your data to a server to make the picture.

    Tools built on the Spotify API log into your account, fetch recent tracks and process them on their own machines. You trust a stranger with your listening in exchange for an image, and many publish no privacy policy at all.

    Your data

    On a stranger’s server

    Quilore has no server-side processing. Parsing runs in this tab.

What Quilore claims

We do not claim “no cookies” or “no tracking”. An advertising network runs here. The claim is narrower and stronger.

  1. 01

    Your listening data never leaves your device.

    Open DevTools, go to the Network tab, filter by Fetch or XHR, then drop your export in. No request carries a play, a timestamp or a total. The file is read by the FileReader API inside this tab. There is no server that could receive it.

    Verifiable in DevTools
  2. 02

    The statistics come from the raw file, not from estimates.

    Each play is a JSON object in the file Spotify produced. We count them. No model, no estimation, no interpolation. If a play is in the file it is in the total, and if it is not, it is not.

    From the file itself
  3. 03

    Every statistic is free. There is no tier.

    Lifetime total, per-artist breakdown, hour-of-day clock, skip rate, first play ever: all of it, no account, no upgrade. The product is funded by the advertising beside it, never by withholding the data.

    No paywall

Third parties on this page

Named, not hidden

None of these receives your listening data. Two of them do see your IP address, which is why they are listed by name rather than left out.

Deezer

Fetches album artwork by artist and album name, only for what is on your screen. It never learns how much you played anything. There is a switch to turn it off.

How to verify

DevTools, Network, filter “deezer”

Lanyard

A public read-only endpoint that reports whether the two developers are online, for the contact chips. It sends nothing about you and receives no data of yours, but it does see your IP.

How to verify

DevTools, Network, filter “lanyard”

Discord CDN

Serves the avatar images for those same two chips. Static files only. Like any image host it sees your IP when the picture loads.

How to verify

DevTools, Network, filter “discordapp”

Satisfied?

Request your export from Spotify. It takes five to fourteen days.

Request your data