Trust & Compliance

Domain Registration Agreement

The terms that apply to domain registration, renewal, transfer, and management.

Last updated: 29 October 2026 Applies to all Luveedu Cloud services
Domain Registration Agreement

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

This Domain Registration Agreement sets out the terms that apply when you register, renew, transfer, restore, or manage a domain name through Luveedu Cloud. It is issued by Ariyan Debnath (Wenxenith Technologies LLP), trading as Luveedu and Luveedu Cloud, and it binds every person or entity that submits a domain order through our website, our control panel, or our support channels.

Domain names are not supplied by us directly. They are registered through ICANN-accredited registrars, including Dynadot and other registrar partners, and they are subject to the rules of the registry that operates the relevant top-level domain. This agreement explains how those rules interact with our own, what we do on your behalf, and what you must do to keep a registration valid and resolvable.

A domain registration is a limited, renewable right to use a name for a fixed term. It is not a sale of the name, not a guarantee of continued availability, and not a grant of any trademark or other intellectual property right. Please read this agreement in full before you place an order.

1.Scope and Parties

This agreement binds the person or entity identified as the registrant of a domain name ordered through Luveedu Cloud, together with any person who submits an order, manages a domain in an account, or pays for a registration on behalf of that registrant. It also binds Ariyan Debnath (Wenxenith Technologies LLP), trading as Luveedu and Luveedu Cloud, which we refer to in this agreement as we, us, or our.

We act as a reseller and service provider of domain registration services. The registrar of record for a domain is an ICANN-accredited registrar with which the registration is held, and the registry is the organisation that operates the relevant top-level domain. A registration therefore involves three parties: you as the registrant, the registrar of record, and the registry. We interface with the registrar on your behalf, but we are not the registry and we do not control registry operations.

The registrar of record for each domain is identified in your control panel and in the public registration data described in the chapter on Registrant Data and Verification. Where the registrar of record changes, whether because of a transfer between registrars or an internal migration, this agreement continues to apply to the registration without interruption.

If you register a domain for a client, an employer, or any other third party, you are the registrant of record unless and until a change of registrant is completed under this agreement. You remain responsible for every obligation in this agreement, including payment, the accuracy of registrant data, and compliance with registry rules, even where a third party uses the domain.

This agreement applies to every domain name in your account, including names obtained by registration, by transfer from another registrar, by internal transfer between your own accounts, or by any bulk operation that we make available.

2.Registrar, Registry, and ICANN

We maintain relationships with ICANN-accredited registrars, including Dynadot, and with other registrar partners. The registrar of record is bound by the ICANN Registrar Accreditation Agreement and by the consensus policies that ICANN adopts from time to time. Those obligations flow through to your registration.

The registry for each top-level domain publishes its own registration policies, naming rules, eligibility criteria, and dispute procedures. Registries also implement technical policies on reservation, allocation, and deletion. You are bound by the policies of the relevant registry for as long as the domain is registered in that top-level domain.

ICANN policies that may affect your registration include, among others, the transfer policy, the requirements for public registration data through WHOIS and RDAP, the Expired Registration Recovery Policy, the Uniform Domain-Name Dispute-Resolution Policy, and the Uniform Rapid Suspension system. ICANN may adopt temporary policies or amend existing policies, and those changes bind registrations when they take effect.

Where a mandatory law, an ICANN policy, or a registry policy conflicts with this agreement, the mandatory law, the ICANN policy, or the registry policy prevails to the extent of the conflict. In that event we are not in breach of this agreement for complying with the higher rule, and we are not obliged to offer a substitute arrangement that the higher rule prohibits.

We do not control ICANN, any registry, or any registrar of record, and we cannot override a decision that they are entitled to make. Where a registry or ICANN requires an action, our ability to delay, reverse, or mitigate that action is limited to what the applicable rules allow.

3.Eligibility and Registrant Warranties

You must be at least eighteen years of age and legally capable of entering into a binding contract, or you must be a company, partnership, trust, or other entity that is duly formed and authorised to carry on business. By submitting an order, you confirm that you satisfy this requirement.

You represent and warrant to us, to the registrar of record, and to the relevant registry, on each day that a domain remains registered, that:

  • every statement you make in the order and in the registrant data is true, complete, and accurate, and you will keep it current;
  • the registration and use of the domain does not infringe the intellectual property, privacy, or other rights of any third party;
  • the domain is not registered or used for an unlawful purpose, including fraud, phishing, malware distribution, unauthorised access, or the sale of prohibited goods or services;
  • the domain is not registered or used in breach of our Terms and Conditions or our Acceptable Use Policy;
  • you have the authority to bind the registrant, and where the registrant is an entity, you are authorised to act for it;
  • you will comply with applicable law in every jurisdiction in which the domain is used or accessed; and
  • you are eligible to hold the domain under the rules of the relevant registry, including any local presence, nexus, or documentary requirement.

If you submit an order on behalf of a third party, you warrant that you have the authority of that party to register the name, to accept this agreement on behalf of that party, and to disclose the registrant data that the order requires. You must not register a domain in the name of another person without the informed consent of that person.

A breach of any warranty in this chapter is a material breach of this agreement. We may suspend, cancel, or transfer the registration, decline to renew it, and report the matter to the registrar or the registry, without refund and without liability to you.

4.Registration Process and Acceptance

An order submitted through our website or control panel is an offer to purchase a registration. Acceptance occurs only when the registry confirms that the domain has been created and the registration appears in your account. A search result, an entry in a shopping cart, a pending order, or a pre-registration expression of interest is not a reservation and creates no right to the name.

We do not guarantee that any domain is available, that an order will be accepted, or that a registration will be completed within a stated time. Availability is determined by the registry at the moment it processes the request, and two requests for the same name may be submitted at almost the same time. Where a registration cannot be completed, we will refund the amount paid for that registration in accordance with the Refund Policy.

A registry may reject or decline a registration for reasons that include a reserved or blocked name, a premium name subject to different terms, an eligibility or nexus failure, an invalid character or script combination, a sanctions or compliance restriction, or a registry policy that prohibits the registration. A rejection by the registry is not a fault on our part, and our only obligation is to return the amount we received for the unsuccessful order, less any non-recoverable charge.

Premium names, reserved names, and names released from previous registrations may be offered on non-standard terms. A premium registration may carry a higher registration fee and a higher renewal fee, and those amounts are shown before you confirm the order. Names released by a registry may be allocated through a waitlist, a ballot, or an auction, and a bid placed in an auction is a binding commitment to pay if you are the successful bidder.

We may refuse, hold, or cancel an order where we are required to do so by law, by ICANN, by a registry, or by a registrar, or where we reasonably suspect fraud, a breach of our policies, or an attempt to register a name for an abusive purpose. Where we cancel an order for one of these reasons, we are not liable for any loss that you claim to have suffered as a result.

5.Registrant Data and Verification

We collect the registrant name, organisation, postal address, email address, telephone number, and any other information that the registrar or the registry requires. The data must be accurate and complete at the time of the order, and you must update it within seven days of any change. A mailbox that you do not monitor, or an address that no longer exists, is a breach of this chapter even where the domain continues to resolve.

Registrant data is published in the public registration data system for the top-level domain, which is accessible through WHOIS and, increasingly, through RDAP. The published record normally includes the domain name, the registrar, the creation and expiry dates, the name servers, the status codes, and the registrant details, subject to any privacy or proxy service described in this agreement and subject to any redaction that the registry or ICANN applies.

Under the 2013 Registrar Accreditation Agreement, the registrar of record must verify either the email address or the postal address of the registrant within fifteen days of a registration, a transfer, or a material change to the registrant data. The registrar, or we on behalf of the registrar, will send a verification request to the registrant email address or by another method the registrar accepts. You must respond and complete the verification within fifteen days of the request.

If you do not complete verification within the required period, the registrar must suspend the domain. A suspended domain is removed from resolution, may be placed on a registrar hold or a registry hold, and may ultimately be cancelled or deleted. A domain that is suspended or deleted for failure to verify is not eligible for a refund, and we are not liable for any loss of traffic, email, revenue, or reputation that follows.

Where registrant data is false, incomplete, or misleading, we may suspend or cancel the registration immediately, decline any renewal or transfer, and report the matter to the registrar, the registry, or a competent authority. We may also require re-verification after a change of registrant, a transfer, a complaint, or a periodic review, and the same consequences apply if verification is not completed.

You are responsible for the consequences of any failure by a third party to whom you have given access to your account, including a designer, a developer, an agency, or a former employee who changes the registrant email address without authority.

6.Privacy and Proxy Services

