Політика щодо повідомлень про порушення

We will investigate and record all reports of abuse submitted to us. Where appropriate, we may take action if a violation of any of our terms of service is confirmed or when required to do so if an activity violates the policies of ICANN or appropriate Registry. We may request additional information from you about your report. Kindly note that we retain the authority to disclose received abuse reports and associated information to the specific customer for the purpose of abuse resolution process optimization and preventing potential miscommunication. However, please note we may not be able to provide you with specific updates in response to your specific report due to privacy reasons. As part of our investigation it may also be necessary for us to validate your complaint with our customer.

Process for handling abuse:

WHOIS INACCURACY

How to submit the complaint

• Complainant needs to fill the whois reporting form available at https://www.hostinger.com/report-abuse
• Enter the domain name and describe the whois inaccuracy.
• Enter you name and email address on which you wish to receive our reply.
• Click send.

Process to address whois inaccuracy complaint

• Our Abuse team will send a mail to the Registrant of the domain name asking them to correct the whois details of their domain name within the 7 days.
• If the Registrant fails to modify the whois details / fails to update the registrar with the sufficient proof to prove that the current / modified whois details are accurate; the domain name will be suspended for whois inaccuracy after the allotted 7 day period gets over.

SPAM

How to submit the complaint

• Complainant needs to fill the spam reporting form available at https://www.hostinger.com/report-abuse
• Enter the domain name and COMPLETE headers & body of the spam mail. Message headers & body are the most important proof of the spam and without it we cannot verify the complaint.
• Enter you name and email address on which you wish to receive our reply.
• Click Send.

Process to address spam complaint

• Our Abuse team will verify the spam headers/body to determine from where the spam was originated and the Type of spam.
• In case of compromised/hacked domain scenario and first promotional spam instance, a warning will be sent to the domain registrant. Subsequent spam complaint will result in suspension of the domain.
• In case of deliberate phishing / 419 scam / Malware distribution, the domain name will be suspended directly.

OTHER ABUSE (Phishing/419 scam)

How to submit the complaint

• Complainant needs to fill the abuse reporting form available at https://www.hostinger.com/report-abuse
• Enter the domain name and the detailed complaint. Complaint should include details of abuse along with the evidence to support it.
• Enter your name and email address on which you wish to receive our reply.
• Click Send.

Process to address other abuse complaint

• Our Abuse team will go through the complaint to determine the type of the abuse.
• In case of compromised/hacked domain, a warning will be sent to the domain registrant. If the registrant fails to remove the unauthorized content, the domain name will be suspended.
• In case of deliberate abuse like phishing / Malware / 419 scam / Child Pornography the domain name will be suspended directly.

After submitting an abuse report, a ticket is received at our centralized ticketing system to track reports. Each of the reports has a unique ID, which is used for internal administration purposes. After the investigation, this unique id will be referenced to respond accordingly with our review and any subsequent next steps.
 

 GENERAL DATA REQUEST POLICY

1. Types of requests. We receive the following types of requests concerning customer data:
   • Data requests. A data request is a request for information or documents relating to customer accounts in connection with official criminal investigations or other official legal proceedings. Except in limited emergency situations (see below), we require data requests to be made through formal U.S. legal process and procedures, and we respond to such requests as required by law. Examples of data requests include:
     • Subpoenas
     • Court Orders
     • Search Warrants
     • Legal process received from outside the United States may require a Mutual Legal Assistance Treaty (MLAT) with the United States
     • Other forms of legal process such as Civil Investigative Demands
   • Preservation requests. A preservation request asks Hostinger to preserve customer account records in connection with official criminal investigations or other official legal proceedings. Preservation requests must include the following information:
     • Identification of the account(s) at issue (as further described in Section 4 below);
     • Identification of the investigating agency and/or specific pending official proceedings (requests must be signed on law enforcement letterhead );
     • Assurances that the requesting agency or individual is taking steps to obtain appropriate legal process for access to the data that we are being asked to retain; and
     • A valid return email address and phone number.
   • Emergency requests. An emergency request is only appropriate in cases involving imminent serious bodily harm or death. We respond to emergency requests when we believe in good faith that such harm may occur if we do not respond without delay.
     
     Notice to customers. Our policy is to notify customers of requests for their data unless we are prohibited from doing so by statute or court order.
     
     Information to include in a request. The following information must be included in a request for customer data:
   • First and last name of the customer and email address associated with the account; and
   • Domain name and/or IP address associated with the account.
     
     We may not be able to respond to a request without this information.
     
     Additionally, we reserve the right to request a copy of the complaint and any supporting documentation that demonstrates how the information requested is related to the pending litigation and the underlying subpoena.
      
