Regularly sending the I.P.
Whilst Monzo might only be using the data for what they say, as pointed out the regular traffic show more than necessary is being sent and processed.
1 Like
OK. Opinion then rather than knowing something extra, specifically?
Hence the words ālook likeā
Thanks for clarifying. Iām out of my element in web based stuff so I was trying to work out if there was something behind what you were saying that I was missing.
1 Like
I reckon Monzo have to supply all or nothing to use the Facebook plugins.
But some people try to keep their online trail to a minimum , and that can be done with using privacy focused browsers etc, but constantly letting Facebook know about someoneās devices and locale is not something I think is āfairā
4 Likes
This seemsā¦ Worrying.
Particularly the on device free/used space numbers. This can be used as a very effective method of fingerprinting an individual user.
3 Likes
Thanks for raising this, all. So at the moment it seems weāre using the FB SDK āas-isā.
Itās quite possible that it is running more often than we would need it to, and perhaps operating in manners that arenāt necessary. Weāre looking into it to find out, and will find out if weāre able to disable parts of it whilst still maintaining the behaviour we require.
14 Likes
Hereās a good example by the Met Office, giving privacy conscious users a way to disable analytics:
7 Likes
Really keen on hearing the results of this - seems daft that you need to put FB code on my phone in the first place even for install tracking.
7 Likes
Monzo is free, if itās free youāre the product.
Facebooks tracking libraries are free to Monzo too because customers are the product.
They like data.
A bank is not the same business model as an advertising company, so apples to oranges.
Any update on this more generally, @simonb?
1 Like
Hey all 
Thanks for the prod @BenLeo 
Just followed up on this and weāve managed to disable the Facebook SDK post-signup on Android 
So, on Android now it calls the SDK once on signup (for the ad tracking which we mentioned before) and then disables it, so there shouldnāt be any calls to any Facebook APIs after youāve signed up.
Once weāre 100% certain it doesnāt break anything that we need (weāre pretty sure already) then we can push the changes to iOS as well.
Iād like to say thanks to all of you who raised concerns over this behaviour. This was never anything surreptitious on our part, and I think this is a great example of the community both holding us to account and helping us to improve things. So a big thank you to you all! 
36 Likes
Whatās the behaviour on Android for people who previously signed up before this change - is it disabled now for them too?
2 Likes
Yep!
4 Likes
Nice 
3 Likes
This is excellent news.
6 Likes
A big well done to Monzo for this. A legitimate issue was raised and Monzo fixed it.
11 Likes
Glad to see some movement on this, I brought this up multiple times on twitter with no success. I will look forward to seeing these changes in the iOS app.
However, I still have concerns about tracking in the Monzo app:
- The ad tracking on sign up should either be non existent or shared upon explicit extent
- What about the rest of the trackers in the iOS app? - Crashlytics/fabric/answers, Google Maps, the various Firebase libraries
3 Likes
Wonderful news, thank you! Very happy.
Hi, how long until this change is made in the iOS app? - there have been at least 6 updates since this announcement and there are still multiple calls being made to graph.facebook.com.
I would also like to note that there are also still multiple requests being made to these domains: play.googleapis.com, reports.crashlytics.com, cloudconfig.googleapis.com, app-measurement.com - there may well be more; this is just what Iāve observed on some of the main screens/actions in the app.
5 Likes