Where a privacy or proxy service is available for a top-level domain and is ordered for a domain, the service replaces the published registrant name, organisation, postal address, email address, and telephone number with the contact details of the service. The purpose is to reduce unsolicited contact and casual data harvesting, not to conceal the identity of the registrant from a person with a legitimate legal claim.

The following information generally remains public even where a privacy service is active: the domain name, the registrar of record, the creation, update, and expiry dates, the name servers, the domain status codes, and, for some top-level domains, the registrant country or the registrant organisation. Some registries require the publication of additional fields, and some do not permit any form of redaction or proxy at all.

A privacy or proxy service is not an anonymity service. The registrant remains fully responsible for the domain, for the accuracy of the underlying data, and for every use of the name. The service provider may suspend or remove the privacy service, and disclose the underlying data, where the domain is used for abuse, where a verified complaint is received, where a court or regulator requires disclosure, or where disclosure is necessary to prevent harm or to comply with law.

We may disclose the underlying registrant data to a registrar, a registry, a dispute resolution provider, a law enforcement agency, or a party with a lawful basis for the request, in accordance with the chapter on Non-Public Registrant Data Requests and our Privacy Policy. We may act without prior notice to you where notice is prohibited, where notice would defeat the purpose of the request, or where urgent action is required.

Privacy and proxy services are optional, are not available for every top-level domain, and are charged separately. Fees for a privacy or proxy service are non-refundable once the service has been ordered, including where the service is later suspended or removed because of abuse or a legal requirement.

7.Fees, Renewals, and Auto-Renewal

Registration, renewal, transfer, restoration, and privacy fees are shown at checkout before you confirm an order. Prices are stated in the currency displayed at checkout and may be subject to applicable taxes, levies, and payment processing charges. By confirming an order you authorise us and our payment providers to charge the amount shown, and to store the payment method for future renewal charges where you have enabled that option.

Auto-renewal is enabled by default for domain registrations. Where auto-renewal is active, we or the registrar may attempt to charge the payment method on file in advance of the expiry date, within a window that the registrar or the registry sets for the relevant top-level domain. You may disable auto-renewal in the control panel. If you disable it, or if the payment method fails, you are solely responsible for renewing the domain before it expires.

We send renewal reminders as a courtesy to the registrant email address and the account email address. Reminders are not a guaranteed service, may be delayed or filtered, and do not replace your own calendar or monitoring. A failure to receive a reminder does not extend the registration, does not create a right to reinstatement, and does not make us liable for an expired domain.

An early renewal adds a further term to the existing registration and does not shorten the current term. A renewal is charged at the price in effect when the renewal is processed, which may differ from the price paid at registration. We may change renewal prices, and where we do so we will make reasonable efforts to give notice before the renewal is processed. A premium name may renew at a premium price even where the initial registration was purchased at a standard price.

A failed payment may be retried, and a domain may enter the expiry and redemption process described in this agreement if payment is not completed. Renewal fees, including early renewals and auto-renewals that have been processed, are non-refundable except where the Refund Policy expressly provides otherwise.

8.Expiry, Grace Periods, and Redemption

A registration runs for a fixed term. When the term ends, the domain does not become available immediately. It passes through a sequence of stages that the registry defines and that the Expired Registration Recovery Policy requires the registrar to disclose. The stages and their lengths vary between top-level domains, and the dates shown in your control panel are the best available indication rather than a guarantee.

In the first stage, the auto-renew grace period, the domain has expired but may still be renewed at the standard renewal price. The registrar may also delete the domain during this period. In the second stage, the redemption grace period, the domain has been deleted from the registry zone but can still be restored. Under the Expired Registration Recovery Policy, the redemption period is at least thirty days, and the registrar must publish the fees and the process that apply.

A restoration requires payment of a redemption or restore fee set by the registry, together with any administration fee that we or the registrar charge. A domain in the redemption period does not resolve, and the previous name servers and DNS records may be removed or may be retained only temporarily. A restored domain may return without its previous configuration, and you are responsible for restoring DNS records from your own records.

After the redemption period, the domain enters a pending delete stage and is then released by the registry. Once released, the name can be registered by any person, including through a backorder, a waitlist, or an auction. We do not guarantee that an expired domain can be recovered at any stage, and we are not liable for the loss of a name that is deleted because it was not renewed in time.

You are responsible for monitoring expiry dates and for keeping a current payment method on file. Where a domain is important to your business, you should renew it well before the expiry date and should not rely on a single reminder or on auto-renewal alone.

