Three weeks after refusing to compel a defamation defendant to consent to his AI providers releasing his chats, a federal court ordered him to sign consent forms, fill in every field, get them notarized, and send them to OpenAI and xAI himself. The orders that got there add up to a practical checklist for getting data out of an AI provider: identify the accounts, learn the provider’s requirements, draft the consent to match, start with deletion logs, and use the party’s own export. Reading time: approximately 10 minutes.
Meet and Confer Podcast · Kelly Twigger · 🎧 Listen · 📄 Case in Minerva26: Fontainebleau Fla. Hotel, LLC v. Botach, No. 1:25-cv-20251, ECF Nos. 322 and 330, · Decision: Orders After Discovery Hearings: limited consent for deletion logs ordered (ECF No. 322); expanded, notarized consent for all account data and content ordered after the first consent was modified, with Rule 37 fees awarded and privilege waiver taken under advisement (ECF No. 330) · Date: Signed November 6 and November 11, 2026 · Judge: United States Magistrate Judge Marty Fulgueira Elfenbein · Court: United States District Court, Southern District of Florida
Read the full order on Minerva26 →
Listen on Meet and Confer → | Read the transcript →
By Kelly Twigger
Podcast | Transcript
Discoverable Isn’t the Same as Obtainable
In our last episode, United States Magistrate Judge Marty Fulgueira Elfenbein of the Southern District of Florida held that a defamation defendant’s AI prompts were discoverable because they could show the specific intent to harm that removes Florida’s cap on punitive damages. She also refused to make the defendant sign consent forms so the AI providers would release his chats. Three weeks and a string of orders later, the same court ordered him to sign those consent forms, fill in every field, get them notarized, and send them to OpenAI and xAI himself, from the email addresses on his accounts.
The Court didn’t change its rule. The record changed. And the record shows, step by step, what it actually takes to get information out of an AI provider. That’s the lesson of this episode: knowing AI chats are discoverable is only the first step. Getting them is a process, and you need to know it before you need it.
One correction from our last episode. We reported that no objection to the October 21 order had been filed, which was true when we recorded. Later on October 30, Boteach filed objections with District Judge Jeffrey T. Kuntz under Rule 72(a) (ECF No. 309), arguing that the hotel had ample opportunity to seek this discovery earlier under Rule 26(b)(2)(C)(ii), that the allowed categories need a tighter connection to the injury, and that the requests aren’t proportional. The hotel opposed on November 13, and Judge Kuntz hasn’t ruled.
Case of the Week
How the Consent Door Opened
The case is Fontainebleau Florida Hotel, LLC v. Botach, a defamation case headed to a damages trial in February 2027. Liability is resolved, and the hotel is seeking uncapped punitive damages, which turn on whether the defendant, Shmuley Boteach, intended to harm the hotel. On October 21, in ECF No. 289, Magistrate Judge Elfenbein allowed discovery of his AI chats about the hotel and its people, including deleted chats, from him and through subpoenas to four AI providers. She denied the hotel’s request to compel consent, but left a door open: if the hotel hit a specific legal or practical impediment that ordinary subpoenas couldn’t solve, it could come back with a particularized showing.
The production deadline of October 30 passed without Boteach producing AI content, after Judge Kuntz denied an emergency stay that afternoon (ECF No. 308). At a November 5 hearing, memorialized in ECF No. 322, the hotel told the Court that the AI providers had said two things: they maintain deletion logs showing whether communications were deleted, and they would not release those logs without the account holder’s consent. The order doesn’t say whether that came from responses to the subpoenas or from the hotel’s counsel contacting the providers directly. Either way, the hotel was talking to the providers, and that was the particularized showing the Court had asked for.
Boteach said he had already obtained his own account data from ChatGPT and Grok and sent it to an eDiscovery vendor, and that a broader consent would duplicate that work. The Court split the difference. It ordered him to finish the vendor review, produce responsive nonprivileged communications, and log anything withheld under Rule 26(b)(5)(A). And it ordered him to sign a consent limited to deletion logs, so the providers would be asked only whether anything was deleted, not for a second copy of everything. The Court made no finding that Boteach deleted anything or engaged in spoliation
The Consent Form That Didn’t Work
At the continued hearing on November 9, memorialized in ECF No. 330, the hotel reported that Boteach had signed the consent but materially modified the form, left out the account-identifying information and the notarization, and sent it through his lawyers instead of from the email addresses on his AI accounts. The providers would not process it. The hotel’s counsel read into the record an email from in-house counsel for ChatGPT explaining what was wrong. Boteach acknowledged signing the forms but disputed whether some of the requested information was necessary, and said his account data was still being processed by his vendor.
The Court found that the consent did not meet the requirements the providers needed to process it, and that his failure to timely produce AI account data in his possession, custody, or control continued to violate its orders. In the Court’s words, his modification of the required form “rendered it useless.” These providers follow their processes to the letter; the processes are audited, and the companies need to be able to show they followed them.
The Court’s Checklist
With discovery closing and no AI content produced, the Court expanded the consent and spelled out exactly how it had to be done. This is the checklist:
An updated form from the requesting party. The hotel prepares consent forms authorizing the providers, including ChatGPT and OpenAI and Grok and xAI, to disclose all account data and content, including deletion logs.
No changes to the language. Boteach must complete and sign the forms without altering or qualifying the language the Court required.
Every account identifier, notarized. He must fill in usernames, email addresses, and the physical addresses associated with the accounts, and have the forms notarized.
Sent from the account itself. He must send the forms directly to the providers by 9 a.m. on November 12 from the email address on each AI account, not from any other address, including his lawyers’.
The provider’s own process. For xAI, he must also submit the authorization through xAI’s privacy portal, because that is what xAI requires.
The Court kept its no-duplication structure: if the deletion logs show nothing was deleted, no second review is required; if they show deletions, Boteach must review the additional data and produce what is responsive. It also took under advisement the hotel’s request to find privilege waived because no log had been served, ordered a Rule 26(b)(5)(A) log, and awarded the hotel its fees for the November 5 and 9 hearings under Rule 37(b)(2)(C), finding that Boteach had violated at least two prior orders without substantial justification.
The Vendor Gets Called In
On November 10, in a paperless order (ECF No. 325), the Court required a knowledgeable representative of Boteach’s eDiscovery vendor, the one “processing and running the search terms on the Court-ordered artificial intelligence discovery,” to appear at the November 12 status conference and answer the Court’s questions. You don’t see that often.
Two things stand out. First, the AI data is being searched with search terms, like any other ESI, and that is potentially a problem. AI conversations are their own kind of source, and you have to guess what terms will capture the responsive content, so the search terms used here matter. Second, after weeks of hearing that the data was still being processed, the Court wanted to hear directly from the people processing it. The conference lasted two hours and ten minutes, with a written order to follow that had not been entered as of our recording. On November 13, Boteach filed a notice of compliance stating he served his AI data on the hotel that day, two weeks after the original deadline. The notice doesn’t say what was produced, whether a privilege log came with it, or whether the consents went to the providers.
Your Checklist for Getting Data From an AI Provider
Everything in this story comes down to the steps you need to take to get information from an AI provider. Here is how I break them down.
Identify the tools and accounts early. You can’t draft a consent or a subpoena without knowing which providers, which accounts, and which email addresses are involved. Ask in an interrogatory or deposition, early enough to account for a 30-day response time. Better yet, put it in your Rule 16 report so the parties agree to exchange that information during the meet and confer. Third-party subpoenas take time, and here the answer may decide the punitive damages case.
Talk to the provider’s legal team before you draft anything. The hotel learned from the providers themselves that they keep deletion logs and need consent to release them, and that shaped every order that followed. Ask what they keep, how long they keep it, and exactly what a consent must include: the form, the account identifiers, notarization, where it must come from, and whether there is a portal. We don’t know from these orders whether the hotel served the subpoenas first to start that conversation, and many companies require that before they will talk to you. Start early.
Draft the consent to the provider’s specifications and ask the court to order it signed without changes. ECF No. 330 shows what happens when a party alters the form or sends it the wrong way: it doesn’t work, and you lose time you may not have. Cite this case as authority for why the form must be completed as written, and be clear with the court about your timeline.
Use deletion logs as your first step. If the other side says it still has its accounts and can produce the data, the logs tell you whether you need anything more. It’s the same idea as the sampling we’ve used for years with other sources of ESI, it’s a targeted ask a court is more likely to grant, and it’s exactly where this Court started.
Remember the party’s own export. The Court treated Boteach’s AI account data, meaning his actual inputs and outputs, as within his possession, custody, or control. The party’s own export may be the fastest source, and the provider’s records become the check on it: was anything deleted, and is there content at the provider that no longer exists in the user’s account?
The Rules Behind It
None of the orders in this case cite the following rule sections. This is my analysis of why the Court’s approach makes sense under rules you already know.
Rule 26(b)(2)(B) addresses ESI from sources that are not reasonably accessible because of undue burden or cost. It’s addressed less often now than when backup tapes were the issue, but “reasonably accessible” takes on new meaning here. A chat a user deletes may look gone from the user’s side, but if the provider still has it, or has a log showing it was deleted, the information is accessible from a different source. Deleting a chat on your end doesn’t take it out of discovery.
Rule 26(b)(2)(C)(i) limits discovery that can be obtained from a more convenient, less burdensome, or less expensive source. That was essentially Boteach’s argument on November 5, and the Court’s structure respected it by starting with deletion logs only and keeping the no-second-review rule when it expanded the consent.
Rule 37(e) sanctions apply only when ESI is lost and cannot be restored or replaced through additional discovery. If something exists at another source, it’s findable and may not be lost at all, which is why deletion logs matter so much. They can answer the spoliation question before anyone has to litigate it.
What the orders do say is that Boteach’s AI account data was in his possession, custody, or control, the language of Rule 34. If a user can export the account, the data is theirs to produce, which is consistent with existing case law on possession, custody, or control, now applied to AI artifacts. And on the Stored Communications Act, which I raised last episode: none of these orders mention it, and this is not a case where providers refused a subpoena under the statute. The record shows the providers required the user’s consent before releasing deletion logs and account data. That’s consistent with how the SCA has been applied to other providers, but the Court didn’t rely on it, and you shouldn’t say it did.
What to Do This Week
Recognize that discoverable isn’t the same as obtainable. The order in our last episode told us AI prompts are discoverable when they go to an element. These orders show the work it takes to actually get them.
Get the provider’s requirements first. Build your consent form around them. Account identifiers, notarization, sending from the account email, and any portal submission all mattered here.
Ask for deletion logs early. They are the most efficient way to answer whether anything was lost if you have a basis to suspect it, and they let a court avoid ordering duplicative review.
If you’re producing, take the deadlines seriously and start your vendor immediately. This Court called the vendor into the courtroom, awarded fees under Rule 37, and took waiver of privilege under advisement because the log wasn’t served on time.
What to Watch Next
I’m watching five things: Judge Kuntz’s ruling on Boteach’s Rule 72(a) objections to the October 21 order, which are now fully briefed; the written order from the November 12 conference, which should tell us what the vendor said and what the Court ordered next; what the November 13 production contained, whether the consents reached the providers, and what the deletion logs show; whether the Court finds privilege waived; and the amount of the fee award, along with whether the hotel files the civil contempt motion the Court authorized. All of it has to play out before a February 2027 damages trial.
Listen to the full episode
This week’s Case of the Week segment of the Meet and Confer podcast, Episode 198, marks six years of the series and walks through every Fontainebleau order since our last episode, including the checklist for getting data from an AI provider. Listen on Meet and Confer →
See Minerva26 in action
Minerva26 is the discovery intelligence platform that connects case law, rules, and real-world workflows. We curate and tag close to 50,000 discovery decisions by issue, including every order on the Fontainebleau docket under the Generative AI and Prompts tags. And because getting information from an AI provider starts with the right notice, Minerva26 now includes a preservation notice template that asks the provider to hold the account data and tell you exactly what it needs before it will disclose it, including its consent requirements. Book a 30-minute demo
Related on Minerva26: Fontainebleau Fla. Hotel, LLC v. Botach (Oct. 21, 2026, ECF No. 289) · Fontainebleau Fla. Hotel, LLC v. Botach (Oct. 28, 2026, ECF No. 303) · Fontainebleau Fla. Hotel, LLC v. Botach (Oct. 30, 2026, ECF No. 308) · Fontainebleau Fla. Hotel, LLC v. Botach (Nov. 6, 2026, ECF No. 322) · Fontainebleau Fla. Hotel, LLC v. Botach (Nov. 11, 2026, ECF No. 330)
This decision is available on the Minerva26 platform with full issue tagging. If you’re a litigator navigating discovery strategy and want to stay ahead of decisions like this one, visit Minerva26.com to learn more or schedule a demo. Every decision covered on Case of the Week is searchable by issue, jurisdiction, and judge.
Kelly Twigger is CEO and founder of Minerva26 and Principal at ESI Attorneys. She has been a discovery strategist and practicing attorney for nearly 30 years. Case of the Week is a segment of the Meet and Confer podcast, breaking down one recent ESI discovery decision each week into practical strategy you can use.
- 📩 Get the newsletter
- 🎧 Listen to Meet and Confer
- 🔁 Share this post on LinkedIn


