Trust & Compliance

Vulnerability Disclosure Policy

How to report a security vulnerability to us, and the protection we offer for good-faith research.

Last updated: 29 October 2026 Applies to all Luveedu Cloud services
Vulnerability Disclosure Policy

Luveedu Cloud · Wenxenith Technologies LLP · Last updated 29 October 2026 · luveedu.cloud

Luveedu Cloud welcomes reports from security researchers, and from members of the public, who believe they have found a security weakness in systems that we own and operate. This policy explains which systems are in scope, how to report a finding, the conduct we expect during research, and the protection we offer when research is carried out in good faith.

This policy is a statement of intent and a set of expectations. It is not a contract, it does not create any right to a reward, and it does not alter our Terms and Conditions, our Acceptable Use Policy, or any other agreement between you and Ariyan Debnath (Wenxenith Technologies LLP), trading as Luveedu and Luveedu Cloud.

1.Purpose and Scope

This policy sets out how we prefer to receive security information and how we will work with the person who reports it. We support coordinated disclosure, which means that a finding is shared with us privately, that we are given a reasonable opportunity to investigate and correct it, and that public discussion follows only after a fix is available or after the period described in this policy has ended.

The policy applies to systems that we own and operate. It does not apply to websites, applications, servers, or data that belong to our customers, even where those systems are hosted on our infrastructure. Testing a customer system without the documented permission of that customer is not authorised by this policy and may be unlawful.

In this policy, Business Day means a day other than a Saturday, Sunday, or public holiday in India. A reference to our platform means the websites, client area, interfaces, and supporting infrastructure that we operate in order to deliver shared hosting, cloud hosting, WordPress hosting, reseller hosting, Linux VPS, Windows VPS, domains registered through ICANN-accredited registrars, email hosting, transactional email, email security, anycast DNS, CDN, SSL, object storage, remote databases, security and cleanup services, the OCuLus plugin, WebX Gen, and our AI tools.

This policy is published for the benefit of researchers. It does not create an obligation to investigate every report, to accept every finding as valid, or to compensate any person. Our internal commitments are described in Chapter 7 so that expectations remain realistic.

2.In-Scope Systems

The following systems are in scope for this policy, provided that testing is carried out in accordance with Chapter 5. Only systems that we own and operate are included.

  • luveedu.cloud and the public pages published on that domain, including plan pages, documentation, status pages, and the pages that describe our policies.
  • luveedu.com and the pages published on that domain.
  • manager.luveedu.cloud, being the client area, authentication flows, account management, billing interfaces, and support interfaces.
  • Subdomains of luveedu.cloud that we use for our own services, documentation, control panels, and internal tooling that is reachable from the public internet.
  • Public APIs that we publish for domain search, pricing, provisioning, and related functions, including their authentication and rate limiting behaviour.
  • DNS and mail infrastructure that we operate for our own domains, including authoritative name servers and the mail exchangers that receive our own correspondence.

If you are uncertain whether a particular host belongs to us, contact us before you begin testing. A host that resolves to our network is not necessarily operated by us, because we provide infrastructure to customers who bring their own domains and applications.

3.Out-of-Scope

The following are outside the scope of this policy. Reports concerning these areas will normally be closed without detailed analysis, and testing them may breach our Terms and Conditions or the rights of a third party.

  • Customer-hosted websites and applications, including any content, plugin, theme, script, or database that a customer controls, even where the hosting is purchased from us.
  • Third-party services that we resell or integrate, including registrars, certificate authorities, payment processors, CDN partners, and upstream network providers. These should be reported to the provider concerned.
  • Social engineering directed at our staff, customers, or suppliers, including phishing, pretexting, and attempts to obtain credentials or information by deception.
  • Physical attacks against any office, data centre, or member of staff, and any attempt to gain entry to a facility.
  • Denial of service, stress testing, load testing, and any activity that degrades or is intended to degrade the availability of a service.
  • Spam, including the sending of unsolicited email, and any testing of mail filters by sending bulk messages.
  • Brute force attacks against authentication, and any attempt to guess credentials, tokens, or one-time codes.
  • Rate limiting behaviour, including reports that a limit exists, that a limit can be reached, or that a limit is not applied to a particular endpoint, where no further impact is demonstrated.
  • Missing security headers and similar configuration observations where no exploitable impact is shown.
  • Self-XSS and any issue that requires the victim to paste attacker-supplied content into a developer console or to install software.
  • Outdated library reports that identify a version number without a working proof of concept that demonstrates exploitability in our environment.
  • Automated scanner output submitted without validation, including reports that consist only of tool output, screenshots of scanner results, or generic remediation advice.

The list is illustrative of the boundary of this policy and is not exhaustive. We may treat any activity that places our systems, our customers, or a third party at risk as out of scope, regardless of whether it appears in the list above.

4.How to Report

Send reports to [email protected]. This address is monitored by the security response contact named at the end of this policy. Please do not send security reports to the support address, to a sales address, or to an individual member of staff, because those channels do not have the same handling process.

A report that can be reproduced and assessed should include the following information.

  • a clear description of the weakness and the component affected;
  • the steps required to reproduce the behaviour, in sufficient detail that we can follow them without further questions;
  • the affected URL, IP address, hostname, or API endpoint;
  • the potential impact, including what an attacker could achieve and what data could be reached;
  • any proof of concept, request and response captures, or screenshots that support the description; and
  • the name and contact details you wish us to use when we respond, and whether you wish to be acknowledged.

Do not attach live malware, active exploit payloads that execute on opening, or weaponised documents. Provide a description, a harmless proof of concept, or a link to a location that we can retrieve safely. If you believe that sensitive material must be transmitted, ask us first for a secure channel. We can arrange an encrypted exchange, and we will confirm the method before any material is sent.

Please write in English. If a report is incomplete, we may ask for clarification. We may also close a report where a reasonable request for clarification is not answered within 15 Business Days.

5.Rules of Engagement

Research is authorised under this policy only where it is carried out in good faith and in accordance with the rules below. Any activity that departs from these rules is not authorised, and the protection described in Chapter 6 does not apply to it.

  • Test only the systems listed in Chapter 2, and only to the extent necessary to confirm a suspected weakness.
  • Do not access, download, copy, or retain data that does not belong to you. If access to such data occurs unintentionally, stop immediately, do not examine the data further, and report the event.
  • Do not violate the privacy of any person, and do not attempt to identify, contact, or profile any customer, employee, or supplier.
  • Do not degrade, interrupt, or place additional load on any service. Use the minimum number of requests required to demonstrate the finding.
  • Stop at the first evidence of access. Do not escalate privileges, move laterally, or attempt to determine the full extent of an exposure.
  • Do not use a finding for any purpose other than reporting it to us, and do not disclose it publicly before a fix is available or before the period in Chapter 8 has ended.
  • Do not test against production data where a lesser test would establish the same point, and do not create accounts, orders, or invoices that you do not intend to cancel.

You are responsible for the actions of any person who carries out research on your behalf or under your direction. If you engage a third party, the same rules apply to that party, and you remain accountable for compliance.

6.Our Commitments and Safe Harbour

Where research is carried out in good faith and in accordance with this policy, we will not initiate or support legal action against the researcher for the act of accessing the system, for the act of reporting the finding, or for the reasonable steps taken to demonstrate it. We will not report the researcher to law enforcement, and we will not ask a third party to pursue a claim, on the basis of that conduct alone.

This commitment is limited to the conduct described in this policy. It does not extend to activity that causes harm, that accesses or retains data beyond what is necessary, that interferes with the rights of a customer or a third party, or that is carried out for extortion, for competitive advantage, or for publicity. It does not apply where the researcher has acted in bad faith or has concealed the nature of the activity.

This policy is not a waiver of any right, and it is not an admission of liability. We reserve all rights in respect of conduct that falls outside this policy, including the right to pursue civil remedies and to refer matters to the appropriate authorities. Nothing in this policy limits or excludes any right that a person may have under applicable law, and nothing in this policy creates a right that does not otherwise exist.

We may revise, suspend, or withdraw this policy at any time in accordance with Chapter 13. The protection described here applies to research that is completed while the policy is in force and that complies with the version in force at the time of the research.

7.Acknowledgement, Triage, and Remediation

We acknowledge reports within 3 Business Days, using the contact details that you provide. If you do not receive an acknowledgement within that period, please resend the report and state that it is a resend. We aim to provide a triage decision within 10 Business Days, meaning a determination of whether the report is in scope, whether the behaviour is reproducible, and whether it is assessed as a security weakness.

How We Assess Severity

Severity is assigned by us, taking into account the technical impact, the privileges required, the extent of exposure, and the number of systems or customers affected. We consider industry frameworks as a reference, but our assessment governs. We may ask for further information, and we may reproduce the finding on our own test systems rather than on production.

Remediation Targets

The following targets describe the period in which we aim to deploy a fix after a finding has been validated. They are internal targets, they are not guarantees, and they may be adjusted where a fix depends on a third party or where a change requires planned maintenance.

  • Critical - validated findings that permit unauthenticated access to sensitive data or full system compromise. Target: 7 days.
  • High - validated findings that permit authenticated privilege escalation or exposure of customer data. Target: 30 days.
  • Medium - validated findings with limited impact or a significant precondition. Target: 90 days.
  • Low - findings with minimal impact or those that depend on unlikely user behaviour. Target: the next scheduled maintenance cycle.

We will keep you informed of material progress at reasonable intervals. Where a finding is not accepted, we will explain the reason, which may include that the behaviour is intended, that it is out of scope, that it cannot be reproduced, or that it is assessed as low risk. You may respond with additional evidence, and we will consider it.

Where a fix is deployed, we may offer to retest your finding to confirm that the behaviour is no longer present. Retesting is carried out within the rules in Chapter 5. A retest does not extend the protection in Chapter 6 to any new activity beyond confirming the specific finding.

8.Coordinated Disclosure Timeline

We ask that public disclosure be deferred for 90 days from the date on which we acknowledge the report. This period allows us to validate the finding, develop and deploy a fix, and notify any affected party where notification is required. It is consistent with common industry practice and with the expectations of the researchers and providers with whom we work.

The period may be extended by agreement. An extension is normally appropriate where the fix depends on an upstream provider, where a change must be coordinated across several systems, or where a fix requires a scheduled maintenance window. We will not request an extension without explaining the reason, and we will not use an extension to avoid remediation.

The period may be shortened, or disclosure may occur earlier, where a fix has already been deployed and verified, where the finding is being actively exploited, or where a third party has already published details. In those circumstances we will confirm in writing that disclosure may proceed. We may also publish a security advisory on our own initiative, and we will credit the researcher where permission has been given.

If we cannot reach agreement on timing, we ask that disclosure be limited to the minimum information needed to describe the issue, that proof of concept code be withheld, and that any information that could be used to exploit an unpatched system be omitted. We reserve the right to publish our own account of the finding and its remediation.

9.Recognition

We are grateful for reports that help us protect our customers, and we are willing to acknowledge valid findings. Acknowledgement is made on request, using the name and the contact details that the researcher provides. Where a researcher prefers not to be named, we will record the report as anonymised.

No monetary reward is offered under this policy. We do not operate a bug bounty programme, we do not publish a reward schedule, and no payment is implied by the existence of this policy, by an acknowledgement, or by the publication of a fix. Any reward would require a separate written agreement signed on behalf of Ariyan Debnath (Wenxenith Technologies LLP), and no member of staff has authority to promise one in a support conversation.

An acknowledgement may be published in a security advisory, in a changelog, or in a dedicated acknowledgements section. We will not publish a researcher name, handle, or contact detail without consent, and consent may be withdrawn before publication. We may decline to acknowledge a report where the conduct in Chapter 5 has not been followed.

10.Duplicate and Previously Reported Issues

The same weakness is frequently reported by several researchers. Where a report duplicates an issue that is already under investigation or already known to us, the first complete report received establishes priority for acknowledgement. A later report of the same root cause is treated as a duplicate, even where the endpoint, the parameter, or the affected host differs.

We determine duplication by root cause rather than by symptom. Two reports that describe the same underlying defect in the same component are duplicates, while two reports that describe different defects in the same component are not. Where a duplicate report adds materially new information, we will note the contribution and may acknowledge it separately.

A report concerning an issue that we have already remediated, or that has already been reviewed and closed, may be closed without further action. Where this occurs, we will tell the researcher what we can disclose about the earlier assessment, taking care not to reveal information that belongs to another reporter or that could assist an attacker.

