Definitions, scope of agreement, acceptance, and domain name selection

Introduction and Preamble 1.1 This “Domain Registration Agreement” (the “Agreement”) is a legally binding agreement between Mubdie Ltd, the domain registration services registrar/provider operating of the mubdie.net website (“Mubdie”, “we”, or “the Registrar”), and the person or entity registering a domain name via the Mubdie Services(“you”, “the registrar”, or “the name holder”). This Agreement applies to all applications for registration, renewal, transfer, or any services related to the registration of domain names made available by us (collectively, the “Services”). 1.2  The provisions of this Agreement shall apply as of the effective date and shall apply to all transactions carried out via  the mubdie.net  Site or through channels contracted with Mubdie or its partners, unless expressly stated otherwise in the Product Offer at the time of purchase.

Definitions 2.1 “Registration Information” or “WHOIS Data” means all data that you are required to provide in the registration process, which may include: Registrar’s name, administrative contact, technical contact, mailing address, email, phone numbers, etc., as required by the Registry or ICANN Policies.2.2 “Domain Privacy Service” means a service that replaces public  WHOIS data with alternative contact data managed or provided by Mubdie or its partners.2.3 “Registry Policies” means the terms, operation, and appendices of each Registry or TLD that may apply to a particular domain, which are deemed to be supplementary to this Agreement and apply to the extent that they conflict with the provisions of this Agreement. 2.4 “Dispute Policy” means the applicable dispute resolution policies including but not limited  to the UDRP, URS, and any other ICANN-approved transfer or dispute policies .

Acceptance of the Terms and Registrant Representations3.1 By accepting this Agreement or by clicking on the consent box during the purchase process, you acknowledge and agree that you have read and legally bound this Agreement, and that you are authorized and lawful to enter into this Contract. Your continued use of the Services after any modification constitutes an implied acceptance of the modifications.3.2 You represent and warrant that all information you provide to us is true, complete and current, that you retain the necessary powers to register the name that is the subject of the request and that registration and use will not infringe the rights of a third party or subject you to legal prosecution.

Domain Name Choice and Obligations Relating to Third Party Rights 4.1 You are solely responsible for choosing a domain name and ensuring that it is free from infringement of intellectual property rights or any legal rights of a third party. By accepting this Agreement, you acknowledge that to the best of your knowledge and belief that the registration or intended use of the domain does not infringe the rights of a third party, and that you will not use the domain for illegal or harmful purposes.
4.2 If we receive a legal notice or enforcement request regarding your domain, we may suspend, cancel or transfer the domain in compliance with the law, the Registry Policy or the requests of law enforcement. We reserve the right to take any operational action we deem appropriate to protect Mubdie  Systems or to comply with the requirements.

Scope of Application and Reference Documentation5.1 The set of relevant documents and policies are hereby incorporated by reference in this Agreement and include, but are not limited to: the Privacy Notice, the Domain Registration Services Privacy Notice Addendum, the Acceptable Use Policy, the Dispute Policy, and the Copyright Claims Policy. Any such policies are part of this Agreement and the Registrar shall comply with them.5.2 Where there is a conflict between the provisions of this Agreement and the provisions of the particular  TLD  registries, the provisions of the  TLD Registry shall prevailFor registrations subject to that record.

Quick Executive Notes (for quick on-site access)

• Purchase interface: Next to the approval box place a clear text link “I have read and agreed to the Domain Registration Agreement” with a timestamp of approval saved in the  WHMCS Registry.
• Short Consent Text (for checkout): “I agree to Mubdie Ltd’s Domain Registration Agreement and Privacy Policy; I understand the auto-renewal terms and WHOIS policies.”
• View an immediate warning if a customer chooses a domain that is subject to eligibility restrictions or a variable price rule, with a link to the relevant registry extension.

Legal Alerts for Local Review

• I recommend that the Jurisdiction and Governance Clause in the case of Mubdie Ltd  be reviewed to determine the appropriate jurisdiction for different product pages (e.g., Managed Purchases from an Indian Provider/Registrar vs. Managed Purchases from an International Entity).
• I caution that the text of representations (such as a statement “does not infringe the rights of a third party”) should be audited to comply with consumer protection requirements and local laws in the target markets.

Fees, Payment, Renewal and Expiration Policy

Brief Introduction
This section outlines payment terms and fees, registrar billing responsibilities, auto-renewal policy, expired domain procedures, and reminders and refunds. The text is intended for inclusion as a separate chapter of Mubdie Ltd’s Domain Registration Agreement and applies to all products and services related to domain registration across mubdie.net.

1. Fees & Admission

• Payment of Fees: The Registrar is obliged to pay all fees declared at the time of order completion and as described on the product or invoice page.
• Non-Refundable: Fees paid are non-refundable unless the refund policy states otherwise in writing and express.
• Registry fees: Fees may include amounts transferred to the  Registry or third parties; you will be notified of the renewal or registration price at checkout.
• Variable pricing: Some TLDs are subject to variable pricing or premium fees, please review the TLD appendices when choosing a domain as prices may vary when you renew.

2. Payment Methods and Automatic Debit Authorization

• Accepted Payment Methods: Mubdie Ltd accepts credit/term cards, electronic payment services (e.g. PayPal), wire transfers or any other method we announce from time to time.
• Auto-renew authorization: By entering credit card or other payment method details, you authorize, but not oblige, Mubdie Ltd to automatically charge the renewal fee from the registered payment method for renewal of the Services when due, unless you notify us that you do not wish to participate in optout in accordance with the provisions of this clause.
• Updating your payment data: You are responsible for keeping your payment information up to date; failure to update it will result in a renewal failure and Mubdie Ltd  accepts no responsibility for the loss of the domain as a result of a failure to successfully renew for a payment data related reason.

3. Auto-renewal policy and withdrawal notices