9.Transfers In

To transfer a domain to us from another registrar, the domain must normally be unlocked at the losing registrar, an authorisation code must be obtained from that registrar, and the administrative contact must be able to approve the transfer. Most top-level domains impose a waiting period of sixty days after a registration or a previous transfer before another transfer is permitted, and some registries impose longer or different periods.

A transfer normally completes within five to seven days. The losing registrar may approve the request sooner, and some transfers complete almost immediately where the losing registrar does not object. During the process the domain continues to resolve through the losing registrar as name servers, so a brief interruption is unusual but is not excluded.

A transfer may fail for reasons outside our control, including:

  • an incorrect or expired authorisation code;
  • a registrar lock or a registry lock that the losing registrar has not removed;
  • a pending dispute, a court order, or a suspension applied by the losing registrar;
  • an unpaid balance at the losing registrar, or a refusal by that registrar to release the domain;
  • the sixty-day lock after a registration, a previous transfer, or a change of registrant;
  • an expired domain that is outside the renewal or redemption window; or
  • a registry rejection based on eligibility, documentation, or a restricted top-level domain.

Where a transfer fails, we will refund the transfer fee in accordance with the Refund Policy, after deducting any amount that the registry or the losing registrar does not return to us. Where a transfer succeeds, the fee is not refundable, and the transfer normally adds a renewal year to the existing term where the registry permits it.

A transfer between registrars does not by itself change the registrant. If the registrant of record must change at the same time, a separate change of registrant is required, and that change may itself impose a new sixty-day transfer lock.

10.Transfers Out

You may transfer a domain away from us at any time, subject to the rules of the relevant registry and the ICANN transfer policy. To begin, submit a request through our support channels from the account that holds the domain. Where the request is properly authorised and the domain is eligible, we will remove the registrar lock and provide the authorisation code, generally within one business day.

We do not obstruct a transfer out. We will not refuse a transfer, or delay one beyond the period the applicable policy allows, in order to retain your business. We may decline or postpone a transfer only where the applicable policy permits, including where there is an unpaid balance for the preceding registration period, where the domain is subject to a pending dispute or a court order, where a fraud or security hold is in place, or where the request cannot be authenticated.

A transfer out ends our management of the domain. Services that depend on the domain, including DNS hosting, email, SSL certificates, and website hosting configured against the domain, may stop working once the transfer completes. You are responsible for arranging replacement services, for exporting DNS records, and for taking any backup you require before the transfer.

We retain records of the registration, the transfer, and the associated account activity for the period required by ICANN, by the registrar, and by applicable law. Retention continues after the transfer and is governed by our Privacy Policy.

11.Change of Registrant

A change of registrant means a material change to the registrant name, the registrant organisation, or the registrant email address. A correction to a postal address, a telephone number, or a name server is not a change of registrant. A change of registrant transfers control of the name and is treated seriously.

A change of registrant must be requested from the account that holds the domain. We will send a notification to the current registrant email address and to the proposed new registrant email address, and the change will proceed only after the required confirmations are received. Where the change is requested by a person who is not the current registrant, we may require the consent of the current registrant and evidence of the authority to act.

We may ask for evidence of identity, evidence of the authority to act for an organisation, a signed authorisation, or a combination of these. We may also carry out fraud and security checks, and we may place a temporary hold on the domain while those checks are completed. Where the evidence is not provided, or where the request appears to be an attempt to take control of a domain without authority, we will decline the change and may restrict the account.

Under the ICANN transfer policy, a change of registrant imposes a sixty-day lock on transfer to another registrar, unless the current registrant and the new registrant both expressly opt out in the manner the policy requires. The lock is applied by the registrar and cannot be waived by us. A change of registrant does not alter the registration term, does not reset the expiry date, and may attract an administration fee where the registrar permits one.

12.Registry and TLD-Specific Rules

Each top-level domain is governed by the policies of its registry, and those policies vary considerably. A rule that applies to one extension may not apply to another, and a practice that is permitted in one registry may be prohibited in the next. You are responsible for checking the rules that apply to the extension you choose before you place an order.

Some registries impose eligibility criteria. A country-code top-level domain may require a local presence, citizenship, residency, or a registered business in the relevant country. A sponsored or restricted generic top-level domain may limit registration to a defined community or require membership of a professional body. Some registries require documentary evidence, such as a certificate of incorporation, a tax registration, or a signed declaration, and set a deadline for providing it.

