Doe A v. Veer Hospitality Phoenix LLC

District Court, W.D. Washington·Decided July 22, 2025·No. 2:24-cv-01270·Unknown

Opinion

UNITED STATES DISTRICT COURT WESTERN DISTRICT OF WASHINGTON AT SEATTLE JANE DOE A, CASE NO. C24-1270 MJP Plaintiff, ORDER ON PLAINTIFF’S MOTION FOR PROTECTIVE v. ORDER SEATAC HOTELS LLC, et al., Defendants. This matter comes before the Court on Plaintiff’s Motion for Protective Order. (Dkt. No. 112.) Having reviewed the Motion, Defendants’ Response (Dkt. No. 113), the Reply (Dkt. No. 115), and all supporting materials, the Court GRANTS in part the Motion, and ENTERS a Protective Order, separately from this Order. The Court finds this matter suitable for decision without oral argument. Starting in 2012, Jane Doe A was forced into commercial sex trafficking at two SeaTac hotels: Motel 6 and Quality Inn. (Amended Complaint ¶ 30 (Dkt. No. 74.) For approximately four years, Doe A’s traffickers would rotate her between these hotels, where she was forced to

work for “days at a time, encountering the same staff” and taking well over five “dates” per day. (AC ¶ 31, 40.) Doe A has filed suit against the owners/franchisees of both hotels, and the franchisors, alleging that they participated and benefitted from the forced sex trafficking of Doe A in violation of the Trafficking Victims Protection Reauthorization Act (TVPRA). Doe A now seeks entry of a protective order concerning the exchange of confidential information, including her identity. Although the Parties were able to reach agreement on many aspects of a stipulated protective order, they dispute several provisions, which the Court reviews. First, the Parties dispute how and whether Defendants must obtain Court approval before sharing Doe A’s identity with her traffickers. Second, they dispute whether Doe A may disclose certain discovery to “coordinating” counsel in other TVPRA cases pending against the same

Defendants. Third, the Parties dispute whether the protective order should include a provision for “highly confidential” information. Fourth, the Parties dispute whether confidential discovery materials can be retained after the litigation terminates. Fifth, the Parties dispute the scope of who must sign an acknowledgement to be bound by the Protective Order before accessing or being shown confidential information. A. Protective Order Standard Under Rule 26(c)(1), “[t]he court may, for good cause, issue an order to protect a party or person from annoyance, embarrassment, oppression, or undue burden or expense[.]” Fed. R. Civ.

P. 26(c)(1). “A party asserting good cause bears the burden, for each particular document it seeks to protect, of showing that specific prejudice or harm will result if no protective order is granted.” Foltz v. State Farm Mut. Auto. Ins. Co., 331 F.3d 1122, 1130 (9th Cir. 2003). “Broad allegations of harm, unsubstantiated by specific examples or articulated reasoning, do not satisfy

the Rule 26(c) test.” Beckman Indus., Inc. v. Int’l Ins. Co., 966 F.3d 470, 476 (9th Cir. 1992) (quotation and citation omitted). B. Court Approval to Contact Trafficker is Reasonable The Court agrees in principle with Doe A that Defendants must obtain prior-Court approval before sharing her identity with her traffickers. But, as reflected in the Protective Order, the Court adopts a different protocol than what Doe A proposes. First, Doe A has identified a reasonable fear for her safety if her identity is given to her traffickers. As alleged, Doe A is the victim of sex trafficking, who endured four years of coerced commercial sexual acts at the hands of her traffickers in the SeaTac area. (See Am. Compl. ¶¶ 30-31, 34-42.) Doe A’s traffickers used threats of force against her and her family, and Doe A

now argues that she continues to fear for her safety from her traffickers. Although Doe A has not filed a declaration, her counsel avers that “Plaintiff lives in a constant state of fear that her traffickers or their associated will harm her and her family.” (Declaration of Meagan Verschueren ¶ 8 (Dkt. No. 112-1).) Based on the review of the briefing, it does not appear that Defendants dispute Doe A’s general fear of harm from her traffickers. As Doe A’s counsel avers, the Parties “agree Defendants must provide notice to Plaintiff before contacting her traffickers and/or their associates[.]” (Id. ¶ 9.) Indeed, Defendants agree that Plaintiff should be permitted to use a pseudonym in pre-trial filings. (See Defs. Resp. at 1.) Based on the record before the Court,

it finds that Doe A has a fear of harm from her traffickers if her identity is released to them. This fear justifies some form of protective order. The Court finds that a blend of the proposals submitted by the Parties adequately protects Doe A from harm. The Court reviews the competing proposals and then explains its reasoning.

Doe A proposes that Defendant must provide the Court with an ex-parte notice and obtain the Court’s approval before contacting revealing her identity to her traffickers. (See Plaintiff’s Proposed Protective Order § IV(E) (Dkt. No. 112-1 at 68).) Under Doe A’s rubric, Defendants must provide Doe A and the Court with an ex-parte application and notice that describes the information sought, why the information is sought from the traffickers and not someone else, any alternative means to get that information, and the necessity of disclosing the name and identity to the traffickers. (Id.) The Court is then to weigh the request to see if it is relevant and “proportional to the needs of the case and the risks involved.” (Id.) If the Court approves the request, Defendants then have to give Plaintiff 14-days’ notice of where the contact will occur and all the information that will be disclosed regarding Plaintiff. (Id. § IV(E)(1).) Doe A suggests

that this methodology adopted in a similar case in this District: Doe v. Salesforce.com Inc., C24- 435 TL (W.D. Wash.). This is largely accurate, though the Protective Order in Salesforce does not require evidence as to alternative means or any statement that the Court would weigh the “risks involved” in determining whether to allow the disclosure. See id., Dkt. No. 94. Defendants’ counter-proposal puts the burden on Doe A to move for a new protective order after Defendants identify their desire to contact the traffickers and share Doe A’s identity with them. (Defendants’ Proposed Protective Order § 3(G) (Dkt. No. 114 at 16).) Under Defendants’ proposal, they would merely give notice of the contact at least 20 days before it occurs, and Doe A would then need to move for a protective order after meeting and conferring.

(Id.) The proposal does not contain any provision on how the Court would assess such a motion for protective order. The Court finds that, with small alterations, Doe A’s proposed methodology is more appropriate given the existing evidence of harm that could arise with the disclosure of her

identity to her traffickers and the relative burdens. Requiring Defendants to obtain approval before disclosing Plaintiff’s identity to her traffickers reasonably allows the Court to determine whether the risk of harm to Doe A from the specific disclosure is proportional to the needs of the case. That said, the Court believes it is appropriate to require Doe A to file a response to Defendants’ request for approval before the Court rules. This also allows Doe A to outline any specific concerns with the proposed disclosure and build an evidentiary record as to why the disclosure might be improper. It also gives the Court an opportunity to interrogate the issue with input from both Parties. As detailed in the Protective Order, Defendants must file a sealed request with the Court to disclose Doe A’s identity to her traffickers and Doe A, who shall get notice, must then file a sealed response to identify specific concerns and provide supporting

Free access — add to your briefcase to read the full text and ask questions with AI

Doe A v. Veer Hospitality Phoenix LLC, (W.D. Wash. 2025).

Doe A v. Veer Hospitality Phoenix LLC (Doe A v. Veer Hospitality Phoenix LLC) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related