1.1 	A bill for an act
1.2 	relating to privacy; delaying expiration of the legislative commission on data 
1.3 	practices; expanding rideshare data classification to include all government entities; 
1.4 	providing unredacted information to the parties in a closed case under certain 
1.5 	circumstances; enabling reporting of information related to use of electronic device 
1.6 	location tracking warrants; requiring a government entity to obtain a search warrant 
1.7 	before accessing electronic communication information; restricting the sharing of 
1.8 	location information on ignition interlock devices in certain circumstances; 
1.9 	regulating the use of unmanned aerial vehicles by law enforcement agencies;
1.10 	amending Minnesota Statutes 2018, sections 3.8843, subdivision 7; 13.201; 13.72, 
1.11 	subdivision 19; 171.306, subdivision 2; 363A.35, subdivision 3; 465.719, 
1.12 	subdivision 14; 626A.08, subdivision 2; 626A.26, subdivision 3; 626A.27, 
1.13 	subdivision 2; 626A.28, subdivisions 3, 4, 5; 626A.31, subdivision 1; 626A.37, 
1.14 	subdivision 4; proposing coding for new law in Minnesota Statutes, chapter 626; 
1.15 	repealing Minnesota Statutes 2018, sections 13.72, subdivision 9; 626A.28, 
1.16 	subdivisions 1, 2; 626A.29; 626A.30.
1.17 	BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA:

1.18 	Section 1. Minnesota Statutes 2018, section 3.8843, subdivision 7, is amended to read:
1.19 		Subd. 7.Expiration. This section expires June 30, 2019 2026.

1.20 	Sec. 2. Minnesota Statutes 2018, section 13.201, is amended to read:
1.21 	13.201 RIDESHARE DATA.
1.22 	The following data on participants, collected by the Minnesota Department of 
1.23 	Transportation and the Metropolitan Council a government entity to administer rideshare 
1.24 	programs, are classified as private under section 13.02, subdivision 12, or nonpublic under 
1.25 	section 13.02, subdivision 9: residential address and telephone number; beginning and 
1.26 	ending work hours; current mode of commuting to and from work; place of employment; 
1.27 	photograph; biographical information; and type of rideshare service information requested.

2.1 	Sec. 3. Minnesota Statutes 2018, section 13.72, subdivision 19, is amended to read:
2.2 		Subd. 19.Transit customer data. (a) Data on applicants, users, and customers of public 
2.3 	transit collected by or through the Metropolitan Council's a government entity's personalized 
2.4 	web services or the Metropolitan Council's regional fare collection system are private data 
2.5 	on individuals. As used in this subdivision, the following terms have the meanings given 
2.6 	them:
2.7 	(1) "regional fare collection system" means the fare collection system created and 
2.8 	administered by the council that is used for collecting fares or providing fare cards or passes 
2.9 	for transit services which includes:
2.10 	(i) regular route bus service within the metropolitan area and paratransit service, whether 
2.11 	provided by the council or by other providers of regional transit service;
2.12 	(ii) light rail transit service within the metropolitan area;
2.13 	(iii) rideshare programs administered by the council;
2.14 	(iv) special transportation services provided under section 473.386; and
2.15 	(v) commuter rail service;
2.16 	(2) "personalized web services" means services for which transit service applicants, 
2.17 	users, and customers must establish a user account; and
2.18 	(3) "metropolitan area" means the area defined in section 473.121, subdivision 2.
2.19 	(b) The council A government entity may disseminate data on user and customer 
2.20 	transaction history and fare card use to government entities, organizations, school districts, 
2.21 	educational institutions, and employers that subsidize or provide fare cards to their clients, 
2.22 	students, or employees. "Data on user and customer transaction history and fare card use" 
2.23 	means:
2.24 	(1) the date a fare card was used;
2.25 	(2) the time a fare card was used;
2.26 	(3) the mode of travel;
2.27 	(4) the type of fare product used; and
2.28 	(5) information about the date, time, and type of fare product purchased.
2.29 	Government entities, organizations, school districts, educational institutions, and employers 
2.30 	may use customer transaction history and fare card use data only for purposes of measuring 
2.31 	and promoting fare card use and evaluating the cost-effectiveness of their fare card programs. 
3.1 	If a user or customer requests in writing that the council limit the disclosure of transaction 
3.2 	history and fare card use, the council may disclose only the card balance and the date a card 
3.3 	was last used.
3.4 	(c) The council A government entity may disseminate transit service applicant, user, 
3.5 	and customer data to another government entity to prevent unlawful intrusion into government 
3.6 	electronic systems, or as otherwise provided by law.

