No opinion. [No Response]

Similar documents
Yes. [No Response] General Questions

Yes. [No Response] General Questions

WHOIS Survey Prepared on behalf of:

Contact Data Disclosure in the.uk WHOIS. Summary of Consultation Feedback. Nominet.uk Policy Process Secretariat

Contact Data Disclosure in the.uk WHOIS

2. COLLECTIO OF PERSO AL I FORMATIO

Privacy and WHOIS Data Policy

Summary of feedback on the proposed changes to.uk policy arising from GDPR

GENERAL PRIVACY POLICY

OnlineNIC PRIVACY Policy

TERMS AND CONDITIONIONS FOR WHOIS DATA COLLECTION AND DISPLAY

Privacy Policy May 2018

PRIVACY POLICY. 1. What Information We Collect

The types of personal information we collect and hold

Blue Alligator Company Privacy Notice (Last updated 21 May 2018)

PRIVACY POLICY Commitment to Privacy

Beam Suntory Privacy Policy WEBSITE PRIVACY NOTICE

NYSVMS WEBSITE PRIVACY POLICY

Privacy Policy. Third Party Links

The information we collect

The registration of Domain Names will be centralized and managed through all DOT accredited Registrars selected by the Registry.

Housecall Privacy Statement Statement Date: 01/01/2007. Most recent update 09/18/2009

Privacy Policy Statement Last update 25 th May 2018.

Proposed Final Report on the Post-Expiration Domain Name Recovery Policy Development Process Executive Summary

PRIVACY POLICY OUR SERVICES. Last modified: November 29, 2015

When you provide personal information to us it will only be used in the ways described in this privacy policy.

Our Privacy Policy. Last modified: December 12th Summary of changes can be consulted at the bottom of this Privacy Policy.

SYDNEY FESTIVAL PRIVACY POLICY

Hertfordshire Natural History Society

TABLE OF CONTENTS. Page

1. Anti-Piracy Services. 2. Brand Protection (SAAS) 3. Brand Protection Services. Data Protection and Permitted Purpose. Services

The Center for Affiliated Learning ( the CAL ) Privacy Policy

EIT Health UK-Ireland Privacy Policy

TERMS & CONDITIONS. Complied with GDPR rules and regulation CONDITIONS OF USE PROPRIETARY RIGHTS AND ACCEPTABLE USE OF CONTENT

Website Privacy Policy

Advisory Concerning Inter-Registrar Transfer Policy. 23 August 2007

INNOVENT LEASING LIMITED. Privacy Notice

TechTarget, Inc. Privacy Policy

This policy is a public document and has been prepared in light of the National Privacy Principle 5: Openness.

Newsletters We may send out newsletters to our customers providing them with articles and information which we believe may be of interest to you.

UCSU Student and Applicant Data Privacy Statement

SALES LEAD MULTIPLIER INC. PRIVACY POLICY

Bend Mailing Services, LLC, dba BMS Technologies ( us, we, or our ) operates the website (the Service ).

PRIVACY NOTICE. 1.2 We may obtain or collect your Personal Data from various sources including but not limited to:

RAKUNA s PRIVACY POLICY

Government-issued identification numbers (e.g., tax identification numbers)

Privacy Policy Mobiliya Technologies. All Rights Reserved. Last Modified: June, 2016

Priv ac y Policy. Last upda ted:

Privacy Policy. We may collect information either directly from you, or from third parties when you:

DATA PROTECTION AND PRIVACY POLICY

Eight Minute Expert GDPR. Login. Password

HASS RECORD GUIDANCE. Version 1

June 27, Via Electronic Mail. Federal Trade Commission Office of the Secretary Room H Pennsylvania Avenue, NW Washington, D.C.

Matters Related to WHOIS

It applies to personal information for individuals that are external to us such as donors, clients and suppliers (you, your).

In this policy, whenever you see the words we, us, our, it refers to Ashby Concert Band Registered Charity Number

Privacy Policy I. COOKEVILLE COMMUNICATIONS PRIVACY POLICY II. GENERAL PRIVACY GUIDELINES

Proposal for a model to address the General Data Protection Regulation (GDPR)

PRIVACY POLICY. Personal Information Our Company Collects and How It Is Used

TIA. Privacy Policy and Cookie Policy 5/25/18

Data locations. For our hosted(saas) solution the servers are located in Dallas(USA), London(UK), Sydney(Australia) and Frankfurt(Germany).

Last updated: 25 May 2018

About Us. Privacy Policy v1.3 Released 11/08/2017

