Trust & Compliance

Domain Name Dispute Resolution Policy

How complaints about a domain name registered through Luveedu Cloud are handled, and what we will and will not do.

Last updated: 29 October 2026 Applies to all Luveedu Cloud services
Domain Name Dispute Resolution Policy

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

This Domain Name Dispute Resolution Policy explains how a complaint about a domain name registered through Luveedu Cloud is handled. It describes the mandatory administrative proceedings that apply to domain names, the role that we play, the locks and holds that may be applied while a proceeding is pending, and the effect of a panel decision or a court order.

We do not decide who is entitled to a domain name. That question is decided by an accredited dispute resolution provider, by a panel appointed under the applicable rules, or by a court of competent jurisdiction. Our role is to apply the procedural steps that the applicable rules require, to preserve the status quo while a proceeding is pending, and to implement a decision or order once it is issued.

This policy applies in addition to the mandatory policies of ICANN and of the relevant registry. Where those policies impose a requirement that differs from this policy, the mandatory policy prevails, and we will follow it.

1.Purpose and Scope

This policy applies to every domain name registered through Luveedu Cloud, whether the registration was made directly with us, obtained by transfer, or acquired through a change of registrant or an internal account transfer. It applies to generic top-level domains, to country-code top-level domains, and to sponsored and restricted extensions, subject to the rules of the relevant registry.

The policy is issued by Ariyan Debnath (Wenxenith Technologies LLP), trading as Luveedu and Luveedu Cloud. It governs the conduct of a dispute as it affects us as the provider of the registration service. It does not displace the rules of a dispute resolution provider, the procedure set out in the applicable policy, or the jurisdiction of a court.

This policy does not apply to a complaint about hosting content, email, or another service that is separate from the domain registration, except where a dispute about a domain also engages our Acceptable Use Policy or our abuse handling process. Those matters are dealt with under the relevant service terms.

A dispute may be brought by a trademark owner, by a licensee, by a party with another recognised right, or by a registry or a regulator acting under its own rules. A dispute between two private parties about entitlement to a name is resolved through the mechanisms described in this policy, not by us.

2.Definitions

In this policy, the following terms have the meanings given below. Other capitalised terms carry the meaning given in the Domain Registration Agreement or in our Terms and Conditions.

  • Complainant means the party that files a complaint against a domain name.
  • Respondent means the registrant of the domain name against which a complaint is filed.
  • Provider means a dispute resolution service provider accredited by ICANN, or another body authorised to administer a proceeding under the rules of the relevant registry.
  • Panel means the single panellist or the three-member panel appointed by a Provider to decide a complaint.
  • UDRP means the Uniform Domain-Name Dispute-Resolution Policy adopted by ICANN, together with the Rules for Uniform Domain Name Dispute Resolution Policy and the applicable supplemental rules of the Provider.
  • URS means the Uniform Rapid Suspension system adopted by ICANN for clear-cut cases of abusive registration in eligible top-level domains.
  • INDRP means the .IN Domain Name Dispute Resolution Policy and its rules, which apply to domain names in the .in extension and in related extensions administered by the .IN Registry.
  • Registry means the organisation that operates the relevant top-level domain and maintains the authoritative register.
  • Registrar of Record means the ICANN-accredited registrar with which the domain is held at the time of the complaint.
  • Registration Agreement means our Domain Registration Agreement, including the registry rules incorporated into it.

3.Mandatory Administrative Proceedings

By registering a domain name through us, you agree to be bound by the UDRP, as incorporated by reference into the Registration Agreement and into the registration agreement of the registrar of record. The UDRP applies to all open generic top-level domains and to a number of country-code top-level domains that have adopted it voluntarily.

The URS applies to eligible generic top-level domains as a faster procedure for clear-cut cases of abusive registration. The URS does not transfer a domain to the complainant. Where a URS complaint succeeds, the domain is suspended for the remainder of its registration term, and the suspension may be lifted only in the circumstances that the URS rules allow.

Domain names in the .in extension and in related extensions administered by the .IN Registry are subject to the INDRP. The INDRP has its own rules on filing, responses, panel appointment, fees, and remedies, and it is administered under the authority of the .IN Registry. A complainant must use the procedure that applies to the extension in question.

Other country-code top-level domains operate their own dispute procedures, which may differ materially from the UDRP. Some provide for administrative resolution, some require court proceedings, and some combine both. You are bound by the procedure that the relevant registry has adopted, and you are responsible for understanding it before you register a name in that extension.