3.7 	Sec. 4. Minnesota Statutes 2018, section 171.306, subdivision 2, is amended to read:
3.8 		Subd. 2.Performance standards; certification; manufacturer and provider 
3.9 	requirements. (a) The commissioner shall establish performance standards and a process 
3.10 	for certifying devices used in the ignition interlock program, except that the commissioner 
3.11 	may not establish standards that, directly or indirectly, require devices to use or enable 
3.12 	location tracking capabilities without a court order.
3.13 	(b) The manufacturer of a device must apply annually for certification of the device by 
3.14 	submitting the form prescribed by the commissioner. The commissioner shall require 
3.15 	manufacturers of certified devices to:
3.16 	(1) provide device installation, servicing, and monitoring to indigent program participants 
3.17 	at a discounted rate, according to the standards established by the commissioner; and
3.18 	(2) include in an ignition interlock device contract a provision that a program participant 
3.19 	who voluntarily terminates participation in the program is only liable for servicing and 
3.20 	monitoring costs incurred during the time the device is installed on the motor vehicle, 
3.21 	regardless of whether the term of the contract has expired; and
3.22 	(3) include in any contract between the manufacturer and an Internet or cellular service 
3.23 	provider a requirement that the provider not sell or transfer to, or share with, another entity, 
3.24 	information about the actual or approximate location of the device at any point in time 
3.25 	unless required to do so under a court order or warrant.
3.26 	(c) The manufacturer of a certified device must include with an ignition interlock device 
3.27 	contract a separate notice to the program participant regarding any location tracking 
3.28 	capabilities of the device.
3.29 	(d) The manufacturer of a certified device may not sell or transfer to, or share with, any 
3.30 	entity, other than the Department of Public Safety, information about the actual or 
3.31 	approximate location of a device at any point in time unless required to do so under a court 
3.32 	order or warrant.

4.1 	Sec. 5. Minnesota Statutes 2018, section 363A.35, subdivision 3, is amended to read:
4.2 		Subd. 3.Access to closed files. (a) Except as otherwise provided in this subdivision, 
4.3 	human rights investigative data contained in a closed case file are private data on individuals 
4.4 	or nonpublic data. The name and address of the charging party and respondent, factual basis 
4.5 	of the allegations, the statute under which the action is brought, the part of the summary of 
4.6 	the investigation that does not contain identifying data on a person other than the complainant 
4.7 	or respondent, and the commissioner's memorandum determining whether probable cause 
4.8 	has been shown are public data.
4.9 	(b) The commissioner may make human rights investigative data contained in a closed 
4.10 	case file inaccessible to the charging party or the respondent in order to protect medical or 
4.11 	other security interests of the parties or third persons.
4.12 	(c) Except for paragraph (b), when the charging party files a case in district court, the 
4.13 	commissioner may provide private data or nonpublic data in a closed case file to the charging 
4.14 	party and respondent.

4.15 	Sec. 6. Minnesota Statutes 2018, section 465.719, subdivision 14, is amended to read:
4.16 		Subd. 14.Data classification. The following data created, collected, or maintained by 
4.17 	a corporation subject to this section are classified as private data under section 13.02, 
4.18 	subdivision 12, or as nonpublic data under section 13.02, subdivision 9: (1) data relating 
4.19 	either (i) to private businesses consisting of financial statements, credit reports, audits, 
4.20 	business plans, income and expense projections, customer lists, balance sheets, income tax 
4.21 	returns, and design, market, and feasibility studies not paid for with public funds, or (ii) to 
4.22 	enterprises operated by the corporation that are in competition with entities offering similar 
4.23 	goods and services, so long as the data are not generally known or readily ascertainable by 
4.24 	proper means and disclosure of specific data would cause harm to the competitive position 
4.25 	of the enterprise or private business, provided that the goods or services do not require a 
4.26 	tax levy; and (2) any data identified in sections section13.201and 13.72, subdivision 9,
4.27 	collected or received by a transit organization.

4.28 	Sec. 7. [626.085] SEARCH WARRANT REQUIRED FOR ELECTRONIC 
4.29 	COMMUNICATION INFORMATION.
4.30 		Subdivision 1.Definitions. As used in this section, the following terms have the meanings 
4.31 	given them:
5.1 	(1) "electronic communication" means the transfer of signs, signals, writings, images, 
5.2 	sounds, data, or intelligence of any nature in whole or in part by a wire, radio, 
5.3 	electromagnetic, photoelectric, or photo-optical system;
5.4 	(2) "electronic communication information" means any information about an electronic 
5.5 	communication or the use of an electronic communication service, limited to the contents 
5.6 	of electronic communications and precise or approximate location of the sender or recipients 
5.7 	at any point during the communication;
5.8 	(3) "electronic communication service" has the meaning given in section 626A.01, 
5.9 	subdivision 17; and
5.10 	(4) "government entity" has the meaning given in section 626A.42, subdivision 1, 
5.11 	paragraph (d).
5.12 		Subd. 2.Warrant required; exceptions. (a) Except as provided in paragraph (b), a 
5.13 	government entity must obtain a search warrant to require disclosure of electronic 
5.14 	communication information.
5.15 	(b) A government entity may request disclosure of electronic communication information 
5.16 	without a search warrant if the agency has valid consent from one authorized to give it, or 
5.17 	exigent circumstances exist where there is a danger to the life or physical safety of an 
5.18 	individual.
5.19 		Subd. 3.Notice to subject. A government entity accessing electronic communication 
5.20 	information under subdivision 2 must provide notice to the subject of the information 
5.21 	consistent with the requirements of subdivision 4 and section 626.16.
5.22 		Subd. 4.Notice; temporary nondisclosure of search warrant. (a) Within a reasonable 
5.23 	time but not later than 90 days after the court unseals the search warrant under this 
5.24 	subdivision, the issuing or denying judge shall cause to be served on the persons named in 
5.25 	the warrant and the application an inventory which shall include notice of:
5.26 	(1) the fact of the issuance of the warrant or the application;
5.27 	(2) the date of the issuance and the period of authorized, approved, or disapproved 
5.28 	collection of electronic communication information, or the denial of the application; and
5.29 	(3) the fact that during the period electronic communication information was or was not 
5.30 	collected.
5.31 	(b) A search warrant authorizing collection of electronic communication information 
5.32 	must direct that:
6.1 	(1) the warrant be sealed for a period of 90 days or until the objective of the warrant has 
6.2 	been accomplished, whichever is shorter; and
6.3 	(2) the warrant be filed with the court administrator within ten days of the expiration of 
6.4 	the warrant.
6.5 	(c) The prosecutor may request that the search warrant, supporting affidavits, and any 
6.6 	order granting the request not be filed. An order must be issued granting the request in whole 
6.7 	or in part if, from affidavits, sworn testimony, or other evidence, the court finds reasonable 
6.8 	grounds exist to believe that filing the warrant may cause the search or a related search to 
6.9 	be unsuccessful, create a substantial risk of injury to an innocent person, or severely hamper 
6.10 	an ongoing investigation.
6.11 	(d) The search warrant must direct that following the commencement of any criminal 
6.12 	proceeding utilizing evidence obtained in or as a result of the search, the supporting 
6.13 	application or affidavit must be filed either immediately or at any other time as the court 
6.14 	directs. Until such filing, the documents and materials ordered withheld from filing must 
6.15 	be retained by the judge or the judge's designee.
6.16 		Subd. 5.Reports. (a) At the same time as notice is provided according to the requirements 
6.17 	of subdivision 4, the issuing or denying judge shall report to the state court administrator:
6.18 	(1) the fact that a warrant was applied for under this section;
6.19 	(2) the fact that the warrant was granted as applied for, was modified, or was denied;
6.20 	(3) the period of collection of electronic communication information authorized by the 
6.21 	warrant, and the number and duration of any extensions of the warrant;
6.22 	(4) the offense specified in the warrant or application, or extension of a warrant; and
6.23 	(5) the identity of the applying investigative or peace officer and agency making the 
6.24 	application and the person authorizing the application.
6.25 	(b) On or before November 15 of each even-numbered year, the state court administrator 
6.26 	shall transmit to the legislature a report concerning: (1) all warrants authorizing the collection 
6.27 	of electronic communication information during the two previous calendar years; and (2) 
6.28 	all applications that were denied during the two previous calendar years. Each report shall 
6.29 	include a summary and analysis of the data required to be filed under this section. The report 
6.30 	is public and must be available for public inspection at the Legislative Reference Library 
6.31 	and the state court administrator's office and website.
7.1 	(c) Nothing in this section prohibits or restricts a service provider from producing an 
7.2 	annual report summarizing the demands or requests it receives under this section.