.LATROBE TLD REGISTRATION POLICY

What information do we collect online and how is it used?

I. INFORMATION WE COLLECT

PRIVACY NOTICE STORM RECRUITMENT UNIT 11, 2 ND FLOOR CHARLESLAND CENTRE, GREYSTONES, CO. WICKLOW 1. INTRODUCTION

The West End Community Trust Privacy Policy

General website Privacy

APM Accreditation for training providers Application Guidance Notes

Policy on Privacy and Management of Personal Information

Guidelines Concerning the Transmission, Etc. of Specified Electronic Mail

Spree Privacy Policy

Money back guarantee and refund policy

PRIVACY POLICY Last Updated May, 2018

PRIVACY NOTICE Olenex Sarl

Website Privacy Policy

Information you give us when you sign up to the World Merit Hub. In addition, when you sign up to the World Merit Hub, we will usually ask for:

ATHLETICS WORLD CUP PRIVACY NOTICE

Privacy Policy Effective Date: October 4, 2017

CITYTOUCH PRIVACY POLICY

4. Save as expressly set out herein no license is granted in respect of any intellectual property rights vested in F1000 or other third parties.

Privacy Policy and WHOIS Data

Policy & Procedure Privacy Policy

Our Privacy Statement

PRIVACY POLICY QUICK GUIDE TO CONTENTS

Privacy Policy Effective Date - May 2017

PRIVACY POLICY. Privacy Policy Updated as of February 24, 2016

.CAM Registry. GDPR integration. Version nd May CAM AC Webconnecting Holding B.V. Beurs plein AA Rotterdam

CAREERBUILDER.COM - PRIVACY POLICY

Privacy Policy FUNDRISE, LLC

MASTERCARD PRICELESS SPECIALS INDIA PRIVACY POLICY

We will never knowingly collect the personal information of minors.

Proposed Interim Model for GDPR Compliance-- Summary Description

Inspiring Insights Ltd Privacy Policy - May Important Information. 2. The data we collect and how we store it.

Terms & Conditions. Privacy, Health & Copyright Policy

Privacy and Cookies Policy

Privacy Policy- Introduction part Personal Information

Outgoing Ltd Official Ticketing Agent Terms and Conditions

PRIVACY POLICY Let us summarize this for you...

Transcription:

General Questions Q1. Do you agree that the proposals to refine the WHOIS opt-out eligibility and to provide a framework for registrar privacy services meets the policy objectives set out in the consultation document? No opinion Q2. Do you wish to highlight any potential stakeholder impacts or concerns should the proposal to refine the WHOIS opt-out eligibility criteria be implemented? Please explain, providing examples and evidence to support your view, where possible. I think the definition of 'primarily' used to advertise or promote goods, service or facilities is going to be subjective and problematic. At what point is the site 'primarily' to advertise/promote? Will Nominet be seeking submissions on levels of income? I think it's helpful to draw clear lines on what is (a) business use, (b) personal use, and (c) uses which may be considered as either, and in case of (c) what the presumption would be. I would err on side of regarding a site as a business if it seeks to make income directly (whether through affiliate revenue, advertising or selling goods) even if it's in small amounts, and only personal if it's providing information about an individual's services but in itself does not generate income. e.g. listing/linking one's businesses on a personal site is not a business in itself; an author linking to a book they wrote would be running a business site; however if that was an affiliate link (i.e. the site makes money), then it could be. Whatever the rules, clear guidance is key. Q3. Do you wish to highlight any potential stakeholder impacts or concerns should privacy services be permitted to operate in the way in which we have proposed? Please explain, providing examples and evidence to support your view, where possible. I have found a significant proportion of the spam e-mail I receive are from throw-away domains registered through privacy services. There are a few legitimate uses for these services, but in the most I find they are abused. I do not think this can be prevented in an open registry (it's just a question of whether it's regulated or unrelated) however I would urge Nominet to provide a way to query domains to provide some feedback if the domain is registered using a privacy service (e.g. a DNSBL type service); this does not need to be realtime (i.e. it can be cached for a

