Ok, so my question is what data are we actually allowed to store from the API?
I’m creating a website and I’d like to store the users bio, logo, their email, twitch id for the case that in the future twitch does decide to allow users to change their username, the total viewer count, follower count, current/last game played (e.g. Mario Cart 64) & current viewer count if the stream is online.
As it is this is how I currently see what data belongs to which and therefore isn’t allowed to be stored.
User Data:
Bio
Email
Account creation date
ID
Profile picture
Channel Data:
Game name
Total viewer count
Follower count
Stream Data: (allowed)
Viewer count
If we are not in fact allowed to store any of the above for periods longer than 24 hours, how can we go about creating sites that require similar data to socialblade/loots/streamhatchet and others?
Specifically, I would like to be able to store some of the data that is returned from http://api.twitch.tv/kraken/channels/twitch and https://api.twitch.tv/kraken/streams?channel=twitch and later expand into more.
Could we get some information as to why the 24hour limit exists? As well as what data specifically is meant? You’ve done such a good job at explaining why/when the auth token must be deleted.
I would also like to know this. Additionally, is there an ID that never changes? Right now I am using the username as unique identifier, but if Twitch ever decided to allow to change this, it would really screw up my application.
“Twitch user data for users not created by your application may be stored for no more than twenty-four (24) hours.”
Interpreted literally, this means we can not store anything useful from Twitch like emails and usernames. We need more info. If we can’t store the username and other useful info for authentication, this makes the Twitch API nearly useless.
I think that if we understood the motivation behind a time-restricted retention policy, we might be able to make better judgement calls when faced with uncertainty.
Is there any movement on this?
If no one is able to explain the restriction and no one particularly cares what we store or for how long, then why not remove it from the TOS?