7.3 	Sec. 8. [626.19] USE OF UNMANNED AERIAL VEHICLES.
7.4 		Subdivision 1.Application; definitions. (a) This section applies to law enforcement 
7.5 	agencies that maintain, use, or plan to use an unmanned aerial vehicle in investigations, 
7.6 	training, or in response to emergencies, incidents, and requests for service.
7.7 	(b) For purposes of this section, the following terms have the meanings given:
7.8 	(1) "law enforcement agency" has the meaning given in section 626.84, subdivision 1; 
7.9 	and
7.10 	(2) "unmanned aerial vehicle" or "UAV" means an aircraft that is operated without the 
7.11 	possibility of direct human intervention from within or on the aircraft.
7.12 		Subd. 2.Use of unmanned aerial vehicles limited. Except as provided in subdivision 
7.13 	3, a law enforcement agency may not operate a UAV without a search warrant issued under 
7.14 	this chapter.
7.15 		Subd. 3.Authorized use. (a) A law enforcement agency may use a UAV during or 
7.16 	immediately after an emergency situation that involves the risk of death or serious physical 
7.17 	harm to a person.
7.18 	(b) A law enforcement agency may use a UAV over a public event where there is a 
7.19 	substantial risk to the safety of participants or bystanders. If a law enforcement agency 
7.20 	collects information under this paragraph it must document each use, connect each 
7.21 	deployment to a unique case number, and provide a description of the facts giving rise to a 
7.22 	substantial risk.
7.23 	(c) A law enforcement agency may operate a UAV to counter a high risk of a terrorist 
7.24 	attack by a specific individual or organization if the agency determines that credible 
7.25 	intelligence indicates this risk.
7.26 	(d) A law enforcement agency may use a UAV to prevent the loss of life and property 
7.27 	in natural or man-made disasters and to facilitate the operational planning, rescue, and 
7.28 	recovery operations in the aftermath of these disasters.
7.29 	(e) A law enforcement agency may use a UAV for officer training purposes.
7.30 	(f) A law enforcement agency may operate a UAV for a non-law-enforcement purpose 
7.31 	at the request of a government entity, as defined in section 13.02, subdivision 7a, provided 
8.1 	that the government entity makes the request in writing and specifies the reason for the 
8.2 	request and proposed period of use.
8.3 		Subd. 4.Limitations on use. (a) A law enforcement agency operating a UAV must fully 
8.4 	comply with all Federal Aviation Administration requirements and guidelines.
8.5 	(b) The governing body overseeing the law enforcement agency must approve the 
8.6 	agency's acquisition of a UAV.
8.7 	(c) Unless specifically authorized in a warrant, a law enforcement agency must use a 
8.8 	UAV to collect data only on a clearly and narrowly defined target and avoid data collection 
8.9 	on individuals, homes, or areas other than the defined target.
8.10 	(d) A law enforcement agency may not deploy a UAV with facial recognition or other 
8.11 	biometric-matching technology unless expressly authorized by a warrant.
8.12 	(e) A law enforcement agency may not equip a UAV with weapons.
8.13 	(f) A law enforcement agency may not use a UAV to collect data on public protests or 
8.14 	demonstrations unless expressly authorized by a warrant or an exception applies under 
8.15 	subdivision 3. A law enforcement agency must document which exception applies or whether 
8.16 	a warrant was obtained.
8.17 		Subd. 5.Data classification; retention. (a) Data collected by a UAV are private data 
8.18 	on individuals or nonpublic data, subject to the following:
8.19 	(1) if the individual requests a copy of the recording, data on other individuals who do 
8.20 	not consent to its release must be redacted from the copy;
8.21 	(2) UAV data may be disclosed as necessary in an emergency situation under subdivision 
8.22 	3, paragraph (a);
8.23 	(3) UAV data may be disclosed to the government entity making a request for UAV use 
8.24 	under subdivision 3, paragraph (f);
8.25 	(4) UAV data that are criminal investigative data are governed by section 13.82, 
8.26 	subdivision 7; and
8.27 	(5) UAV data that are not public data under other provisions of chapter 13 retain that 
8.28 	classification.
8.29 	(b) Section 13.04, subdivision 2, does not apply to data collected by a UAV.
9.1 	(c) Notwithstanding section 138.17, a law enforcement agency must delete data collected 
9.2 	by a UAV as soon as possible, and in no event later than seven days after collection unless 
9.3 	the data is part of an active criminal investigation.
9.4 		Subd. 6.Evidence. Information obtained or collected by a law enforcement agency in 
9.5 	violation of this section is not admissible as evidence in a criminal, administrative, or civil 
9.6 	proceeding against the data subject.
9.7 		Subd. 7.Remedies. An aggrieved party may initiate a civil action against a law 
9.8 	enforcement agency to obtain all appropriate relief to prevent or remedy a violation of this 
9.9 	section, including remedies available under chapter 13.
9.10 		Subd. 8.Written policies required. The chief officer of every state and local law 
9.11 	enforcement agency that uses or plans to use a UAV must establish and enforce a written 
9.12 	policy governing UAV use. The agency must post the written policy on its website, if the 
9.13 	agency has a website.
9.14 		Subd. 9.Notice; disclosure of warrant. (a) Within a reasonable time but not later than 
9.15 	90 days after the court unseals a warrant under this subdivision, the issuing or denying judge 
9.16 	shall cause to be served on the persons named in the warrant and the application an inventory 
9.17 	that shall include notice of:
9.18 	(1) the fact of the issuance of the warrant or the application;
9.19 	(2) the date of the issuance and the period of authorized, approved, or disapproved 
9.20 	collection of information, or the denial of the application; and
9.21 	(3) the fact that during the period information was or was not collected.
9.22 	(b) A warrant authorizing collection of information with a UAV must direct that:
9.23 	(1) the warrant be sealed for a period of 90 days or until the objective of the warrant has 
9.24 	been accomplished, whichever is shorter; and
9.25 	(2) the warrant be filed with the court administrator within ten days of the expiration of 
9.26 	the warrant.
9.27 	(c) The prosecutor may request that the warrant, supporting affidavits, and any order 
9.28 	granting the request not be filed. An order must be issued granting the request in whole or 
9.29 	in part if, from affidavits, sworn testimony, or other evidence, the court finds reasonable 
9.30 	grounds exist to believe that filing the warrant may cause the search or a related search to 
9.31 	be unsuccessful, create a substantial risk of injury to an innocent person, or severely hamper 
9.32 	an ongoing investigation.
10.1 	(d) The warrant must direct that following the commencement of any criminal proceeding 
10.2 	using evidence obtained in or as a result of the search, the supporting application or affidavit 
10.3 	must be filed either immediately or at any other time as the court directs. Until such filing, 
10.4 	the documents and materials ordered withheld from filing must be retained by the judge or 
10.5 	the judge's designee.
10.6 		Subd. 10.Reporting. (a) By January 15 of each year, each law enforcement agency that 
10.7 	deploys a UAV shall report to the commissioner of public safety the following information 
10.8 	for the preceding calendar year:
10.9 	(1) the number of times a UAV was deployed, organized by the types of incidents and 
10.10 	the types of justification for deployment;
10.11 	(2) the number of criminal investigations aided by the deployment of UAVs;
10.12 	(3) the number of deployments of UAVs for reasons other than criminal investigations; 
10.13 	and
10.14 	(4) the total cost of the agency's UAV program.
10.15 	(b) By June 15 of each year, the commissioner of public safety shall compile a full and 
10.16 	complete report summarizing the information submitted to the commissioner under paragraph 
10.17 	(a), and submit the report to the chairs and ranking minority members of the senate and 
10.18 	house of representatives committees having jurisdiction over criminal justice and public 
10.19 	safety issues and make the report public on the department's website.
10.20 	(c) By January 15 of each year, any judge who has issued a warrant under this section 
10.21 	that expired during the preceding year, or who has denied approval during that year, shall 
10.22 	report to the state court administrator:
10.23 	(1) the fact that a warrant or extension was applied for;
10.24 	(2) the kind of warrant or extension applied for;
10.25 	(3) the fact that the warrant or extension was granted as applied for, was modified, or 
10.26 	was denied;
10.27 	(4) the period of UAV use authorized by the warrant and the number and duration of 
10.28 	any extensions of the warrant;
10.29 	(5) the offense specified in the warrant or application or extension of a warrant; and
10.30 	(6) the identity of the law enforcement agency making the application and the person 
10.31 	authorizing the application.
11.1 	(d) By June 15 of each year, the state court administrator shall transmit to the chairs and 
11.2 	ranking minority members of the senate and house of representatives committees having 
11.3 	jurisdiction over criminal justice and public safety issues and post on the supreme court's 
11.4 	website a full and complete report concerning the number of applications for warrants 
11.5 	authorizing or approving operation of UAVs or disclosure of information from the operation 
11.6 	of UAVs under this section and the number of warrants and extensions granted or denied 
11.7 	under this section during the preceding calendar year. The report must include a summary 
11.8 	and analysis of the data required to be filed with the state court administrator by paragraph 
11.9 	(c).