2. Submitting a request. All requests should be mailed or emailed to the following:
   
   Attention to: Hostinger International Ltd.,
   61 Lordou Vironos str.,
   6023 Larnaca, Cyprus
   
   OR email to: compliance@hostinger.com
   
   IMPORTANT NOTE: IN THE EVENT YOU SEND US A NOTICE OF ANY KIND VIA EMAIL AND DO NOT RECEIVE A RESPONSE FROM US, PLEASE SUBMIT A DUPLICATE COPY VIA PAPER. DUE TO THE VAGARIES OF THE INTERNET AND EMAIL COMMUNICATION IN PARTICULAR, INCLUDING WITHOUT LIMITATION THE BURDENS OF SPAM AND THE OCCASIONAL UNINTENDED EFFECTS OF SPAM FILTERS, SENDING AN ALTERNATE FORM OF NOTICE, WILL HELP ASSURE THAT YOUR NOTICE IS RECEIVED BY US AND ACTED ON IN A TIMELY MANNER.
3. Fees. We may seek reimbursement for costs in responding to requests as provided by law and may charge additional fees for costs in responding to unusual or burdensome requests.
4. Available information. Depending on the type of formal legal process provided, we may be able to respond with one or more of the following types of data:

   • Non-content. We will produce non-content information such as basic subscriber information which may include the following subject to a valid request:
     • Name
     • Email addresses
     • Date and time of account creation
     • Billing information
     • IP Logs

   • Content. We will only produce customer content (such as website files and email content) pursuant to a valid search warrant from an entity with proper jurisdiction.

NON-PUBLIC REGISTRANT DATA (NPRD) REQUEST POLICY

For privacy reasons, personal information contained in registration data is no longer displayed in our public RDAP (previous WHOIS). However, as an ICANN accredited registrar, Hostinger is required to provide a process for third parties to request access to non-public registration data ("NPRD"). This policy sets forth the general guidelines for submitting such requests based on demonstrated  legitimate interest ("Legitimate Interest"). This policy fully respects and protects the  fundamental interests, rights and freedoms of data subjects, in line with the General Data Protection Regulation ("GDPR") or other applicable privacy laws. 

This policy is not a substitute for other less-intrusive mechanisms available in part General Data Request Policy above.  A Disclosure Request for  NPRD should be considered only when other avenues are not sufficient,given the potential impact to the data subject’s privacy.

Key Considerations:

• Legitimate Interest. You must demonstrate Legitimate Interest in the NPRD  being requested. This must be done in a manner that does not jeopardize the fundamental interests, rights and freedoms of the relevant data subject, in line with the GDPR or other applicable privacy laws. To establish Legitimate Interest, you should conduct a three-part balancing test ("Legitimate Interest Assessment" or "LIA") and submit your results for review by Hostinger. 
• Data Protection. You must demonstrate that you have implemented appropriate technical and organizational measures to ensure that any NPRD received through this process will be performed in a manner compliant with GDPR or other applicable privacy laws. Additionally, Hostinger, at its discretion, but at your expense, may require an audit of your data processing practices to ensure such practices comply with GDPR or other applicable privacy laws.
• Data Handling of NPRD. You will be responsible for properly disposing of the NPRD within 30 days of receipt or when you can no longer rely on Legitimate Interest as the lawful basis of processing NPRD; whichever is sooner.

How to submit a request for NPRD

• Requests for disclosure of NPRD (“Disclosure Requests” or “Requests”) may be submitted via email to: compliance@hostinger.com. 
• Required Format and Content. Disclosure Requests must include:
  • Identity of the requestor
    • Contact details (full name, address, email, phone number).
    • Nature/type of entity (e.g., law enforcement, attorney, IP rights holder, private individual).
    • Proof of authorization (e.g., Power of Attorney or similar, if applicable).
  • Data requested - list of data element values.
  • Legal rights & rationale - explanation of the legal rights relied upon and justification for disclosure.
  • Good faith affirmation - statement that the request is made in good faith.
  • Lawful processing agreement – confirmation that any disclosed data will be processed in accordance with GDPR or other applicable law.

Requests missing required elements will not be processed until corrected.

• Acknowledgement and timeline. A substantive response will be provided within thirty (30) calendar days from the date of acknowledgement, unless exceptional circumstances require additional time.
  • Requests must only be for current domain registrations. We do not provide historical or archived NPRD through this process.
  • Requests must include the exact domain name under review. We do not fulfill partial match requests through this process.
  • Requests are reviewed and fulfilled on a per-domain basis. We do not provide search results across multiple related domains or NPRD using this process.
  • We will not provide any additional contact details aside from the following: registrant, admin or tech name and email address.
• If Hostinger concludes, at its sole discretion, that you have demonstrated a Legitimate Interest for the NPRD requested, we will provide you limited access to the requested NPRD.
  • If we conclude you have not demonstrated a Legitimate Interest to NPRD, no information will be provided.