Skip to content

Legal c safeharbor - #65

Merged
amsultan2010 merged 2 commits into
mainfrom
amsultan2010/legal-c-safeharbor
Aug 6, 2026
Merged

amsultan2010 merged 2 commits into
mainfrom
amsultan2010/legal-c-safeharbor

Conversation

@amsultan2010

Copy link
Copy Markdown
Owner

No description provided.

Crosscode stores files users upload, which makes the provider a hosting
service. Both the US §512(c) safe harbor and the DSA hosting regime attach
only if specific things are done in advance, and both are conditional on
actually acting on a notice.

- docs/dmca.md: the six §512(c)(3)(A) notice elements, the designated agent's
  contact, the §512(g)(3) counter-notice procedure and its 10-14 business day
  statutory window, and a three-strike repeat-infringer policy. Flags that
  registering the agent with the Copyright Office is an owner action, not a
  code change, and that the registration expires after three years — an
  expired one is legally identical to none.
- docs/dsa-contact.md: Art. 11/12 single point of contact (abuse@, English),
  Art. 16 notice-and-action, Art. 17 statement of reasons, and the Art. 15(2)
  micro-enterprise transparency exemption stated rather than assumed. Art. 13
  EU legal representative marked as consciously deferred.
- docs/abuse-handling.md: internal runbook, repo-only, not registered in
  GENERATED_PAGES and not linked from the footer. Names the actual tables and
  statements a takedown needs, and ends with ten capability gaps the service
  cannot currently close — most importantly that deleting one file's changes
  from the middle of a room's sequence silently breaks the contiguity
  listChanges relies on, so whole-project deletion is the only safe
  granularity today.

Plumbing: both public pages registered in GENERATED_PAGES, the docs sidebar,
the vite rollup inputs, the landing footer's Trust column, and .gitignore
(the generated HTML is build output like every other page's).

generate-docs.mjs now strips HTML comments before rendering. The renderer runs
with html:false, so a `<!-- LAWYER: ... -->` note left in a source file was
being escaped and printed on the published page as visible text.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 6, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
crosscode Ready Ready Preview Aug 6, 2026 5:56pm

@amsultan2010
amsultan2010 merged commit a2f37df into main Aug 6, 2026
2 checks passed
@amsultan2010
amsultan2010 deleted the amsultan2010/legal-c-safeharbor branch August 9, 2026 21:25

This branch was successfully deployed

1 active deployment
Preview — 855fe042 Deployed Aug 6, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant