Skip to content

Tos update#3917

Open
iiamlewis wants to merge 3 commits into
v31from
TOS-update
Open

Tos update#3917
iiamlewis wants to merge 3 commits into
v31from
TOS-update

Conversation

@iiamlewis
Copy link
Copy Markdown
Contributor

@iiamlewis iiamlewis commented May 13, 2026

Description:

Bump "Last Updated" dates to 5/13/2026 and replace OpenFront LLC references with OpenFront Inc. across Terms of Service and Privacy Policy. Update corporate designation to a Delaware corporation, change registered agent/address to Paracorp Incorporated (2140 South Dupont Hwy, Camden, DE), and switch governing law from California to Delaware. Minor wording clarifications in the introduction and contact/legal sections.

Please complete the following:

  • I have added screenshots for all UI updates
  • I process any text displayed to the user through translateText() and I've added it to the en.json file
  • I have added relevant tests to the test directory
  • I confirm I have thoroughly tested these changes and take full responsibility for any bugs introduced

Please put your Discord username so you can be contacted if a bug or regression is found:

iamlewis

Bump "Last Updated" dates to 5/13/2026 and replace OpenFront LLC references with OpenFront Inc. across Terms of Service and Privacy Policy. Update corporate designation to a Delaware corporation, change registered agent/address to Paracorp Incorporated (2140 South Dupont Hwy, Camden, DE), and switch governing law from California to Delaware. Minor wording clarifications in the introduction and contact/legal sections.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cb4d6c78-35f4-4e7e-a744-b18f520b7672

📥 Commits

Reviewing files that changed from the base of the PR and between dce8374 and 6ca85ee.

📒 Files selected for processing (1)
  • LICENSING.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • LICENSING.md

Walkthrough

Privacy policy, Terms of Service, and repository licensing documents were updated to replace OpenFront LLC with OpenFront Inc., update last‑updated dates and copyright years, change governing law to Delaware where present, and revise mailing/contact addresses to Paracorp Incorporated / Camden, DE as applicable.

Changes

Legal & Licensing Updates

Layer / File(s) Summary
Privacy policy entity and address updates
resources/privacy-policy.html
Last-updated date set to 5/13/2026; introductory definition now identifies "OpenFront" as OpenFront Inc., a Delaware corporation; Section 1 data controller mailing address updated to Paracorp Incorporated (Delaware); Section 7 company name updated to OpenFront Inc.; Section 14 legal enquiries address changed to OpenFront Inc. at Paracorp Incorporated.
Terms of service entity, jurisdiction, and contact updates
resources/terms-of-service.html
Last-updated date set to 5/13/2026; introduction identifies provider as OpenFront Inc., a Delaware corporation; Governing Law changed to State of Delaware; Contact Us mailing address replaced with Camden, Kent County, DE (c/o Paracorp Incorporated).
Repository licensing and contributor wording updates
LICENSING.md
Multiple copyright and attribution lines updated from OpenFront LLC to OpenFront Inc.; Phase 4 contributor/attribution bullets rewritten and contributors/copyright phrasing adjusted; External/Proprietary Assets years updated to 2024–2026.
LICENSE-ASSETS textual updates
LICENSE-ASSETS
/resources BY‑SA attribution wording clarified to require credit to "OpenFront" or "OpenFront Inc."; /proprietary copyright holder updated to OpenFront Inc. and Contributors (2024–2026); external/proprietary asset notice changed to OpenFront Inc.
Proprietary LICENSE holder and contributions clause
proprietary/LICENSE
Copyright holder changed to OpenFront Inc.; contributions license grant clause updated to reference OpenFront Inc..

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

From LLC to Inc., the pages align,
Delaware named in each legal line,
Dates and credits now freshly set,
Camden mail and Paracorp met,
Docs updated — the change is fine.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Tos update' is too vague and generic; it doesn't clearly convey what specific changes were made to the Terms of Service. Use a more descriptive title such as 'Update TOS and Privacy Policy to reflect OpenFront Inc. and Delaware incorporation' to clearly indicate the scope of changes.
✅ Passed checks (4 passed)
Check name Status Explanation
Description check ✅ Passed The description is well-detailed and directly related to the changeset, clearly outlining all updates to legal documents and corporate information.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@iiamlewis iiamlewis added the will not stale PRs that will not be closed by the stale action label May 13, 2026
@iiamlewis iiamlewis added this to the v32 milestone May 13, 2026
@iiamlewis iiamlewis changed the base branch from main to v31 May 13, 2026 09:58
@iiamlewis
Copy link
Copy Markdown
Contributor Author

