Well, @Welshdog, I do not appreciate rogue code when it comes to password managers, for obvious reasons, that's all. I like this product for the features and value it offers, but yes, that rogue code (for whatever reason it exists) does give me a cause to be concerned. And the only reason I say this is that I have never encountered any app from any developer that caused this particular issue in my 15 years of using a Mac. @Vinod Kumar thank you for your elaborate posts, I will read through them and respond further if the need arises. I have not been available and online a lot since I last posted. You responded just about a week ago, so I am glad I have not kept you waiting as much for a response. From what I gleaned as I skimmed over your posts, it seems you are confident that this will not be a privacy issue at any point in time, so that is good enough for me. Further, since you are talking about system configurations, I am ready to provide any in-depth log and report I can, should you want. Do let me know what I can do in that regard, though I wonder what we might be able to achieve, as you suggest this is not something in your control. iCloud is not customised by me in any way, everything is set to whatever the defaults are, and, frankly, I am not even aware of iCloud backing up my system files on the Mac, let alone the ability to configure such backups at user's end. I always understood iCloud to backup only the iOS and iPadOS files. The only other thing that comes to my mind is that since this issue is more in Apple's domain as you suggest, then shouldn't the developer company (Enpass) try and reach Apple and get them to fix this? It is possible that most users of your software will never even realise that rogue entry's existence, but when they do, they will unnecessarily panic, and they will only point at Enpass. Shouldn't Enpass work with Apple to have a fix for this, for Enpass's own short and long-term repute?
About Culture At Enpass This is for the entire team at Enpass. This is not out of scope of Enpass, the way Mr Dogra wants to brush it off as in his comment. This file that is not getting delisted from iCloud, exists as part of the app, in the Group Containers. Mr Dogra goes on to say he 'feels' that users should contact Apple about this. I want to know from the Enpass team, are you sure you hired the right person for the job? If I have an issue with a developer's app on macOS or Windows, do I contact Apple or Microsoft about it or do I contact the developer who coded the app about it? It is the developer's responsibility to contact Apple if they think the fault lies with Apple. The app is not the customers', the app belongs to the developer and they are responsible for it. Again, to the managing team, you sure you picked the right person for the job, who does not take ownership of the product and work but instead chooses to dump the responsibility on another party? How does Mr Dogra propose that users contact Apple about an issue with your app? And why must they do so when the app belongs to the developer and users only pay for using it? Are you going to pay the users for getting the issue with your app fixed for you? What nonsense does your team member put out for people, does he take us for fools? The only way users can contact Apple about your app is through reporting issues with the app to Apple, and that does not go well for you, because if you make the users report this to Apple, they will make sure to include in the note how unresponsive and unhelpful you have been in solving this issue since years now. It reflects poorly on your competitiveness. About The Issue As can be seen, the file is very much under your domain, installed by the app. Why is it not getting deleted from iCloud and why is it even existing in iCloud in the first place, when no other password manager does that, is squarely on you. As has been noted before, you have been sitting behind your keyboards laughing the matter away, but this is serious and you are answerable. As developer, you get access to Apple's team for help with issues. Set your damn ego aside and get it sorted if you think you cannot sort this out or this is going to blow in your faces when Reddit forums and every other conceivable discussion that includes Enpass gets down to just one thing - security and privacy issues with Enpass password manager and how the developer team is unable to fix the security and privacy issues with Enpass over at least 2 years. You are not going to like that discussion. It is requested that the team understands the gravity of the situation and acts in the interest of users. This is not a joke going on and we have paid for Enpass. We do not own you, but you certainly owe us solutions to problems arising out of your code. Nobody will fix it for you, certainly not the users. It is between you and Apple to fix this. You and your team needs to understand this and get your heads on the issue. It is about time. Stop lying to users who pay you, that you are on it and what not. This is a security and privacy nightmare with Enpass password manager wherein Enpass can keep looking users up with email even when the user has stopped using the app. This is not good at all. You know it. Just fix this.