11.10 	Sec. 9. Minnesota Statutes 2018, section 626A.08, subdivision 2, is amended to read:
11.11 		Subd. 2.Application and orders. (a) Applications made and warrants issued under this 
11.12 	chapter shall be sealed by the judge. Custody of the applications and orders shall be wherever 
11.13 	the judge directs. Such applications and orders shall be disclosed only upon a showing of 
11.14 	good cause before a judge of the district court and shall not be destroyed except on order 
11.15 	of the issuing or denying judge, and in any event shall be kept for ten years.
11.16 	(b) Notwithstanding paragraph (a), the filing, sealing, and reporting requirements for 
11.17 	applications made and warrants issued under this chapter that involve location information 
11.18 	of electronic devices, as defined in section 626A.42, are governed by section 626A.42, 
11.19 	subdivision 4. However, applications and warrants, or portions of applications and warrants, 
11.20 	that do not involve location information of electronic devices continue to be governed by 
11.21 	paragraph (a).

11.22 	Sec. 10. Minnesota Statutes 2018, section 626A.26, subdivision 3, is amended to read:
11.23 		Subd. 3.Exceptions. Subdivision 1 does not apply with respect to conduct authorized:
11.24 	(1) by the person or entity providing a wire or electronic communications service;
11.25 	(2) by a user of that service with respect to a communication of or intended for that user; 
11.26 	or
11.27 	(3) in sections section 626.085, 626A.05 to 626A.09,or 626A.28, or 626A.29.

