Jump to content

xarthangrol

Members
  • Content count

    23
  • Joined

  • Last visited

  1. I know, I have several, and it costs me only $1.62 USD per month to host three domains on the same package, which is unmetred with databases. I don't feed ads to try and get that $1.62 back nor do I collect data from users' computers. If people want to pay $30 per month for unlimited space and features they'll never use, that's up to them. Some people also lack the knowledge about what web hosting is because they have been fed Google and other walled gardens and site builders since birth. The value of data is worth more than the value of bits on a server, which may be why Google is a billion-dollar company and the users are probably not getting richer by using it. Anyway, closer to my original issue; it's not the data that people give away with their own hand or voice that concerns me, it's the data that is covertly taken that does. As I've said before, someone stole my credit card details online and spent over $3,000 on medical supplies in a country I've never been to. Someone stole my wife's details and defrauded her. All that as a result of data being stored on the WWW. Even using AWS is insecure if not set up properly. As Steps has mentioned, this topic has probably run it's course. Thanks for your contributions, folks.
  2. Yes, there is that. But there may be a lot of that assumed majority who just don't want to voice their opinion or might think it's a waste of time saying anything. If they remain silent, there's no way to tell what their opinion really is. Anyway, my original question has lost all direction now, and I'm glad it was answered several pages ago.
  3. It's not. You pay an ISP to connect to it. Without paying that monthly fee, you wouldn't have any access to it. Besides, the internet is all of the servers and computers on the network not websites, documents and online services; that's the World Wide Web, which uses the internet.
  4. Not true. Not every app needs to collect data (in order to keep). Not even those online. There are developers that want the data to make money, not just analyse trends or how it works with different systems. Yes, EULAs and other policies are long, but should still be read, even if only for key points. Stay off the grid? That's the wrong attitude. Companies need to change their attitude's towards how data is used and when it is necessary. Maybe that's why privacy has been in the news so much recently, not to mention the update to Europe's privacy laws. Many people have been born into a world of data sharing that it is just accepted, handing over a pot of gold to developers.
  5. I have been a victim of a £3,000 credit card fraud, and my wife had bailiffs after here for a mobile contract in her name that wasn't hers. So, like you, I care about what is being sent from my computer. I think that if instead of an app taking data, a real person entered people's homes, snooped around their computers and took info without saying what it was, there would be more people against it. And there will be people who'll say it's not the same thing, but it is. You just don't see it happening.
  6. Does the website open in the app or in the OS's default browser? There are a more browser-based apps these days, using technology like Electron. If the Affinity website opens in the app, then the privacy policy for the website would apply directly, but only when the website is being used in the app, and not when the website is not being accessed. If help documentation is pulled from the Affinity website, then that would also be cause to note the privacy policy as the app would be accessing the Affinity website. If the app pulls data from AWS, then AWS's policies may apply but not the Affinity's as the Affinity website would not be accessed.
  7. Indeed, personalisation is put into generic communications.
  8. Because they are part of the website's functionality, especially if APIs are integrated into the code, and pass information from the website to those systems as a direct consequence of using the Affinity website.
  9. Indeed they do need it (we agree on something at last ) for the purposes of verifying identification for purchasing, but there's no need to keep it. I suppose an e-mail address and/or an order number would be enough. The e-mail address or order number would be the primary key in a customers database. There's no need to keep full names and addresses online at all. An e-mail probably would be necessary to notify users of actions on their accounts and serve as a means to recover account access to download a product again if required.
  10. Not really. You are focussed on the website policy, but I am focussed on the product EULA, which has already been established to be a separate thing. A website privacy policy does not apply to software use, unless the software is part of the website, such as online services. If you have read the website privacy policy from the top, you would have seen that it states that we are bound to the privacy policy 'while using the Affinity website', which clearly means that we are not bound to it when not using the website. As soon as we close the browser and terminate the connection with the website, the privacy policy ceases to apply.
  11. I'm asking about the product EULA (section 16) not the website policy, which are separate things. Perhaps the wording, 'and affiliates', in section 16 is not required as it implies that 3rd parties have access to data that the user provides. However, it seems to be that section 16 is not about software data but ANY information that is given by the user to Serif for product support and services purposes. I'm guessing that could be information like: account number installation IDs if Serif still uses them recordings of telephone support e-mails between users and support agents chat messages transcripts any hardware information given references to software that may be given during troubleshooting system logs everything
  12. Patrick's replies have given me confidence to strongly consider Affinity Photo in the very near future. I bought many versions of the '... Plus' range of software many years ago, so I look forward to rejoining with Affinity. Back to the topic. The thing that concerns me the most about privacy policies is non-disclosure of exactly which entities/affiliates/partners/third parties have access to data, and what their policies are. By the time data has been shared with third parties that then share it with their third parties, data ends up all over the place with no end-user control. I am sure that Serif would have contracts or a code of practice in place to ensure that any affiliates do not retain the data they have access to. Still, it would be useful to know who/what they are. The issue I have is not what information I knowingly give away, but what is unknowingly taken, which is why I asked to know exactly what is collected. Perhaps a precise list of data collected could be included in the licence.
  13. Which is why I suggested tidying up the policy because the top line states, 'Welcome to Affinity from Serif. Please read this Privacy Policy carefully as you agree to be bound by it while using the Affinity website.' (my bold emphasis), which is why I mentioned that if I am using an Affinity application and not using the website at the same time, the policy would not apply because there would be no '[...] while using the Affinity website' in action. So, by not using the website while using an Affinity app, I would not be bound to the policy.
  14. Okay. So, I was right about it being for the website and not the apps? Thank you for the link to the product EULA. I couldn't find it before.
  15. Fantastic! Thank you Patrick. Nicely explained. Maybe the Serif legal team could tidy up that privacy policy to make it completely clear from the beginning or have separate ones for the website and apps. Thanks again.
×