Country-code top-level domains operate under the law and the policies of the relevant country. The .in extension, for example, is administered by the .IN Registry and is subject to the .IN Domain Name Dispute Resolution Policy, commonly known as INDRP, as well as to the published registration rules of that registry. Requirements for documentary evidence, local presence, and permitted name structure can change, and a failure to satisfy them can result in deletion of the domain.

Registries also impose technical and naming rules. These may cover permitted characters, script and language combinations for internationalised domain names, transliteration and variant handling, the length of labels and of the full name, prohibited prefixes and suffixes, and lists of reserved or blocked names. A registration that does not comply with these rules may be rejected at the time of the order or deleted later.

Where a registry determines that a registrant is not eligible, or that the required documentation has not been provided within the deadline, the registry may suspend or delete the domain. In that event the registration fee is not refundable, and we are not liable for any loss. We may also decline to submit an order where we are not satisfied that the eligibility requirement can be met.

13.Suspension, Cancellation, and Deletion by Registry or Authority

A registry, a registrar, ICANN, a court, a regulator, a law enforcement agency, or a dispute resolution provider may require a domain to be suspended, placed on hold, transferred, cancelled, or deleted. A requirement may arise from a court order, a lawful direction, a panel decision in an administrative proceeding, a sanctions or export control measure, a registry policy enforcement action, or a takedown request based on abuse.

We will comply with a requirement of that kind. We are not obliged to investigate the merits of the underlying decision, to delay compliance in order to obtain your instructions, or to challenge the decision on your behalf. Where the requirement is urgent, for example where a domain is being used for phishing or malware distribution, we may act immediately and before any notice to you.

Separately, we may suspend or cancel a registration where you breach this agreement, our Terms and Conditions, or our Acceptable Use Policy, where an invoice remains unpaid, where registrant data cannot be verified, where we reasonably suspect fraud, or where the registration exposes us, the registrar, or the registry to legal or regulatory risk.

We will give notice of a suspension or cancellation where we are permitted to do so and where notice would not defeat the purpose of the action. A suspension or cancellation under this chapter does not create a right to a refund. A domain will be restored only where the authority that required the action permits restoration and where the applicable fees have been paid.

We are not liable for any loss of traffic, revenue, email, data, ranking, or goodwill that results from a suspension, cancellation, deletion, or transfer carried out under this chapter, whether the action was taken by us, by the registrar of record, or by a registry or authority.

14.Non-Public Registrant Data Requests

A request for registrant data that is not published may be made by a law enforcement agency, a regulator, a court, an intellectual property owner with a documented claim, a dispute resolution provider, a registry, a registrar, an auditor, or a party acting under a legal process. A request from a member of the public without a legal basis will not normally be granted.

We verify the identity of the requester and the legal basis for the request before we disclose anything. Depending on the circumstances, we may require a court order, a subpoena, a formal request from a competent authority, a statutory demand, or a declaration of the basis for the claim. We may also ask the requester to narrow the request to the data that is actually necessary.

We assess each request for proportionality, for the sensitivity of the data, and for the risk of harm to the registrant. We may disclose data without notice to you where notice is prohibited by law, where notice would prejudice an investigation, where the request concerns serious abuse, or where urgent action is required to prevent harm.

Where the applicable law permits, we may recover our reasonable costs of responding to a request. Disclosure is made in accordance with our Privacy Policy and applicable data protection law. We do not sell registrant data, and we do not disclose it for marketing purposes.

You must not use a privacy or proxy service to conceal a registration that is unlawful, fraudulent, or abusive. Concealment of that kind is a breach of this agreement and may result in suspension, disclosure, and cancellation of the registration.

15.Customer Responsibility and Indemnity

You are responsible for the management of your domains. That includes monitoring expiry dates, maintaining a current payment method, keeping the registrant email address and postal address accurate, responding to verification requests, and keeping your own record of DNS configuration and name servers. You should take a backup of DNS records and website content before any transfer, renewal lapse, or change of registrant.

You are responsible for clearing the use of a name against the trademark, company name, and other rights of third parties in every jurisdiction in which you trade. We do not carry out trademark clearance, do not provide legal advice, and do not warrant that a registration is free of third-party rights. A registry acceptance or a completed registration is not a determination that the name is lawful to use.

