<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Andrew Cluev</title>
    <description>The latest articles on DEV Community by Andrew Cluev (@onecoderegister).</description>
    <link>https://dev.to/onecoderegister</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4165873%2F85667111-18c1-40ac-b5f0-0c4fb7278592.jpg</url>
      <title>DEV Community: Andrew Cluev</title>
      <link>https://dev.to/onecoderegister</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/onecoderegister"/>
    <language>en</language>
    <item>
      <title>Human vs. Anthropic: 11.4 Million Accounts and the Right to Digital Property</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Tue, 03 Nov 2026 13:53:24 +0000</pubDate>
      <link>https://dev.to/onecoderegister/human-vs-anthropic-114-million-accounts-and-the-right-to-digital-property-35g6</link>
      <guid>https://dev.to/onecoderegister/human-vs-anthropic-114-million-accounts-and-the-right-to-digital-property-35g6</guid>
      <description>&lt;h1&gt;
  
  
  Human vs. Anthropic
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;From the "Intellectual Property Law" series&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;11.4 million blocked accounts.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;11.4 million personal digital archives potentially affected.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;11.4 million potential legal disputes.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;These numbers raise an uncomfortable question about the relationship between artificial intelligence companies and the people who use their services.&lt;/p&gt;

&lt;p&gt;The figure of 11.4 million accounts has been cited in discussions of account restrictions. It should not be interpreted as a verified count of lost archives or established legal violations.&lt;/p&gt;

&lt;p&gt;But the underlying problem deserves serious attention.&lt;/p&gt;

&lt;h2&gt;
  
  
  A confrontation over digital ownership
&lt;/h2&gt;

&lt;p&gt;Confrontation.&lt;/p&gt;

&lt;p&gt;That is the word we choose to describe what is happening.&lt;/p&gt;

&lt;p&gt;On one side stands Anthropic, a private company entitled to establish and enforce its own terms of service.&lt;/p&gt;

&lt;p&gt;Anthropic's terms generally recognize users' rights to outputs generated through its services, subject to applicable conditions.&lt;/p&gt;

&lt;p&gt;On the other side stands the individual who has spent months developing projects, writing documents, creating code, and building a personal digital archive using Claude.&lt;/p&gt;

&lt;p&gt;Then the account is suspended.&lt;/p&gt;

&lt;p&gt;And the user may discover that access to years of work has disappeared.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Who owns digital content if its creator cannot access, use, or retrieve it?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  We are not challenging the right to suspend accounts
&lt;/h2&gt;

&lt;p&gt;Let us be clear.&lt;/p&gt;

&lt;p&gt;We are not arguing that every decision by Anthropic to terminate a service agreement is unlawful.&lt;/p&gt;

&lt;p&gt;A company may have legitimate reasons to restrict access to its services.&lt;/p&gt;

&lt;p&gt;But terminating a service agreement and preventing a person from retrieving their own digital content are two different issues.&lt;/p&gt;

&lt;p&gt;Our concern is the second.&lt;/p&gt;

&lt;p&gt;We believe users should retain meaningful rights to possess, use, and dispose of their digital materials, even after access to an AI service has been terminated.&lt;/p&gt;

&lt;p&gt;These are fundamental principles associated with ownership.&lt;/p&gt;

&lt;p&gt;The precise legal rights depend on the applicable jurisdiction, the nature of the content, and the contractual relationship.&lt;/p&gt;

&lt;p&gt;Nevertheless, we believe that account suspension should not automatically result in the loss of access to a user's digital archive.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should a complete digital archive contain?
&lt;/h2&gt;

&lt;p&gt;A simple text export is not always enough.&lt;/p&gt;

&lt;p&gt;A developer may have created dozens of interconnected projects. A researcher may have organized hundreds of conversations, documents, and working materials.&lt;/p&gt;

&lt;p&gt;Without the original structure, reconstructing that work may become extremely difficult.&lt;/p&gt;

&lt;p&gt;We believe users should be entitled to request an archive that preserves, wherever technically possible:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The original organization of projects and folders.&lt;/li&gt;
&lt;li&gt;Conversations and associated materials.&lt;/li&gt;
&lt;li&gt;Files created or uploaded by the user.&lt;/li&gt;
&lt;li&gt;Relationships between projects and their contents.&lt;/li&gt;
&lt;li&gt;Information necessary to identify and verify the exported materials.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;A meaningful digital export should preserve not only the content but also the structure needed to understand and use it.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters for developers
&lt;/h2&gt;

&lt;p&gt;Consider a developer who uses Claude to work on a software project for several months.&lt;/p&gt;

&lt;p&gt;The account is suddenly suspended.&lt;/p&gt;

&lt;p&gt;Even if the developer retains intellectual property rights to the code, those rights may be of limited value if important project materials are inaccessible.&lt;/p&gt;

&lt;p&gt;This distinction matters.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ownership of digital content and the ability to retrieve that content are not the same thing.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;At Ecode, we work on a related aspect of digital ownership: helping developers register cryptographic fingerprints of their code with trusted timestamps.&lt;/p&gt;

&lt;p&gt;Such records can help document the existence of a particular file at a particular time.&lt;/p&gt;

&lt;p&gt;They cannot restore an inaccessible Claude archive.&lt;/p&gt;

&lt;p&gt;But both issues are connected by a broader principle: individuals should have reliable ways to document their digital work and protect their interests in it.&lt;/p&gt;

&lt;h2&gt;
  
  
  11.4 million questions about digital rights
&lt;/h2&gt;

&lt;p&gt;11.4 million accounts reportedly blocked.&lt;/p&gt;

&lt;p&gt;How many users still need access to their projects?&lt;/p&gt;

&lt;p&gt;How many have been unable to obtain a complete archive?&lt;/p&gt;

&lt;p&gt;How many may have grounds to pursue legal remedies?&lt;/p&gt;

&lt;p&gt;These questions deserve answers.&lt;/p&gt;

&lt;p&gt;As Anthropic faces growing public scrutiny and discussion of a potential IPO, we believe it is especially important to address what happens to user-created content after account suspension.&lt;/p&gt;

&lt;p&gt;We want to hear Anthropic's position on meaningful access to personal digital archives.&lt;/p&gt;

&lt;h2&gt;
  
  
  We are collecting complaints and examining legal options
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Aimperia and the Ecode project are collecting reports from users whose Claude accounts have been suspended.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We are examining the circumstances of these cases and assessing the possibility of a collective legal action to protect users' rights to digital content.&lt;/p&gt;

&lt;p&gt;No conclusion has yet been reached about the legal merits of individual complaints or whether collective proceedings can be brought.&lt;/p&gt;

&lt;p&gt;If your Claude account was suspended and you were unable to retrieve your conversations, projects, files, or other materials, we invite you to share your experience.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Submit your case here:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://aimperia.ai/anthropic-form" rel="noopener noreferrer"&gt;https://aimperia.ai/anthropic-form&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Learn more about the initiative:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/anthropic.html" rel="noopener noreferrer"&gt;https://onecoderegister.io/anthropic.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We are particularly interested in understanding whether users received their complete archives, whether exported files preserved project structures, and whether they encountered obstacles when attempting to download their data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Digital ownership should not become meaningless when access to a service ends.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>privacy</category>
      <category>discuss</category>
      <category>legal</category>
    </item>
    <item>
      <title>Can't access your Claude archive? Ecode's complaint form is now open.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Fri, 30 Oct 2026 06:43:42 +0000</pubDate>
      <link>https://dev.to/ecode/cant-access-your-claude-archive-ecodes-complaint-form-is-now-open-14l6</link>
      <guid>https://dev.to/ecode/cant-access-your-claude-archive-ecodes-complaint-form-is-now-open-14l6</guid>
      <description>&lt;p&gt;An account restriction can leave weeks of work out of reach.&lt;/p&gt;

&lt;p&gt;Conversations, code revisions, documents and project notes may still be needed long after someone stops using Claude.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;We have opened a complaint form for users who cannot retrieve their materials or have unresolved refund issues.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/anthropic.html?utm_source=devto" rel="noopener noreferrer"&gt;Open the complaint form&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  What can you report?
&lt;/h2&gt;

&lt;p&gt;The Ecode team is collecting reports about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Blocked or restricted access&lt;/strong&gt; to Claude.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Archives that cannot be exported.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Missing conversations, files or incomplete exports.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Unresolved refund requests.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Documented losses&lt;/strong&gt; connected with these incidents.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can describe what happened and indicate what you are seeking, such as a complete copy of your archive, a refund or compensation for documented losses.&lt;/p&gt;

&lt;h2&gt;
  
  
  What details will help?
&lt;/h2&gt;

&lt;p&gt;Please include:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;When the problem started&lt;/strong&gt; and which Claude product you used.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Which materials became inaccessible&lt;/strong&gt;, such as conversations, code or documents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Whether you requested an export&lt;/strong&gt; and what you received.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What Anthropic support replied.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Whether the problem was later resolved.&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If your access was restored, your archive became available or a refund arrived, please include that too. We need the full outcome to assess the circumstances accurately.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Please do not post personal information or confidential materials in public comments.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What Ecode is working towards
&lt;/h2&gt;

&lt;p&gt;We are collecting reports to assess possible collective legal action against Anthropic concerning access to user archives, refunds and documented losses.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;No lawsuit has been filed yet.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The legal route remains under review. Whether claims can be brought together will depend on the country, applicant status, contract terms and circumstances of each case.&lt;/p&gt;

&lt;p&gt;Submitting the form does not mean that a lawsuit has been filed on your behalf or that a particular outcome is guaranteed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Ecode is involved
&lt;/h2&gt;

&lt;p&gt;Ecode helps preserve dated evidence about code files without requiring users to upload their source code.&lt;/p&gt;

&lt;p&gt;This initiative concerns access to the materials themselves, including conversations, documents and code created while using Claude.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Registering a file's digital fingerprint does not back up its contents or recover an inaccessible Claude archive.&lt;/strong&gt; These are different needs, and the complaint form addresses the second one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you submit
&lt;/h2&gt;

&lt;p&gt;Describe the problem and indicate what evidence you have, such as a restriction notice, support correspondence or payment confirmation.&lt;/p&gt;

&lt;p&gt;Please do not send passwords, payment card details or confidential files before a secure transfer channel has been agreed.&lt;/p&gt;




&lt;h2&gt;
  
  
  Tell us what happened
&lt;/h2&gt;

&lt;p&gt;If you have been affected, the complaint form is now open.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://onecoderegister.io/anthropic.html?utm_source=devto" rel="noopener noreferrer"&gt;Submit your report&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If someone on your team is dealing with this, please share the link with them.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/" rel="noopener noreferrer"&gt;About Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>claude</category>
      <category>privacy</category>
      <category>ai</category>
    </item>
    <item>
      <title>Claude suspended the account. The user still wanted their conversations.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Thu, 29 Oct 2026 12:59:27 +0000</pubDate>
      <link>https://dev.to/onecoderegister/claude-suspended-the-account-the-user-still-wanted-their-conversations-400l</link>
      <guid>https://dev.to/onecoderegister/claude-suspended-the-account-the-user-still-wanted-their-conversations-400l</guid>
      <description>&lt;p&gt;An account appeal and a request for your conversations aren't the same request.&lt;/p&gt;

&lt;p&gt;On October 1, Reddit user W0rking_Kale_oof reported that their Claude account had been suspended.&lt;/p&gt;

&lt;p&gt;They said the data export returned basic user information but no conversation history. In a follow-up, they also said they had contacted Anthropic through its privacy contact page.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.reddit.com/r/claude/comments/1wutq5d/account_suspended_suspicious_signals/" rel="noopener noreferrer"&gt;Read the report&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The user described accessing Claude from Hong Kong through NordVPN. This report alone doesn't establish the exact reason for the suspension, whether it was justified, or whether the archive was later recovered.&lt;/p&gt;

&lt;p&gt;Anthropic's current guidance allows data exports after bans, while noting that available content can be restricted depending on the Usage Policy violation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://support.claude.com/en/articles/8241253-safeguards-warnings-and-appeals" rel="noopener noreferrer"&gt;Read Anthropic's guidance&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Ecode is doing
&lt;/h2&gt;

