Add terms of service #172
Add terms of service #172
Conversation
|
Warning Rate limit exceeded@cp-megh-l has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 40 seconds before requesting another review. ⌛ 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. 📒 Files selected for processing (1)
WalkthroughThe pull request introduces a comprehensive Terms of Service document for Canopas Software's mobile application, Grouptrack. The document establishes a legal framework defining the rights, responsibilities, and expectations for both the company and its users. It covers critical aspects such as user registration, service usage, intellectual property rights, user contributions, prohibited activities, dispute resolution, and data privacy guidelines. Changes
Sequence DiagramsequenceDiagram
participant User
participant Grouptrack App
participant Canopas Software
User->>Grouptrack App: Agrees to Terms of Service
Grouptrack App->>Canopas Software: Validate user acceptance
Canopas Software-->>Grouptrack App: Confirm terms acceptance
Grouptrack App-->>User: Grant application access
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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: 5
🧹 Nitpick comments (4)
docs/terms-of-service.md (4)
81-84: Consider expanding industry-specific regulations.Since the app deals with location data and family safety, consider mentioning relevant regulations like GDPR (for EU users) and COPPA (for children's data protection).
542-543: Use relative links for Privacy Policy.Replace the hardcoded URL with a relative link to make the document more maintainable.
-Policy: https://canopas.github.io/group-track-android/privacy-policy. By using the Services, you +Policy: [Privacy Policy](../privacy-policy.md). By using the Services, you🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
542-542: Bare URL used
null(MD034, no-bare-urls)
803-823: Enhance open-source licensing section.Since this is an open-source project, consider:
- Explicitly stating the project's license (e.g., MIT)
- Adding a link to the LICENSE file
- Clarifying contribution guidelines
- Explaining how users can access the source code
🧰 Tools
🪛 LanguageTool
[style] ~807-~807: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ... of the open-source license will govern with respect to that portion of the software. **User C...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
🪛 markdownlint-cli2 (0.17.2)
810-810: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
818-818: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
1-841: Address formatting and style issues.Several formatting issues were identified by static analysis:
- Replace bare URLs with proper Markdown links
- Use proper heading hierarchy instead of bold text for section titles
- Fix inconsistent line endings
- Remove redundant wordings like "any and all", "prior to", etc.
🧰 Tools
🪛 LanguageTool
[style] ~37-~37: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...ian read and agree to these Legal Terms prior to you using the Services. We recommend t...(EN_WORDINESS_PREMIUM_PRIOR_TO)
[uncategorized] ~49-~49: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ervices.md#6-prohibited-activities) 7. [USER GENERATED CONTRIBUTIONS](https://github.com/canop...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[typographical] ~106-~106: Do not use a colon (:) before a series that is introduced by a preposition (‘to’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...ve, non-transferable, revocable license to: access the Services; and download or pr...(RP_COLON)
[typographical] ~107-~107: Conjunctions like ‘and’ should not follow semicolons. Consider using a comma, or removing the conjunction.
Context: ...evocable license to: access the Services; and download or print a copy of any portion of the C...(CONJUNCTION_AFTER_SEMICOLON)
[style] ~132-~132: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...ohibited-activities)" section carefully prior to using our Services to understand the (a...(EN_WORDINESS_PREMIUM_PRIOR_TO)
[uncategorized] ~154-~154: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’.
Context: ...-exclusive, transferable, royalty-free, fully-paid, worldwide right, and license to: use, ...(HYPHENATED_LY_ADVERB_ADJECTIVE)
[typographical] ~154-~154: Do not use a colon (:) before a series that is introduced by a preposition (‘to’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...ully-paid, worldwide right, and license to: use, copy, reproduce, distribute, sell,...(RP_COLON)
[style] ~176-~176: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...nt permissible by applicable law, waive any and all moral rights to any such Submission and...(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~185-~185: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...you expressly agree to reimburse us for any and all losses that we may suffer because of yo...(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[uncategorized] ~207-~207: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...cessary; (3) you have the legal capacity and you agree to comply with these Legal Te...(COMMA_COMPOUND_SENTENCE)
[style] ~214-~214: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...nd or terminate your account and refuse any and all current or future use of the Services (...(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~250-~250: ‘until such time as’ might be wordy. Consider a shorter alternative.
Context: ...ior approval for each recurring charge, until such time as you cancel the applicable order. The le...(EN_WORDINESS_PREMIUM_UNTIL_SUCH_TIME_AS)
[style] ~266-~266: Consider using an alternative to avoid wordiness and strengthen your wording.
Context: [email protected]. Fee Changes We may, from time to time, make changes to the subscription fee a...(FROM_TIME_TO_TIME)
[style] ~266-~266: Consider shortening or rephrasing this to strengthen your wording.
Context: ...e Changes** We may, from time to time, make changes to the subscription fee and will communica...(MAKE_CHANGES)
[style] ~273-~273: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...an cancel your subscription at any time prior to the next billing date to avoid further ...(EN_WORDINESS_PREMIUM_PRIOR_TO)
[uncategorized] ~282-~282: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...required by law, fees are non-refundable and we do not provide refunds or credits fo...(COMMA_COMPOUND_SENTENCE)
[style] ~301-~301: Consider a shorter alternative to avoid wordiness.
Context: ... information obtained from the Services in order to harass, abuse, or harm another person. ...(IN_ORDER_TO_PREMIUM)
[uncategorized] ~313-~313: Possible missing comma found.
Context: ... Attempt to impersonate another user or person or use the username of another user. - ...(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~327-~327: Try using a synonym here to elevate your writing.
Context: ...f the software comprising or in any way making up a part of the Services. - Except as may...(CONSTITUTE_COMPRISE)
[uncategorized] ~336-~336: Possible missing comma found.
Context: ...s as part of any effort to compete with us or otherwise use the Services and/or th...(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~347-~347: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... unlawful or unauthorized usage. ## 7. USER GENERATED CONTRIBUTIONS The Services may invite ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~365-~365: ‘each and every’ might be wordy. Consider a shorter alternative.
Context: ... consent, release, and/or permission of each and every identifiable individual person in you...(EN_WORDINESS_PREMIUM_EACH_AND_EVERY)
[style] ~366-~366: ‘each and every’ might be wordy. Consider a shorter alternative.
Context: ...ibutions to use the name or likeness of each and every such identifiable individual person t...(EN_WORDINESS_PREMIUM_EACH_AND_EVERY)
[style] ~375-~375: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...sparage, intimidate, or abuse anyone. - Your Contributions are not used to harass or...(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~378-~378: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... applicable law, regulation, or rule. - Your Contributions do not violate the privac...(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~379-~379: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... publicity rights of any third party. - Your Contributions do not violate any applic...(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[formatting] ~393-~393: Insert a comma after “to us,”.
Context: ...rrant that you have the right to grant, to us an unrestricted, unlimited, irrevocable...(INTRODUCTORY_PHRASE_MISSING_COMMA)
[uncategorized] ~394-~394: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’.
Context: ...-exclusive, transferable, royalty-free, fully-paid, worldwide right, and license to host, ...(HYPHENATED_LY_ADVERB_ADJECTIVE)
[uncategorized] ~413-~413: Possible missing comma found.
Context: ...sponsible for your Contributions to the Services and you expressly agree to exonerate us...(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~413-~413: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...ou expressly agree to exonerate us from any and all responsibility and to refrain from any ...(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~429-~429: Try using a more descriptive synonym here to elevate your writing.
Context: ...ng negative reviews; (6) you should not make any conclusions as to the legality of c...(MAKE_CONCLUSIONS)
[style] ~436-~436: Consider simply using “of” instead.
Context: ...ily represent our opinions or the views of any of our affiliates or partners. We do not a...(OF_ANY_OF)
[style] ~472-~472: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...ng any maintenance and support services with respect to the App as specified in the terms and c...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~475-~475: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...sh any maintenance and support services with respect to the App; (3) in the event of any failur...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~479-~479: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...no other warranty obligation whatsoever with respect to the App; (4) you represent and warrant ...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[typographical] ~495-~495: Conjunctions like ‘or’ should not follow semicolons. Use a comma instead.
Context: ...t login information through the Services; or (2) allowing us to access your Third-Pa...(CONJUNCTION_AFTER_SEMICOLON)
[style] ~499-~499: Consider simply using “of” instead.
Context: ...rd-Party Account, without breach by you of any of the terms and conditions that govern yo...(OF_ANY_OF)
[uncategorized] ~517-~517: Possible missing comma found.
Context: ...twork Content for any purpose, including but not limited to, for accuracy, legality,...(AI_HYDRA_LEO_CPT_BUT_CBUT)
[style] ~535-~535: This wording could be more concise.
Context: ... disable all files and content that are excessive in size or are in any way burdensome to our sys...(ADJECTIVE_IN_ATTRIBUTE)
[style] ~595-~595: ‘WITHOUT WARNING’ might be wordy. Consider a shorter alternative.
Context: ...NFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION. If we termina...(EN_WORDINESS_PREMIUM_WITHOUT_WARNING)
[uncategorized] ~606-~606: Possible missing comma found.
Context: ... any time or for any reason at our sole discretion without notice. However, we have no obl...(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~610-~610: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ervices will be available at all times. We may experience hardware, software, or o...(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~651-~651: Consider using only “public” to avoid wordiness.
Context: ...epresentative capacity on behalf of the general public or any other persons. ### Exceptions t...(GENERAL_XX)
[style] ~684-~684: ‘ANY AND ALL’ might be wordy. Consider a shorter alternative.
Context: ... TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL I...(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[misspelling] ~724-~724: Did you mean “be”?
Context: ...ITATIONS OF LIABILITY IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS ...(WE_BE)
[uncategorized] ~724-~724: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...YEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[typographical] ~727-~727: Except for inverted sentences, ‘WILL WE’ requires a question mark at the end of the sentence.
Context: ...VISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRAR...(MD_PRP_QUESTION_MARK)
[uncategorized] ~738-~738: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...torneys’ fees and expenses, made by any third party due to or arising out of: (1) your Cont...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[typographical] ~743-~743: Conjunctions like ‘or’ should not follow semicolons. Use a comma instead.
Context: ...mited to intellectual property rights; or (6) any overt harmful act toward any ot...(CONJUNCTION_AFTER_SEMICOLON)
[uncategorized] ~743-~743: “you” seems less likely than “you’re” (you are).
Context: ...ny other user of the Services with whom you connected via the Services. Notwi...(AI_HYDRA_LEO_CP_YOU_YOUARE)
[style] ~758-~758: This phrase could be redundant. Consider writing “routine”.
Context: ...se of the Services. Although we perform regular routine backups of data, you are solely respons...(REGULAR_ROUTINE)
[style] ~797-~797: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...f having drafted them. You hereby waive any and all defenses you may have based on the elec...(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~807-~807: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ... of the open-source license will govern with respect to that portion of the software. **User C...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~825-~825: Consider a shorter alternative to avoid wordiness.
Context: ...d non-infringement. ## 28. CONTACT US In order to resolve a complaint regarding the Servi...(IN_ORDER_TO_PREMIUM)
🪛 markdownlint-cli2 (0.17.2)
20-20: Bare URL used
null(MD034, no-bare-urls)
30-30: Bare URL used
null(MD034, no-bare-urls)
88-88: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
101-101: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
117-117: Bare URL used
null(MD034, no-bare-urls)
128-128: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
246-246: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
253-253: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
258-258: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
262-262: Bare URL used
null(MD034, no-bare-urls)
264-264: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
269-269: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
275-275: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
280-280: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
445-445: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
465-465: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
542-542: Bare URL used
null(MD034, no-bare-urls)
619-619: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
810-810: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
818-818: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
829-829: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
831-831: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
833-833: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
835-835: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
837-837: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
839-839: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
841-841: Bare URL used
null(MD034, no-bare-urls)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/terms-of-service.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/terms-of-service.md
[style] ~37-~37: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...ian read and agree to these Legal Terms prior to you using the Services. We recommend t...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[uncategorized] ~49-~49: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ervices.md#6-prohibited-activities) 7. [USER GENERATED CONTRIBUTIONS](https://github.com/canop...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[typographical] ~106-~106: Do not use a colon (:) before a series that is introduced by a preposition (‘to’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...ve, non-transferable, revocable license to: access the Services; and download or pr...
(RP_COLON)
[typographical] ~107-~107: Conjunctions like ‘and’ should not follow semicolons. Consider using a comma, or removing the conjunction.
Context: ...evocable license to: access the Services; and download or print a copy of any portion of the C...
(CONJUNCTION_AFTER_SEMICOLON)
[style] ~132-~132: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...ohibited-activities)" section carefully prior to using our Services to understand the (a...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[uncategorized] ~154-~154: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’.
Context: ...-exclusive, transferable, royalty-free, fully-paid, worldwide right, and license to: use, ...
(HYPHENATED_LY_ADVERB_ADJECTIVE)
[typographical] ~154-~154: Do not use a colon (:) before a series that is introduced by a preposition (‘to’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...ully-paid, worldwide right, and license to: use, copy, reproduce, distribute, sell,...
(RP_COLON)
[style] ~176-~176: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...nt permissible by applicable law, waive any and all moral rights to any such Submission and...
(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~185-~185: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...you expressly agree to reimburse us for any and all losses that we may suffer because of yo...
(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[uncategorized] ~207-~207: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...cessary; (3) you have the legal capacity and you agree to comply with these Legal Te...
(COMMA_COMPOUND_SENTENCE)
[style] ~214-~214: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...nd or terminate your account and refuse any and all current or future use of the Services (...
(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~250-~250: ‘until such time as’ might be wordy. Consider a shorter alternative.
Context: ...ior approval for each recurring charge, until such time as you cancel the applicable order. The le...
(EN_WORDINESS_PREMIUM_UNTIL_SUCH_TIME_AS)
[style] ~266-~266: Consider using an alternative to avoid wordiness and strengthen your wording.
Context: [email protected]. Fee Changes We may, from time to time, make changes to the subscription fee a...
(FROM_TIME_TO_TIME)
[style] ~266-~266: Consider shortening or rephrasing this to strengthen your wording.
Context: ...e Changes** We may, from time to time, make changes to the subscription fee and will communica...
(MAKE_CHANGES)
[style] ~273-~273: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...an cancel your subscription at any time prior to the next billing date to avoid further ...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[uncategorized] ~282-~282: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...required by law, fees are non-refundable and we do not provide refunds or credits fo...
(COMMA_COMPOUND_SENTENCE)
[style] ~301-~301: Consider a shorter alternative to avoid wordiness.
Context: ... information obtained from the Services in order to harass, abuse, or harm another person. ...
(IN_ORDER_TO_PREMIUM)
[uncategorized] ~313-~313: Possible missing comma found.
Context: ... Attempt to impersonate another user or person or use the username of another user. - ...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~327-~327: Try using a synonym here to elevate your writing.
Context: ...f the software comprising or in any way making up a part of the Services. - Except as may...
(CONSTITUTE_COMPRISE)
[uncategorized] ~336-~336: Possible missing comma found.
Context: ...s as part of any effort to compete with us or otherwise use the Services and/or th...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~347-~347: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... unlawful or unauthorized usage. ## 7. USER GENERATED CONTRIBUTIONS The Services may invite ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~365-~365: ‘each and every’ might be wordy. Consider a shorter alternative.
Context: ... consent, release, and/or permission of each and every identifiable individual person in you...
(EN_WORDINESS_PREMIUM_EACH_AND_EVERY)
[style] ~366-~366: ‘each and every’ might be wordy. Consider a shorter alternative.
Context: ...ibutions to use the name or likeness of each and every such identifiable individual person t...
(EN_WORDINESS_PREMIUM_EACH_AND_EVERY)
[style] ~375-~375: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...sparage, intimidate, or abuse anyone. - Your Contributions are not used to harass or...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~378-~378: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... applicable law, regulation, or rule. - Your Contributions do not violate the privac...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~379-~379: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... publicity rights of any third party. - Your Contributions do not violate any applic...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[formatting] ~393-~393: Insert a comma after “to us,”.
Context: ...rrant that you have the right to grant, to us an unrestricted, unlimited, irrevocable...
(INTRODUCTORY_PHRASE_MISSING_COMMA)
[uncategorized] ~394-~394: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’.
Context: ...-exclusive, transferable, royalty-free, fully-paid, worldwide right, and license to host, ...
(HYPHENATED_LY_ADVERB_ADJECTIVE)
[uncategorized] ~413-~413: Possible missing comma found.
Context: ...sponsible for your Contributions to the Services and you expressly agree to exonerate us...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~413-~413: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...ou expressly agree to exonerate us from any and all responsibility and to refrain from any ...
(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~429-~429: Try using a more descriptive synonym here to elevate your writing.
Context: ...ng negative reviews; (6) you should not make any conclusions as to the legality of c...
(MAKE_CONCLUSIONS)
[style] ~436-~436: Consider simply using “of” instead.
Context: ...ily represent our opinions or the views of any of our affiliates or partners. We do not a...
(OF_ANY_OF)
[style] ~472-~472: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...ng any maintenance and support services with respect to the App as specified in the terms and c...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~475-~475: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...sh any maintenance and support services with respect to the App; (3) in the event of any failur...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~479-~479: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...no other warranty obligation whatsoever with respect to the App; (4) you represent and warrant ...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[typographical] ~495-~495: Conjunctions like ‘or’ should not follow semicolons. Use a comma instead.
Context: ...t login information through the Services; or (2) allowing us to access your Third-Pa...
(CONJUNCTION_AFTER_SEMICOLON)
[style] ~499-~499: Consider simply using “of” instead.
Context: ...rd-Party Account, without breach by you of any of the terms and conditions that govern yo...
(OF_ANY_OF)
[uncategorized] ~517-~517: Possible missing comma found.
Context: ...twork Content for any purpose, including but not limited to, for accuracy, legality,...
(AI_HYDRA_LEO_CPT_BUT_CBUT)
[style] ~535-~535: This wording could be more concise.
Context: ... disable all files and content that are excessive in size or are in any way burdensome to our sys...
(ADJECTIVE_IN_ATTRIBUTE)
[style] ~595-~595: ‘WITHOUT WARNING’ might be wordy. Consider a shorter alternative.
Context: ...NFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION. If we termina...
(EN_WORDINESS_PREMIUM_WITHOUT_WARNING)
[uncategorized] ~606-~606: Possible missing comma found.
Context: ... any time or for any reason at our sole discretion without notice. However, we have no obl...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~610-~610: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ervices will be available at all times. We may experience hardware, software, or o...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~651-~651: Consider using only “public” to avoid wordiness.
Context: ...epresentative capacity on behalf of the general public or any other persons. ### Exceptions t...
(GENERAL_XX)
[style] ~684-~684: ‘ANY AND ALL’ might be wordy. Consider a shorter alternative.
Context: ... TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL I...
(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[misspelling] ~724-~724: Did you mean “be”?
Context: ...ITATIONS OF LIABILITY IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS ...
(WE_BE)
[uncategorized] ~724-~724: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...YEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[typographical] ~727-~727: Except for inverted sentences, ‘WILL WE’ requires a question mark at the end of the sentence.
Context: ...VISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRAR...
(MD_PRP_QUESTION_MARK)
[uncategorized] ~738-~738: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...torneys’ fees and expenses, made by any third party due to or arising out of: (1) your Cont...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[typographical] ~743-~743: Conjunctions like ‘or’ should not follow semicolons. Use a comma instead.
Context: ...mited to intellectual property rights; or (6) any overt harmful act toward any ot...
(CONJUNCTION_AFTER_SEMICOLON)
[uncategorized] ~743-~743: “you” seems less likely than “you’re” (you are).
Context: ...ny other user of the Services with whom you connected via the Services. Notwi...
(AI_HYDRA_LEO_CP_YOU_YOUARE)
[style] ~758-~758: This phrase could be redundant. Consider writing “routine”.
Context: ...se of the Services. Although we perform regular routine backups of data, you are solely respons...
(REGULAR_ROUTINE)
[style] ~797-~797: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...f having drafted them. You hereby waive any and all defenses you may have based on the elec...
(EN_WORDINESS_PREMIUM_ANY_AND_ALL)
[style] ~807-~807: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ... of the open-source license will govern with respect to that portion of the software. **User C...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~825-~825: Consider a shorter alternative to avoid wordiness.
Context: ...d non-infringement. ## 28. CONTACT US In order to resolve a complaint regarding the Servi...
(IN_ORDER_TO_PREMIUM)
🪛 markdownlint-cli2 (0.17.2)
docs/terms-of-service.md
20-20: Bare URL used
null
(MD034, no-bare-urls)
30-30: Bare URL used
null
(MD034, no-bare-urls)
88-88: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
101-101: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
117-117: Bare URL used
null
(MD034, no-bare-urls)
128-128: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
246-246: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
253-253: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
258-258: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
262-262: Bare URL used
null
(MD034, no-bare-urls)
264-264: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
269-269: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
275-275: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
280-280: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
445-445: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
465-465: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
542-542: Bare URL used
null
(MD034, no-bare-urls)
619-619: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
810-810: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
818-818: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
829-829: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
831-831: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
833-833: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
835-835: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
837-837: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
839-839: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
841-841: Bare URL used
null
(MD034, no-bare-urls)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build
Summary by CodeRabbit