Request for Disclosure of Nonpublic Registration Data

Request for Disclosure of Nonpublic Registration Data

1. Purpose

NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") may redact or otherwise withhold certain personal Registration Data from public RDDS output in accordance with applicable law, the ICANN Registration Data Policy, and applicable registry requirements.

This Policy explains how a third party may request lawful disclosure of non-public Registration Data for a domain name sponsored by NiceNIC.

A request does not create an automatic right to disclosure. Each properly formed request is assessed on its own merits.

2. Where to Submit a Request

A disclosure request must be submitted through the disclosure-request mechanism identified on NiceNIC's website/legal page. Where an ICANN-facilitated registration-data request service is available and supported by NiceNIC, a requester may also use that service.

Requests sent through unrelated sales, social-media, or general messaging channels may be redirected to the formal mechanism so the request can be securely logged and reviewed. NiceNIC may nevertheless preserve or act on information received through another channel where required by law, necessary to address an emergency, or appropriate for security or abuse handling.

3. Required Information

A request should contain, at minimum:

  1. 1.Requester identity

    • full name;
    • organization, if applicable;
    • contact information;
    • the nature/type of requester (for example, individual, law firm, intellectual-property representative, cybersecurity investigator, law-enforcement authority, or other entity); and
    • evidence of authority or power of attorney where the requester acts for another person.

  2. 2.Domain name

    • the domain name for which disclosure is requested.

  3. 3.Data requested

    • the specific non-public Registration Data elements requested.

  4. 4.Legal rights and basis

    • the requester's legal rights, legitimate interest, statutory authority, legal process, or other specific basis for requesting the data;
    • the purpose for which the requested data will be used; and
    • information sufficient for NiceNIC to evaluate necessity, proportionality, jurisdiction, and applicable data-protection requirements.

  5. 5.Supporting evidence

    • documents or evidence supporting the request, where relevant.

  6. 6.Good-faith affirmation

    • an affirmation that the request is made in good faith.

  7. 7.Lawful-processing undertaking

    • an undertaking that any data disclosed will be processed lawfully and only for the stated lawful purpose, subject to applicable law.

NiceNIC may request clarification or additional information where reasonably necessary to evaluate a request.

4. Review Standard

NiceNIC reviews each properly formed request on its merits. Depending on the request and applicable law, NiceNIC may consider:

  • the requester's identity and authority;
  • the legal basis and jurisdiction;
  • the nature and seriousness of the asserted rights or harm;
  • whether the requested data is necessary and proportionate;
  • whether less intrusive means are available;
  • the interests, rights, and freedoms of the data subject;
  • confidentiality, privilege, security, and due-process considerations;
  • applicable ICANN or registry requirements; and
  • any other factor required or permitted by law.

NiceNIC does not guarantee disclosure merely because a request has been submitted.

5. Acknowledgement and Response Time

For a disclosure request that meets NiceNIC's required format:

  • NiceNIC will acknowledge receipt without undue delay and no later than two (2) business days after receipt; and
  • NiceNIC will respond without undue delay and no later than thirty (30) calendar days after acknowledgement , absent exceptional circumstances.

If exceptional circumstances require additional time, NiceNIC will communicate the status or extension as appropriate and permitted.

A response will either:

  • provide all or part of the requested data; or
  • explain the specific reason(s) why NiceNIC cannot provide all or part of the requested data, to the extent permitted by law and security considerations.

6. Urgent Requests

NiceNIC gives appropriate priority to requests involving a credible and imminent threat to life, serious bodily harm, critical infrastructure, child safety, or another genuine emergency.

The ICANN Registration Data Policy contains a separate Section 10.7 framework for authenticated urgent requesters. Under ICANN's implementation note, the mandatory Section 10.7 urgent-response timelines become effective only when ICANN fully implements the applicable Consensus Policy authentication process.

Until that trigger occurs, NiceNIC will handle urgent requests as promptly as reasonably practicable based on the circumstances, applicable law, and available authentication.

7. Law Enforcement, Court Orders, and Legal Process

Governmental, law-enforcement, regulatory, or judicial requests should identify the issuing authority, legal basis, jurisdiction, scope, and any applicable confidentiality or urgency requirement.

NiceNIC may seek clarification, authentication, narrowing, or legal review where appropriate and may challenge or decline a request that is invalid, overbroad, unlawful, or outside the requesting body's authority, unless NiceNIC is legally required to comply.

8. Abuse of the Request Process

NiceNIC may take reasonable steps to prevent abuse of the disclosure process, including requiring additional information, restricting repetitive or clearly abusive requests, or denying requests that do not satisfy applicable requirements.

9. Recordkeeping

NiceNIC may retain records of disclosure requests, acknowledgements, supporting materials, internal decisions, and responses as required for compliance, audit, security, dispute, and legal purposes.

10. Privacy

Personal data submitted through the disclosure process will be handled in accordance with the NiceNIC Privacy Policy and applicable law.