Reseller Agreement

This Domain Name Registration Agreement ("Agreement") is entered into by and between:


CV Jogjacamp, an entity organized and existing under the laws of the Republic of Indonesia, with its principal place of business at Jl. Perintis Kemerdekaan 33, Yogyakarta 55161, acting as an ICANN-accredited domain name registrar ("Registrar"),

and

The individual or legal entity applying for, registering, transferring, or renewing a domain name ("Registrant").


By registering, transferring, or renewing a domain name through the Registrar, the Registrant agrees to be bound by the terms and conditions of this Agreement and all applicable ICANN consensus policies and Registry Operator requirements.


1. Registration Data and Accuracy


1.1. The Registrant agrees to provide accurate, complete, and up-to-date registration information, including the Registrant's name, organization (where applicable), postal address, email address, telephone number, and other registration data required under applicable ICANN policies.


1.2. The Registrant shall promptly update and correct registration data during the registration term whenever any information changes or becomes inaccurate.


1.3. The Registrant acknowledges that the Registrar may verify or re-verify registration data in accordance with applicable ICANN policies and the Registrar's procedures.


1.4. Failure to provide or maintain accurate registration data, or failure to respond to applicable verification or re-verification requests, may result in suspension or cancellation of the domain name registration where permitted or required by applicable ICANN policies.


2. Expiration, Renewal and Redemption


2.1. Pre-Expiration Notifications


The Registrar shall send expiration reminders to the Registrant via email using the contact email address associated with the domain name registration.


At least two pre-expiration reminders shall be sent:

• The first reminder no later than 30 days prior to the expiration date; and


• The second reminder no later than 7 days prior to the expiration date.

The Registrar may send additional reminders through available communication channels where applicable.


2.2. Post-Expiration Notifications


Following expiration of the domain name, the Registrar shall send post-expiration notifications to the Registrant via email using the contact email address associated with the domain name registration.


Post-expiration notifications may include information regarding the domain's expired status, applicable renewal or recovery options, applicable deadlines, and potential deletion of the domain name.


2.3. Expiration and Auto-Renewal


Upon expiration, the domain name may enter the applicable Auto-Renew Grace Period in accordance with the applicable Registry Operator requirements and ICANN policies.


During this period, the Registrant may renew the domain name subject to the applicable renewal terms and fees.


2.4. Redemption


If the domain name is not renewed within the applicable period following expiration and enters the Redemption Period, the Registrant may be required to pay the applicable redemption or restore fee to recover the domain name, subject to applicable Registry Operator requirements and ICANN policies.


2.5. Deletion


If the domain name is not renewed or restored within the applicable recovery period, the domain name may be deleted in accordance with applicable ICANN policies and Registry Operator requirements.


2.6. Renewal Fees


The Registrar's current domain renewal fees are available at:


http://resellercamp.com/reseller-pricing


The applicable renewal fee may vary depending on the domain extension, registration term, and other applicable conditions.


2.7. Redemption/Restore Fees


The Registrar's current domain redemption/restore fees are available at:


http://resellercamp.com/reseller-pricing


Applicable redemption or restore fees may vary depending on the domain extension and Registry Operator requirements.


2.8. Registrant Responsibility


The Registrant is responsible for renewing the domain name before its expiration date and for maintaining an accurate and accessible email address and other contact information to ensure receipt of registration-related notifications.


3. Domain Name Transfer Policy


3.1. Transfer Rights


The Registrant has the right to transfer the domain name to another registrar, subject to applicable ICANN policies, Registry Operator requirements, and the terms of this Agreement.


3.2. Transfer Authorization


Where required, the Registrar may send a Form of Authorization ("FOA") or other applicable transfer authorization request to the Registrant's registered email address.


The Registrant must respond to the transfer authorization request in accordance with the applicable ICANN Transfer Policy and within the applicable period specified in the request.


3.3. AuthInfo Code


The Registrar shall provide the AuthInfo code to the Registrant upon a valid request, subject to applicable ICANN policies, Registry Operator requirements, and applicable law.


3.4. Transfer Lock


The Registrar may apply a ClientTransferProhibited status where permitted or required by applicable ICANN policies, Registry Operator requirements, or at the Registrant's request.


3.5. Transfer Restrictions


A transfer may be restricted or denied where permitted or required by applicable ICANN policies, including applicable transfer lock periods, pending disputes, or other circumstances specified under the applicable Transfer Policy.


3.6. Transfer Policy Compliance


The Registrant agrees to comply with the applicable ICANN Transfer Policy and any subsequent amendments or replacement policies.


4. Domain Disputes and Suspension


4.1. Domain Name Dispute Policies


The Registrant agrees to be bound by applicable domain name dispute policies, including:

• the Uniform Domain Name Dispute Resolution Policy (UDRP);