day) to prevent its abuse for other purposes. This way mail server administrators can decide to score any e-mails (or other protocols) originating from that domain accordingly. It may be worth giving some further thought to potential abuses of throw-away registrations in other ways too so this could be part of a bigger piece of work, however spam presents a huge cost to business (in time wasted, and in having to purchase commercial spam filtering services to deal with the problem) and the costs are on the recipient of spam (the victim). Q4. Please provide any other views on the direct impact these proposals may have on you or your organisation. It would be helpful if you could advise your interest in the WHOIS, and the stakeholder group(s) you represent. We are a registrar. We deal mainly with businesses so privacy/opt-out services are not a key business issue for us; we support opt-out where required and would consider supporting any registry-backed free privacy service on a similar basis. Q5. Do you have a commercial interest in the domain name industry, including but not limited to acting on behalf of registrants in the registration of domain names or holding domain names in your own name? Registrar We would now like to ask you specific questions relating to each proposal. Not all questions are mandatory. These are set out below for your convenience: Do you agree with our assessment of the options we have chosen to not recommend? Are the proposed criteria for eligibility of the opt-out clear and logical enough for WHOIS users and registrants? Do they meet your expectations as a WHOIS user or registrant? Do you agree that domains used to collect personal data should be excluded from eligibility to opt out? If you do not agree, we would like your thoughts on whether your concerns could be mitigated by being able to use a privacy service. Are there any process or technical consequences of the proposed changes to WHOIS opt-out eligibility that Nominet should take into account or would discourage implementation of this proposal? Do you think we should change the WHOIS query output so that the name of registrants who are optedout are withheld from publication, as well as their address? What obligations, if any, should registrars be subject to in relation to drawing the attention of registrants to the availability of the WHOIS opt-out?

Are there any specific standards that registrars should be asked to meet in order to provide a privacy service? Are there process or technical issues in separating collection from publication of contact data in the way we have suggested that Nominet should be aware of? Should the framework be restricted only to Nominet Channel Partner and Accredited Channel Partner Tag holders? If you believe the framework should not be restricted, and that other parties should be permitted to operate privacy services, please explain why and provide comments on how Nominet could identify, monitor, and enforce the framework for third parties. No, I do not wish to answer any of the additional questions i. Publish less data on the WHOIS ii. Removing the individual/trading tests from the opt-out iii. Align opt-out eligibility with the E-Commerce Directive iv. Do nothing in relation to privacy services / WHOIS opt-out v. Prohibit privacy services vi. Develop a Nominet privacy service for registrars to sell on to their customers (white-labelled solution) vii. Regulate privacy services offered by registrars WHOIS opt-out proposal Q7a. To qualify to use the opt-out we are proposing that: The registrant must be an individual; and,

The domain name must not be used: o to transact with customers (merchant websites); o to collect personal data from subjects (ie data controllers as defined in the Data Protection Act); o to primarily advertise or promote goods, services, or facilities. Are the proposed criteria for eligibility of the opt-out clear and logical enough for WHOIS users and registrants? Q7b. Do the criteria meet your expectations as a WHOIS user or registrant? Q7c. Do you agree that domains used to collect personal data should be excluded from eligibility to opt out? If you do not agree, we would like your thoughts on whether your concerns could be mitigated by being able to use a privacy service. Q8. Are there any process or technical consequences of the proposed changes to WHOIS opt-out eligibility that Nominet should take into account or would discourage implementation of this proposal? Please explain with details about whether this would affect registrants, registrars, WHOIS users, or other stakeholders.

Q9. Do you think we should change the WHOIS query output so that the name of registrants who are opted-out are withheld from publication, as well as their address? Q10. What obligations, if any, should registrars be subject to in relation to drawing the attention of registrants to the availability of the WHOIS opt-out? Privacy Services proposal Q11. Which, if any of these standards do you think registrars should be asked to meet in order to provide a privacy service? Q12. Are there process or technical issues in separating collection from publication of contact data in the way we have suggested that Nominet should be aware of? For example, updating registration data of domains currently held using a privacy service to the registry moving domains with privacy from a registrar to another (TAG change), where the new registrar does not offer privacy transfer of a domain(s) to a privacy service transfer of a domain(s) to a new registrant minimising the incidence of abuse use of the RFC5733 contact disclose field for both name and address Please explain with details about whether this would affect registrants, registrars, WHOIS users, or other stakeholders.

Q13. Whilst noting that the proposed privacy services framework would not apply to Self-Managed Tag users where domains must be connected to the registrant, should the framework be restricted only to Nominet Channel Partner and Accredited Channel Partner Tag holders? Do you wish to provide any supporting evidence in your submission? No The feedback we receive will inform our decision on changes to our WHOIS policy. We will publish all formal stakeholder responses after this decision has been made. Please tell us if you agree to the publication of your response by selecting one of the options below. Anonymous responses will not be published although they will be taken into account. Yes I am happy for Nominet to publish my response, along with my name and organisation