A Provider may consolidate complaints, extend deadlines, admit supplemental filings, or apply sanctions for abusive conduct in accordance with its rules. We are not a party to those procedural decisions and do not control them.

4.Your Representations

By registering a domain name, you represent and warrant that the registration is not made for an unlawful purpose, that it does not infringe the rights of any third party, and that it is not being registered or used in bad faith. These representations apply at the time of registration and continue for as long as the domain remains registered.

You further represent that you are not registering the name primarily to sell, rent, or otherwise transfer it to the owner of a trademark or service mark for valuable consideration, to prevent the owner of a mark from reflecting it in a corresponding domain name, or to disrupt the business of a competitor. Registrations of that kind are the classic forms of abusive registration identified in the UDRP.

You represent that the information you have provided in the registration is accurate and complete, that you will keep it current, and that you will not use a privacy or proxy service to conceal a registration that is unlawful or abusive.

A breach of these representations is a breach of the Registration Agreement. It may result in suspension or cancellation of the domain, and it may be relied upon by a complainant in an administrative proceeding.

5.Evidence of Registration and Use

In a proceeding under the UDRP, the complainant must establish three elements: that the domain is identical or confusingly similar to a trademark or service mark in which the complainant has rights, that the respondent has no rights or legitimate interests in the domain, and that the domain was registered and is being used in bad faith. The burden of proof rests with the complainant.

A panel assesses bad faith on the evidence before it. Factors commonly considered include the following:

  • an offer to sell, rent, or transfer the domain to the complainant or to a competitor for consideration beyond the documented out-of-pocket costs of registration;
  • a pattern of registering domain names in order to prevent mark owners from reflecting their marks in corresponding domain names;
  • registration of the domain primarily to disrupt the business of a competitor;
  • use of the domain to attract internet users for commercial gain by creating a likelihood of confusion with the mark of the complainant;
  • registration of the domain with knowledge of the mark, combined with use that exploits the reputation of that mark; and
  • concealment of identity, or provision of false contact details, in connection with the registration.

A panel also assesses whether the respondent has rights or legitimate interests in the domain. A bona fide use in connection with the offering of goods or services, a legitimate non-commercial or fair use, and use of a name that the respondent is commonly known by are among the circumstances that may establish a legitimate interest. The assessment is made on the evidence, and the respondent bears the burden of demonstrating a legitimate interest once the complainant has made a prima facie case.

In a URS proceeding, the standard is higher. The complainant must show that the registration is abusive on the basis of clear and convincing evidence, and the procedure is designed for cases in which the outcome is not seriously in doubt.

6.Our Role

We are a reseller of registrar services and the interface through which you manage the domain. We are not a dispute resolution provider, we are not a panel, and we do not adjudicate entitlement to a domain name. We do not assess the merits of a complaint, the strength of a trademark, or the credibility of a respondent.

Our role is procedural. We receive notices from a Provider, a registry, a court, or an authority, we verify that the notice relates to a domain in our system, we apply the locks and holds that the applicable rules require, and we implement the outcome once it is final. We also provide the registration data and the registration history that a Provider requires, to the extent that we hold it and are permitted to disclose it.

We may lock a domain, place it on hold, or restrict a transfer as soon as we become aware of a proceeding or a credible complaint, without waiting for a request from the Provider. A lock of that kind protects the integrity of the proceeding and does not indicate any view on the merits.

We may communicate with both parties about procedural steps, but we do not provide legal advice to either party, do not represent either party, and do not act as a mediator. A party that needs advice should consult independent counsel.

7.Locking, Suspension, and Transfer During Proceedings

When a complaint is filed, the Provider notifies the registrar of record. The registrar is required to lock the domain and to confirm the lock to the Provider. A registrar lock prevents a transfer to another registrar and prevents a change of registrant while the lock is in place. The domain normally continues to resolve during the proceeding, unless the Provider or a court orders otherwise or the registry applies a hold.

The registrar may also place the domain on a client hold or a server hold. A hold removes the domain from resolution or blocks a specific operation, and it may be applied where the domain is the subject of a URS proceeding, a court order, a law enforcement request, or a registry enforcement action. A hold may interrupt websites and email that depend on the domain.

A transfer is not permitted while a proceeding is pending, and it will not be permitted until the proceeding is concluded and any resulting lock has been released in accordance with the applicable rules. We will not release a lock at the request of one party alone where the applicable rules require the consent of the Provider or the conclusion of the proceeding.

Implementation of a decision follows the timelines in the applicable rules. A decision to transfer a domain is implemented after the period for appeal or review has expired, or after the Provider directs implementation. A decision to cancel a domain is implemented in the manner and on the timeline that the Provider specifies. A URS suspension is implemented on the direction of the Provider and remains in place for the balance of the registration term unless it is lifted.

Where a court order requires a different outcome from a panel decision, we will follow the order of the court, provided that the order is valid on its face and is addressed to us or to the registrar of record.

8.Court Proceedings and Orders

Either party may bring a court proceeding in a jurisdiction that the applicable rules recognise. Under the UDRP, the complainant must submit to the jurisdiction of the courts at the location of the registrar of record, or at the location of the registrant as shown in the registration data, and the respondent may bring proceedings in the same forum.

A court proceeding does not automatically suspend an administrative proceeding. The Provider may proceed, may suspend, or may terminate the administrative proceeding in accordance with its rules, and a panel may decide whether to continue in the light of the court proceeding.

We will comply with a valid court order that requires us to lock, transfer, suspend, cancel, or disclose information about a domain. Where the order is directed to the registrar of record or to the registry rather than to us, we will cooperate with the registrar and the registry to the extent that we are able.

We are not liable for any loss that results from compliance with a court order, including loss of traffic, email, revenue, or data, or from a delay in implementing an order while it is verified.

9.Trademark and Other Complaints

A complaint that concerns the content of a website, the use of a mark in commerce, or an allegation of passing off may engage the Copyright and Trademark Policy in addition to this policy. A complaint that concerns phishing, malware, spam, fraud, or another form of abuse may engage the Abuse Handling Policy and our Acceptable Use Policy.

A complaint may be made through more than one channel at the same time. A takedown request under the abuse process does not prevent a complainant from also filing a UDRP or URS complaint, and an administrative proceeding does not prevent a separate complaint about the content that is served from the domain.

Where a complaint alleges both a trademark issue and an abuse issue, we may act on the abuse issue independently of the administrative proceeding, including by suspending the domain, where the evidence justifies immediate action. Action of that kind is taken under our service terms and does not constitute a finding on entitlement to the name.

We may suspend a service while a complaint is investigated, and we may restore it if the complaint is not substantiated. Fees paid for the registration or for related services are not refundable as a result of a complaint, except where the Refund Policy expressly provides otherwise.

10.Response and Participation

A respondent has the right to respond to a complaint within the period that the Provider sets. Under the UDRP Rules, the response is normally due within twenty days of the date on which the complaint was transmitted, subject to any extension that the Provider grants. Under the URS, the response period is shorter and the rules are stricter.

We will forward a notice that we receive to the registrant email address on record, and we will make reasonable efforts to contact the registrant through the account email address. We are not responsible for a failure to respond that results from an outdated email address, a full mailbox, a spam filter, or a failure by the respondent to monitor the contact address.

A respondent that does not respond within the period set by the Provider is in default. In a UDRP proceeding, the panel decides the complaint on the basis of the complaint and the evidence that has been submitted, and a default does not automatically result in a decision for the complainant, although it removes the respondent from the evidentiary process. In a URS proceeding, the absence of a response has the consequences set out in the URS rules.

A respondent may be represented by counsel. The Provider deals with the representative that the respondent nominates, and we will follow the direction of the Provider on communications, subject to any requirement to serve the registrant directly.

11.Fees and Costs

Provider fees are set by the Provider and are borne by the party that the applicable rules require to pay them. In a UDRP proceeding the complainant normally pays the Provider fee when the complaint is filed. In a URS proceeding the fee structure is set by the URS rules, and a respondent that elects to file a response may be required to pay a response fee.

We do not set Provider fees, do not receive them, and do not refund them. A dispute about a Provider fee is a matter between the party and the Provider.

We may charge an administrative fee for work that we are required to perform in connection with a proceeding, including lock implementation, data production, transfer implementation, and correspondence, where the applicable rules or our published price list permit a charge of that kind. Any such fee is separate from the Provider fee and is not a condition of participation in the proceeding.

Each party bears its own legal costs unless a panel or a court orders otherwise. A panel may declare a complaint or a response to be abusive and may make an order about costs in the circumstances that the applicable rules allow.

12.Appeals and Reconsideration

A UDRP decision may be challenged in court by either party within the period that the applicable rules and the law allow. The decision is implemented after that period has expired, unless a court orders otherwise or the Provider directs a different timeline.

A URS determination is subject to the limited review mechanisms set out in the URS rules, including a de novo appeal to a three-member panel in the circumstances that the rules describe. A URS suspension is not an appealable merits decision in the same sense as a UDRP decision, and the routes available are defined by the URS procedure.

An INDRP decision may be challenged in the manner that the INDRP rules and Indian law permit. A party that wishes to challenge a decision should obtain independent legal advice, because the deadlines are strict and a failure to observe them may make the decision final.

We are not obliged to stay the implementation of a decision beyond the period that the applicable rules require. We will not delay implementation merely because a party announces an intention to appeal, unless a court order or a direction from the Provider requires us to do so.

13.Repeat Disputes and Account Measures

A pattern of adverse decisions, repeated complaints about the same account, or evidence that an account is being used to register names for the purpose of monetising the rights of others may result in measures against the account. Measures may include a requirement for additional verification, restrictions on new registrations, a restriction on transfers, suspension of the account, or termination of the account.

We may consider decisions in administrative proceedings, court judgments, registry determinations, and credible reports from rights holders when assessing a pattern. We may also consider the registration history of the account, including registrations that were cancelled or transferred after a complaint.

A measure taken under this chapter is a commercial and risk management decision. It does not constitute a finding that the account holder has infringed any right, and it does not prevent the account holder from pursuing an available remedy in the proper forum.

We may also report suspected abuse to a registrar, a registry, a Provider, or a competent authority, and we may cooperate with an investigation. We will do so in accordance with our Privacy Policy and applicable law.

14.No Liability for Outcomes

We are not liable for the outcome of a dispute, for a decision of a panel, for a judgment of a court, or for a determination of a registry. We do not warrant that a complainant will succeed, that a respondent will retain a domain, or that a proceeding will be concluded within a particular time.

We are not liable for a transfer, cancellation, suspension, hold, or lock that is carried out in compliance with a decision, an order, or a direction, or for any loss of traffic, email, revenue, data, ranking, or goodwill that results. This exclusion applies whether the action is taken by us or by the registrar of record or the registry.

We are not liable for a delay in implementing a decision where the delay is caused by a verification step, a court order, a Provider direction, a registry process, or an event outside our reasonable control.

Nothing in this chapter excludes liability that cannot be excluded by applicable law. The general limitation of liability in the Domain Registration Agreement and in our Terms and Conditions applies to every claim connected with a dispute.

15.Relationship with Other Documents

This policy must be read together with our Domain Registration Agreement, our Terms and Conditions, and our Privacy Policy.

The Domain Registration Agreement governs the registration itself, including renewals, transfers, registrant data, and the locks that may be applied to a domain. This policy governs the conduct of a dispute and the steps that we take while a proceeding is pending. The Terms and Conditions govern the use of our services generally.

Where this policy and the Domain Registration Agreement differ on a matter of procedure, this policy prevails for the duration of the proceeding. Where either document differs from the rules of a Provider, the rules of the Provider prevail for the proceeding, and where either differs from an ICANN policy or a registry policy, that policy prevails.

This policy is governed by the laws of India, and the courts at Tripura have jurisdiction over any dispute that concerns our conduct under this policy, without prejudice to the jurisdiction of a Provider, a panel, or a court in a proceeding that the applicable rules recognise.

16.Contact

Notices relating to a domain dispute, including a copy of a complaint, a provider notice, a court order, or a request for registration data in connection with a proceeding, must be sent to [email protected].

General questions about a domain, a control panel operation, or a renewal should be sent to [email protected]. A message sent to a support address is not a formal notice of a dispute and may not be treated as one.

Our postal address is Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India. Correspondence should be addressed to the Domain Dispute Contact identified on this page.

A notice should identify the domain, the account, the Provider or court concerned, the reference number of the proceeding where one has been assigned, and the action that is requested. Where a deadline applies, the notice should state the deadline and include the supporting document so that we can verify and act in time.

We acknowledge dispute notices within two Business Days and aim to complete the procedural steps required of us within the deadlines set by the Provider, the registry, or the court.

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.