{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicy64pd2ve5nzyvgu4pb4rd4gz5eu7wu445e6nfy6tgc6ljnhls2e",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mep7pnoxbop2"
  },
  "path": "/t/urgent-gdpr-violation-no-export-option-for-chatgpt-team-workspace-data/1090657?page=3#post_50",
  "publishedAt": "2026-02-12T23:49:23.000Z",
  "site": "https://community.openai.com",
  "textContent": "Ah, this seems to be a thread that just keeps on giving. I hopped back in after about a year to see what’s changed and to add an update from my side. First, a few key points:\n\nGDPR doesn’t require a specific “button”, that might be correct. But it does require usable access/portability “without hindrance” at scale. Article 20 requires a “structured, commonly used, machine-readable format”, and European Data Protection Board guidance frames portability around practical reuse, _not_ “HTML is machine-readable so who cares”.\n\nOpenAI’s own Help Center now states that ChatGPT Business (formerly Team) workspaces cannot export data and that merges are permanent. That’s not a missing UI toggle but rather documented, well-established lock-in; a literal “wallet-garden” approach, pardon the pun. The joke is serious, though: make the mistake of merging those workspaces and you can get taken for a ride: pay up or cry over your session data.\n\nI also don’t see why any of this couldn’t be solved without enabling employer surveillance: allow per-user export of their own conversations (or admin-controlled export permissions with audit logging). IMHO this “no export whatsoever” policy punishes legitimate small businesses/solo owners and creates real business continuity risk.\n\nAnd when the Team plan launched, it wasn’t even marketed as “business only” in the way the “Business” plan is framed now. It was pitched as collaboration + projects + higher limits, while still keeping a sense of separation between workspaces.\n\nTo reiterate (since this discussion keeps getting derailed): in my case it was always about my own data. I bought the plan, I paid for it, I just wanted my own sessions out. And I couldn’t do it without serious (and frankly desperate) scraping, because help/support either wouldn’t help or dragged their feet.\n\n**Update on my situation:** after escalating this through support and privacy channels, after months, I eventually received a message from the Help Center saying my data had been prepared and was ready for export as a single .zip via a download link. By the time I got to it, the link had already expired. The ticket was then closed, and I couldn’t continue the thread to request a re-issued link. “Always a day late and a dollar short” fits a little too well here.\n\nSo yes: after months of limbo and workarounds, the official “export” they finally offered boiled down to a short-lived link you had to catch in time. If you weren’t online at that exact moment, tough luck: file another ticket, get back in the complaints queue, and hope your ticket gets re-escalated. And that’s assuming the data is still retrievable after you’ve been off the subscription model long enough.\n\nThis is completely untenable as a core business practice. GDPR exists (at least on the EU side) to protect individuals’ ability to access and move their own personal data in practice, not just in theory.\n\nAnd no, I don’t buy the idea that renaming “Team” to “Business” makes GDPR irrelevant. GDPR still applies whenever personal data is being processed. What does change is that “Business” packaging makes it easier to hide behind contractual and administrative complexity. Either way, the end result is the same: users lose practical control over their own archive, and in my view that’s not acceptable for anything marketed as a serious productivity platform.\n\nI can’t say what’s going on inside OpenAI, but I don’t expect this to change this year either. This thread is heading toward becoming one of those “they’ve been doing this forever, what did you expect” receipts: predatory lock-in by design, or sheer negligence, take your pick.\n\nAnd even if we accept “it’s a Business plan now”: what if a project owner needs their archive exported ASAP for continuity, compliance, or litigation hold? The current situation is ridiculous on multiple levels.\n\n_“Always has been.”, murmured the cynic._",
  "title": "Urgent: GDPR Violation – No Export Option for ChatGPT Team Workspace Data"
}