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
Posting some concerns raised by a Japanese coworker after using gitlocalize.com for few days.
He came to me showing some privacy concern, seeing lot of request sent to mc.yandex.ru each time he was doing an action scared him a bit. Even if it's just text translation, and it's not that sensitive information, he didn't feel at ease with that .ru extension every time he is editing a text or moving the mouse around.
I'm almost sure those are just used for metrics (Yandex Metrica), but it indeed looks a bit aggressive and track every single user interaction (it feels a bit like a keylogger). This behavior would be probably fine on a public website, but when there are personal information, github data and repository data involved, I can see why people would be a bit on edge.
Could it be possible to be less aggressive on user tracking and/or use another tracking service on gitlocalize.com?
The text was updated successfully, but these errors were encountered:
@kefniark Thank you for reporting the issue. Unfortunately, Yandex Metrica is an important tool we use to be sure that our users have the best experience with GitLocalize. And it can't be replaced at the moment with another one.
Summary
Posting some concerns raised by a Japanese coworker after using
gitlocalize.com
for few days.He came to me showing some privacy concern, seeing lot of request sent to
mc.yandex.ru
each time he was doing an action scared him a bit. Even if it's just text translation, and it's not that sensitive information, he didn't feel at ease with that.ru
extension every time he is editing a text or moving the mouse around.I'm almost sure those are just used for metrics (Yandex Metrica), but it indeed looks a bit aggressive and track every single user interaction (it feels a bit like a keylogger). This behavior would be probably fine on a public website, but when there are personal information, github data and repository data involved, I can see why people would be a bit on edge.
Could it be possible to be less aggressive on user tracking and/or use another tracking service on
gitlocalize.com
?The text was updated successfully, but these errors were encountered: