Parties and incorporation
These standard registry terms describe the responsibilities of HMJP Limited (RC1203744), trading as DotNaija, and an approved registrar partner. They become part of the partner relationship when incorporated into an executed agreement or accepted onboarding terms. Publication alone does not appoint a registrar or grant access credentials.
A signed agreement and its schedules identify the contracting parties, enabled services, commercial arrangements, and any negotiated variations. Mandatory law prevails.
Appointment and permitted activity
The registrar may submit authorised transactions for approved namespaces using the access and interfaces made available to it. It must not represent itself as the owner of the registry, imply broader accreditation, or allow an unapproved party to use its credentials.
Resellers remain under the registrar’s supervision. The registrar is responsible for their compliance and must maintain a reachable operational and compliance contact.
Registrant agreements and verification
Before submitting a registration, the registrar must obtain the registrant’s agreement to the Terms of Service, AUP, applicable namespace criteria, and relevant privacy disclosures.
The registrar must check required data and authority evidence, keep an auditable record of the instruction, communicate lifecycle deadlines, and provide a procedure for corrections. Registration data must identify the actual registrant or a lawfully permitted arrangement; false ownership details are prohibited.
Technical access and transaction controls
| Area | Registrar obligation |
|---|---|
| Access | Use assigned credentials, protect secrets, and restrict access to authorised personnel. |
| Transactions | Submit accurate, authorised requests and retain transaction identifiers. |
| DNS | Validate nameserver and security changes before submission. |
| Incidents | Report compromise promptly and cooperate in containment. |
| Integration changes | Follow published interface requirements and agreed transition notices. |
The Technical and Syntax Policy governs valid submissions. A successful request receipt is not necessarily a successful transaction; the final registry response and record determine the outcome.
Fees and reconciliation
The accepted partner schedule controls prices, currency, prefunding or credit arrangements, invoice dates, and settlement. No credit facility or discount is implied by this public document.
The registrar must reconcile its records, raise discrepancies with supporting transaction details, and explain retail fees to registrants. Taxes and refunds follow the agreed schedule and applicable law. See the Prices and Pricing Policy.
Data protection and confidentiality
Each party must identify its controller or processor role for the relevant activity, use an appropriate lawful basis, minimise data, and protect confidential information. A separate processing agreement is required where the relationship calls for one.
Registrar data must remain accurate and accessible for legitimate registry operations. Non-public data may not be harvested or repurposed for marketing. Security incidents affecting shared records must be reported without undue delay with sufficient information to coordinate the response.
Abuse, disputes, and legal requests
The registrar must maintain a working abuse contact, assess forwarded reports, provide relevant records lawfully, and carry out required mitigation within the timeframe communicated for the incident. Urgent risk may justify immediate registry action.
The registrar must preserve applicable dispute restrictions and not move a registration to frustrate an investigation or binding decision. Reporters use the abuse service; rights disputes follow the Dispute Resolution Policy.
Monitoring and service continuity
DotNaija may request proportionate evidence of compliance with these obligations. Reviews must respect confidentiality and personal-data requirements. Identified deficiencies may require a correction plan or restricted access.
If the registrar ceases trading, loses access, or terminates its agreement, the parties must cooperate on an orderly transition, protect registrant data, reconcile outstanding transactions, and communicate the available transfer route.
Suspension, termination, and surviving duties
Material breach, compromise, insolvency affecting service, non-payment under the agreement, or legal necessity may justify restriction or termination. Notice and cure periods follow the signed agreement, except where urgent protective action is justified.
Termination does not cancel accrued payment duties, confidentiality, lawful preservation, or obligations needed to transfer affected registrations. It does not authorise a registrar to retain customer domains as leverage outside lawful contractual rights.
Liability, notices, and governing law
Liability limits, service credits, termination notice, and dispute venue follow the executed agreement and mandatory law. The Terms of Service supply the general service framework where applicable.
Nigerian law governs unless an executed agreement lawfully provides otherwise. Formal notices must use the parties’ agreed channels. Prospective partners should contact the Registrar Desk or registry team for onboarding and the applicable contract schedules.