Trustroots / trustroots

Travellers' community for sharing, hosting and getting people together.
https://www.trustroots.org
GNU Affero General Public License v3.0
398 stars 136 forks source link

Research onesignal.com privacy implications #485

Closed chmac closed 7 years ago

chmac commented 7 years ago

Would be great to get a clear, concise summary of:

mrkvon commented 7 years ago

Still WIP and messy. Already some insight.

https://onesignal.com/privacy_policy https://onesignal.com/tos

Disclaimer: I'm not a lawyer. I'm a dilletante. I don't fully understand the legal context of the research.

TLDR

onesignal.com collects a lot of data, including email addresses, location, behaviour, probably also the text of the notifications users receive. They try to label the users (i.e. sports fan if you're often around stadiums (how far can this go?)) and predict their behaviour.

They make money by selling the data to their Clients (i.e. to ad companies for making personalized advertising).

They will keep the data as long as they need to meet their purposes.

To say something nice: At least they are quite clear about their attitude in their Privacy Policy. With examples etc. They're rather foggy about it in their FAQ, though.

The questions by @chmac

My impression?

I advise not to use this service. I would not choose them for my projects. I perceive them as Big Brother Service. However, i'm rather sensitive to this, so you better make your own judgement.

Slightly more detail

Users = us Clients = brands, ad companies, the ones who pay

Detail with quoting (read the bold text for overview)

SDK - software development kit End Users - trustroots members Clients - onesignal's partners, advertisers, ... (the bodies who want the data)

What they collect

Web SDK

  • Web pages visited that have implemented the SDK, and information about those visits (e.g., session duration, time-stamp, referring URLs)
  • What push notifications an End User has been sent (is this the actual text of notification, or not? I.e. text of the messages?)
  • ... transactions and interactions with apps and websites IP address, from which geographic location may be inferred, as well as system configuration information Email address which we may (in our discretion) hash or otherwise deidentify (they don't promise the deidentifying though!) ... browser [info], such as, browser language type and version of operating system (e.g., Android, iOS); network provider; language setting; time zone A unique cookie identifier, which may uniquely identify an End User (such as in de-identified or anonymous form).

Mobile SDK

[installed] Apps ... [and some usage info] Purchases made within an app. ... transactions and interactions with apps and websites Mobile advertising identifiers, such as iOS IDFAs and Android Advertising IDs (“Mobile IDs”). (They may associate these ids with other data.) Precise Location information, generally an End User’s lat/long data (i.e., GPS-level data) or WiFi information, which we may associate with Mobile IDs, and which may be collected whether or not an app is in use. Email address ... IP address ... [system configuration information] Information associated with or related to devices, such as device type (e.g., mobile, tablet); type and version of operating system (e.g., Android, iOS); network provider; mobile browser (e.g. Safari, Chrome, etc.); language setting; time zone; and network status type (such as WiFi).

How they use it

TODO - they give a lot of detail.

To Provide Services to Marketers, Advertisers and Platforms They Work With

simison commented 7 years ago

Looks like https://www.pushwoosh.com is an identical big service, with smart/safe terms and free for our scale.

https://www.pushwoosh.com/privacy-policy/ https://www.pushwoosh.com/terms-of-use/

simison commented 7 years ago

@mrkvon suppose we can go ahead with Pushwoosh.com instead and forget about Onesignal. Closing this.

Thanks a bunch for research. :thumbsup:

(If there are some other big gateways worth considering, follow ups @ #394)

nicksellen commented 7 years ago

Pushwoosh does not support Remote API [1] in the free tier [2].

[1] http://docs.pushwoosh.com/docs/createmessage [2] https://www.pushwoosh.com/pricing/

simison commented 7 years ago

Oh, that’s unfortunate. I didn’t imagine there would be any other way than via API.

On 28 Mar 2017, at 9.51, Nick Sellen notifications@github.com wrote:

Pushwoosh does not support Remote API [1] in the free tier [2].

[1] http://docs.pushwoosh.com/docs/createmessage [2] https://www.pushwoosh.com/pricing/

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

chmac commented 7 years ago

I'd be very happy to see what @mrkvon makes of onesignal.com. It seems to be an option that would scale with us, and so I think it makes sense to wait for a more detailed review of their offer from a privacy perspective.

simison commented 7 years ago

@chmac, @mrkvon wrote above:

I advise not to use this service.

chmac commented 7 years ago

Aha, I see, the original comment was updated so it didn't arrive by email. Got it.

simison commented 7 years ago

@chmac I looked at Boxcar.io last night — I like how their API/documentation is more simple than Onesignal's. It's just 7e/mo (or free up to 100 devices) so not breaking the bank.

They also have big customers so no problem there.