Update Hub managed terms: add usage stats clause and revise reference marketing#155
Update Hub managed terms: add usage stats clause and revise reference marketing#155
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 35 minutes and 35 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThe pull request updates two managed terms documents (German and English versions) with an effective date change to April 2026. A new §3.11 section was added authorizing the Provider to collect, process, and store aggregated, non-personal statistical and technical usage data for operational purposes, explicitly stating no personal data is involved. Additionally, §8 regarding reference marketing was modified to grant customer consent upon contract conclusion rather than as optional consent, and revocation mechanics were adjusted to require good cause unless the Provider's legitimate interest prevails. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@content/hub-managed-terms.de.md`:
- Around line 112-114: Sections 8.1 and 8.2 conflict: 8.1 treats reference use
as based on "ausdrückliche Zustimmung" while 8.2 limits withdrawal to "wichtiger
Grund" and allows provider's overriding "berechtigtes Interesse"; choose one
lawful basis and make both clauses consistent—either (A) keep consent: change
8.2 to state the customer may withdraw the consent at any time by emailing
hub-support@cryptomator.org and that withdrawal applies prospectively without
requiring a "wichtiger Grund" or provider override, or (B) switch 8.1 to rely on
"berechtigtes Interesse" and reword 8.1 to explicitly cite the legitimate
interest and change 8.2 to reflect a limited right to object according to GDPR
rules (including the provider's ability to override if their legitimate interest
prevails); update the wording in both 8.1 and 8.2 to reflect the chosen approach
and remove the inconsistent phrases ("ausdrückliche Zustimmung" vs. "wichtiger
Grund"/"überwiegt").
- Line 47: Der Text in §3.11 widerspricht §3.10: §3.11 verbietet jede Weitergabe
an Dritte, während §3.10 die Nutzung von Subunternehmern erlaubt; passe §3.11 so
an, dass er ausdrücklich erlaubt, dass aggregierte, nicht-personenbezogene
Nutzungs- und Telemetriedaten von Subunternehmern im Sinne von §3.10 verarbeitet
werden dürfen (z. B. durch Ergänzung wie "sofern dies gemäß §3.10 durch
vertraglich verpflichtete Subunternehmer erfolgt, die denselben
Vertraulichkeits- und Datenschutzpflichten unterliegen"), oder füge eine
Ausnahmeklausel hinzu, die klarstellt, welche Drittempfänger (z. B.
Subunternehmer, Hosting-/Analyse-Dienstleister) zulässig sind und dass
personenbezogene Daten weiterhin ausgeschlossen bleiben; referenziere dabei die
Vertragsstellen §3.10 und §3.11 beim Textänderungsentwurf.
In `@content/hub-managed-terms.en.md`:
- Around line 116-118: Sections "8.1" and "8.2" are inconsistent because 8.1
frames use of the Customer as a reference on "express consent" while 8.2
restricts revocation to "good cause" and defers to the Provider's legitimate
interest; choose one legal basis and make both clauses consistent: either (A)
keep "express consent" in 8.1 and remove the "for good cause" and "unless the
Provider's legitimate interest prevails" language from 8.2 so revocation by
email to hub-support@cryptomator.org is unconditional and prospective, or (B)
change 8.1 to state the Provider relies on a "legitimate interest" (not consent)
and adjust 8.2 to reflect that revocation is only effective if the Customer
demonstrates overriding interests (keeping the "unless the Provider's legitimate
interest prevails" wording); update the text of 8.1 and 8.2 accordingly so they
consistently reference the chosen legal basis.
- Line 50: §3.11 currently forbids disclosure of telemetry to third parties but
§3.10 allows subcontractors, creating a contractual inconsistency; update §3.11
to state that telemetry is only shared with third-party subprocessors engaged
under §3.10 and bound by equivalent confidentiality and data-processing
obligations, explicitly limit such sharing to aggregated, non-personal metrics
(no identifiers, emails, IPs, vault names), and require the Provider to ensure
subcontractors cannot re-identify data and are subject to the same security, use
restrictions and audit/contractual controls referenced in §3.10.
🪄 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: ca15a149-420d-4b86-b312-f8ec2ed2c91b
📒 Files selected for processing (2)
content/hub-managed-terms.de.mdcontent/hub-managed-terms.en.md
2 participants
No description provided.