&lt;p&gt;Ecode is studying cases involving users' access to conversations, files, code, and other materials created while using Claude.&lt;/p&gt;

&lt;p&gt;We plan to pursue collective legal action against Anthropic, potentially through a class action, to protect users' access to and rights in these materials.&lt;/p&gt;

&lt;p&gt;We are preparing the legal position and the process for reviewing similar cases. We aim to be ready soon to help affected users document their situation and assess requests for copies of their work.&lt;/p&gt;

&lt;p&gt;The initiative is still being prepared. No lawsuit filing or guaranteed outcome is being announced here.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this belongs with Ecode
&lt;/h2&gt;

&lt;p&gt;Our code registration service helps preserve dated evidence through SHA-256 fingerprints, database registration, trusted RFC 3161 timestamps, and Polygon records.&lt;/p&gt;

&lt;p&gt;Users receive a certificate and verification files without uploading their source code.&lt;/p&gt;

&lt;p&gt;The legal initiative addresses access to the materials themselves. Ecode registration cannot retrieve missing Claude conversations.&lt;/p&gt;

&lt;p&gt;If you experienced an incomplete export after a suspension, a short, non-confidential description would help. Please mention whether the problem was later resolved.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_29_claude_history" rel="noopener noreferrer"&gt;About Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>claude</category>
      <category>privacy</category>
      <category>ai</category>
    </item>
    <item>
      <title>Copilot can work under an organization's identity. Keep records of the output.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Thu, 29 Oct 2026 12:57:29 +0000</pubDate>
      <link>https://dev.to/onecoderegister/copilot-can-work-under-an-organizations-identity-keep-records-of-the-output-29jm</link>
      <guid>https://dev.to/onecoderegister/copilot-can-work-under-an-organizations-identity-keep-records-of-the-output-29jm</guid>
      <description>&lt;p&gt;On October 27, GitHub announced a public preview of server-to-server authentication for Copilot.&lt;/p&gt;

&lt;p&gt;Services built with the Copilot SDK can make requests on behalf of an organization without relying on a signed-in employee's credentials.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.blog/changelog/2026-10-27-github-copilot-supports-server-to-server-authentication/" rel="noopener noreferrer"&gt;Read GitHub's announcement&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This separates an automated service's access from an individual login.&lt;/p&gt;

&lt;p&gt;For teams, there's another question worth documenting: what files did the work produce, and which version did the team approve?&lt;/p&gt;

&lt;p&gt;Keep the files, review history, and relevant agreements.&lt;/p&gt;

&lt;p&gt;I'm part of the Ecode team. Ecode can add a separate dated record for code files using SHA-256 fingerprints, database registration, trusted RFC 3161 timestamps, and Polygon records.&lt;/p&gt;

&lt;p&gt;You receive a certificate and verification files. The source code stays on your device.&lt;/p&gt;

&lt;p&gt;These records can support an authorship claim alongside the wider development history. They don't identify who wrote each line or decide ownership of AI-assisted output.&lt;/p&gt;

&lt;p&gt;Ecode registration is free, with no card or subscription.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_29_team_records" rel="noopener noreferrer"&gt;Learn about Ecode&lt;/a&gt;
&lt;/h2&gt;

</description>
      <category>github</category>
      <category>ai</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Making your project public? Keep your own record, too.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Thu, 29 Oct 2026 12:56:26 +0000</pubDate>
      <link>https://dev.to/onecoderegister/making-your-project-public-keep-your-own-record-too-157h</link>
      <guid>https://dev.to/onecoderegister/making-your-project-public-keep-your-own-record-too-157h</guid>
      <description>&lt;p&gt;You've finished the first public version of your project. Before sharing the link, keep a copy of the files you're releasing.&lt;/p&gt;

&lt;p&gt;Your repository and development history already matter. A separate dated record can add another piece of evidence.&lt;/p&gt;

&lt;p&gt;I'm part of the Ecode team. Our free service registers code fingerprints without uploading the source.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you receive
&lt;/h2&gt;

