Contact / Initial scope
Start a conversation with Kloy.ai
Share your business context and one high-level protection, detection, or patch-gap question. We use it to review the inquiry and determine whether a further, properly scoped conversation may be appropriate.
A product family, available telemetry, and current workflow help us understand the request.
We compare the request with the public coverage direction and current availability.
Authorization, scope, and an approved channel come before any sensitive exchange.
Prefer email? Reach us directly at official@kloy.ai. We review inquiries to determine whether a further scoped discussion is appropriate.
Do not send vulnerability details, credentials, payloads, personal datasets, or reproduction steps through this public form.
Inquiry guide / Public channel
Before the first conversation
Clear answers about fit, response expectations, sensitive information, and what follows a submission.
Who is Kloy intended for?
Kloy is intended for security operations, detection engineering, security product, and infrastructure teams that need reviewed defensive context before remediation is complete. Fit depends on the question, product family, available context, and authorized use.
What belongs in an initial inquiry?
Provide a product family or technology category, one high-level defensive question, the telemetry category available to your team, and the current workflow. Keep the description non-sensitive. Scope and deliverables must be agreed in writing before any sensitive exchange.
What systems and delivery options are in scope?
Public areas of interest include selected commercial software, infrastructure, network appliances, AI infrastructure, and embedded systems. No product family, version, interface, feed, API, rule format, integration, delivery date, or service level is supported unless Kloy confirms it in writing.
Is Kloy a scanner or replacement for existing security tools?
No. Kloy is not presented as an asset-by-asset scanner. It adds reviewed root-cause, protection, and detection context for a qualified defensive question, and does not replace asset management, patch management, incident response, legal review, or your team's own risk decisions.
What information can be sent through this public channel?
Send only ordinary business contact details and a high-level defensive question you are authorized to share. Do not send credentials, personal datasets, exploit code, payloads, reproduction steps, or undisclosed vulnerability details. If further discussion is appropriate, authorization, scope, confidentiality, and an approved channel are established first.
Does submitting the form create an engagement or confidentiality duty?
No. A submission only asks Kloy to review the inquiry. No customer relationship, service commitment, confidentiality duty, authorization to perform work, or obligation to accept the request arises until the parties enter an appropriate written agreement.
Is this an emergency channel, and when should I expect a response?
No. The public form is not an emergency or 24/7 incident-response channel, and Kloy does not publish a response-time guarantee for public inquiries. Use established incident-response and vendor-support channels for urgent events. Kloy may respond, request non-sensitive clarification, decline, or confirm that no current scope or availability exists.