• Withdrawal Period: To avoid automatic renewal, Mubdie Ltd  must receive notice of withdrawal intention at least sixteen (16) calendar days prior to the specified renewal date, or such other deadline as we expressly announce in our operational discretion.
• Alternate Notice Period: We may announce different timeouts for some TLDs or depending on registry policies; the published time limit applies for those domains.
• Renewal Period: When an opt-out request is not accepted within the time limit,Mubdie Ltd  may automatically renew the domain for one or two years depending on the registry requirements for the TLD type, at the current rate at the time of renewal.

4. Reminders, billing, and non-payment

• Reminders: Mubdie Ltd may send renewal reminders at its discretion (by email, client panel or any registered means of communication) but is not legally obligated to guarantee that you receive such reminders.
• Payment Failure: If an attempt to automatic deduction or alternative means fails to pay within the periods specified in the Renewal Notice, the Registrar may lose the validity of the domain at the expiration stages of the registry (including the Redemption Period, if applicable).
• Redemption costs: Any redemption fees or reactivation charges charged by the Registrar or Mubdie Ltd are the responsibility of the Registrar and must be paid for the restoration of the domain if applicable.

5. Expired domains and Mubdie Ltd procedures

• Placing Mubdie Ltd’s information in WHOIS: In the event that your domain expires for non-renewal,Mubdie Ltd  may include its contact details in the WHOIS Output in accordance with applicable registry policies.
•  ED Transfer: You agree that Mubdie Ltd  may, in its sole discretion, renew or transfer an expired domain to a third party as part of its Expired Domain Transfer processes, and may reserve the right to profit or deduct operational costs when doing so.
• Loss of Rights: Failure to renew the domain immediately results in the loss of rights in respect thereof in accordance with the relevant registry procedures; Mubdie Ltd is not obligated to provide compensatory reactions for any damage thereafter.

6. Accounting Invoices and Records

• Invoicing: Mubdie Ltd issues  purchase invoices and renews the information you provide during registration; the Registrar is required to keep copies of the necessary tax records and documents in their country.
• Authenticity of the e-invoice: The invoice or electronic notice sent to the registrar is sufficient evidence of the obligation to pay the fee unless otherwise required by legally acceptable proof.
• Invoice Review: If invoices differ or correct, Mubdie Ltd  must be notified within thirty (30) days from the date of issue; after this period the invoice is considered acceptable unless otherwise proved.

7. Special Prices, Discounts & Promotions

• Temporary Offers: Mubdie Ltd may offer promotions or special quotes to service providers or specific time periods, the terms of each offer apply and are displayed on the offer page at the time of purchase.
• Upgrade and partial payment: When you change the registration or upgrade period from one tier to another, difference fees or partial refunds may apply in accordance with the Account and Debit Policy in the Control Panel.
• No Warranty for the Future: Promotions are offered only on their own terms of time and do not oblige Mubdie Ltd to repeat them or maintain the same prices upon renewal.

8. Refund of Payments and Returns

• General Refund Terms:  Returns are only granted in accordance with an explicit written policy. In the event  that Mubdie Ltd  refuses to register a domain or delete the order within a reasonable period of time (e.g. thirty to 30 days of payment) in accordance with the Rejection Policy, the registrant will be refunded the amount paid only if the refund policy so provides.
• Exceptional Refunds: Refunds that may be granted by law or as a result of dispute resolution, and tax rights or third-party fees may be deducted prior to any refund.
• Third Party Damages: Any amounts made to a  Registry or a third-party provider are normally not under the control of Mubdie Ltd and may not be refundable on the terms of such parties.

9. Liability for Credit Information and Fraud

• Registrar’s Liability: The Registrar is solely responsible for any use or misuse of credit cards or a payment method registered in their account. Any unauthorized use must be immediately reported to Mubdie Ltd.
• Verification and fraud:  Mubdie Ltd  reserves the right to take security verification measures or reject suspicious transactions, and may delay or suspend the activation of the Service until the verification procedures are completed.
• Cashback for proven fraud: If it is proven by a judicial or authorised investigation that a payment was made as a result of fraud and was not known to the Registrar, the Provider’s Reverse Payment Policies shall apply in accordance with local laws.

10. Notices for TLDs and Registry Policies Compliance

• Application of TLD extensions: Some TLDs require payment terms, special renewal or redemption policies (such as Premium pricing policies, non-transfer periods, or eligibility verification requirements). Links to the appendices or summaries thereof are displayed to the Registrar at the completion of the purchase and become part of your obligations with respect to that domain.
• Conflict of Terms: Where there is a conflict between the provisions of this Article and the Registry Terms of a particular TLD, the Registry Terms shall prevail for that domain.

11. Operational Recommendations for Integration into Mubdie.net and WHMCS Interface

• Consent box: On the checkout page, place a clear consent text: “I agree to Mubdie Ltd’s Domain Registration Agreement and Privacy Policy. I understand that automatic renewal will take place unless I report the withdrawal 16 days in advance.”
• Client Options: Add two clear options in the client panel: (a) turn on/off auto-renewal, and (b) turn on/off the WHOIS  privacy service.Attach a brief explanation of the effects of each option.
• Multi-channel notifications: Send reminders via email and account panel 30, 14, and 3 days before the renewal date (alert notifications; renewal is regulated).
• Billing records: Keep a copy of the agreement text and the version accepted by the customer at each payment to protect evidence of approval.

12. Suggested texts for practical use

• Checkout consent line (Arabic): “I agree to Mubdie Ltd’s Domain Registration Agreement and Privacy Policy. I understand that the automatic renewal will be implemented unless I report the withdrawal 16 days in advance.”
• سطر موافقة للـ checkout (إنجليزي): “I agree to the Mubdie Ltd Domain Registration Agreement and Privacy Policy. I understand autorenewal will occur unless I optout at least 16 days prior to renewal.”
• Caution when selecting a Private or Premium domain: “Caution: This domain is subject to price conditions or transfer restrictions specified by the registry — please check the linked extension before completion.”

13. Legal Notes and Areas Warranting a Local Lawyer Review