&lt;p&gt;Ecode combines:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A SHA-256 fingerprint calculated on your device.&lt;/li&gt;
&lt;li&gt;Database registration.&lt;/li&gt;
&lt;li&gt;A trusted RFC 3161 timestamp.&lt;/li&gt;
&lt;li&gt;A Polygon blockchain record.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You receive a certificate with a QR code, a timestamp file, and a blockchain transaction link.&lt;/p&gt;

&lt;p&gt;Keep these with the exact files you registered and your development history. Together, they can help support an authorship claim if questions arise later.&lt;/p&gt;

&lt;p&gt;Registration doesn't replace your project's license or prove that every line is yours.&lt;/p&gt;

&lt;p&gt;Your source code stays on your device. Registration is free. No card or subscription is needed.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_29_public_release" rel="noopener noreferrer"&gt;Create a dated record with Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>opensource</category>
      <category>productivity</category>
    </item>
    <item>
      <title>A blocked Claude account, a delayed export, and the right to keep your work</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Wed, 28 Oct 2026 14:29:48 +0000</pubDate>
      <link>https://dev.to/onecoderegister/a-blocked-claude-account-a-delayed-export-and-the-right-to-keep-your-work-33ef</link>
      <guid>https://dev.to/onecoderegister/a-blocked-claude-account-a-delayed-export-and-the-right-to-keep-your-work-33ef</guid>
      <description>&lt;p&gt;Losing access to Claude and losing access to your saved work are different problems.&lt;/p&gt;

&lt;p&gt;An earlier Reddit report shows why the distinction matters.&lt;/p&gt;

&lt;p&gt;User questionaskingguy123 said their account was suspended over an age check. Verification returned an error, and they couldn't export their conversations.&lt;/p&gt;

&lt;p&gt;There was an important update: after 15 days of waiting for support, the user reported that export options had appeared. They then received a ZIP containing conversations and memories.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.reddit.com/r/claude/comments/1u1n3eu/what_do_i_do_claude_account_suspended/" rel="noopener noreferrer"&gt;Read the report and update&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This is the user's account of events, not an independently verified finding. Their update says the export succeeded. It would be wrong to describe this as permanent data loss.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Ecode is preparing
&lt;/h2&gt;

&lt;p&gt;The Ecode team is studying cases involving access to conversations, files, and project materials after Claude account restrictions.&lt;/p&gt;

&lt;p&gt;We plan to pursue collective legal action against Anthropic, potentially through a class action, to protect users' access to and rights in materials created using Claude.&lt;/p&gt;

&lt;p&gt;We aim to be ready soon to help affected users document their cases and assess requests for copies of their materials. The intake process is still being prepared.&lt;/p&gt;

&lt;p&gt;The legal route and suitable groups of claimants remain under review. We aren't announcing a filed lawsuit or guaranteed recovery.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this connects to Ecode
&lt;/h2&gt;

&lt;p&gt;Ecode helps preserve evidence about digital work. Our code registration service uses SHA-256 fingerprints, database registration, trusted RFC 3161 timestamps, and Polygon records.&lt;/p&gt;

&lt;p&gt;Users receive a certificate and verification files without uploading their source code.&lt;/p&gt;

&lt;p&gt;The legal initiative concerns access to the archive itself. Registering a file cannot recover missing Claude conversations.&lt;/p&gt;

&lt;p&gt;Anthropic's current help page provides for exports after bans, while noting that the available data may be restricted depending on the Usage Policy violation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://support.claude.com/en/articles/8241253-safeguards-warnings-and-appeals" rel="noopener noreferrer"&gt;Read Anthropic's guidance&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you had trouble getting your archive, a short description would be useful. Please say whether access was later restored, and leave out private conversations and account details.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_28_claude_delayed_export" rel="noopener noreferrer"&gt;About Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>claude</category>
      <category>privacy</category>
      <category>ai</category>
    </item>
    <item>
      <title>Copilot can approve more actions automatically. Keep your starting files.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Wed, 28 Oct 2026 14:27:53 +0000</pubDate>
      <link>https://dev.to/onecoderegister/copilot-can-approve-more-actions-automatically-keep-your-starting-files-3e2l</link>
      <guid>https://dev.to/onecoderegister/copilot-can-approve-more-actions-automatically-keep-your-starting-files-3e2l</guid>
      <description>&lt;p&gt;On October 26, GitHub announced general availability of assisted permissions for Copilot.&lt;/p&gt;

&lt;p&gt;A model evaluates permission requests. Actions classified as clearly safe can proceed automatically. Other actions still need your approval.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.blog/changelog/2026-10-26-github-copilot-assisted-permissions-generally-available/" rel="noopener noreferrer"&gt;Read GitHub's announcement&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This is a good moment to check a simple habit: save important versions before automated tools make substantial changes.&lt;/p&gt;

&lt;p&gt;Keep version history and backups. If you also want a separate dated record of a code file, Ecode can help.&lt;/p&gt;

&lt;p&gt;I'm part of the Ecode team. Our free service combines a SHA-256 fingerprint, database registration, a trusted RFC 3161 timestamp, and a Polygon record.&lt;/p&gt;

&lt;p&gt;You receive a certificate and verification files. Your source code stays on your device.&lt;/p&gt;

&lt;p&gt;Register the version you want to document, then keep its exact files and certificate together.&lt;/p&gt;

&lt;p&gt;Those records can help support an authorship claim alongside your development history. They don't approve an agent's actions or undo its changes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_28_copilot_permissions" rel="noopener noreferrer"&gt;Learn about Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Selling your side project? Keep a record of what you hand over.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Wed, 28 Oct 2026 14:27:02 +0000</pubDate>
      <link>https://dev.to/onecoderegister/selling-your-side-project-keep-a-record-of-what-you-hand-over-253e</link>
      <guid>https://dev.to/onecoderegister/selling-your-side-project-keep-a-record-of-what-you-hand-over-253e</guid>
      <description>&lt;p&gt;You've found a buyer for your side project. Before sending the final files, keep a clear record of what you're handing over.&lt;/p&gt;

&lt;p&gt;Save the delivered version, the agreement, and the messages confirming delivery.&lt;/p&gt;

&lt;p&gt;I'm part of the Ecode team. Our free service can add dated evidence for your code files without uploading the source.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Ecode provides
&lt;/h2&gt;

&lt;p&gt;Ecode combines:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A SHA-256 fingerprint calculated on your device.&lt;/li&gt;
&lt;li&gt;Database registration.&lt;/li&gt;
&lt;li&gt;A trusted RFC 3161 timestamp.&lt;/li&gt;
&lt;li&gt;A Polygon blockchain record.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You receive a certificate with a QR code, a timestamp file, and a blockchain transaction link.&lt;/p&gt;

&lt;p&gt;Keep these with the exact files you delivered. Together with your development history, they can help support an authorship claim and document the version involved in the sale.&lt;/p&gt;

&lt;p&gt;Registration doesn't transfer ownership or replace your agreement with the buyer.&lt;/p&gt;

&lt;p&gt;Your source code stays on your device. Registration is free. No card or subscription is needed.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_28_project_sale" rel="noopener noreferrer"&gt;Register your code with Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>startup</category>
      <category>productivity</category>
    </item>
    <item>
      <title>A 257-byte Claude export. What happens to the user's work?</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:14:23 +0000</pubDate>
      <link>https://dev.to/onecoderegister/a-257-byte-claude-export-what-happens-to-the-users-work-44mf</link>
      <guid>https://dev.to/onecoderegister/a-257-byte-claude-export-what-happens-to-the-users-work-44mf</guid>
      <description>&lt;p&gt;A download link doesn't settle the problem if the download doesn't contain your conversations.&lt;/p&gt;

&lt;p&gt;In a public Reddit post, user Hot-Comb-4743 reported that after two Claude accounts were banned, the export links returned only a 257-byte ZIP file instead of their conversations.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.reddit.com/r/Anthropic/comments/1v2ejlk/after_banning_claude_doesnt_give_any_real/" rel="noopener noreferrer"&gt;Read the user's report&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This is an earlier user report, not a newly confirmed incident. We haven't independently verified the export or established what happened to the underlying data.&lt;/p&gt;

&lt;p&gt;Anthropic's current guidance says banned users can export data, but the available content may be restricted depending on the Usage Policy violation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://support.claude.com/en/articles/8241253-safeguards-warnings-and-appeals" rel="noopener noreferrer"&gt;Read Anthropic's guidance&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Ecode initiative
&lt;/h2&gt;

&lt;p&gt;We are already studying cases involving blocked access to Claude conversations, files, and project materials.&lt;/p&gt;

&lt;p&gt;Ecode plans to pursue collective legal action against Anthropic, potentially through a class action, to protect users' access to and rights in materials created using Claude.&lt;/p&gt;

&lt;p&gt;Our immediate goal is to help affected users document their cases and assess requests for a usable copy of their materials.&lt;/p&gt;

&lt;p&gt;We aim to make that help available soon. The intake process is still being prepared. We are not announcing a filed lawsuit or a guaranteed outcome.&lt;/p&gt;

&lt;h2&gt;
  
  
  How this connects to Ecode
&lt;/h2&gt;

&lt;p&gt;Ecode helps people preserve evidence of their digital work.&lt;/p&gt;

&lt;p&gt;For code files you already have, our free service combines a SHA-256 fingerprint, database registration, a trusted RFC 3161 timestamp, and a Polygon record.&lt;/p&gt;

&lt;p&gt;You receive a certificate and verification files while your source code stays on your device. These records can help support an authorship claim alongside your original files and development history.&lt;/p&gt;

&lt;p&gt;The legal initiative concerns access to the materials themselves. Ecode registration cannot recover missing Claude chats.&lt;/p&gt;

&lt;p&gt;If you faced an incomplete export after a ban, a short description in the comments would help us understand the situation. Please leave out private conversations, passwords, and account details.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_27_claude_archive" rel="noopener noreferrer"&gt;About Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>claude</category>
      <category>privacy</category>
      <category>ai</category>
    </item>
    <item>
      <title>GitHub improves leak monitoring. Code evidence doesn't need a public upload.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:10:59 +0000</pubDate>
      <link>https://dev.to/onecoderegister/github-improves-leak-monitoring-code-evidence-doesnt-need-a-public-upload-eah</link>
      <guid>https://dev.to/onecoderegister/github-improves-leak-monitoring-code-evidence-doesnt-need-a-public-upload-eah</guid>
      <description>&lt;p&gt;On October 23, GitHub announced improvements to public monitoring for leaked secrets.&lt;/p&gt;

&lt;p&gt;The update includes ongoing checks to show whether supported exposed credentials are still active.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.blog/changelog/2026-10-23-public-monitoring-adds-triage-validity-api-and-webhooks/" rel="noopener noreferrer"&gt;Read GitHub's announcement&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It also raises a separate point about documenting your own work: you don't have to make source code public to create a dated record of it.&lt;/p&gt;

&lt;p&gt;I'm part of the Ecode team. Ecode calculates a SHA-256 fingerprint on your device. Your source code stays there.&lt;/p&gt;

&lt;p&gt;The service registers the fingerprint in a database, adds a trusted RFC 3161 timestamp, and creates a Polygon blockchain record.&lt;/p&gt;

&lt;p&gt;You receive a certificate with a QR code, a timestamp file, and a blockchain transaction link.&lt;/p&gt;

&lt;p&gt;Keep those records with the original files and development history. They can help support an authorship claim.&lt;/p&gt;

&lt;p&gt;Ecode doesn't scan for leaked credentials or check whether code is secure. Those checks still matter.&lt;/p&gt;

&lt;p&gt;Registration is free. No card or subscription is needed.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_27_public_monitoring" rel="noopener noreferrer"&gt;Learn about Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>security</category>
      <category>privacy</category>
    </item>
    <item>
      <title>Showing a prototype? Keep a record of the code behind it.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:09:46 +0000</pubDate>
      <link>https://dev.to/ecode/showing-a-prototype-keep-a-record-of-the-code-behind-it-2ci1</link>
      <guid>https://dev.to/ecode/showing-a-prototype-keep-a-record-of-the-code-behind-it-2ci1</guid>
      <description>&lt;p&gt;You've built a prototype. Tomorrow, you're showing it to a potential partner or investor.&lt;/p&gt;

&lt;p&gt;A demo video shows what the app does. Keep the code behind that demo, too.&lt;/p&gt;