• the Uniform Rapid Suspension System (URS); and


• any other applicable dispute resolution policy or procedure.

4.2. Suspension or Lock


The Registrar may lock, suspend, or otherwise restrict a domain name where permitted or required by applicable ICANN policies, Registry Operator requirements, a court order, or an applicable dispute resolution proceeding.


5. Registrant Rights and Obligations


5.1. Registrant Rights


Subject to applicable ICANN policies and this Agreement, the Registrant has the right to:

• manage and update its registration data;


• transfer the domain name to another registrar;


• receive applicable registration-related notifications;


• receive clear and accessible information regarding applicable policies and fees; and


• receive information regarding the Registrar's domain registration, renewal, and redemption processes.

5.2. Registrant Obligations


The Registrant shall:

• provide and maintain accurate and up-to-date registration data;


• promptly respond to applicable verification or re-verification requests;


• use the domain name in accordance with applicable law;


• comply with applicable ICANN consensus policies and Registry Operator requirements; and


• ensure that the email address associated with the domain registration remains accessible for registration-related communications.

6. Registration Data Verification


6.1.


The Registrar may validate and verify registration data provided by the Registrant in accordance with applicable ICANN policies and the Registrar's registration data verification procedures.


6.2.


Where the Registrar receives information indicating that registration data may be inaccurate, the Registrar may contact the Registrant or Account Holder, as applicable, and may require verification or re-verification of the relevant registration data.


6.3.


The Registrant agrees to cooperate with applicable verification and re-verification requests and to provide accurate information within the timeframe specified by the Registrar.


7. Fees and Payments


7.1.


The Registrant agrees to pay the applicable fees for domain registration, renewal, transfer, restoration, redemption, or other applicable domain services.


7.2.


Current fees applicable to domain registration and related services are made available through the Registrar's official website.


7.3.


The Registrar may update applicable fees from time to time. The applicable fee at the time of the relevant transaction shall apply.


8. Modifications and Amendments


The Registrar may amend this Agreement from time to time to reflect changes to applicable ICANN policies, Registry Operator requirements, applicable law, or the Registrar's services.


Material amendments shall be communicated or published through the Registrar's official website or other appropriate means.


Continued registration, renewal, or use of the domain name following the effective date of an amendment constitutes acceptance of the amended Agreement, to the extent permitted by applicable law.


9. Applicable Policies


The Registrant acknowledges and agrees to comply with all applicable ICANN consensus policies, temporary policies, Registry Operator requirements, and other applicable policies governing domain name registrations.


Where this Agreement conflicts with a mandatory ICANN consensus policy or Registry Operator requirement, the applicable policy or requirement shall prevail to the extent of the conflict.


10. Governing Law and Jurisdiction


This Agreement shall be governed by and construed in accordance with the laws of the Republic of Indonesia.


Subject to any applicable ICANN policy or dispute resolution procedure, any dispute arising out of or in connection with this Agreement shall be submitted to the competent courts of Yogyakarta, Indonesia.


11. Acceptance of Agreement


By registering, transferring, or renewing a domain name through the Registrar, the Registrant acknowledges that they have read, understood, and agreed to this Agreement and all applicable ICANN policies and Registry Operator requirements.

---

This policy explains the lifecycle of a domain name registered through ResellerCamp, including renewal, expiration, auto-renewal grace period, redemption, and deletion.


The specific lifecycle and applicable fees may vary depending on the applicable Registry rules and the domain extension (TLD).


1. Domain Registration


A domain name is registered for the selected registration period once the registration request has been successfully processed and the applicable registration fee has been paid.


The domain's expiration date is displayed in the applicable domain management system and may also be reflected in the domain's registration data.


2. Domain Renewal


A domain name may be renewed before its expiration date at the applicable regular annual renewal fee for the relevant domain extension.


Renewal is subject to the applicable Registry rules and the domain's status.


For current renewal fees, please refer to our Domain Pricing page.


3. Expiration


If a domain name is not renewed before its expiration date, the domain enters the post-expiration lifecycle.


Once a domain has expired, the associated website and related online services may become inaccessible.


The domain may still be eligible for renewal during the Auto (Grace) Renewal Period, subject to the applicable Registry rules.


4. Auto (Grace) Renewal Period


The Auto (Grace) Renewal Period lasts for 37 days after the domain's expiration date.


During this period:

• The domain may still be renewed at the regular annual renewal fee.


• The domain's website may be inaccessible after expiration.


• The domain remains subject to the applicable Registry and Registrar policies.


• Renewal during this period is subject to domain availability and applicable Registry restrictions.

5. Redemption Grace Period (RGP)


If the domain is not renewed during the Auto (Grace) Renewal Period, it may enter the Redemption Grace Period (RGP).


The Redemption Grace Period lasts for approximately 30 days after the Auto (Grace) Renewal Period.


