Skip to content

RIP EU Online dispute resolution #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 22, 2025

Conversation

SailReal
Copy link
Member

No description provided.

@SailReal SailReal requested a review from tobihagemann July 21, 2025 16:20
Copy link
Contributor

coderabbitai bot commented Jul 21, 2025

Walkthrough

The 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 effort

1 (~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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
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: 0

🧹 Nitpick comments (4)
content/terms.de.md (1)

5-6: Consider using a proper heading instead of italic text for the effective date

markdownlint flags 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 2025
content/hub-managed-terms.en.md (1)

6-7: Minor MD lint issue: prefer a heading for the effective date

Same MD036 warning as in the German file. Converting the line to ### Effective date: July 2025 keeps the styling consistent and quiets the linter.

content/hub-managed-terms.de.md (1)

6-7: Italic date triggers MD036 – switch to a heading

Replace 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

📥 Commits

Reviewing files that changed from the base of the PR and between bf37fd6 and 419cb08.

📒 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 necessity

Art. 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 the https://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 link

The 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 platform

Like 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 link

The 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.

@SailReal SailReal merged commit 202c78f into develop Jul 22, 2025
3 of 4 checks passed
@SailReal SailReal deleted the feature/rip-out-of-court-dispute-resolution branch July 22, 2025 08:24
Copy link
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: 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

markdownlint rightfully 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

📥 Commits

Reviewing files that changed from the base of the PR and between 4b9a398 and e65e299.

📒 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 simplified

The 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.

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.

2 participants