• Limitation of Liability and Monetary Limitations: Review the limitations of liability and financial limitations set out in other terms of the Agreement to comply with the requirements of local laws in Mubdie Ltd’s target markets (e.g., Saudi Arabia, India, United States).
• Handling Local Payments: If operations managed across local entities (Indian Registrar/US Entity are differentiated), it is advisable to specify separate price and renewal notices depending on the operating entity to avoid jurisdictional conflicts and tax compliance.
• Local consumer requirements: Make sure that the text of your refund policy and discounts comply with local consumer laws that may require a refund in certain cases despite the “non-refundable” clause.

Agreement Term, Agreement Amendments, Account Security and Termination

Introduction
This article explains the terms and  duration of the Agreement, Mubdie Ltd’s authority to amend the terms of the Agreement and Services, the rules for account management and login security, termination procedures and their consequences, and related notice procedures. This article complements the provisions of the General Agreement and applies to all registrations of domains and linked services via mubdie.net.

1. Term and Extension 1.1 The term of the Agreement is directly related to the registration period of each domain name registered or reserved through Mubdie Ltd. The terms of this Agreement shall remain in effect for the duration of each Domain’s registration, and shall automatically extend for the duration of any renewal executed in accordance with the provisions of this Agreement. 1.2 If Registrar extends the Registration Term or purchases additional Periods, the provisions of this Agreement shall be extended successively to cover the Extension Period, and in the event that the Domain is transferred to another Registrar, the provisions of this Agreement shall terminate with respect to that Domain and the relationship shall subsequently be subject to such terms as may be established by the new Registrar.
2. Amendments to the Agreement and Services2.1 Right to Modification:Mubdie Ltd may, as it deems appropriate, revise or amend this Agreement or change the description or level of the services provided. Amendments become effective immediately upon posting on the mubdie.net website or communicating to the Registrar in accordance with the notification mechanism set forth in this Agreement.2.2 Acceptance of Modifications: Your continued use of the Services after any modification is posted is expressly and effective acceptance of the modification. If you do not agree to a major modification, you may terminate the Agreement under the termination mechanism set forth herein subject to redemption provisions (if any). 2.3 Notices of Change: We will use our reasoning to notify Registrar of material amendments prior to their effective date (such as a change of jurisdiction, material renewal rates, or amendments affecting Registrar’s obligations), but failure of Registrar to receive notice for a reason independent of Mubdie Ltd does not define acceptance or preclude the amendment from taking effect.
3. Scope of Change to Services and Compliance with Registry Policies 3.1 TLD Registry Compliance: Any change in services or procedures that arises as a result of updates to TLD Registrypolicies, ICANN requirements, or applicable legislation shall be effective automatically when effective and shall apply to relevant registrations even if it conflicts with the provisions of this Agreement.3.2 Notice of Extensions: When new operational or pricing requirements are introduced for a domain, we display or brief about the appendices on the product interface and consider them part of the registrar’s obligations to the extent they apply to the domain.
4. Modification of Account Data and How to Implement it 4.1 Modification Authority: To change any account information (including: administrative email address, mailing address, billing data, payment details), the registrar must log in to the account panel and use the custom modification procedures.
   2 Proof of Identity: We reserve the right to request reasonable proof of identity or additional authentication before accepting certain material changes (such as transfer of ownership or change of registrar’s name).4.3 Responsibility for Update: It is the responsibility of Registrar to maintain the accuracy of the Registration Data and to update it within seven (7) days of any change. Any failure to do so is a material breach of this Agreement.
5. Account Security and Login Safekeeping5.1 Confidentiality of Login Data: It is the Registrar’s responsibility to maintain the confidentiality of the Account ID, Password and other means of authentication, and not to share them with any third party. 5.2 Unauthorized Use: Mubdie Ltd is not liable for any damages resulting from unauthorized use of the Registrar’s Account if this is the result of the Registrar’s disclosure of login information or failure to take reasonable security measures.5.3 Suspicious Activity Monitoring: We reserve the right to monitor unusual activity and take temporary measures (disabling, suspension, account freeze) to prevent fraud or abuse, and we may require you to provide proof of identification before reactivating the Services.
6. Two-factor authentication and account recovery6.1 Authentication encouragement: Registrants are encouraged to enable two-factor authentication (2FA) to increase account protection. 6.2 Recovery procedures: If you lose your authentication method or password, you must follow the official recovery procedures via your account panel or Mubdie Ltd support, which may require government identification or other documents before issuing a reset or regain of access.
7. Learning from Notices and Official Communication Methods7.1 Notification Methods: Official notifications are sent to: (a) the email registered in your account, (b) messages within the Client Dashboard, or (c) your registered address if necessary a notice by mail. All notices sent by such means are valid and legally enforceable.7.2 Responsibility for updating the means of communication: It is the responsibility of the Registrar to receive and maintain the notices. If the registered means of communication fail to deliver for any reason related to you, the notification shall be deemed to have been communicated to you on the date it was sent according to the records Our dispatch.
8. Temporary Suspension and Final Suspension of Data and Service8.1 Reasons for Suspension:Mubdie Ltd may suspend, suspend or suspend any domain or service temporarily or permanently for reasons including, but not limited to: compliance with a court order or law enforcement request, violation of the terms of this Agreement or Registry Policies, security risks, or fraudulent activity. 8.2 Post-Suspension Procedures:  When a service is suspended for a remedial reason (such as remedial breaches), we will notify the registrar and give them a reasonable opportunity to remedy unless legal or operational requirements prevent it. If the suspension is the result of a serious breach or injunction, we shall only reactivate by decision we deem appropriate or upon a court order. 8.3 No liability for losses: Mubdie Ltd  shall not be liable for any direct or indirect damages or losses resulting from any suspension or suspension necessitated by the reasons set forth in this Agreement or the Registry Policies.
9. Termination and its impact on domains and services9.1 Your right to termination: You may terminate this Agreement by terminating your domain registration or by notifying Mubdie Ltd in accordance with the notice mechanisms set out in the Agreement. Termination of the Agreement does not justify a refund of a fee unless an express refund policy states otherwise. 9.2 Mubdie Ltd’s Right to Termination: We may terminate the Agreement immediately or upon notice if: (a) you have committed a material breach of its Terms and you have not remedied it within a reasonable time (usually thirty to 30 days unless otherwise specified), (b) there is illegal activity or poses a risk to the security or stability of systems, or (c) you have received a court or government order that requires action.9.3 Effect of Termination: Upon termination of the Agreement or cancellation of a domain registration, the rights associated with the domain are forfeited under the Registry Frameworks, and the Domains may be offered for sale or granted to a third party in accordance with the Registry Rules. Indemnification Terms, Limitations Liability, and non-waiver are effective after termination.
10. Record keeping, backups and data retention policy10.1 Recording consents: Mubdie Ltd keeps a record of the consents you have made (e.g. agreeing to the terms, turning on auto-renewal) with a timestamp for each consent. 10.2 Backups: We maintain operational backups of system data in accordance with our internal backup policies, but Mubdie Ltd does not guarantee the restoration of third-party site data or content or any configurations subject to change outside of our system.10.3 Retention Period: We may retain records of transactions and correspondence for certain periods of time for compliance, accounting, or litigation purposes; local legal retention requirements apply where applicable.
11. Legal Effect in the Event of a Change of Operating Entity or Transfer of Registration Activity11.1 Transfer of Rights and Obligations: In the event of a change in Mubdie Ltd’s operating structures or transfer of the Domain Registration Activity to another entity, the rights and obligations relating to this Agreement may be transferred to the transferee with prior notice as required by applicable laws. Registrar’s continued use of the Service after notification shall be deemed to be an acceptance of such transfer.11.2 Notify Registrar: We will inform Registrar of any material information about the new entity (name, country of incorporation, and any implications for Terms of Use or Payment Methods).
12. Enforcement provisions and notes for local legal review12.1 Customizable texts: If Mubdie Ltd wishes to apply a different compensation ceiling or notice period for specific markets (e.g. Saudi Arabia or India), or to include provisions that are compatible with local consumer protection rules, local extensions may be included on the product page that become part of the agreement applicable to that purchase.12.2 Lawyer Review Recommendation: I recommend that you review the texts of termination provisions, limitation of liability, and notice periods related to automatic renewal before a competent attorney in each target market (especially Saudi Arabia, India, and the United States) to ensure compliance with local consumer protection and trade laws.
13. Practical texts for use in the Mubdie.net interface

