Hi,
Please bear with me, this post is very long, and hastily written.
I haven't really back on Transtastic since I posted my question in the technical forums a few days ago, but thought that I would explain what my question was about and where it is coming from.
As I am the person that probably first rattled the cage, I thought I would clarify some things.
To summarise my concerns regarding the safety of members data on the Transtastic site.
I am not particularly bothered that our membership user names passwords might possibly be hacked and our personal information obtained from Transtastic. Transtastic is as likely to be as secure as any other site. In my case, even if they got my credentials, they are unique to Transtastic and are of little use elsewhere as a login credentials.
I am more concerned about the bigger picture about the protection of our other data. The data that members don’t explicitly provide, but is potentially collected during our activity on the Transtastic site.
I need to break into techy stuff (sorry Mal), but I will try and keep it as light as possible
By using Jainrain as the authentication (login) mechanism, Jainrain will have a unique identifier for each member account being authenticated (usually using something like the OpenId or OpenAuth web technologies). All standard stuff and is used across most social media platforms.
As a member of Transtastic, if you already use the single social media login facility (Twitter or Facebook buttons), then those other sites already have your openId and WILL track you over their own sites, collect the metrics of your preferences, behaviours, favourites, along with all the things that they can collect and sell about you. They can collect the data directly themselves (e.g. Facebook) and also using 3rd party companies such as Jainrain.
When it comes to Transtastic, what I am interested in is, besides the login system, what other Jainrain software hooks does the Transtastic code use?
Just using Jainrain as a simple login and logoff provider does not provide much in the way of shared identity - browser tracking cookies and others technologies such as the so-called adobe flash supercookies (supercookies are generally stored outside of the browsers cookie mechanisms) will track you, as on any other site on the web, but by being careful in how you surf the web, your activity will not reveal much about your identity.
I do not question that Jainrain is a legitimate and professional site; whether such technologies are ethical is another matter - Facebook has just lost a French case and about to lose another data tracking case in Germany.
The question I have for the Transtastic IT team is; after the one-off login/logoff, what other Jainrain software calls are made? This is where individual member's movements over/through/around the Transtastic site are reported directly and indirectly to Jainrain.
What I would like to know is what is allowed to be tracked by the by Transtastic itself via software - read web library – that is to say software calls back from the Transtastic site to Jainrain. For example user state can be saved; for example, along with a whole bunch of other stuff, you can call into Jainrain to remember the last page visited and return the user to that page at their next login. Nice toolkit and feature to have on your website, but the data is saved onto Jainrain servers. Transtastic no longer has ownership of the data, it is held by the 3rd party. This would be considered storing user’s data directly onto Jainrain.
If Transtastic makes a Jainrain authentication call before each action (for example 'check authenticated-user before posting an image', or 'check-authenticated user before liking a photo', 'check-authenticated user before reading the forum'), then this authentication allows Jainrain to implicitly build up user activity even though Transtastic does not directly share this data with Jainrain.
As such, if you only have a single-identity login on Transtastic via an email login (my user name, password and email are not used anywhere else on the web) then this may seem to protect my Transtastic identity from my real life identity, but as I explained earlier, if you use a single-click social-media login button, then your activities are already shared with other social media sites.
Google, Facebook etc. say that any data they hold is anonymised. Whilst in practical terms this is true, in practice it offers little or no protection once the meta-data is shared.
So having a single-identity (unique email login), used only for Transtastic, does not necessarily protect me and my identity. As someone else on this thread has already mentioned, industrial data-mining algorithms are used every second of every day to capture a user’s meta-data and activities. Services like Jainrain provide (sell on) your unique openId identifier along with your web activities. By data mining, and some relatively simple statistical algorithmics, it is possible to cross-correlate the profile of one unique openId to other unique identifiers. So from just being Halina on Transtastic, they can map me as being GeorgeWolf on my Google sign-in, my flirtyShirtSimon account on Microsoft, and essentially map me and Transtastic identity to any other account that I use anywhere on the web. However, to be able to do this, they need to share meta-data so that they can then use datamining and identity-matching algorithms. That is to say, if they don’t have any meta-data to map against, they cannot perform the matching.
For example, Google, Facebook et al keep a database of openId identities and a statistical hit-list for comparing and linking identities. That is to say, person with ID=1231321d234234 may have a 85% certainty compared to ID=8723423423kh. As your surfing goes on, these stats change. It is said that based merely on surfing habits, Google and Facebook can in less that 24hrs cross identify user accounts with other unique identities (e.g. openID number), but they need the your surfing-activities’ meta-data for these statistic algorithms to work.
There is a reason I don't have any photos or face on Transtastic. A potential employer could who map my tranny life to my drab life would fuck up my career, given the sort of work I do. Your answers regarding data privacy and the collection of activity on Transtastic is very important to me personally.
When I joined Transtastic, when I read the terms and conditions, there was the usual clauses about cookie use, but nothing regarding how Transtastic shares its data with 3rd parties. I think that the site terms and conditions need to be updated to reflect what data, if any, Transtastic is sharing, either directly or indirectly with 3rd party companies.
A year or so ago, there was a case of a Gay Social Media website, and after some beneath the hood changes to the forum, the members, thinking that they had ring-fenced their private identity to the gay forum, started to be targeted by adverts from gay sex sites onto their main public Facebook, Twitter pages, personal emails and the like. The change was due to the forum implementing a 3rd party authentication system. Such is the power of datamining information that is collected and sold by third party companies. This cross-identification process and the sending of spam and adverts isn’t even done by humans, it is all automated.
Sorry if I have shaken the Transtastic cage and got the residents a bit agitated, but I do believe that this information is important for the members to know, and more importantly, for the Transtastic Site Ownership to know. While some members couldn’t give a flying-f**k about their identity being public (you know who you are ;-) ), there are many others who want to keep their Transtastic life away from everywhere except Transtastic.
It strikes me, and I hope I am wrong, that outside of the data that Transtastic is knowingly in charge of, Transtastic may have been coasting along without realising as to how its member’s data may be being collected. You will only really find out after the code has been inspected. I do not for one moment blame Transtastic in any way, in fact many a website has been caught out and unknowingly sharing important member data without realising that they were doing so.
Thanks,
Halina
Hugs, x
This post was edited by Deleted Member at February 15, 2016 2:19 PM GMT