This Domain Registration Agreement (“Agreement”) is between BYTES GLUE SOFTWARE SERVICES AND SOLUTIONS - FZCO (“BytesGlue”, “we”, or “us”) and the person or organisation recorded as the registered name holder or acting with authority for that holder (“you” or the “Holder”).
1. Parties and registrar
BytesGlue is a domain reseller and service provider. We are not an ICANN-accredited registrar and do not present ourselves as one. The sponsoring registrar is Hosting Concepts B.V., trading as Openprovider, Rotterdam, the Netherlands. The registrar of record may also be identified through an ICANN WHOIS/RDAP lookup at lookup.icann.org.
You agree to the current Openprovider Domain Registration Agreement, Openprovider General Terms applicable to the service, this Agreement, and all applicable ICANN, registry and TLD-specific rules. They are incorporated into each accepted order.
2. Each domain order
Each order record identifies the requested domain, Holder, order date, registration period, quoted price, currency, registrar auto-renew selection, WHOIS privacy selection where supported, applicable extension, registry-specific fields, accepted agreement version and acceptance time. Submitting holder details creates an order and may redirect you to Stripe Checkout; it does not itself register a domain. Registration becomes effective only after full cleared payment, successful submission to Openprovider and confirmation by the applicable registry.
Availability and prices are provisional until provider action. BytesGlue rechecks availability and the provider price before Checkout. A domain can still become unavailable between that check and registration. We will not automatically charge a higher price than the accepted order. If confirmed registration cannot proceed at the paid terms before a domain is created, we submit a full refund as described in our Refund Policy.
3. Required registration information
You must provide complete, accurate and reliable Holder details: legal name, postal address, email, telephone number, organisation where applicable, and the name of an authorised person for an organisational Holder. Required fields are mandatory; fax and other fields are voluntary unless required by the registry.
You must notify BytesGlue and correct registration information immediately, and no later than five calendar days after any change, and respond within fifteen days to an accuracy inquiry from BytesGlue, Openprovider or the registry. Materially false, unreliable or stale information may result in suspension or cancellation.
Unless you provide and we approve different contacts, you direct us to reuse the Holder details for administrative and billing contacts and to use BytesGlue or an approved provider contact for technical administration. At least two nameservers or an approved nameserver group will be assigned. Nameserver or contact changes require your explicit instruction.
4. Authority and third-party data
You represent that you are the Holder or have authority to bind the named Holder. If you provide another person’s information, you confirm that you gave them equivalent privacy notice and obtained their express consent for the disclosures and processing described here. If a domain is licensed to another user, the Holder remains responsible for accurate contacts and may be liable for wrongful use unless applicable disclosure requirements are met.
5. Registration-data processing
Registration data is used to check availability and eligibility, create and maintain registrar and registry records, administer DNS and transfers, verify contacts, prevent abuse and fraud, send mandatory lifecycle communications, resolve disputes, and comply with law and domain policies.
Required data is disclosed to Openprovider, the applicable registry operator, ICANN where applicable, WHOIS/RDAP systems as permitted or required, verification and technical providers, and authorities or dispute-resolution providers where legally required. Data may be processed outside your country. Where the extension supports it and the order enables it, Openprovider WHOIS Privacy Protection replaces public contact details with privacy-service data; it does not prevent required private disclosure to the registrar, registry or lawful recipients, and registry policy can limit or override availability. You can request access or correction through privacy@bytesglue.com or the authenticated portal. See our Patakaran sa Privacy and Openprovider’s legal policies.
6. Registration and availability
Domain services are provided on a first-come, first-served basis. No search result, quote, invoice or payment guarantees registration. Openprovider or a registry may deny, cancel, correct, redirect, lock, hold or transfer a registration as permitted by its policies, a binding decision, applicable law, non-payment, security requirements or correction of an error.
You acquire a time-limited registration right, not ownership of the domain name itself or a proprietary right in the registry database.
7. Verification and communications
The Holder email must remain reachable. For TLDs requiring verification, Openprovider or its provider may send a verification message after registration, transfer or contact change. You must complete verification within the stated deadline, commonly fifteen days. Failure can suspend the domain and associated services. You authorise required service, verification, expiry, abuse and policy communications even when marketing messages are disabled.
8. Lawful use and third-party rights
You represent that neither the registration nor its intended use infringes another party’s rights. You must not use a domain for malware, abusive botnets, phishing, piracy, fraud, counterfeiting, unlawful content, deceptive activity, trademark or copyright infringement, or other prohibited conduct. You are responsible for investigating name availability and legal rights before ordering.
You will indemnify and hold harmless BytesGlue, Openprovider and the applicable registry operator, together with their personnel and agents, from claims, liabilities, costs and reasonable legal expenses arising from your registration or use, to the extent permitted by applicable law.
9. Fees and refunds
BytesGlue sets the client price shown in the accepted order. Registry, registrar, premium, restoration, tax and currency costs may change. Successfully processed registrations, renewals, transfers, restorations and deletions are generally final and non-refundable, including mistaken orders and premium domains, except where mandatory law or a confirmed provider exception requires otherwise. See our Patakaran sa Refund.
If payment is confirmed but Openprovider conclusively rejects the registration before creating the domain, or the domain or accepted provider price changed before submission, BytesGlue submits a full Stripe refund. An ambiguous provider response is held for reconciliation before retry or refund so that a completed registration is not duplicated or incorrectly refunded. “Refund submitted” is not final; “Refunded” is recorded only after Stripe’s signed webhook confirms it, and bank posting time varies.
10. Renewal, expiry, deletion and restoration
New registration orders default registrar auto-renewal to on, and the order form lets you turn it off before submission. When on, Openprovider may attempt renewal automatically at the then-current renewal price before its controlling deadline, subject to successful billing and provider eligibility. Auto-renewal is not a fixed-price guarantee. When off, renewal requires a separate authenticated request and provider action. The controlling deadline is the expiration or renewal date shown in Openprovider, which can be earlier than the registry expiry date. You remain responsible for accurate contacts, reviewing renewal notices and resolving payment or eligibility issues before that deadline.
Openprovider normally sends required renewal notices approximately thirty days and seven days before expiry and promptly after expiry when not renewed. We may send additional portal or email reminders. You must keep the Holder email accurate and must not obstruct these notices.
If a domain is not renewed, it may stop resolving, be deleted, enter grace, quarantine, redemption or pending-delete states, incur non-refundable restoration fees, or become available to another party. Registry recovery periods are not guaranteed. Full details appear in our Domain Renewal, Expiration and Deletion Policy.
11. Transfers and holder changes
We will process an authenticated Holder request for an eligible authorization code or domain unlock within five calendar days for gTLDs, subject to the limited grounds for denial permitted by applicable transfer policy. Registry-specific processes may differ. Transfers can be restricted after initial registration, recent transfer, holder change, dispute, non-payment, legal order or fraud concern.
We do not apply a discretionary initial-registration transfer lock during the pilot. If that setting changes, we will request separate explicit informed consent. Holder changes require authenticated instructions and any registry-required documentation. For each authenticated, reviewed Change of Registrant request, you explicitly authorise BytesGlue and Openprovider to act as your Designated Agents to approve that change on your behalf and, to the extent the applicable policy permits, you explicitly opt out of the resulting 60-day inter-registrar transfer lock. This designated-agent authority does not authorise any unrelated holder change.
12. Registry action and disputes
You agree to applicable dispute policies, including the ICANN Uniform Domain Name Dispute Resolution Policy (UDRP), Uniform Rapid Suspension procedure (URS), Transfer Dispute Resolution Policy, court orders and registry procedures. For domain disputes, you submit without prejudice to other applicable jurisdictions to the courts of the Holder’s domicile and the place where Openprovider is located. Registry timestamps and records control provider or registry transaction discrepancies.
13. Generic top-level domains
For generic extensions such as .com, .net and .org, the latest ICANN Registrar Accreditation Agreement, consensus policies and registrant protections apply. Review Registrant Rights and Responsibilities and Registrant Benefits.
14. .ae supplement
For .ae, you also accept the current .ae registration supplement and .aeDA policies. You authorise necessary disclosure to .aeDA and acknowledge permitted public WHOIS disclosure. You must satisfy continuing eligibility, provide true and complete data, avoid registrations intended to divert trade, exploit misspellings or block another eligible registrant, and accept the aeDRP dispute policy.
A .ae owner change requires a written request from both the current and new Holder, retained for registry inspection. Transfer confirmation must come from the Registrant; the authorization code is sent directly to the Registrant and is not disclosed to BytesGlue. Deleted .ae registrations are not refundable.
15. .io supplement
For .io, you also accept the current NIC.IO Terms and Conditions, rules and dispute policy. The fee is non-refundable, accurate data and consent for registry disclosure are required, and sanctioned-country or region connections prohibited by the registry are not eligible. An explicit deletion enters redemption without a soft-quarantine period.
16. Records and support
We retain order, payment, refund, acceptance, transfer and material written-communication records throughout the relationship and for at least two years afterwards, or longer where required by law, tax, dispute or domain policy. Openprovider may request relevant compliance evidence. Domain support and abuse reports may be sent to domains@bytesglue.com.
17. Changes and precedence
ICANN, Openprovider and registries may change mandatory policies. Renewing or materially changing a domain may require acceptance of a newer version. For a specific domain, mandatory law and registry or ICANN policy prevail, followed by the applicable Openprovider agreement, this Agreement, the accepted order and our general Terms of Service.
18. Governing law
Our relationship is otherwise governed by the law and dispute provisions in the BytesGlue Terms of Service, without limiting mandatory ICANN, registry, registrar or local-law jurisdiction provisions described above.