11.28 	Sec. 11. Minnesota Statutes 2018, section 626A.27, subdivision 2, is amended to read:
11.29 		Subd. 2.Exceptions. A person or entity may divulge the contents of a communication:
11.30 	(1) to an addressee or intended recipient of the communication or an agent of the 
11.31 	addressee or intended recipient;
12.1 	(2) as otherwise authorized in section 626.085, 626A.02, subdivision 2, paragraph (a); 
12.2 	626A.05; or section 626A.28;
12.3 	(3) with the lawful consent of the originator or an addressee or intended recipient of the 
12.4 	communication, or the subscriber in the case of remote computing service;
12.5 	(4) to a person employed or authorized or whose facilities are used to forward a 
12.6 	communication to its destination;
12.7 	(5) as may be necessarily incident to the rendition of the service or to the protection of 
12.8 	the rights or property of the provider of that service; or
12.9 	(6) to a law enforcement agency, if the contents:
12.10 	(i) were inadvertently obtained by the service provider; and
12.11 	(ii) appear to pertain to the commission of a crime.

12.12 	Sec. 12. Minnesota Statutes 2018, section 626A.28, subdivision 3, is amended to read:
12.13 		Subd. 3.Records concerning electronic communication service or remote computing 
12.14 	service. (a) Except as provided in paragraph (b) or chapter 325M, a provider of electronic 
12.15 	communication service or remote computing service may disclose a record or other 
12.16 	information pertaining to a subscriber to or customer of the service, not including the contents 
12.17 	of communications covered by subdivision 1 or 2, to any person other than a governmental 
12.18 	entity.
12.19 	(b) A provider of electronic communication service or remote computing service may 
12.20 	disclose a record or other information pertaining to a subscriber to or customer of the service, 
12.21 	not including the contents of communications covered by subdivision 1 or 2, to a 
12.22 	governmental entity only when the governmental entity:
12.23 	(1) uses an administrative subpoena authorized by statute, or a grand jury subpoena;
12.24 	(2) obtains a warrant;
12.25 	(3) obtains a court order for such disclosure under subdivision 4; or
12.26 	(4) has the consent of the subscriber or customer to the disclosure.
12.27 	(c) A governmental entity receiving records or information under this subdivision is not 
12.28 	required to provide notice to a subscriber or customer.
12.29 	(d) Notwithstanding paragraph (b), a provider of electronic communication service or 
12.30 	remote computing service may not disclose location information covered by section 626A.42
12.31 	to a government entity except as provided in that section.

13.1 	Sec. 13. Minnesota Statutes 2018, section 626A.28, subdivision 4, is amended to read:
13.2 		Subd. 4.Requirements for court order. A court order for disclosure under subdivision 
13.3 	2 or 3 must issue only if the governmental entity shows that there is reason to believe the 
13.4 	contents of a wire or electronic communication, or the records or other information sought, 
13.5 	are relevant to a legitimate law enforcement inquiry. A court issuing an order pursuant to 
13.6 	this section, on a motion made promptly by the service provider, may quash or modify such 
13.7 	order, if the information or records requested are unusually voluminous in nature or 
13.8 	compliance with such order otherwise would cause an undue burden on such provider.

13.9 	Sec. 14. Minnesota Statutes 2018, section 626A.28, subdivision 5, is amended to read:
13.10 		Subd. 5.No cause of action against a provider disclosing certain information. No 
13.11 	cause of action lies in any court against any provider of wire or electronic communication 
13.12 	service, its officers, employees, agents, or other specified persons for providing information, 
13.13 	facilities, or assistance in accordance with the terms of a court order, warrant, subpoena, or 
13.14 	certification under sectionssection 626.085 or 626A.26 to 626A.34.

13.15 	Sec. 15. Minnesota Statutes 2018, section 626A.31, subdivision 1, is amended to read:
13.16 		Subdivision 1.Payment. Except as otherwise provided in subdivision 3, a governmental 
13.17 	entity obtaining the contents of communications, records, or other information under sections
13.18 	section626A.27, or626A.28, and 626A.29 shall pay to the person or entity assembling or 
13.19 	providing the information a fee for reimbursement for costs that are reasonably necessary 
13.20 	and that have been directly incurred in searching for, assembling, reproducing, or otherwise 
13.21 	providing the information. The reimbursable costs must include any costs due to necessary 
13.22 	disruption of normal operations of the electronic communication service or remote computing 
13.23 	service in which the information may be stored.

13.24 	Sec. 16. Minnesota Statutes 2018, section 626A.37, subdivision 4, is amended to read:
13.25 		Subd. 4.Nondisclosure of existence of pen register, trap and trace device, or mobile 
13.26 	tracking device. (a) An order authorizing or approving the installation and use of a pen 
13.27 	register, trap and trace device, or a mobile tracking device must direct that:
13.28 	(1) the order be sealed until otherwise ordered by the court; and
13.29 	(2) the person owning or leasing the line to which the pen register or a trap and trace 
13.30 	device is attached, or who has been ordered by the court to provide assistance to the applicant, 
13.31 	not disclose the existence of the pen register, trap and trace device, mobile tracking device, 
14.1 	or the existence of the investigation to the listed subscriber, or to any other person, unless 
14.2 	or until otherwise ordered by the court.
14.3 	(b) Paragraph (a) does not apply to an order that involves location information of 
14.4 	electronic devices, as defined in section 626A.42. Instead, the filing, sealing, and reporting 
14.5 	requirements for those orders are governed by section 626A.42, subdivision 4. However, 
14.6 	any portion of an order that does not involve location information of electronic devices 
14.7 	continues to be governed by paragraph (a).

