Revision history [back]

There is virtually zero security on Jolla right now and there are lots of technical ideas on Together about what security model should be like and how to balance developer stats gathering interests with user's privacy control.

Technical solutions are cool and might be good, but they never can protect everything and who knows when/if they are built at all. Let's go for legal way (or call it respectful promises way) already now.
What if it was simply mandatory in Harbour and App Store to tell about the app privacy levels?

Sure if we accept it, there will be a need for a separate discussion on what privacy declaration structure would be detailed enough for developers yet simple enough for the users to actually understand it.

What I could think of right now, is something like the following set of choices:

• App can tell about the fact that it was started at all (minimal reporting useful for stats): Yes | No | Yes, but can be disabled by user
• App can tell about this or that feature being used, no user text strings transferred (e.g. if you prefer using grid or list view in the cool launcher app): Yes | No | Yes, but can be disabled by user
• App can transfer user strings to the server (e.g. for recommending "people who use Weather app often, tend to prefer MeeCast app later"): Yes | No | Yes, but can be disabled by user | Yes and here is the detailed list of what is transmitted

What do you think?

There is virtually zero security on Jolla right now and there are lots of technical ideas on Together about what security model should be like and how to balance developer stats gathering interests with user's privacy control.

Technical solutions are cool and might be good, but they never can protect everything and who knows when/if they are built at all. Let's go for legal way (or call it respectful promises way) already now.
What if it was simply mandatory in Harbour and App Store to tell about the app privacy levels?

Sure if we accept it, there will be a need for a separate discussion on what privacy declaration structure would be detailed enough for developers yet simple enough for the users to actually understand it.

What I could think of right now, is something like the following set of choices:

• App can tell about the fact that it was started at all (minimal reporting useful for stats): Yes | No | Yes, but can be disabled by user
• App can tell about this or that feature being used, no user text strings transferred (e.g. if you prefer using grid or list view in the cool launcher app): Yes | No | Yes, but can be disabled by user
• App can transfer user strings to the server (e.g. for recommending "people who use Weather app often, tend to prefer MeeCast app later"): Yes | No | Yes, but can be disabled by user | Yes and here is the detailed list of what is transmitted

What do you think?

There is virtually zero security on Jolla right now and there are lots of technical ideas on Together about what security model should be like and how to balance developer stats gathering interests with user's privacy control.

Technical solutions are cool and might be good, but they never can protect everything and who knows when/if they are built at all. Let's go for legal way (or call it respectful promises way) already now.
What if it was simply mandatory in Harbour and App Store to tell about the app privacy levels?

Sure if we accept it, there will be a need for a separate discussion on what privacy declaration structure would be detailed enough for developers yet simple enough for the users to actually understand it.

What I could think of right now, is something like the following set of choices:

• App can tell about the fact that it was started at all (minimal reporting useful for stats): Yes | No | Yes, but can be disabled by user
• App can tell about this or that feature being used, no user text strings transferred (e.g. if you prefer using grid or list view in the cool launcher app): Yes | No | Yes, but can be disabled by user
• App can transfer user strings to the server (e.g. for recommending "people who use Weather app often, tend to prefer MeeCast app later"): Yes | No | Yes, but can be disabled by user | Yes and here is the detailed list of what is transmitted

What do you think?

There is virtually zero security on Jolla right now and there are lots of technical ideas on Together about what security model should be like and how to balance developer stats gathering interests with user's privacy control.

Technical solutions are cool and might be good, but they never can protect everything and who knows when/if they are built at all. Let's go for legal way (or call it respectful promises way) already now.
What if it was simply mandatory in Harbour and App Store to tell about the app privacy levels?

Sure if we accept it, there will be a need for a separate discussion on what privacy declaration structure would be detailed enough for developers yet simple enough for the users to actually understand it.

What I could think of right now, is something like the following set of choices:

• App can tell about the fact that it was started at all (minimal reporting useful for stats): Yes | No | Yes, but can be disabled by user
• App can tell about this or that feature being used, no user text strings transferred (e.g. if you prefer using grid or list view in the cool launcher app): Yes | No | Yes, but can be disabled by user
• App can transfer user strings to the server (e.g. for recommending "people who use Weather app often, tend to prefer MeeCast app later"): Yes | No | Yes, but can be disabled by user | Yes and here is the detailed list of what is transmitted

What do you think?

There is virtually zero security on Jolla right now and there are lots of technical ideas on Together about what security model should be like and how to balance developer stats gathering interests with user's privacy control.

Technical solutions are cool and might be good, but they never can protect everything and who knows when/if they are built at all. Let's go for legal way (or call it respectful promises way) already now.
What if it was simply mandatory in Harbour and App Store to tell about the app privacy levels?

Sure if we accept it, there will be a need for a separate discussion on what privacy declaration structure would be detailed enough for developers yet simple enough for the users to actually understand it.

What I could think of right now, is something like the following set of choices:

• App can tell about the fact that it was started at all (minimal reporting useful for stats): Yes | No | Yes, but can be disabled by user
• App can tell about this or that feature being used, no user text strings transferred (e.g. if you prefer using grid or list view in the cool launcher app): Yes | No | Yes, but can be disabled by user
• App can transfer user strings to the server (e.g. for recommending "people who use Weather app often, tend to prefer MeeCast app later"): Yes | No | Yes, but can be disabled by user | Yes and here is the detailed list of what is transmitted

What do you think?

There is virtually zero security on Jolla right now and there are lots of technical ideas on Together about what security model should be like and how to balance developer stats gathering interests with user's privacy control.

Technical solutions are cool and might be good, but they never can protect everything and who knows when/if they are built at all. Let's go for legal way (or call it respectful promises way) already now.
What if it was simply mandatory in Harbour and App Store to tell about the app privacy levels?

Sure if we accept it, there will be a need for a separate discussion on what privacy declaration structure would be detailed enough for developers yet simple enough for the users to actually understand it.

What I could think of right now, is something like the following set of choices:

• App can tell about the fact that it was started at all (minimal reporting useful for stats): Yes | No | Yes, but can be disabled by user
• App can tell about this or that feature being used, no user text strings transferred (e.g. if you prefer using grid or list view in the cool launcher app): Yes | No | Yes, but can be disabled by user
• App can transfer user strings to the server (e.g. for recommending "people who use Weather app often, tend to prefer MeeCast app later"): Yes | No | Yes, but can be disabled by user | Yes and here is the detailed list of what is transmitted

What do you think?