Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Hi everyone!
Would a Non-Streaming SDA that aggregates and analyzes user-specific usage data from different platforms be compliant with the Developer Policy? We are concerned about Section III.5 & III.13
What we plan:
Our product matches users based on common interests. Instead of manually entering the interests, users can sync their profile to a variety of platforms. Their platform specific usage-data is used to create an interest-profile(s).
Concerning III.5:
We don’t offer any streaming functionality, so that part won’t apply to us. What we are concerned about is the ‘content’ wording. We want users to be able to compare their interest in musical artists and genres, as well as in a variety of non-music categories.
For example, we are cooperating with YouTube, to enable users to compare their subscribed channels. We offer YouTube ‘content’ inasmuch as we list the relevant channel's name, picture, and a link to it on YouTube. We plan to do similar things with other platforms, such as: Subreddits on Reddit, profiles on Instagram and of course artists and genres on Spotify (and possibly other music streaming services). Would this be allowed?
Concerning III.13:
We only process the specific usage data of the user who connects their profile. The user has full control over which data they share, what it is used for, and can delete it at any time. We use different API Endpoints (listed below) to basically create two lists for the user. One of their favorite artists and one of their favorite genres. Entries in these lists consist of:
These lists get created with the Following API Endpoints (users can (de-)select specific ones):
Would a product like that be conceivable? And if so, would it be eligible for commercial use? If it helps, I am glad to provide additional information.
Any help or pointers would be greatly appreciated!
Greetings,
Sam