RIP EU Online dispute resolution #130
Conversation
WalkthroughThe changes update the effective dates in multiple German and English legal documents, moving them to July 2025. Sections related to extrajudicial or online dispute resolution were revised by removing references to the EU Commission's online dispute resolution platform, including links and explanatory text. The dispute resolution sections were simplified by consolidating multiple clauses into a single statement that the provider (Skymatic) is neither obligated nor willing to participate in dispute resolution before a consumer arbitration board. No other substantive or public API changes were made. Estimated code review effort1 (~5 minutes) 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
content/terms.de.md (1)
5-6: Consider using a proper heading instead of italic text for the effective date
markdownlintflags the emphasis-as-heading pattern (MD036).
Changing_Stand: Juli 2025_to a level-3 heading keeps the visual emphasis while silencing the linter:
- _Stand: Juli 2025_ +### Stand: Juli 2025content/hub-managed-terms.en.md (1)
6-7: Minor MD lint issue: prefer a heading for the effective dateSame MD036 warning as in the German file. Converting the line to
### Effective date: July 2025keeps the styling consistent and quiets the linter.content/hub-managed-terms.de.md (1)
6-7: Italic date triggers MD036 – switch to a headingReplace the emphasised date with a heading (
### Stand: Juli 2025) for linter compliance and visual consistency across documents.content/terms.en.md (1)
5-6: Resolve MD036 warning by using a heading for the effective date- _Effective date: July 2025_ +### Effective date: July 2025
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
content/hub-managed-terms.de.md(2 hunks)content/hub-managed-terms.en.md(2 hunks)content/impressum.de.md(0 hunks)content/impressum.en.md(0 hunks)content/terms.de.md(2 hunks)content/terms.en.md(2 hunks)
💤 Files with no reviewable changes (2)
- content/impressum.de.md
- content/impressum.en.md
🧰 Additional context used
🧠 Learnings (1)
content/hub-managed-terms.de.md (1)
Learnt from: iammajid
PR: #129
File: i18n/de.yaml:1237-1238
Timestamp: 2025-07-08T07:52:25.438Z
Learning: The Cryptomator website uses informal address ("du" form) consistently in German translations, as they are "on first name terms" with their users. Formal address ("Sie") should be avoided to maintain the friendly, approachable tone.
🪛 markdownlint-cli2 (0.17.2)
content/terms.en.md
5-5: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
content/hub-managed-terms.de.md
6-6: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🔇 Additional comments (4)
content/terms.de.md (1)
110-112: Removal of the EU ODR-platform reference – please double-check legal necessityArt. 14 EU Regulation 524/2013 (ODR) still obliges traders who enter into online sales/service contracts with consumers to provide both the link and an email address—even if they declare non-participation in ADR.
Before merging, confirm with legal counsel that deleting the sentence and thehttps://ec.europa.eu/consumers/odr/link does not create a compliance gap for Skymatic’s B2C business.content/hub-managed-terms.en.md (1)
222-224: Verify legality of dropping the EU ODR platform linkThe clause now states only non-participation in ADR. Ensure that the EU-wide requirement to at least link to the (currently still accessible) ODR platform no longer applies to SaaS B2C contracts, or add the reference back.
content/hub-managed-terms.de.md (1)
218-220: Re-check statutory duty to mention the EU ODR platformLike the English version, the German SaaS AGB now omits the ODR link. Please confirm that Art. 14 VO (EU) 524/2013 and § 36 VSBG no longer oblige Skymatic to provide that information when addressing Verbraucher.
content/terms.en.md (1)
114-116: Legal compliance check: Omission of EU ODR platform linkThe mandatory ODR link was removed. Please confirm that Skymatic’s T&C no longer falls under Art. 14 ODR Regulation requirements; otherwise the URL and email address must be reinstated.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/hub-managed-terms.en.md (1)
6-6: Replace emphasis with a proper heading to satisfy MD036 and improve semantics
markdownlintrightfully flags the italicised line as an anti-pattern (“emphasis used instead of a heading”). A heading communicates structural intent and is friendlier to screen-readers and anchor links.-_Effective date: July 2025_ +### Effective date: July 2025
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/hub-managed-terms.en.md(2 hunks)content/terms.en.md(2 hunks)
🪛 markdownlint-cli2 (0.17.2)
content/hub-managed-terms.en.md
6-6: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🚧 Files skipped from review as they are similar to previous changes (1)
- content/terms.en.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
content/hub-managed-terms.en.md
6-6: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🔇 Additional comments (1)
content/hub-managed-terms.en.md (1)
222-224: Section 17 looks good—anchor is retained, content simplifiedThe revised heading and single-sentence statement are clear and legally accurate, and the
{#dispute-resolution}anchor remains stable for incoming links. No further action needed here.
No description provided.