@CodeRabbit your thick run again

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

@iiamlewis Sure, kicking off a fresh review now! 🐰

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@openfrontio openfrontio Bot had a problem deploying to staging May 13, 2026 10:04 Failure
Celant
Celant previously approved these changes May 13, 2026
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@resources/terms-of-service.html`:
- Around line 63-68: Update all remaining references of the legal entity from
"OpenFront LLC" to "OpenFront Inc." across the repo: edit proprietary/LICENSE,
LICENSE-ASSETS, and LICENSING.md to replace "OpenFront LLC" with "OpenFront
Inc." and ensure any accompanying descriptor (e.g., "a Delaware corporation")
and copyright/contributor/license-grant lines reflect the new entity; preserve
original license text and attribution wording except for the entity name change.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ff7e8dbe-b303-48d2-864e-650e7004b591

📥 Commits

Reviewing files that changed from the base of the PR and between aeb8d60 and 773a139.

📒 Files selected for processing (2)
  • resources/privacy-policy.html
  • resources/terms-of-service.html

Comment thread resources/terms-of-service.html
@github-project-automation github-project-automation Bot moved this from Triage to Development in OpenFront Release Management May 13, 2026
@iiamlewis
Copy link
Copy Markdown
Contributor Author

@CodeRabbit review please

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
LICENSING.md (1)

15-15: ⚡ Quick win

Inconsistent capitalization of "contributors".

The term appears as "(and contributors)" (lowercase, in parentheses) at lines 15, 25, 35, and 121, but as "and Contributors" (capitalized, no parentheses) at line 50. This inconsistency in legal text may create ambiguity about whether these refer to the same group.

Consider standardizing the capitalization throughout the document.

📝 Suggested standardization
-**Copyright Holders:** OpenFront Inc. and Contributors
+**Copyright Holders:** OpenFront Inc. (and contributors)

Also applies to: 25-25, 35-35, 50-50, 121-121

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@LICENSING.md` at line 15, Standardize the capitalization and formatting of
the contributors label across the document by choosing one canonical form (e.g.,
"and Contributors" or "(and contributors)") and replacing all instances of the
alternate form so they match; specifically replace occurrences of "(and
contributors)" and "and Contributors" so every mention uses the selected string,
updating the entries that currently show "(and contributors)" at the other
occurrences to the chosen canonical form to ensure consistency in the LICENSING
text.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@LICENSING.md`:
- Line 116: The footer line contains a double period in the sentence "For
questions, contact OpenFront Inc.."; edit that line to remove the extra period
so it reads "For questions, contact OpenFront Inc." — locate and update the
exact string to ensure only a single trailing period remains.

---

Nitpick comments:
In `@LICENSING.md`:
- Line 15: Standardize the capitalization and formatting of the contributors
label across the document by choosing one canonical form (e.g., "and
Contributors" or "(and contributors)") and replacing all instances of the
alternate form so they match; specifically replace occurrences of "(and
contributors)" and "and Contributors" so every mention uses the selected string,
updating the entries that currently show "(and contributors)" at the other
occurrences to the chosen canonical form to ensure consistency in the LICENSING
text.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0a50acd5-3e5a-43a5-b4c2-19da128d40f1

📥 Commits

Reviewing files that changed from the base of the PR and between 773a139 and dce8374.

📒 Files selected for processing (3)
  • LICENSE-ASSETS
  • LICENSING.md
  • proprietary/LICENSE
✅ Files skipped from review due to trivial changes (1)
  • proprietary/LICENSE

Comment thread LICENSING.md Outdated
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

@iiamlewis Sure! Kicking off a fresh review of your TOS/Privacy Policy updates now. 🐰

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@openfrontio openfrontio Bot had a problem deploying to staging May 13, 2026 10:22 Failure
Copy link
Copy Markdown
Contributor

@Celant Celant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Failing tests

@openfrontio openfrontio Bot had a problem deploying to staging May 13, 2026 10:38 Failure
Copy link
Copy Markdown
Contributor

@Celant Celant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why it won't deploy properly, but I doubt it's an actual issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

will not stale PRs that will not be closed by the stale action

Projects

Status: Development

Development

Successfully merging this pull request may close these issues.

2 participants