During the Redemption Grace Period:

• The domain is no longer available for regular renewal.


• The domain may be restored subject to the applicable Registry rules.


• A redemption/restore fee equivalent to 10 times the regular annual renewal fee applies to restore the domain.


• Restoration is subject to the applicable Registry requirements and successful processing of the restore request.

For current redemption/restore fees, please refer to our Domain Pricing page.


6. Pending Delete / Delete Period


If the domain is not restored during the Redemption Grace Period, it will enter the Pending Delete / Delete Period.


This period generally lasts approximately 5-7 days after the Redemption Grace Period.


During this period:

• The domain cannot be renewed or restored through the normal renewal or redemption process.


• The domain is scheduled for deletion by the Registry.


• Once deleted, the domain may become available for registration by the general public, subject to the applicable Registry rules.

After the domain has been deleted by the Registry, ResellerCamp cannot guarantee that the same domain name will be available for re-registration.


7. Expiration and Renewal Notifications


ResellerCamp provides notifications relating to domain expiration and renewal through the notification methods available in the applicable domain management system.


Pre-Expiration Notifications


Prior to the domain's expiration date, expiration and renewal information may be communicated through the applicable notification channel associated with the domain or reseller account.


These notifications are intended to provide information regarding the upcoming expiration and the option to renew the domain before expiration.


Post-Expiration Notifications


After a domain has expired, applicable notifications may be provided through the available notification channel associated with the domain or reseller account.


Post-expiration notifications may include information regarding the domain's expired status, applicable renewal options, and the applicable deadlines for renewal or restoration.


Customers/resellers are responsible for maintaining accurate and up-to-date contact and account information to ensure that applicable notifications can be delivered successfully.


8. Renewal, Post-Expiration and Redemption Fees


The applicable fees depend on the domain extension and the stage of the domain lifecycle.

Domain Lifecycle Stage	Applicable Fee
Regular Renewal	Regular annual renewal fee
Auto (Grace) Renewal Period	Regular annual renewal fee
Redemption Grace Period	10 × regular annual renewal fee
Pending Delete / Delete Period	Renewal or restoration is no longer available

For the latest applicable fees, please refer to our Domain Pricing page.


9. Important Notice


The lifecycle periods described above are based on the applicable domain lifecycle and may be subject to change in accordance with Registry policies, ICANN requirements, and the rules applicable to the relevant TLD.


ResellerCamp reserves the right to update this policy when required to reflect changes to applicable Registry or ICANN policies.


For questions regarding a specific domain name, renewal status, or restoration eligibility, please contact ResellerCamp through the applicable support channel.

---

ResellerCamp supports the transfer of domain name registrations between ICANN-accredited registrars in accordance with the applicable ICANN Transfer Policy and Registry requirements.


This policy explains the requirements and general process for transferring a domain name from ResellerCamp to another registrar.


1. Transfer Eligibility


A domain name may be transferred to another registrar provided that the transfer meets the applicable ICANN and Registry requirements.


A transfer may be restricted or denied in certain circumstances, including:

• The domain name was registered within the previous 60 days.


• The domain name was transferred to the current Registrar within the previous 60 days, except where an applicable exception applies.


• The domain name is subject to a 60-day inter-registrar transfer lock following a Change of Registrant, where applicable.


• The domain name is subject to a lock or restriction permitted under the ICANN Transfer Policy or applicable Registry policy.


• The transfer is prohibited due to a pending UDRP, URS, TDRP, court order, or other applicable dispute or legal restriction.


• There is evidence of fraud or a reasonable dispute regarding the identity of the person authorizing the transfer.


• The Registered Name Holder has expressly objected to the transfer.


• Payment is owed for a previous registration period, where applicable.

The applicable transfer restrictions may vary depending on the domain extension and Registry requirements.


2. Requirements for Transfer


Before initiating a transfer, the Registered Name Holder should ensure that:

• The domain name is not subject to an applicable transfer restriction.


• The domain name is unlocked and does not have a registrar-imposed transfer lock that prevents the transfer.


• The Registered Name Holder has access to the current registration information and can authorize the transfer.


• A valid AuthInfo / EPP Code is available when required.


• The transfer request is properly authorized through the applicable transfer authorization process.

If the domain is locked, the Registered Name Holder may request that the Registrar provide a reasonable means to remove the lock.


3. Transfer Authorization


The transfer process requires authorization from the Registered Name Holder in accordance with the applicable ICANN Transfer Policy.


The Gaining Registrar is responsible for obtaining the required authorization from the Registered Name Holder through the applicable Standardized Form of Authorization (FOA).


The Registrar of Record may also be required to confirm the Registered Name Holder's intent to transfer through the applicable confirmation process.


A transfer cannot proceed where the required authorization has not been obtained.


4. AuthInfo / EPP Code


The Registered Name Holder may request the domain's AuthInfo / EPP Code from the Registrar when required for the transfer process.


Where applicable, the AuthInfo / EPP Code will be provided through the available secure mechanism.


The Registrar will provide the AuthInfo / EPP Code within the timeframe required by the applicable ICANN policy.


5. Transfer Process


The general transfer process is as follows:

1. The Registered Name Holder initiates a transfer request with the Gaining Registrar.


2. The Gaining Registrar obtains the required authorization from the Registered Name Holder.


3. The Gaining Registrar submits the transfer request to the Registry.


4. ResellerCamp, as the Registrar of Record, processes the transfer request in accordance with the applicable ICANN Transfer Policy.


5. Where required, ResellerCamp sends the applicable transfer confirmation request to the Registered Name Holder.


6. If the transfer is approved or no valid denial is received within the applicable period, the transfer will proceed in accordance with the Registry and ICANN requirements.


7. Once the transfer is completed, the domain will be managed by the Gaining Registrar.

The applicable transfer process may vary depending on the TLD and Registry requirements.


6. Transfer Approval and Default Approval


If a transfer request is received and there is no valid reason to deny the transfer, ResellerCamp will process the transfer in accordance with the applicable ICANN Transfer Policy.


Where applicable, failure by the Registrar of Record to respond to a Registry transfer notification within the required timeframe may result in the transfer being approved by default.


7. Reasons for Transfer Denial


ResellerCamp may deny a transfer request only where a valid reason for denial exists under the applicable ICANN Transfer Policy or Registry policy.


Where a transfer is denied, the Registered Name Holder and the potential Gaining Registrar will be provided with the applicable reason for the denial.


Examples of valid reasons for denial may include:

• A reasonable dispute over the identity of the person authorizing the transfer.


• An outstanding payment obligation for a previous registration period, where applicable.


• Express written objection from the Registered Name Holder.


• The domain name is subject to a valid transfer lock.


• The domain name is within 60 days of initial registration.


• The domain name is within 60 days of a previous inter-registrar transfer.


• A pending UDRP, URS, or TDRP proceeding, where applicable.


• A court order prohibiting the transfer.


• A 60-day Change of Registrant inter-registrar transfer lock, where applicable.

The reason for denial will be communicated to the Registered Name Holder and the potential Gaining Registrar as required by the applicable ICANN Transfer Policy.


8. Transfer Lock


A domain name may be subject to a transfer lock where permitted or required by ICANN or Registry policy.


Registered Name Holders must be provided with a reasonable means to remove a Registrar-imposed transfer lock, where applicable.


A 60-day inter-registrar transfer lock may also apply following a Change of Registrant in accordance with the applicable ICANN Transfer Policy, unless the applicable opt-out option was exercised before the Change of Registrant request.


9. Transfer After Registration or Previous Transfer


A domain name generally cannot be transferred to another registrar:

• Within 60 days after the initial registration; or


• Within 60 days after a previous inter-registrar transfer, subject to applicable exceptions.

Registered Name Holders should therefore consider these restrictions when planning a transfer.


10. Transfer During Expiration or Post-Expiration Period


Transfer eligibility may be affected if a domain name has expired or entered a post-expiration lifecycle stage.


A transfer request may not proceed if the domain has expired and the applicable transfer authorization has expired or if the domain is otherwise restricted under the applicable ICANN or Registry policy.


Registered Name Holders should ensure that the domain remains eligible for transfer before initiating the transfer process.


11. Privacy and Registration Data


The Registered Name Holder is responsible for ensuring that the registration information associated with the domain is accurate and up to date.


Where registration data is required for transfer authorization or verification, the applicable ICANN Transfer Policy and Registration Data Policy will apply.


Privacy or proxy services may affect the availability of registration data for the transfer process and may be subject to the applicable service and Registry requirements.


12. Transfer Completion


Once the transfer has been successfully completed, the domain name will be transferred to the Gaining Registrar.


The Registered Name Holder should review the terms and conditions of the Gaining Registrar before completing the transfer.


After a successful inter-registrar transfer, the domain may be subject to the applicable 60-day transfer restriction before another inter-registrar transfer can be initiated, subject to applicable exceptions.


13. Transfer Disputes


If the Registered Name Holder believes that a transfer has been improperly denied or processed, they may contact the Registrar involved in the transfer for assistance.


Transfer disputes between ICANN-accredited registrars may be handled in accordance with the applicable ICANN Transfer Dispute Resolution Policy.


14. Policy Updates


This Transfer Policy may be updated from time to time to reflect changes to ICANN policies, Registry requirements, applicable laws, or ResellerCamp's operational processes.


For questions regarding a specific domain transfer, please contact ResellerCamp through the applicable support channel.