14.8 	Sec. 17. REPEALER.
 14.9 	Minnesota Statutes 2018, sections 13.72, subdivision 9; 626A.28, subdivisions 1 and 2; 
14.10 	626A.29; and 626A.30, are repealed.

14.11 	Sec. 18. EFFECTIVE DATE.
 14.12 	Sections 1, 2, 6, 9, and 16 are effective the day following final enactment.

APPENDIX 

Repealed Minnesota Statutes: S1263-2 

13.72 TRANSPORTATION DEPARTMENT DATA.Subd. 9.Rideshare data. 
The following data on participants, collected by the Minnesota Department of Transportation and the Metropolitan Council to administer rideshare programs, are classified as private under section 13.02, subdivision 12: residential address and telephone number; beginning and ending work hours; current mode of commuting to and from work; and type of rideshare service information requested. 

626A.28 REQUIREMENTS FOR GOVERNMENTAL ACCESS.Subdivision 1.Contents of electronic communications in electronic storage. 
A governmental entity may require the disclosure by a provider of electronic communication service of the contents of an electronic communication that is in electronic storage in an electronic communications system for 180 days or less only under a warrant. A government entity may require the disclosure by a provider of electronic communications services of the contents of an electronic communication that has been in electronic storage in an electronic communications system for more than 180 days by the means available under subdivision 2. 

Subd. 2.Contents of electronic communications in a remote computing service. 
(a) A governmental entity may require a provider of remote computing service to disclose the contents of electronic communication to which this paragraph is made applicable by paragraph (b): 

(1) without required notice to the subscriber or customer, if the governmental entity obtains a warrant; or 

(2) with prior notice if the governmental entity: 

(i) uses an administrative subpoena authorized by statute or a grand jury subpoena; or 

(ii) obtains a court order for such disclosure under subdivision 4; 

except that delayed notice may be given under section 626A.30. 

(b) Paragraph (a) is applicable with respect to any electronic communication that is held or maintained on that service: 

(1) on behalf of, and received by means of electronic transmission from, or created by means of computer processing of communications received by means of electronic transmission from, a subscriber or customer of such remote computing service; and 

(2) solely for the purpose of providing storage or computer processing services to the subscriber or customer, if the provider is not authorized to access the contents of any communications for purposes of providing any services other than storage or computer processing. 

626A.29 BACKUP PRESERVATION.Subdivision 1.Backup copy. 
(a) A governmental entity acting under section 626A.28, subdivision 2, paragraph (b), may include in its subpoena or court order a requirement that the service provider to whom the request is directed create a backup copy of the contents of the electronic communications sought in order to preserve those communications. Without notifying the subscriber or customer of the subpoena or court order, the service provider shall create a backup copy, as soon as practicable, consistent with its regular business practices and shall confirm to the governmental entity that the backup copy has been made. The backup copy must be created within two business days after receipt by the service provider of the subpoena or court order. 

(b) Notice to the subscriber or customer must be made by the governmental entity within three days after receipt of the confirmation, unless notice is delayed under section 626A.30, subdivision 1. 

(c) The service provider must not destroy a backup copy until the later of: 

(1) the delivery of the information; or 

(2) the resolution of any proceedings, including appeals of any proceeding, concerning the subpoena or court order. 

(d) The service provider shall release the backup copy to the requesting governmental entity no sooner than 14 days after the governmental entity's notice to the subscriber or customer if the service provider: 

(1) has not received notice from the subscriber or customer that the subscriber or customer has challenged the governmental entity's request; and 

(2) has not initiated proceedings to challenge the request of the governmental entity. 

(e) A governmental entity may seek to require the creation of a backup copy under paragraph (a) if in its sole discretion the entity determines that there is reason to believe that notification under section 626A.28 of the existence of the subpoena or court order may result in destruction of or tampering with evidence. This determination is not subject to challenge by the subscriber or customer or service provider. 

Subd. 2.Customer challenges. 
(a) Within 14 days after notice by the governmental entity to the subscriber or customer under subdivision 1, paragraph (b), the subscriber or customer may file a motion to quash the subpoena or vacate the court order, with copies served upon the governmental entity and with written notice of the challenge to the service provider. A motion to vacate a court order must be filed in the court which issued the order. A motion to quash a subpoena must be filed in the district court of the county in which the governmental entity issuing the subpoena is located. The motion or application must contain an affidavit or sworn statement: 

