Hi Sven,
I wrote a TelemetryCollector app; maybe you’ll find it useful.
Hi Sven,
I wrote a TelemetryCollector app; maybe you’ll find it useful.
Hi,
The app looks interesting. However, my service will do a bit more than just collecting telemetry. The new service will use a real-time WebSocket connection, which allows me to remotely push notifications to the user’s timeline (also to users on specific app versions). Since quite some users have auto-update disabled, this helps to push messages to users when f.e. the manufacturer changed an API that the user need to update to the latest version.
I’m pretty sure all this will be opt-in, right?
It will be enabled by default, just like the previous service. Are you interested in an opt out feature? I might add that as well
Well, seeing what you plan to do, I will not use your apps, and doing these thing on an opt-out basis should not be allowed in Homey apps in my opinion.
Which part of my plan do you have issues with? IPs will NOT be collected (or used for geoIP) anymore, it will use a more privacy-friendly approach without personally identifiable information
Telemetry service, real time websocket connection, unsolicited push messages etc.
And to add to that, I think you’re not aware what qualifies as Personal Identifiable Information and you use your own definition for it.
Push messages to your phone are always opt in. It will push timeline notifications, and you can enable push messages for these types of timeline notifications in the Homey settings.
Any identifier that can identify you as a person (IP address, email address, physical address, phone number, etc.) is what I would consider as Personal Identifiable Information.
I don’t know how this technically works, but doesn’t this mean that you need to know which Homey to send a message to? So you need to have some kind of unique ID / reference?
Yes, that’s true. This will work the same way as the old service: it generates a unique installation ID on install, and uses that to connect to the WebSocket service. This identifier will be randomly generated, it identifies the app installation so it will be kept until you uninstall the app
Yes, I know that. MAC or Cloud ID for example are device identifiers. However, my solution uses a randomly generated installation identifier, this doesn’t belong to a specific device since it’s wiped after a factory reset (or uninstall of the app)
And which type of telemetry do you mean by that? The telemetry that my apps will collect is very minor, only version, app ID and unique install ID, and it will do error reporting of unexpected errors. Country or language can be left out, not really needed for this service anyway (since the Homey Developer Tools already has a dashboard for that)
From the moment of creation until deletion, so during it’s use, this is considered personal data and is subject to GDPR regulation.
Any and all.
Please educate yourself on this subject.
And this means that you need a privacy policy, which I can definitely add if needed
Every mobile app has some kind of installation tracking and many also have notifications, so this is quite normal for many software.
Also, keep in mind that these are free apps, you don’t need to use them if you don’t want to.
This makes the installation identifiable, not the person. I think this is ok under GDPR as long as you do at no point in time connect it with an IP adress. - Not when it is created and not when it phones home.
But still I wonder what additional enlightenment is expected from being able to identify a particular installation!?
Every mobile app has some kind of installation tracking and many also have notifications, so this is quite normal for many software.
That does not mean that it complies with GDPR nor that it is desireable by the user or is any good otherwise.
Also, keep in mind that these are free apps, you don’t need to use them if you don’t want to.
Not using it is, what I will probably do and will recommend to others.
as long as you do at no point in time connect it with an IP adress
The app doesn’t use IPs, so that should be fine.
nor that it is desireable by the user or is any good otherwise.
Why? The user doesn’t even notice it’s there, the app still works fine and when it can’t reach the service (e.g. no internet) it will still work normally
The user doesn’t even notice it’s there,
That is the worst. It sends data to somewhere and doesn´t tell you. And this data is not even necessary to run the thing or make it better. It is just for pleasing someones curiosity as it seems.
Mate, my trust in you and your apps is destroyed and I am just about to identify remove the apps I have from you. - But mayne through your current telemetry you can help me with that ![]()