• The Notice of Amendment at the time of publication reads: “Amendments to the Terms of Service were posted on [Date of Publication]. By continuing to use the Service after this date, you accept the modifications.”
• Customer pause notice text (example): “Domain service has been temporarily suspended for security or compliance reasons. Please check your dashboard or contact support to resume service.”
• Request a refund/termination button text (if necessary): “I want to terminate domain registration — acknowledge that fees paid may not be refundable as per Mubdie Ltd’s policy.”

 Data Collection, WHOIS, Privacy Policy and Domain Privacy Service

Introduction 1.1 This section explains how Mubdie Ltd  collects registrar data (including  WHOIS registration data), the legal reasons for processing it, how it is displayed or protected, the registrar’s choices regarding the domain privacy service and legal requests for access to the data. The provision applies to all domain registrations and associated services provided via mubdie.net.

2.1 “Registration Information”, “Registration Information” or “WHOIS” means: full name or entity name, mailing address, email, telephone numbers, administrative and technical contacts, and other details requested by the Registry/ICANN or the relevant registries of each TLD.2.2 “Processing” means any processing of personal data including collection, storage, use, disclosure, modification, deletion and transfer.2.3 “”Domain Privacy”  means the replacement of public  WHOIS data with intermediate or alternative contact data managed by Mubdie Ltd or a contracted provider.

Legal Basis and Purposes 3.1 Basis of Processing: We collect and process registration data as contractually requested by registries and/or ICANN and to perform our contract with you regarding domain registration, as well as to comply with legal and operational obligations and to protect network security. 3.2 Specific Purposes: (a) completion of domain registration/transfer/renewal; (b) compliance with registry/ICANN requirements(c) Administrative and technical communication and billing; (d) Enforcement and judicial compliance requests; (e) Fraud and abuse prevention; (f) Support for privacy services, if selected; and (g) Statistics and operational improvement in accordance with the Privacy Notice.

Common Disclosures and WHOIS Visibility 4.1 When Your Data Is Disclosed: Registration Data may be provided to registries to ICANN, public WHOIS  data storekeepers, name-checking service providers, or third parties in accordance with our contracts, registry requirements, or law. 4.2 Nature of Publication: Unless legal exceptions apply (e.g., GDPR rules for EU natural persons or local texts prohibiting this), the Data WHOIS may be publicly accessible via WHOIS rules or RDAP services.4.3 Important Note: If you want greater privacy, use the “Domain Privacy Service” option where the following paragraph explains the scope of Mubdie Ltd’s responsibility and the limits of the service.

 Domain Privacy Service 5.1 Service Provision: When you choose the Domain Privacy Service, we offer the WHOIS (Private WHOIS Contact)  alternative in the public output instead of your original data, while we keep an original copy of your data in Mubdie Ltd’s records and the provider partner where applicable. 5.2 Service Limitations: The Privacy Service does not remove your legal liability for the domain; you remain legally responsible for the content and use and are obligated to keep it  up to date in records Mubdie Ltd.5.3 Exceptional Disclosures: We or the Privacy Provider may disclose original data (a) for court orders or legal subpoenas; (b) to comply with registry/ICANN obligations; (c) when claiming third-party rights (a trademark or copyright dispute) that necessitates disclosure; and (d) if we suspect misuse or criminal activity. 5.4 Posting and Mail Limits: Privacy is not a one-stop mail forwarding service; we may review or filter correspondence or refuse to send junk messages. If a correspondence addresses a substantive legal matter, we will direct it in accordance with the operating policy.

