KeyAuthReviews of keyauth.com

Response from KeyAuthMay 31, 2024

Hello, would you mind changing your review? As this does not reflect on us. You can simply contact our staff by visiting our website https://keyauth.cc and we can upgrade your account manually since you put the wrong owner ID on checkout.

Response from KeyAuthMay 27, 2024

Hello, thank you for your review. However, a few things must be addressed for the public and yourself. 1. We are an authentication service. We provide an API for users to add into their program. We do NOT protect code. It is the users responsibility to protect their own code and application credentials. This is common in all related services that are in this field. 2. I’m not sure what you mean by “ Support and the work team want to understand this and relax their minds and close your account from work”. If you could elaborate more so we could give you a better response that would be great! Regards!

Response from KeyAuthMay 12, 2024

Hello, thank you for your review! However, to clear a few things up for you and for the public. “Issues with host”, is a bit vague. Providing an error message would have been more helpful for us to determine what the issue is. Just taking a guess, I would assume you are talking about the downtime that occurred yesterday. This was due to us upgrading our database, which is an improvement for our users 😁. Not all users were effected either, except for maybe 5 minutes? Have a good day.

Response from KeyAuthMay 10, 2024

Thank you for your review! However, there are a few things that need to be cleared up for the public. 1. "Easily crackable". All of the users who have reported cracks have been users who have not protected their application/app credentials well enough, which would lead to being "cracked". Unfortunately, this will always be debated, even though there is evidence out there from other clients who have protected their application well, and has yet to have any issues. 2. While we have a good number of support members, a lot of them are all over the world. While you may see some online, not all staff members work with every programming language so can only provide support on what they know. We try to assist within 24 hours, but some times it may go past that depending on the volume of tickets we have since we support both Discord as well as web tickets. Have a good day! ——— UPDATE to your updated response: The time that you created your ticket, it must’ve been at a busy time for staff members. I personally do not handle tickets unless the ticket is escalated. But again, support members try to assist people as fast as they can, in the order the ticket was received, and the language the user needs assistance with, Although we provide examples, it is merely that, an example. Users are still required to protect their applications. If a program gets cracked from client-side memory being modified, this is not KeyAuth's fault. KeyAuth is not an obfuscator or client-side protection suite. It is an API that ensures the response from the API wasn't tampered using cryptography and ensures that the server-side is safe. When it comes to the repository on GitHub, those are uploaded by bots. If you review the code, you will see they contain malware. It is hidden, but it is there. We have also submitted a DMCA on it, but we are still waiting for GitHub to remove it. They are a bit backed up with other requests (which can be confirmed by contacting them). But you have every right to express your concerns, but please take into account everything we have stated as it explains/provides an answer to everything you have claimed. Thank you, have a good day!