You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is not exactly an issue per se, but since data privacy is a huge topic (in Germany) right now, I gotta ask: By using this extension: Do we know which data is sent to Twitter? Is there any sensible information we need to worry about?
Or in other words: Are there any paragraphs that we need to add to our data protection declaration...?
Kind regards,
Martin
The text was updated successfully, but these errors were encountered:
thanks for your question. Being curious is not necessarily a bad thing after all.
Using this extension shouldn't be any problem at first, because it doesn't write any cookies at all. The only data sent to Twitter are the OAuth requests and the timeline/search queries configured in the plugin. Of course, you are going to get tracked if you click any link from the output, after entering the Twitter webpage.
You have to pay attention to share buttons, though. These are the ones that always have to be included in the privacy policy. For this purpose, you can give EXT: rx_shariff a try.
In a nutshell: I don't think you have to add any paragraph to the privacy policy when using this extension with the default template. It has been used in some german websites and they only have a paragraph because of the "share" buttons.
Sorry for bothering,
this is not exactly an issue per se, but since data privacy is a huge topic (in Germany) right now, I gotta ask: By using this extension: Do we know which data is sent to Twitter? Is there any sensible information we need to worry about?
Or in other words: Are there any paragraphs that we need to add to our data protection declaration...?
Kind regards,
Martin
The text was updated successfully, but these errors were encountered: