{"slug": "how-law-enforcement-can-request-chatgpt-user-data-via-openai-kodex-lers-portal", "title": "How Law Enforcement Can Request ChatGPT User Data via OpenAI Kodex (LERS Portal)", "summary": "OpenAI received 794 government requests for ChatGPT user data in the first half of 2026 and disclosed data in 539 of them, covering 822 accounts, according to the company's H1 2026 transparency report and Government User Data Request Policy. The 794 total — 620 non-content requests (441 disclosed, 679 accounts), 146 content requests (88 disclosed, 130 accounts) and 28 emergency requests (10 disclosed, 13 accounts) — rose 157% from 309 in H2 2025 and more than elevenfold from 71 in H2 2024, with the disclosure share holding between 68% and 76% across the four reports. Agencies submit requests through OpenAI's law enforcement request portal on Kodex, where non-content data requires a subpoena, court order, search warrant or equivalent and content requires a valid warrant or equivalent, and a separate 250–499 U.S. national security requests (FISA/NSLs) affecting 250–499 accounts are excluded from the table.", "body_md": "[Back to News](https://ministryofcyberaffairs.com/)\n\n# How Law Enforcement Can Request ChatGPT User Data via OpenAI Kodex (LERS Portal)\n\nA practical guide to OpenAI law enforcement requests for ChatGPT user data: non-content, content and emergency categories; H1 2026 disclosure figures; and how to submit through OpenAI's law enforcement request portal (LERS) on Kodex, with warrant, MLAT and user-notice rules from OpenAI policy.\n\nOpenAI's Government User Data Request Policy and H1 2026 transparency report explain how agencies can seek **ChatGPT / OpenAI** account information through lawful process. The practical submission route is **OpenAI's law enforcement request portal (LERS) on Kodex**, a generic shorthand for that government workflow, not an OpenAI product name.\n\n## What an OpenAI law enforcement request can cover\n\n**A. Non-content data**, The report lists name, email address, payment information, and transaction history. For OpenAI US, the policy requires a subpoena, court order, search warrant, or equivalent.\n\n**B. Content data**, Legal process such as search warrants for text or files input or output with OpenAI services (prompts/inputs, generated responses, uploaded or generated files). For OpenAI US, content is disclosed only on a valid warrant or equivalent.\n\n**C. Emergency requests**, Limited disclosures where OpenAI believes data is needed to prevent an emergency involving death or serious physical injury. Requests are case-by-case and must show the threat, urgency, and why ordinary process cannot be obtained in time.\n\n## Government requests: January–June 2026\n\n| Request type | Received | Disclosed | Accounts | \n|---|---|---|---|\n| Non-Content | 620 | 441 | 679 | \n| Content | 146 | 88 | 130 | \n| Emergency | 28 | 10 | 13 | \n| Total | 794 | 539 | 822 | \n\n- Non-Content, received 620; disclosed 441; accounts 679\n- Content, received 146; disclosed 88; accounts 130\n- Emergency, received 28; disclosed 10; accounts 13\n- Total, received 794; disclosed 539; accounts 822\n\nSeparately: **250–499** U.S. national security requests (FISA/NSLs) affecting **250–499** accounts, excluded from the table.\n\n## Requests to OpenAI rose from 71 to 794 in 18 months\n\nGovernment requests for user data received by OpenAI have grown more than elevenfold across its last four transparency reports, while the share in which data was disclosed stayed between 68% and 76%:\n\n- H2 2024: **71** requests, 54 with data disclosed (76%)\n- H1 2025: **146** requests, 105 disclosed (72%)\n- H2 2025: **309** requests, 209 disclosed (68%)\n- H1 2026: **794** requests, 539 disclosed (68%)\n\nRequests more than doubled in the latest six months alone, rising 157% from 309 to 794. Totals exclude U.S. national security requests, which OpenAI reports only in ranges.\n\n## How to submit via the ChatGPT / OpenAI LERS portal on Kodex\n\nPortal: [https://app.kodex.us/openai/signin](https://app.kodex.us/openai/signin)\n\nAll government user-data requests to OpenAI US or OpenAI Ireland must go through Kodex. OpenAI's Kodex help article (title emphasises content removal; body also covers **User Data**) says:\n\n1. Sign in with a verified government account.\n2. Select the OpenAI entity (OpCo, LLC outside EEA/Switzerland; Ireland Ltd. for EEA/Switzerland).\n3. Choose **User Data** for an OpenAI law enforcement request (Content Removal is for takedowns only).\n4. Attach required legal process.\n5. Identify the account unambiguously.\n6. Specify data categories and time period.\n\n## What investigators should include\n\nPolicy minimums: valid enforceable process; officer name/contact; particular record categories; production date if needed; unambiguous account ID; specific time period. Add case/agency references and a short necessity note so the packet matches the process. Emergencies also need the emergency facts, why process cannot wait, and how the data averts the harm.\n\n## Legal-process rules that matter internationally\n\n- **OpenAI US:** non-content via subpoena/court order/warrant/equivalent; content via warrant/equivalent.\n- **Non-U.S. to OpenAI US:** possible direct foreign process if compulsory in the requester's country and consistent with U.S. law/OpenAI policy; otherwise MLAT, CLOUD Act § 2523 agreements, letters rogatory, or similar routes that yield U.S. process.\n- **OpenAI Ireland:** Irish judicial order for Irish authorities; non-Irish agencies use diplomatic/MLA Irish process.\n- **User notice** before disclosure unless prohibited by law; limited exceptions; possible delayed notice.\n- **Preservation (OpenAI US):** up to 90 days under 18 U.S.C. § 2703(f), plus 90-day extension. Without preservation, records may not be retained in the normal course of business.\n\n## Technical records not itemised in the transparency tables\n\nThe H1 report does not list IP addresses, login history, device identifiers, session logs, geolocation, deleted conversations, or API usage logs as separate categories. Confirm availability and required process via Kodex, and preserve early where the policy allows.\n\n## Official resources\n\n- Transparency: [https://openai.com/trust-and-transparency/](https://openai.com/trust-and-transparency/)\n- Policy: [https://cdn.openai.com/pdf/openai-law-enforcement-policy-v.2025-12.pdf](https://cdn.openai.com/pdf/openai-law-enforcement-policy-v.2025-12.pdf)\n- Kodex portal: [https://app.kodex.us/openai/signin](https://app.kodex.us/openai/signin)\n- Kodex guidance (content removal + user-data paths): [https://help.openai.com/en/articles/20001621-submitting-government-content-removal-requests-with-kodex](https://help.openai.com/en/articles/20001621-submitting-government-content-removal-requests-with-kodex)\n- H1 2026 report: [https://cdn.openai.com/trust-and-transparency/report-2026h1-government-requests-for-user-data.pdf](https://cdn.openai.com/trust-and-transparency/report-2026h1-government-requests-for-user-data.pdf)\n\n## FAQ\n\n**Q: Where do I submit a ChatGPT user-data law enforcement request?** A: Kodex at [https://app.kodex.us/openai/signin](https://app.kodex.us/openai/signin), correct OpenAI entity, User Data path.\n\n**Q: Do I need a warrant for ChatGPT content?** A: For OpenAI US, yes, a valid warrant or equivalent; non-content may use a subpoena, court order, warrant, or equivalent.\n\n**Q: Can a non-U.S. agency request OpenAI US data directly?** A: Sometimes, if foreign process would be compulsory locally and fits U.S. law/OpenAI policy; otherwise use MLAT, CLOUD Act § 2523, letters rogatory, or similar.\n\n**Q: Will OpenAI notify the ChatGPT user?** A: Yes before disclosure unless prohibited by law, with limited exceptions and possible delayed notice.\n\n## Conclusion\n\nChatGPT / OpenAI accounts can yield non-content records, content inputs/outputs, or emergency disclosures only through precise, lawful OpenAI law enforcement requests submitted on Kodex with the right entity, path, and legal process.", "url": "https://wpnews.pro/news/how-law-enforcement-can-request-chatgpt-user-data-via-openai-kodex-lers-portal", "canonical_source": "https://ministryofcyberaffairs.com/news/how-law-enforcement-can-request-chatgpt-user-data-via-openai-kodex-lers-portal-043d78cc-449d-4d6f-b00c-07322f562171?utm_source=rss&utm_medium=feed", "published_at": "2026-11-09 04:06:15+00:00", "updated_at": "2026-11-09 04:19:23.901310+00:00", "lang": "en", "topics": ["ai-policy", "artificial-intelligence", "large-language-models"], "entities": ["OpenAI", "ChatGPT", "Kodex", "OpenAI Ireland Ltd.", "OpenAI OpCo LLC"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-law-enforcement-can-request-chatgpt-user-data-via-openai-kodex-lers-portal", "markdown": "https://wpnews.pro/news/how-law-enforcement-can-request-chatgpt-user-data-via-openai-kodex-lers-portal.md", "text": "https://wpnews.pro/news/how-law-enforcement-can-request-chatgpt-user-data-via-openai-kodex-lers-portal.txt", "jsonld": "https://wpnews.pro/news/how-law-enforcement-can-request-chatgpt-user-data-via-openai-kodex-lers-portal.jsonld"}}