(1) stating that the applicant is a customer or subscriber to the service from which the contents of electronic communications maintained for the applicant have been sought; and 

(2) stating the applicant's reasons for believing that the records sought are not relevant to a legitimate law enforcement inquiry or that there has not been substantial compliance with the provisions of this chapter in some other respect. 

(b) Service must be made under this section upon a governmental entity by delivering or mailing by registered or certified mail a copy of the papers to the person, office, or department specified in the notice which the customer has received under sections 626A.26 to 626A.34. For the purposes of this section, the term "delivery" means handing it to the person specified in the notice or handing it to the person in charge of the office or department specified in the notice or the designee of the person in charge. 

(c) If the court finds that the customer has complied with paragraphs (a) and (b), the court shall order the governmental entity to file a sworn response. The response may be filed in camera if the governmental entity includes in its response the reasons that make in camera review appropriate. If the court is unable to determine the motion or application on the basis of the parties' initial allegations and response, the court may conduct additional proceedings as it considers appropriate. Proceedings must be completed and the motion or application decided as soon as practicable after the filing of the governmental entity's response. 

(d) If the court finds that the applicant is not the subscriber or customer for whom the communications sought by the governmental entity are maintained, or that there is a reason to believe that the law enforcement inquiry is legitimate and that the communications sought are relevant to that inquiry, it shall deny the motion or application and order the process enforced. If the court finds that the applicant is the subscriber or customer for whom the communications sought by the governmental entity are maintained, and that there is not a reason to believe that the communications sought are relevant to a legitimate law enforcement inquiry, or that there has not been substantial compliance with the provisions of sections 626A.26 to 626A.34, it shall order the process quashed. 

(e) A court order denying a motion or application under this section shall not be deemed a final order and no interlocutory appeal may be taken therefrom by the customer. 

626A.30 DELAYED NOTICE.Subdivision 1.Delay of notification. 
(a) A governmental entity acting under section 626A.28, subdivision 2, may: 

(1) where a court order is sought, include in the application a request, which the court shall grant, for an order delaying the notification required under section 626A.28, subdivision 2, for a period not to exceed 90 days, if the court determines that there is reason to believe that notification of the existence of the court order may have an adverse result described in paragraph (b); or 

(2) where an administrative subpoena or a grand jury subpoena is obtained, delay the notification required under section 626A.28 for a period not to exceed 90 days upon the execution of a written certification of a supervisory official that there is reason to believe that notification of the existence of the subpoena may have an adverse result described in paragraph (b). 

(b) An adverse result for the purposes of paragraph (a) is: 

(1) endangering the life or physical safety of an individual; 

(2) flight from prosecution; 

(3) destruction of or tampering with evidence; 

(4) intimidation of potential witnesses; or 

(5) otherwise seriously jeopardizing an investigation or unduly delaying a trial. 

(c) The governmental entity shall maintain a true copy of certification under paragraph (a), clause (2). 

(d) Extensions of the delay of notification provided in section 626A.28 of up to 90 days each may be granted by the court upon application, or by certification by a governmental entity, but only in accordance with subdivision 2. 

(e) Upon expiration of the period of delay of notification under paragraph (a) or (d), the governmental entity shall serve upon, or deliver by registered or first-class mail to, the customer or subscriber a copy of the process or request together with notice that: 

(1) states with reasonable specificity the nature of the law enforcement inquiry; and 

(2) informs the customer or subscriber: 

(i) that information maintained for the customer or subscriber by the service provider named in the process or request was supplied to or requested by that governmental authority and the date on which the supplying or request took place; 

(ii) that notification of the customer or subscriber was delayed; 

(iii) what governmental entity or court made the certification or determination under which that delay was made; and 

(iv) which provision of sections 626A.26 to 626A.34 allowed such delay. 

(f) As used in this subdivision, the term "supervisory official" means a peace officer with the rank of sergeant, or its equivalent, or above, a special agent in charge from the Bureau of Criminal Apprehension, the attorney general, the head of the attorney general's criminal division, a county attorney, or the head of a county attorney's criminal division. 

Subd. 2.Preclusion of notice to subject of governmental access. 
A governmental entity acting under section 626A.28 when it is not required to notify the subscriber or customer under section 626A.28, subdivision 2, paragraph (a), or to the extent that it may delay notice under subdivision 1, may apply to a court for an order commanding a provider of electronic communications service or remote computing service to whom a warrant, subpoena, or court order is directed, for a period as the court considers appropriate, not to notify any other person of the existence of the warrant, subpoena, or court order. The court shall enter an order if it determines that there is reason to believe that notification of the existence of the warrant, subpoena, or court order will result in: 

(1) endangering the life or physical safety of an individual; 

(2) flight from prosecution; 

(3) destruction of or tampering with evidence; 

(4) intimidation of potential witnesses; or 

(5) otherwise seriously jeopardizing an investigation or unduly delaying a trial.