Compliance with data protection laws (GDPR and international restrictions) 6.1 Enforcement of protection laws: If a special legal regime (e.g. GDPR applies to data of natural persons within the European Union), we will apply the processing requirements, access rights, right to rectification, right to erasure and other rights in accordance with the Privacy Notice and its Annexes. Cross-border data transfers: You may transfer your data to operators or registries located outside your country; through our procedure we impose appropriate safeguards (standard transfer agreements or approved legal mechanisms) where required by law.
6.3 Note for GCC and Saudi Markets: We recommend that you include a Local Compliance Note in the Privacy Notice if Saudi/Local Regulations require additional requirements for data processing or transfer.

7.1 Official  Enquiries: Upon receipt of a valid legal request (court order, government subpoena), we may disclose your data as required by law. We will try, where possible and the law allows, to notify you of the existence of a request unless the law restricts disclosure.7.2 Requests from private parties: If you receive a request from a third party for registered data (trademark complainant, civil entity), we will review the request legally and require legal proof or a judicial document before disclosure.7.3 Fees and Procedures: We may charge administrative fees for the preparation of files in response to non-routine formal requests or for data transfers as per company policy; the fees are clearly displayed to the requesting entity prior to implementation.

8.1 Basic retention period: We retain registration data for as long as the domain registration continues and for compliance and accounting purposes for a reasonable period thereafter in accordance with the requirements of the registry and local law. 8.2 Deletion and correction: You can request that your data be corrected or updated via the dashboard; deletion requests are restricted if the data is necessary for legal reasons or for the performance of the contract (e.g. dispute claims period).8.3 Backup Records: We maintain operational backups but may maintain normal records of approvals and transactions for longer periods for litigation and compliance purposes.

Registrar Rights and Means of Enforcement 9.1 Access and Modification: You can access and correct your data via the Account Panel or by requesting documented support; we will respond to requests for amendment within reasonable time frames compliant with applicable laws. 9.2 Objection and Blocking: If you believe that our processing is illegal, you may lodge a complaint internally or with the relevant data protection authority; we will introduce an internal complaints mechanism and respect the decisions of the relevant authorities. Help you comply with requests: When you transfer ownership or change a record, we require additional authentication procedures to ensure the integrity of the change (e.g., administrative email verification or risk identification).

10.1 Principles of Limitation of Purpose: We process only the minimum amount of data necessary to achieve the intended purpose (data minimization).10.2 Technical and organizational measures: We implement appropriate security measures (encryption when in transit, access control, internal access restrictions, periodic reviews).10.3 Notification of data breach: In the event of serious breaches of personal data, we will take notice procedures in accordance with applicable legal requirements and inform the affected and relevant authorities where appropriate.

Links to Third-Party Registries and Licensing Appendices 11.1 Contracting Records: We display links to each TLD’s policy appendices on the purchase interface; the texts of these appendices are part of the registrar’s obligations when choosing a domain.
11.2 Registrar’s Information: When purchasing a domain whose restrictions are subject to a specific country or registry (e.g. .SA or .SA). IN), we display the eligibility conditions and privacy requirements or certificates required prior to completing your purchase.

Communication with Mubdie Ltd and Privacy Requests 12.1 Contact: For access, correction requests or data-related queries, contact the privacy@mubdie.net or the in-account support panel. 12.2 Request Template: We recommend that you include an internal online form in the Client Panel to facilitate and follow up on access and modification requests within  the WHMCS.

13.1 Corporate Data/Entities Alerted: When registering a domain as a business entity, the entity’s information may be publicly displayed and you are required to have legal authorization to publish it. 13.2 Sensitive Personal Data: Mubdie Ltd  does not collect sensitive data (such as health or political affiliation) as part of standard registration forms; if the context warrants, additional safeguards apply and explicit legal consent or support must be obtained.13.3 Foreign Enforcement Requests: We will review requests with legal due diligence and may request a judicial decision or legal basis before disclosing information associated with a registrar in another jurisdiction.

Practical Texts for Use in the Mubdie.net and WHMCS 14.1 Client Summary (abbreviation displayed during purchase): “We collect required registration data from the Registry and ICANN.  WHOIS  data may be publicly displayed; choose the domain privacy service to hide your public data. For more details, see the Privacy Notice.” 14.2  Checkbox Text for Consent (Arabic): “I consent to the collection and use of registration data in accordance with the Mubdie Ltd  Agreement and Privacy Notice. I understand that WHOIS  data may be publicly displayed and that privacy service is available upon request.” 14.3 Detailed Privacy Notice: Include a clear link to the Privacy Notice on the checkout page and the Domain Details page; keep a short, time-stamped version in the Order Log (WHMCS).

Compliance and Operational Recommendations for Mubdie Ltd Creator 15.1 Insert a Local Addendum: Include a special addendum for sensitive markets (Saudi Arabia, UAE, India) that includes local requirements for data transfer/keeping/disclosure.15.2 Documented disclosure policy: Develop a documented internal process for handling official and third-party rights requests (application templates, compliance officer, response time).15.3 Automatic Privacy Check: Upon completion of the purchase, suggest an automated check that suggests to the registrar to enable the privacy service by type of domain and country Risk of publication.

Disputes, ICANN  Policies, Change of Registrar and Transfer of Ownership

Introduction
This article outlines the rules for resolving disputes related to domain names, the procedures for transferring ownership between registrars (Change of Registrant / IRTP), the Registrar’s compliance with ICANN policies and procedures (Registry), and Mubdie Ltd’s response to third-party rights enforcement requests. This article complements the provisions of the Domain Registration Agreement and forms a mandatory part thereof.

