feat: add policy documents

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "restricted",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

.changeset/odd-zebras-find.md

@@ -0,0 +1,5 @@
+---
+"@joinnextblock/github": major
+---
+
+Add policy documents (TOS, DMCA, PRIVACY and RELAY)

.github/workflows/changeset.yml

@@ -0,0 +1,31 @@
+name: Create Changeset
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  changeset:
+    name: Create Changeset
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: 'npm'
+
+      - name: Install Dependencies
+        run: npm ci
+
+      - name: Create Changeset
+        uses: changesets/action@v1
+        with:
+          title: "chore: add changeset"
+          commit: "chore: add changeset"
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release.yml

@@ -0,0 +1,38 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: 'npm'
+
+      - name: Install Dependencies
+        run: npm ci
+
+      - name: Create Release Pull Request or Publish
+        id: changesets
+        uses: changesets/action@v1
+        with:
+          publish: npm run release
+          title: "chore: release"
+          commit: "chore: release"
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.gitignore

@@ -0,0 +1,50 @@
+# Dependencies
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# nyc test coverage
+.nyc_output
+
+# Dependency directories
+jspm_packages/
+
+# Optional npm cache directory
+.npm
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# IDE files
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS generated files
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db

CHANGESETS.md

@@ -0,0 +1,103 @@
+# Changesets Guide for NextBlock GitHub Organization
+
+This repository uses [Changesets](https://github.com/changesets/changesets) to manage versioning and changelogs for the NextBlock GitHub organization documentation and policies.
+
+## What are Changesets?
+
+Changesets are a way to track changes to your repository that should result in a new version being published. They help maintain a clear changelog and automate the release process.
+
+## How to Use Changesets
+
+### 1. Creating a Changeset
+
+When you make changes that should be versioned (like updating policies, documentation, or organization information), create a changeset:
+
+```bash
+npm run changeset
+```
+
+This will prompt you to:
+- Select the type of change (major, minor, patch)
+- Write a description of the changes
+- Select which packages are affected
+
+### 2. Types of Changes
+
+- **Major**: Breaking changes (e.g., major policy updates, structural changes)
+- **Minor**: New features or significant updates (e.g., new policies, updated documentation)
+- **Patch**: Bug fixes or minor updates (e.g., typo fixes, small clarifications)
+
+### 3. Workflow
+
+1. Make your changes to the repository
+2. Create a changeset: `npm run changeset`
+3. Commit your changes and the changeset file
+4. Push to create a pull request
+5. The GitHub Action will automatically create a release PR when changesets are present
+6. Review and merge the release PR to publish the new version
+
+### 4. Available Scripts
+
+- `npm run changeset` - Create a new changeset
+- `npm run version` - Version packages based on changesets
+- `npm run release` - Publish packages (if applicable)
+
+## GitHub Actions
+
+This repository includes two automated workflows:
+
+1. **Create Changeset** (`.github/workflows/changeset.yml`)
+   - Runs on pull requests to main
+   - Helps create changesets for contributors
+
+2. **Release** (`.github/workflows/release.yml`)
+   - Runs on pushes to main
+   - Automatically creates release pull requests when changesets are present
+   - Publishes new versions when release PRs are merged
+
+## Configuration
+
+The changesets configuration is in `.changeset/config.json`:
+
+- **changelog**: Uses the default changelog generator
+- **commit**: Disabled (we handle commits manually)
+- **access**: Restricted (appropriate for organization repositories)
+- **baseBranch**: Main branch
+- **updateInternalDependencies**: Patch level updates
+
+## Best Practices
+
+1. **Always create a changeset** for meaningful changes
+2. **Be descriptive** in your changeset messages
+3. **Use appropriate change types** (major/minor/patch)
+4. **Review release PRs** before merging
+5. **Keep changesets focused** on a single logical change
+
+## Examples
+
+### Policy Update
+```bash
+npm run changeset
+# Select: minor
+# Description: "Updated privacy policy to reflect new data handling practices"
+```
+
+### Documentation Fix
+```bash
+npm run changeset
+# Select: patch
+# Description: "Fixed typos in README and updated contact information"
+```
+
+### Major Organizational Change
+```bash
+npm run changeset
+# Select: major
+# Description: "Restructured organization policies and updated terms of service"
+```
+
+## Need Help?
+
+- [Changesets Documentation](https://github.com/changesets/changesets)
+- [Common Questions](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)
+- Contact the NextBlock team for repository-specific questions

DMCA-POLICY.md

@@ -0,0 +1,95 @@
+**NextBlock™ DMCA Policy**
+
+Effective Date: August 1, 2025
+
+**Section 1**.          **Introduction**
+
+We take your copyright protection seriously. This DMCA Policy was adopted in accordance with the Digital Millennium Copyright Act of 1998 and covers how we handle and respond to notices and allegations that any content or material on our Website infringes on your copyright.
+
+This DMCA Policy is a legally-binding agreement between you and NEXTBLOCK INC., a Texas corporation, doing business as NEXTBLOCK™ (“**we**” or “**us**” or “**our**” or “**NextBlock**”). By using or accessing our Website and Products and Services or by submitting a DMCA notice, you agree to be bound by the terms of this DMCA Policy and our other Terms (see below).
+
+If you object to anything in this DMCA Policy (or otherwise do not understand or agree to be bound by this DMCA Policy), then do not use our Products and Services. If you use our Products and Services in any way, you acknowledge that you have read, understand, and agree to this DMCA Policy.
+
+We may change this DMCA Policy at any time. We will provide you with notice of any material change and tell you the date on which such changes will be effective. We may provide this notice to you by email or by posting a notice on the Website. It is your responsibility to review any changes to this DMCA Policy. If you object to any of the changes to this DMCA Policy (or otherwise do not understand or agree to any of the changes to this DMCA Policy), then do not continue to use our Products and Services. By continuing to access or use our Products and Services following notice of any change to this DMCA Policy, you acknowledge that you have read, understand, and agree to this DMCA Policy as changed.
+
+You may print a copy of this DMCA Policy by using the print button or feature in your browser. We suggest retaining a copy for future reference.
+
+**Section 2.          Our Rules and Policies**
+
+This DMCA Policy, our Terms of Service (“**Terms**”), our Privacy Policy, and our Relay Policy are the Rules and Policies that apply to and govern your access to and use of our Products and Services. Please see our Terms for more information on our Rules and Policies.
+
+This DMCA Policy is incorporated into and is part of our Terms. Any capitalized terms not otherwise defined in this DMCA Policy are defined as set forth in the Terms.
+
+**Section 3.          DMCA Takedown Notice Procedures**
+
+We are committed to protecting your copyrights. We will process all valid DMCA notifications and counter-notifications that we receive in accordance with this section, but we will not adjudicate these disputes.
+
+(1)           Reporting a Copyright Violation.
+
+(A)          If you believe your copyright is being infringed, you can submit a DMCA takedown notice by contacting us at the address listed in Section 4 below. Your claim must be submitted in English and must include at least the following information:
+
+(i)            your physical or electronic signature;
+
+(ii)           identification of the copyrighted work that you claim has been infringed;
+
+(iii)         identification of the material that you claim to be infringing or to be the subject of infringing activity and that is to be removed or access to which is to be disabled, and information reasonably sufficient to permit us to locate the material;
+
+(iv)          your address, telephone number, and email address;
+
+(v)           a statement that you have a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law; and
+
+(vi)          a statement that the information in the notification is accurate, and under penalty of perjury, that you are authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
+
+(B)          If you are not sure if your copyright is being infringed or if you have complied with the notice requirements, we encourage you to consult with an attorney before submitting a DMCA takedown notice or contacting us. It is your sole obligation to ensure that your notice complies with applicable law. Please confirm these requirements with an attorney or see the U.S. Copyright Act, 17 U.S.C. § 512(c)(3) for more information.
+
+(C)          We reserve the right to forward all materials received (including your full contact information) to the opposing party in any DMCA dispute.
+
+(2)           Receipt of a DMCA Takedown Notice. Upon receipt of a valid and complete DMCA takedown notice, we will verify that the notice substantially meets the formal requirements under 17 U.S.C § 512. Once this determination is made, we will take the following actions:
+
+(A)          expeditiously remove or disable access to the material that is claimed to be infringing;
+
+(B)          notify an applicable user, if any, that the material has been removed so that they may file a counter-notice should they wish;
+
+(C)          if proper counter-notice is provided, notify the copyright holder and provide a copy of that counter-notice; and
+
+(D)          if proper counter-notice is provided and if the copyright holder does not file suit within 10 business days, restore the removed material.
+
+(3)           Submitting a Counter-Notification.
+
+(A)          If we receive a DMCA notification and believe that your Content is the subject of such notification, we will provide you with notice and a copy of the DMCA notification.
+
+(B)          If you receive a copy of a DMCA notice from us and believe that your Content has been removed or disabled by mistake or because of misidentification, you can submit a counter-notification by contacting us.  Your counter-notification must be submitted in English and must contain the following information:
+
+(i)            your physical or electronic signature;
+
+(ii)           identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled;
+
+(iii)         a statement under penalty of perjury that you have a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled; and
+
+(iv)          your name, address, and telephone number, and a statement that you consent to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if your address is outside of the United States, for any judicial district in which the service provider may be found, and that you will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.
+
+(C)          If you are not sure how to respond or if you have complied with the counter-notice requirements, we encourage you to consult with an attorney before submitting a counter-notice or contacting us. It is your sole obligation to ensure that your counter-notice complies with applicable law. Please confirm these requirements with an attorney or see the 17 U.S.C. §512(g)(3) for more information.
+
+(D)          We reserve the right to forward all materials received (including your full contact information) to the opposing party in any DMCA dispute.
+
+(4)           Receipt of a Counter-Notice. Upon receipt and verification of your counter-notification, we will forward the counter-notification to the copyright owner. If we do not receive a notice within 10 business days after forwarding the counter-notification that the owner has filed an action seeking a court order to prevent further infringement, we may restore the removed material.
+
+(5)           Access to Content. We may disable or restrict your access to the website after we receive your counter-notification until the dispute is resolved or until 10 business days have passed without notification that the copyright owner has filed an action seeking a court order.
+
+(6)           Termination of Repeat Infringers. We reserve the right to terminate or suspend the Account or access of any repeat copyright infringers.
+
+**Section 4.          Contacting Our Copyright Agent**
+
+You may send any notices and other communication to our copyright agent at the following address:
+
+NEXTBLOCK INC.
+
+Attn: Ian Reis
+
+Re: Copyright Agent
+
+10601 Clarence Dr., Suite 250
+
+Frisco, TX 75033
+
+© 2025 NextBlock™