You agree to defend, indemnify, and hold harmless Ariyan Debnath, Wenxenith Technologies LLP, the Luveedu and Luveedu Cloud brands, and their officers, employees, and agents against any claim, demand, proceeding, liability, loss, damage, cost, or expense, including reasonable legal fees, that arises from or relates to:

  • a domain that you register, renew, transfer, or use, including any claim of trademark or other intellectual property infringement;
  • any content, service, or activity that is accessible through a domain you control;
  • any inaccurate, incomplete, or misleading registrant data that you provide;
  • any breach of this agreement, our Terms and Conditions, or our Acceptable Use Policy; and
  • any unlawful, fraudulent, defamatory, or abusive use of a domain.

This indemnity survives the expiry, cancellation, transfer, or deletion of a domain and the closure of your account. It is in addition to, and does not limit, any other right or remedy available to us.

16.Liability and Service Limits

We do not guarantee that a registration will be accepted, that a domain will remain available, that a name will continue to resolve, or that a registry will continue to operate a top-level domain on its current terms. Registries may change policy, impose new eligibility requirements, or retire an extension, and ICANN may adopt policies that affect a registration. We are not liable for a change of that kind.

To the maximum extent permitted by law, we exclude liability for indirect, incidental, special, punitive, and consequential loss, and for loss of profit, revenue, anticipated savings, business opportunity, goodwill, data, traffic, search ranking, or reputation, however that loss arises and whether or not we were advised of the possibility of the loss.

Our total aggregate liability arising out of or in connection with a particular domain, whether in contract, tort, negligence, or otherwise, is limited to the fees that you paid to us for that domain in the twelve months immediately before the event giving rise to the claim. This limit is aligned with the limitation of liability in our Terms and Conditions.

Nothing in this agreement excludes or limits liability that cannot be excluded or limited by applicable law, including liability for fraud or for death or personal injury caused by negligence.

We are not liable for a failure or delay caused by an event outside our reasonable control, including a registry or registrar outage, a network or name server failure, an ICANN or registry action, a sanctions measure, a denial of service attack, or a failure of a third-party payment provider.

17.Relationship with Other Documents

This agreement forms part of a set of documents that together govern your use of our services. You must read it together with our Terms and Conditions, our Domain Name Dispute Resolution Policy, our Privacy Policy, and our Refund Policy.

For matters that concern a domain registration, renewal, transfer, restoration, or registrant data, this agreement prevails over the Terms and Conditions to the extent of any inconsistency. For all other matters, the Terms and Conditions prevail. The Refund Policy governs the availability of refunds, the Privacy Policy governs the handling of personal data, and the Domain Name Dispute Resolution Policy governs complaints about the registration and use of a domain.

Mandatory law, ICANN policy, and registry policy prevail over every document in this set, in that order of priority. Where a provision of this agreement is found to be invalid or unenforceable, the remaining provisions continue in full force, and the invalid provision is read down to the minimum extent necessary to make it enforceable.

A failure by us to enforce a provision on one occasion is not a waiver of that provision or of any other provision. We may assign or novate this agreement as part of a corporate reorganisation, a merger, or a transfer of the business, and you may not assign it without our written consent.

18.Contact and Notices

Routine support for domain orders, renewals, transfers, DNS configuration, and control panel access is provided at [email protected]. Formal legal notices, complaints about registrant data, requests for non-public data, and correspondence about a dispute must be sent to [email protected].

Our postal address for notices is Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India. Notices relating to this agreement should be addressed to the Domain and Registrant Contact identified on this page.

A formal notice to us must be in writing, must be sent by email to the legal notices address above, must identify the account and the domain concerned, and must state the basis for the notice and the action requested. A notice is effective when we acknowledge receipt, or on the next business day where it is received outside business hours. A notice sent to a support address, to a member of staff personally, or through a social media channel is not a formal notice.

We send notices to the registrant email address and the account email address on record. You are responsible for keeping those addresses current. A notice is deemed received twenty-four hours after it is sent, even if the message is filtered, undelivered, or unread, unless we receive a delivery failure notification.

This agreement is governed by the laws of India. The courts at Tripura have exclusive jurisdiction over any dispute arising out of or in connection with this agreement, without prejudice to any procedure mandated by ICANN, by a registry, or by a dispute resolution provider, including the Uniform Domain-Name Dispute-Resolution Policy and the INDRP.

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.