1. Registrar Dispute Obligations 1.1 Registrar Representation: By accepting this Agreement, you represent and warrant that you have the legal right to register and use a domain name and that registration and use does not infringe the rights of any third party, including intellectual property rights. 2.1 Collaboration with Proceedings: You agree to cooperate fully with any dispute proceeding or legal investigation relating to the domain name, including by providing documents, identity information, or written authorization upon request by Mubdie Ltd, the Registry, dispute service providers, or the courts. Competent.
2. ICANN Policies and Registry Appendices 2.1 Compliance with ICANN Policies: Domain name registrations are subject to all ICANN-approved policies including, but not limited to: UDRP (Uniform Domain-Name Dispute-Resolution Policy), URS (Uniform Rapid Suspension), IRTP (Inter-Registrar Transfer Policy) and any policy subsequently approved by ICANN.2.2  Registry Policy Primacy: Where there is a conflict between the provisions of this Agreement and the terms of the relevant TLD registry, the provisions of the TLD registry shall prevail for the domains subject to that registry.
3. Common Dispute Procedures (UDRP/URS/Other)3.1 Notice of Claim: If a third party files a complaint on the basis of infringement of a trademark or other right under the UDRP or any Registry Policy, Mubdie Ltd will inform the Registrar in accordance with the approved notification mechanisms and commit to following the procedures of the Registry or the competent Dispute Provider.3.2 Temporary Hold/Freezing/Transfer: A dispute resolution body or the Registry may order the seizure, suspension, transfer, or cancellation of the domain temporarily or permanently. Registrar agrees to promptly comply with any effective decision of an authorized dispute party or injunction. 3.3 Defense Costs: You Registrar is responsible for the costs of defending any claims or claims relating to the registration or use of the Domain, including attorneys’ fees and fees of competent authorities unless otherwise provided by law or judicial decision.
4. 1 Transfer Requirements: Any request to change the registrar (Registrant change) or transfer of the domain to another registrar is subject to the authentication procedures set forth in the ICANN and IRTP policies and in the respective registry policies.
   4.2 Proof of authorization: The parties (the transferring party and the receiving party) are obliged to provide electronic documents or approvals proving the authorization of the change or transfer; we may require additional documentation (identity documents, signed authorization) as needed to protect against unauthorized transfer. 4.3 Prohibition and Limitation Period: For the systems of some registries, transfer restrictions may apply (e.g. 60 days after registration or change of registrar); the rules of the respective registry apply to any transfer.4.4 Role of Mubdie Ltd As an authorized representative: We may act as an authorized agent to administer the approval process as per the authorization formula available to us, reserving the right to refuse to execute the transfer if the request conflicts with security requirements, laws, or an ongoing dispute.
5. Third-Party Rights Claims and Disclosure Procedures5.1 Receiving Claims: Upon receipt of a reasonable third-party claim for trademark or other right infringement, we review the claim and may require you to provide clarification or proof. If you do not provide an acceptable settlement or response, we may disclose registration data or take operational action in accordance with the law and registry policies.5.2 Disclosure Procedures: Mubdie Ltd You reserve the right to disclose registration data to requesting parties provided that there is a legal justification (injunction, subpoena, enforcement request) or if Registry or ICANN policies require it. We will attempt to notify you where possible unless the notification is prohibited by law.
6. Operational Precautions Against Disruptive Registrars and Abusive Practices 6.1 Suspension and Suspension: We reserve the right to suspend or cancel registrations when the domain is found to have been used for fraudulent, harmful, or persecutive activities or repeated breach of the terms of this Agreement or the Acceptable Use Policy. 6.2 Notice and Opportunities Policy: In remedial cases, we will notify the Registrar and give them a reasonable period to rectify the situation prior to final cancellation, unless legal requirements or operational risks prevent it. 6.3 Maintain Dispute Records: We keep records of decisions, correspondence, and approvals related to any dispute or transfer of a reasonable period of time as evidence of compliance and compliance with legal requirements.
7. Indemnification and Disclaimer in Dispute Matters 7.1 Obligation to Indemnify: You agree to indemnify and defend Mubdie Ltd and its parent companies, subsidiaries, employees and agents against any claim, indemnity, loss or expense (including reasonable attorneys’ fees) arising out of: (a) an allegation of infringement of the rights of a third party; (b) your breach of this Agreement; or (c) your use or operation of the Domain.7.2 Limitation of Liability: Our limitations and liabilities are governed by the general provisions of this Agreement, including limitations of liability and indemnification of the parties, as may be provided by applicable jurisdictional laws.
8. Internal procedures for handling IP rights complaints8.1 Receiving Infringement Reports: We have prepared a copyright/trademark complaint form within the support page for formal receipt of reports; the report should include: a description of the claim, the significance of the claimant, and legal identification documents. 8.2 Operational Review: Each complaint requires an initial internal review within seven (7) business days; scope may be suspended based on the balance of legal risks and the operation of the Mubdie Ltd. system.8.3 Judicial option: If necessary, we tend to refer the claim to the UDRP/URS or comply with a final injunction, leaving it to the competent courts to decide what may be beyond the jurisdiction of the administrative proceedings.
9. Our Relationships with Registries and Dispute Resolution Providers9.1 Enforcement Obligation: We are committed to full technical and procedural cooperation with the Registry, Authorized Dispute Service Providers, and ICANN as required by contract, rules, or law. 9.2 Third Notices: The Registry or Dispute Provider may impose operational sanctions (e.g., suspension or transfer) directly at the registry level without the need for Mubdie Ltd’s approval, and the responsibility for compliance remains with the Registrar.
10. Practical texts for use in the interface, client panel, and WHMCS10.1 Viewable Brief Summary (upon registration/transfer of ownership): “Your data may be disclosed to third parties in accordance with Registry and ICANN policies. Any dispute over domain registration may be referred to approved dispute resolution mechanisms or to the courts.” 10.2 Checkbox for Consent (Arabic): “I acknowledge that I have read the Dispute Policy and that I agree that my registration is subject to ICANN’s policies and approved dispute resolution procedures.” 10.3 Notice when a transfer is initiated: “The request for a change of registrar has been received; the request is subject to an approval period and transfer restrictions may apply depending on the Registry Policies (e.g., 60-day block).”
11. Statutory Notes and Areas Requiring Local Legal Review11.1 Different International Laws: Enforcement and Objection Mechanisms may vary from jurisdiction to jurisdiction; it is advisable to review dispute and jurisdiction provisions with local counsel in each major market (especially Saudi Arabia, India, and the United States).11.2 Consumer Protection Rules: Some consumer protection laws may restrict termination or indemnification clauses in certain cases; see provisions on limitation of liability and indemnity depending on the state.

