Understanding Your Listening History Request in Your Subject Access Request

When you download your personal data through a Subject Access Request (SAR), you may notice that some tracks you previously listened to are missing from the report.

There are several reasons why your listening history might appear incomplete. Below is a breakdown of the most common factors.

1. The 1,000 Item Export Limit

The most common reason for a discrepancy is that our data export tool is designed to prioritize your most recent activity. Currently, we only show the last 1,000 items of your listening history in the SAR report.

If you have a long history of listening on the platform, any tracks played prior to these last 1,000 entries will not be included in the file.

2. Track and Uploader Availability

Even if a track falls within your last 1,000 plays, it may be hidden or removed from your history export if the original content or the uploader's status has changed.

Please review the following possibilities:

  • Track deletion or removal: The track has been deleted by its owner or removed from the platform for copyright infringement.
  • Privacy Settings: The track has been made private by its owner. If it was a private track already then the secret token may have been changed by the user.
  • Over upload limit: The user who uploaded the track may have gone over their upload limit, or their subscription may have lapsed, causing any tracks over the Basic plan's limit to be hidden from listeners.
  • Account suspension or deletion: The uploader's account may have been deleted by its owner or removed for breaching our terms and conditions in relation to spam, copyrights, abuse etc.

3. Regional Issues

In some cases, the data may be unavailable due to geographical restrictions or errors in how the track was accessed:

  • Unavailable in your region: It may be that the original uploader does not have the necessary rights to make a track available in your territory or if the track availability has been changed. As a consequence the track might not be available in your region.

Was this article helpful?

Have more questions? Submit a request