How we handle your drawings

• Government or defence work, including anything marked Protected or Secret, or anything involving controlled goods.
• Aerospace or defence-contractor work.
• Anything under a contract or agreement that forbids sending it to an outside service or an AI tool.
• Personal information: customer or staff lists, card numbers, SIN or SSN, health records.
• Passwords, keys or sign-in details of any kind.

Upload drawings, specs, checklists and City letters only. CodeCheck does not check files against this list yet, so this list is how those files are kept out. If you are not sure about a file, or want your company's own rules added here, ask first: This site has no contact address set yet, so ask the person who gave you your CodeCheck sign-in to pass your question to Michael O'Brien, who runs CodeCheck.

• To CodeCheck's cloud store. Every file you add, the review results, decisions, comments and messages go to the store described under Where it is stored.
• To the review computer. Reviews run on one computer that reads the sheets; today it is a computer in Michael O'Brien's office. It downloads the drawing set it is reviewing, deletes a downloaded drawing 7 days after downloading it (the default setting), and keeps what it read on each page so a later review does not have to read unchanged sheets again.
• To the AI that reads the sheets. Each page of the drawings and specs as a picture plus the text on it, the lines in What should be there (your checklist, City letter or typed lines), and a short written summary of your space's past decisions. Which AI, and whether it may learn from them, is under the next heading. Each review's history records which AI read the set.
• To Anthropic, from CodeCheck's own site. Steps that run on the site itself (reading a value off a sheet in the code-rule check, drafting replies to City comments, and any review read through the site instead of the review computer's own AI) use Anthropic's Claude Opus 5.5 through Anthropic's API.
• To anyone you send a trade share link. Without signing in, they see the sheets confirmed as that trade and the lines whose proof is all on those sheets, until someone in your space switches the link off or the project is deleted.
• Email invites and alerts. When email is configured, CodeCheck sends trade invites, mentions and guest reply alerts through Resend. These carry the project name, your note or a short reply excerpt, and a link. Drawing files are not attached. Otherwise, the sharer copies the invite link or opens it in their email app.

CodeCheck itself trains nothing. No AI model is trained, fine-tuned or changed by CodeCheck, and nothing in CodeCheck sends your drawings anywhere for training.

The review computer's AI. The review computer is set up to read the sheets with Anthropic's Claude Opus 5.5 (Claude Code), signed in to Michael O'Brien's Claude Max subscription. That is a personal subscription under Anthropic's consumer terms, not a business API account. Whether Anthropic may use those sessions to improve its models is that account's “Help improve Claude” setting. What is confirmed: CodeCheck's own code trains nothing, and hosted drawing reads use Anthropic's Claude Opus 5.5 through Anthropic's API; under its commercial API terms, inputs are not used to train its models. What is not confirmed yet: that the Claude setting is off. This page will say so once it is. Until then, if that matters for a project, don't upload it.

To ask before you upload: This site has no contact address set yet, so ask the person who gave you your CodeCheck sign-in to pass your question to Michael O'Brien, who runs CodeCheck.

Anthropic. Drawings are read by Anthropic's Claude Opus 5.5 through Anthropic's API. Under Anthropic's commercial API terms, inputs are not used to train its models. CodeCheck never trains or changes any model.

CodeCheck writes a short text summary from your space's own decisions and notes: lines marked It's there, Not done or Doesn't apply, and problems confirmed or dismissed. That summary is sent, as plain written guidance, with the later reviews of that same space's projects.

• It is built only from the projects in your space, and used only on your space's reviews. It never goes to another space or another company's reviews.
• It is not model training: no AI model is changed by it. It is text sent along with a review, like the checklist.
• It can steer what the review looks at and how it words a line; it cannot make evidence appear on a sheet.
• There is no switch to turn it off yet.

A space is one company, or a group of companies that chose to work in one space on the same projects, such as KMK and its consultants. Within a shared space the summary comes from all of that space's projects.

• CodeCheck's cloud store. Drawings, specs, review results and comments are kept in a private Vercel Blob store in the United States (US East). They are not stored in Canada. Nothing in the store is public: a signed-in browser is given a link to one file at a time, and the link stops working after 10 minutes.
• The browser of each person who opens a project. The browser keeps a working copy of the project and its drawings. Back up, in a project's menu, saves the project and its drawings to a file on that computer.
• The review computer. Reviews run on one computer that reads the sheets; today it is a computer in Michael O'Brien's office. It keeps a downloaded drawing for 7 days by default, and what it read on each page until that is cleared.

• Accounts signed in to the same space. A space is one company, or a group of companies working together on the same projects, such as KMK and its consultants. The server checks every request against the signed-in account and refuses anything outside that space's folder.
• Michael O'Brien, who runs CodeCheck, as its administrator.
• The holder of CodeCheck's hosting account, who can open the store from the hosting dashboard.
• Anyone you send a trade share link to. Without signing in, they see the sheets confirmed as that trade and the lines whose proof is all on those sheets, until the link is switched off or the project is deleted.

A project stays until the person who created it, or a company admin, deletes it. A deleted project goes to Recently deleted on the home page for 30 days, and anyone in the space can put it back. While it is there its share links stop working and lessons from it drop out of the space's summary within about ten minutes.

After the 30 days it can no longer be put back. Its drawings, review results and the comments on its lines are removed from the cloud store for good only when someone in the space opens Recently deleted, which removes up to three expired projects each time, or deletes a project, which removes up to two. There is no timer yet: when more have expired than that, it takes several of those visits, and if nobody in the space does either, they stay in the store until someone does.

Deleting a project does not remove:

• messages sent in the inbox, even ones that point at that project;
• a small note that the project was deleted and when;
• the review computer's copy: a downloaded drawing goes after 7 days by default, but its page reads stay until they are cleared. To have them cleared, ask: This site has no contact address set yet, so ask the person who gave you your CodeCheck sign-in to pass your question to Michael O'Brien, who runs CodeCheck.
• the copy in each browser until that browser next syncs, and any Back up files people saved.