&lt;p&gt;I'm part of the Ecode team. Our free service helps create dated evidence for code files without uploading the source.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before the meeting
&lt;/h2&gt;

&lt;p&gt;Save the files used for the demo. Register them with Ecode. Keep the certificate and verification files alongside that saved version.&lt;/p&gt;

&lt;p&gt;Ecode combines:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A SHA-256 fingerprint calculated on your device.&lt;/li&gt;
&lt;li&gt;Database registration.&lt;/li&gt;
&lt;li&gt;A trusted RFC 3161 timestamp.&lt;/li&gt;
&lt;li&gt;A Polygon blockchain record.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You receive a certificate with a QR code, a timestamp file, and a blockchain transaction link.&lt;/p&gt;

&lt;p&gt;Your source code stays on your device. Registration is free, with no card or subscription.&lt;/p&gt;

&lt;p&gt;Together with your original files and development history, these records can help support an authorship claim if a dispute comes up.&lt;/p&gt;

&lt;p&gt;They don't replace confidentiality agreements or agreements about ownership.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_27_prototype" rel="noopener noreferrer"&gt;Register your code with Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>startup</category>
      <category>productivity</category>
    </item>
    <item>
      <title>A Claude export without the conversations. Ecode is studying these cases.</title>
      <dc:creator>Andrew Cluev</dc:creator>
      <pubDate>Mon, 26 Oct 2026 14:26:05 +0000</pubDate>
      <link>https://dev.to/ecode/a-claude-export-without-the-conversations-ecode-is-studying-these-cases-29a6</link>
      <guid>https://dev.to/ecode/a-claude-export-without-the-conversations-ecode-is-studying-these-cases-29a6</guid>
      <description>&lt;p&gt;An export button isn't much help if the download doesn't contain the work you need.&lt;/p&gt;

&lt;p&gt;In a public Reddit post, user Overload175 reported that after a Claude account ban, their export contained users.json but no conversations.json.&lt;/p&gt;

&lt;p&gt;They said they couldn't retrieve their past conversations.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.reddit.com/r/Anthropic/comments/1vxkk57/banned_and_cant_retrieve_past_conversations/" rel="noopener noreferrer"&gt;Read the user's account&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This is a user report. We haven't independently verified the account or established why the export was incomplete.&lt;/p&gt;

&lt;p&gt;Claude's current guidance says banned users can export data, but the available data may be restricted depending on the Usage Policy violation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://support.claude.com/en/articles/8241253-safeguards-warnings-and-appeals" rel="noopener noreferrer"&gt;Read Claude's guidance&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Ecode is preparing
&lt;/h2&gt;

&lt;p&gt;The Ecode team is already studying situations in which users lose access to materials created using Claude.&lt;/p&gt;

&lt;p&gt;We plan to bring a collective legal action, potentially a class action, to protect users' access to and rights in those materials.&lt;/p&gt;

&lt;p&gt;We are working on the legal grounds and how to group similar cases. We aim to be ready soon to help affected users document what happened and assess requests for access to their materials.&lt;/p&gt;

&lt;p&gt;A start date for this help has not been announced. No court filing is being announced in this post.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters to us
&lt;/h2&gt;

&lt;p&gt;Ecode helps people preserve dated evidence about code files they possess.&lt;/p&gt;

&lt;p&gt;Our free registration service uses SHA-256 fingerprints, database registration, trusted RFC 3161 timestamps, and Polygon records. It provides a certificate and verification files without uploading the source code.&lt;/p&gt;

&lt;p&gt;The legal initiative addresses another problem: what can users do when they can't obtain their materials from the platform?&lt;/p&gt;

&lt;p&gt;Ecode registration cannot recover missing Claude conversations. We are examining legal ways to seek access to those materials.&lt;/p&gt;

&lt;p&gt;If this happened to you, you're welcome to leave a short, non-confidential description below. Please don't publish private conversations, passwords, or account details.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://onecoderegister.io/?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=ecode_2026_10_26_claude_exports" rel="noopener noreferrer"&gt;About Ecode&lt;/a&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>claude</category>
      <category>privacy</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