Executive Conclusion
 Mubdie Ltd establishes clear and balanced procedures to protect the stability of records and the rights of parties, while retaining the registrar’s rights to defend and object. We will subsequently provide you with automated message forms in Arabic and English for notification of the initiation of a dispute, suspension of a domain, and initiation/completion of a transfer of ownership for inclusion in the WHMCS and the client panel if desired.

Warranties, Disclaimers, Limitations of Liability, Indemnification and Force Majeure

Introduction
This part specifies the warranties (not) provided by Mubdie Ltd, legal disclaimers, limits and limitations of financial liability, the obligation to indemnify, and force majeure actions. The text is drafted in the name of Mubdie Ltd and is configured for transcription into Word as a separate chapter within the Domain Registration Agreement.

1. Guarantees and Confessions

• Absence of Express and Implied Warranties: Except as expressly provided in this Agreement, all Services are provided “as is” and “as available” without any express or implied warranties, including any implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
• No Guarantee of Results: Mubdie Ltd does not guarantee that the Services will meet your requirements or that they will be available uninterrupted, error-free, or that defects will be corrected.
• Limited Reliance on Information: Any technical, commercial or legal materials or advice we provide are not defined as performance undertakings and the Registrar has a duty of legal or technical verification prior to approval.

2. Disclaimer of Damages and Excluded Scope

• Exclusion of Indirect Damages: Mubdie Ltd shall not be liable for any indirect, consequential or incidental damages, loss of profits, loss of data or loss of goodwill, howsoever caused, even if advised of the possibility of their occurrence.
• Limitation of Partial Liability: In respect of any direct claims giving rise to a right to indemnification, Mubdie Ltd’s liability does not exceed, in the aggregate, the sum of the amounts paid by you during the twelve (12) months preceding the claim for the service in dispute, unless expressly provided in this Agreement for another limit.
• Appropriate Exclusions:  The exclusion or limitation limits do not apply to claims of intentional gross negligence, fraud, or any legal obligation that cannot be waived in accordance with applicable law.

3. Indemnity and Registrar’s Obligations

• Obligation to Indemnify: You agree to indemnify, defend and hold harmless Mubdie Ltd and its affiliates, directors, employees and agents from any claims, losses, liabilities or expenses (including reasonable attorneys’ fees) arising from: (a) your breach of this Agreement; (b) allegations that registration, use, or ownership of the domain infringes the rights of a third party; or (c) any content or activity carried out by the Registered Domain.
• Defence and Settlement Department: Mubdie Ltd shall have the right to administer the defence or accept the settlement of any claim in its own manner; the Registrar may not agree to any settlement binding Mubdie Ltd without its prior written consent.
• Financial obligations related to registry/court decisions: If a registry judgment or court decision affects Mubdie Ltd’s right to impose additional costs or penalties, the obligation to pay such costs remains with the registrar unless otherwise acknowledged.

4. Time limits and procedures for filing a lawsuit

• Expiration of Right to Claim: Any contractual or tort claim relating to this Agreement must be filed within twelve (12) months from the date of the alleged incident, otherwise the right to claim shall be deemed to be waived, unless otherwise provided by applicable law.
• Prior Procedures: Prior to filing any lawsuit, the claimant party must notify Mubdie Ltd in writing detailing the principles of the claim and give it a reasonable period (usually thirty 30 days) to attempt a practical settlement or remedy if possible.

5. Force Majeure

• Definition: The affected party is exempt from liability for the delay or failure to perform any obligation resulting from circumstances beyond its reasonable control and available activity such as: natural disasters, wars, civil disturbances, government business, large-scale communications or internet interruptions, complex cyberattacks, failures of third-party core systems, or operational restrictions imposed from records.
• Notification and mitigation procedures: The affected party shall notify the other party in writing as soon as it becomes aware of the event, explain the extent of the impact of the event and its expected duration, and take reasonable steps to mitigate the effects of the event and resume performance as soon as possible.
• Right to Termination: If the force majeure event persists for a reasonable period of time (e.g., 90 days) and cannot be remedied, the unaffected party has the right to terminate the affected agreement or services without compensatory liability.

6. Practical Implementation Items and Local Market Suitability

• Allocation of Liability Ceilings: I propose to include an addendum that makes it easier to assign the liability ceiling to the local market (e.g., the standard $500 limit in some US contracts) so that the value of the cap is determined by the operating entity and the client’s market.
• UI Alert: Suggest short text displayed at purchase: “Legal Alert: Services are provided as is; refer to the warranty clauses and limitations of liability in the Mubdie Ltd Agreement.” The customer acceptance record with a timestamp in WHMCS.
• Note for Local Legal Review: I recommend reviewing the Limitation of Liability and Indemnity clauses in relation to the consumer protection laws of Saudi Arabia, India, and the United States to ensure that they do not conflict with mandatory rules that may invalidate or limit certain exclusions or ceilings.

Suggested texts for practical use

• Brief Paragraph of the Interface (Arabic): “Mubdie Ltd’s services are provided in accordance with the terms provided; there are no express or implied warranties except as expressly stated. The limits of liability are as set forth in the full agreement.”
• فقرة موجزة للواجهة (إنجليزي): “Services are provided ‘asis’ and ‘asavailable’. See full agreement for disclaimers, liability limits and indemnity obligations.”

Conclusion and Final Recommendations

• This article is designed to balance Mubdie Ltd ‘s operational protection with elements of user fairness. I advise setting an appropriate liability ceiling for the operating entity and including a local addendum that allows for adjustment of caps or exceptions for markets with legal restrictions (Saudi Arabia, EU, India). I also recommend the inclusion of internal procedures (SOP) for handling compensation claims and managing infringement complaints to reduce the risk of lawsuits.

Denial Rights, Special Registry Terms, and TLD Appendices

(Customized legal text as Mubdie Ltd — Detailed, stickable to Word, with time references set to 2025, including operational notes and incorporation notes into WHMCS)

Introduction
This article outlines the scope  of Mubdie Ltd’s authority to deny, cancel, or suspend domain registrations, registry-specific requirements that may apply to specific domains, and the procedures for listing TLD Annexes as supplementary documents applicable to the relevant domains. This article enables Mubdie Ltd to ensure compliance with its contracting obligations with registries and ICANN, and to protect the operational structure of the company and customers.

1. Mubdie Ltd’s right to refuse and accept

• Discretion to refuse:  Mubdie Ltd  reserves the right to refuse an application for registration, reservation, or renewal of any domain name at any time and for a period of up to thirty (30) days from the date of receipt of payment without giving a detailed reason;
• Reasons for Denial: Acceptable examples of denial include but are not limited to: failure to meet the eligibility requirements for a TLD, doubts regarding the accuracy of registration data, security or fraud risks, or conflict with registry/ICANN policies.
• Notice and documentation: When an application is rejected, we notify the Registrar with an official letter explaining the reason for the rejection as much as possible, and we keep a chronological record of cases in our system (WHMCS).

2. Right of Registry and Mandatory TLD Extensions

• Registry Policy Precedence: The provisions of any Registryspecific Annex or Registry Policy shall prevail over the provisions of this Agreement to the extent that registrations within that TLD  relate.Posting attachment links on the product page and keeping a record of approval when purchasing is an operational duty.
• Addendum as part of the contract: The appendices for each TLD  become part of the registration agreement with the registrar once they select the domain or appear on the payment page.

3. Components of TLD Extensions (Annex structure — Standard for Each Annex)

• Title and definition:  The name of theTLD, the name of the registry  operator, and the link to the official registry policy.
• Eligibility Requirements: Eligibility Requirements (Nexus/Residency/Profession/Age).
• Transfer and renewal restrictions: Prohibition periods (e.g., 60 days), transfer restrictions after a change of registrar or change of registered registrar.
• Pricing and Special Fees: Premium names, refund fees, billing mechanisms.
• Dispute and Compliance Policies: Applicable dispute resolution mechanisms (UDRP/URS/Local Appendices) and any litigation requirements.
• Privacy Policies and WHOIS: Rules for public data and use of privacy services.
• Operating Procedures: Practical steps for rejection, suspension, reactivation, or transfer of ownership, with sample messages to the customer and stakeholders.
• Third-Party Beneficiary Status: Whether the Registry is a  third-party beneficiary of the Agreement.

4. Practical examples of common supplements (Brief template for .COM/. IN/ccTLDs with Eligibility Requirements)

• .COM/  Verisign Terms (Form): The Registrar adheres to the Verisign Registry Terms which allow it to suspend or transfer domains to protect the stability of the Registry; Premium price restrictions may apply; Mubdie displays the Verisign extension link upon purchase.
• . IN (India): Appendices include a declaration of commitment that the content does not violate Indian laws; the Eligibility Addendum and the Dispute Policy Summary are displayed. IN before completing the payment.
• Sensitive ccTLDs  (e.g. .SA/. AE/.UK/.CA): Requirements for proof of eligibility or local presence are listed in clear font on the purchase interface with a document upload field if required.

5. Detailed Rejection and Suspension Procedures (Operational SOP)

• Initial verification: Automatic WHOIS fact-checking, security forms, and ban lists; doubts are raised to the compliance unit.
• Temporary suspension: If there is an immediate risk (spoofing, hacking, fraudulent activity), the case declares a temporary suspension with an administrative notice to the client and a response time usually not exceeding 7 business days if remedyable.
• Final Cancellation: If the period expires without reform or a judicial/administrative order is issued that requires action, the cancellation shall proceed in accordance with the procedures of the registry.
• Record of Actions: Each step is documented and preserved (reason for suspension, correspondence, technical evidence, termination decision).

6. Usable texts in the interface and client panel

• Pre-payment alert: “This domain is subject to the [Record Name] Registry Terms. Read the appendix before completion.”
• Checkbox for approval: “I acknowledge that I have read the [TLD’s]  Registry Appendices and agree to be part of the Registration Agreement.”
• Automatic comment message: “Your domain has been temporarily suspended due to a security/legal concern, please review the support notice within your account within 7 days.”

7. Split appendices into separate messages when needed

• When there are a large number of extensions (dozens of  TLDs) I suggest sending each extension in a separate message titled: “TLD Extension — [. TLD]” to become independently reviewable and publishable. For each older supplement: the full legal supplement text, a 2–3 line practical summary for the checkout, and a  WHMCS snippet for the user to view.

8. Requirements for Ready-to-Publish Model TLD Extension Content Requirements (Quick Template)

• Title of the Appendix: “Annex to the Register of . TLD — [Registry Name]”
• Statement of Effectiveness: “The following [Registry Name] Registry Terms shall apply to any registrations in . TLD”
• Key Texts: Eligibility Provisions, Restrictions, Special Fees, Dispute Procedures, Transfers of Ownership, References to Official Policies.
• Approval Line for Checkout (Arabic): “I agree to a log extension . TLD and Mubdie Ltd Terms.”
• Note for local legal review if necessary.

9. Compliance notes and customization options for the Saudi and GCC market

• Need for Local Annexes: Some ccTLDs require local scripts or documents  (e.g., .SA requires designated local entities or local agents); prepare a Special Marketplace Annex (Saudi Annex) that includes proof requirements, verification mechanism, and tax/fee rules/fees if applicable.
• Language of the Supplement: I recommend copying the supplement in Arabic and English, indicating the precedence of the two texts and the place of display for the user.

10. Action Plan (Suggested Steps Forward)
11. Choose a range of 3–10 initial TLDs whose extensions you want to deploy now (e.g., .COM, .NET, .SA, . IN, .CO).
12. Present per TLD: (a) a full legal extension; (b) a summary of the checkout; (c) a WHMCS snippet/product page; and (d) a list of additional fields or documents required.
13. After your review, combine the extensions into one formatted file or send them as fragmented messages depending on your preference.