{"id":20280,"date":"2026-09-29T03:05:42","date_gmt":"2026-09-29T03:05:42","guid":{"rendered":"https:\/\/www.backupassist.com\/blog\/?p=20280"},"modified":"2026-09-29T03:05:43","modified_gmt":"2026-09-29T03:05:43","slug":"ai-account-lockout-three-stories","status":"publish","type":"post","link":"https:\/\/www.backupassist.com\/blog\/ai-account-lockout-three-stories","title":{"rendered":"If your AI account vanished tonight, would your work go with it?"},"content":{"rendered":"

In May, I wrote about Andrew Olsson<\/a>, a YouTuber who woke up locked out of Claude with no warning and no explanation. Everything he'd built inside it was gone. I asked: if your AI account closed tonight, with no warning and no appeal, what would you lose?<\/p>\n

The situation has developed since then. In September alone, we saw three examples of how innocent businesses can become collateral damage<\/strong> and lose data.<\/p>\n

    \n
  1. You get locked out by the AI vendor<\/li>\n
  2. The AI vendor shuts down<\/li>\n
  3. The AI vendor gets acquired<\/li>\n<\/ol>\n

    I'll then share how I've been able to mitigate some of them with a few changes to how I work and use these AI tools.<\/p>\n

    1. Your login gets stolen, and you're the one who gets locked out<\/h2>\n

    We're used to a familiar pattern of account theft. Someone steals your login, locks you<\/em> out, and ransoms the account back. What happened to Grant De Swardt is different.<\/p>\n

    De Swardt runs a one-person business in East Sussex, helping companies set up AI agents. On 4 August, he noticed his Claude token usage climbing on a day he hadn't touched it. He disabled everything connected to his account. Usage kept climbing anyway.<\/p>\n

    He asked Anthropic for an itemized list of what was consuming his tokens. They couldn't provide one, so there was no easy way to stop the unauthorized usage. In a last ditch move, Anthropic suspended his entire account for two weeks.<\/p>\n

    Anthropic later told him a compromised session key had been used to create unauthorized tokens on his account. As he relayed to TechCrunch<\/a>, the evidence was "consistent either with credentials\/session data being taken without my knowledge, or with the account having been connected to an outside service." De Swardt says he found no sign his own computer was compromised, and still doesn't know how it happened.<\/p>\n

    He got his account back after 2 weeks, and has since moved to a different tool. Anthropic still has no way for a customer to see what's consuming their usage. "I don't think there's any way that these people can protect themselves,"<\/strong> he told TechCrunch.<\/p>\n

    The attacker didn't lock De Swardt out. The vendor did, correctly, to stop further unauthorized use. For 2 weeks, he was locked out of his account.<\/p>\n

    What would be the impact if this happened to you? Do you have a copy of your critical data if you're locked out of your account? <\/p>\n

    2. The key staff leave for a big company, and the product dies<\/h2>\n

    Cyber risks are just one way to lose access to an AI account, as our next story shows. The career choices of individuals can also be a risk to you.<\/p>\n

    Relay was an AI workflow tool for moving data between apps a small business already runs. Tools like this are incredibly useful – just getting different apps to "talk to each other" has huge business benefits.<\/p>\n

    Like any tool or software service, it takes an investment of time and money to adopt, learn and use the service: connecting systems, testing that they work, changing business processes. <\/p>\n

    Relay had paying customers and $8.1 million in funding. On 14 September, it stopped operating completely.<\/p>\n

    Why, you may ask? Relay's founder, Jacob Bank, left to rejoin Google as VP of Product for Chrome, and members of his team went with him (TechCrunch<\/a>). <\/p>\n

    Relay simply shut the product down. Free users lost access on 15 August. Paying customers had until 14 September, about a month, to export their data and find an alternative service.<\/p>\n

    This is the classic "vendor shuts down" risk.<\/strong> <\/p>\n

    In this case, the founder decided to make a career change. Customers weren't the target of Bank's career move; they were collateral damage.<\/p>\n

    3. Your AI vendor gets acquired; will the purchaser treat you with respect?<\/h2>\n

    It's common for software and AI vendors to get acquired. But this kind of event can put your account, and the work inside it, at risk.<\/p>\n

    Almost nobody reads the terms of service at signup. You click through because you want the tool. Did you read all the T&Cs for Microsoft 365 or AWS or Google Docs?<\/p>\n

    Years later, when a bigger company buys the vendor, it's the written contract that governs the relationship. The purchaser looks at the legal terms, not at the goodwill you had with the old team, and not at any moral obligation you assumed was there.<\/p>\n

    NetNow is a fresh example. It runs credit checks and fraud screening for businesses, and says it's used by 85,000 customers. On 21 September, BlackLine bought it<\/a>. That is the moment a lot of customers start reading paperwork they skipped on day one. <\/p>\n

    When people checked the fine print, two things became clear:<\/p>\n

      \n
    1. On the service: "Either party, be it you or us, can conclude this Terms of Service either with or without reason or prior notification."<\/strong> \u00a714 Ending or Discontinuation<\/a><\/li>\n
    2. On customer data: "It's your responsibility to keep copies of Your Content. NetNow isn't responsible for any content losses or damages."<\/strong> \u00a73(b) Your Content<\/li>\n<\/ol>\n

      Here's the problem. You might have signed up for NetNow, or any AI vendor, when they were a small company – friendly people, a mission you believed in, great tech support.<\/p>\n

      But when a company gets acquired, the prior "good vibes" can change instantly. Small vendors get bought by mid-size ones, which get bought by large ones. Before long, your vendor can be completely different to deal with. Yet, the original contract you agreed to is still in place.<\/strong><\/p>\n

      And NetNow's contract is not good for its customers. It took Rajesh Beri<\/a>, an enterprise AI practitioner, to highlight the worst-case risk. This is how an operational matter becomes a business risk:<\/p>\n

        \n
      1. You risk losing access to those credit files.<\/li>\n
      2. In a lawsuit you can\u2019t prove why you approved or denied credit to an applicant.<\/li>\n
      3. That makes it extremely challenging to defend claims or prove compliance with Regulation B (under the Equal Credit Opportunity Act).<\/li>\n<\/ol>\n

        Collateral damage, then the fix<\/h2>\n

        I find it interesting that the 3 risks existed long before AI, but with the hype and drive towards AI adoption, many people aren't thinking about the risks.<\/p>\n

        That's the problem. If the only copy of your work is in your vendor's tool or account, you take on every risk the vendor has, and more<\/strong>.<\/p>\n\n\n\n\n\n\n\n
        Story<\/th>\nWhat actually happened<\/th>\nWas the work ever separate from the tool?<\/th>\n<\/tr>\n<\/thead>\n
        Claude<\/strong><\/td>\nA stolen login led the vendor to suspend the account<\/td>\nChat sessions, project files live in Anthropic's servers. Export is a separate, manual task you have to do yourself.<\/td>\n<\/tr>\n
        Relay<\/strong><\/td>\nThe product shut down after its founder and staff joined Google<\/td>\nExport was available, and customers got a month's notice to export and save their data.<\/td>\n<\/tr>\n
        NetNow<\/strong><\/td>\nAcquired, drawing attention to the T&Cs.<\/td>\nSome way to pull files appears to exist, but under the T&Cs keeping copies is the customer\u2019s job, and the vendor can cut access with no advance notice and no duty to hand over an export.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        What I've been doing and how I'm thinking about this<\/h2>\n

        In May, I still didn't have a good answer. I exported Claude project files by hand whenever I remembered, because they only ever existed inside the account. I still do periodic exports, but I've changed tack over the past few months.<\/p>\n

        I've been experimenting and trying to find an approach that works for me personally, before rolling it out through the company. It's been pretty successful so far – my new approach is to decouple the tool from the data.<\/strong><\/p>\n

        Since then, I've moved most of my own AI work onto files on my hard drive, and changed the bulk of my work from Claude (on the web) to Claude Code. This has only been possible recently, because a year ago, Claude Code refused to do any task that wasn't coding-related. <\/p>\n

        Here are my new work practices:<\/p>\n