11.Confidentiality and Personal Data

We treat reports as confidential. Access is limited to staff and contractors who need the information in order to assess, reproduce, or remediate the finding. We do not publish a report, or the identity of a reporter, without consent, except where disclosure is required by law or by a competent authority.

We collect the information that a report contains, together with correspondence about it, for the purpose of investigating and remediating the finding, for maintaining a security record, and for meeting legal and regulatory obligations. The lawful basis for processing is our legitimate interest in protecting our systems and our customers, and, where applicable, compliance with a legal obligation.

Report records are retained for as long as needed for the purposes above and are then deleted or anonymised. Where a report becomes part of a legal matter, it may be retained for the duration of that matter and for any applicable limitation period. Personal data is handled in accordance with our Privacy Policy, which describes rights of access, correction, and erasure, and the process for raising a concern.

Where a report contains personal data of a third party, we ask that the researcher minimise what is included and redact what is not necessary. If such data is received, we may delete it, and we will not use it for any purpose other than the investigation. We may need to notify an affected party where the law requires it, and we will do so in a manner that protects the identity of the reporter where possible.

12.Prohibited Conduct and Consequences

The following conduct is prohibited. It is not research, it is not protected by this policy, and it may constitute a criminal offence or a civil wrong.

  • Demanding payment, a reward, or any other benefit in exchange for withholding a report or for delaying disclosure.
  • Threatening to publish a finding, to disrupt a service, or to disclose customer data unless a demand is met.
  • Retaining, copying, selling, or publishing data obtained during research, including data that belongs to a customer.
  • Using a finding to gain access to an account, to alter a system, to install software, or to interfere with a service.
  • Continuing to test after a request to stop, or returning to a system after access has been withdrawn.
  • Concealing the nature of an activity, or misrepresenting a report in order to obtain information or a benefit.

Where prohibited conduct is identified, we may suspend or terminate any account held by the person concerned, block access to our systems, and preserve evidence. We may refer the matter to law enforcement or to another competent authority, and we may pursue civil remedies for loss, including the cost of investigation, remediation, and legal advice. We may also notify affected customers where their data may have been accessed.

Nothing in this Chapter limits the protection in Chapter 6 for research that complies with this policy. The protection is lost only in respect of conduct that falls outside the policy, and a report that is otherwise valid is not disregarded merely because a separate act was prohibited.

13.Changes to This Policy

We may amend this policy from time to time to reflect changes in our systems, in industry practice, or in applicable law. The revised version will be published on this page, and the date shown at the top will be updated. The revised version applies from the date of publication.

Changes are prospective. Research that was carried out in compliance with the version in force at the time will be assessed against that version, even where the policy has since changed. We will not apply a new restriction retrospectively to conduct that was authorised when it occurred.

Where a change materially reduces the scope of the policy or the protection offered, we will describe the change on this page for a reasonable period. Continued research after the date of publication constitutes acceptance of the revised policy. If you do not accept a change, you should stop research on our systems.

14.Contact

Security reports should be sent to [email protected]. This address is the correct channel for new findings, for updates on an existing report, and for requests to arrange a secure exchange. Please include the reference number that we provide where one has been issued.

Questions about this policy, and legal notices connected with it, should also be sent to [email protected]. General service questions should be sent to [email protected], which is the correct channel for account and technical support.

Our postal address is Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India. The entity responsible for the systems described in this policy is Ariyan Debnath (Wenxenith Technologies LLP), trading as Luveedu and Luveedu Cloud.

This policy is governed by the laws of India, and the courts of Tripura have exclusive jurisdiction in respect of any dispute connected with it, subject to any right that cannot be excluded by agreement.

Grievance Redressal

Grievance Officer

Wenxenith Technologies LLP has appointed a Grievance Officer for complaints and notices under this policy. He acts independently of our sales and support teams, and there is no charge to raise a grievance.

Email the Grievance Officer at [email protected]
Include your account email, the policy concerned, and any reference number
Expect an acknowledgement within 48 hours
We provide a written outcome within 30 days
Technical support remains available at [email protected]
Designated Grievance Officer
Shyamal Debnath
Grievance Officer
[email protected]
+91 7641818218
Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India
We acknowledge every grievance within 48 hours and aim to resolve it within 30 days.