Conversation
WalkthroughThe end-user licence agreement documentation was updated with improved markdown formatting for section headers, expanded platform feature descriptions including authentication, authorisation, and advanced billing, added billing account requirements, generalized PCI DSS references, updated contact information with a hyperlink, and revised the last update date. No code or substantive legal terms were changed. Changes
Poem
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 (
|
github-actions
bot
added
the
security and privacy
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx (2)
8-8: Consolidate section headings and remove manual numberingUsing both manual numbering (
1.,2., etc.) and markdown headings (##) can lead to rendering inconsistencies. Consider dropping the numeric prefixes and relying solely on##for section titles. For example:- 8: 1. ## **Our Disclosures** + 8: ## Our DisclosuresThis change will produce cleaner, semantically correct headings and avoid duplicate numbering.
Also applies to: 16-16, 22-22, 35-35, 43-43, 51-51, 58-58, 67-67, 76-76, 84-84, 89-89, 101-101
19-19: Refine list punctuation and compound adjectivesThe list in the Introduction has punctuation issues and missing hyphens:
- Remove the stray comma after “with”
- Hyphenate “software-as-a-service”
- Ensure commas between items:
authentication, authorisation, user management, feature management, experimentation, advanced billing features, and other back-office features- We provide a cloud-based, software as a service platform where we help our customers with, authentication, authorisation user management, feature management, experimentation, advanced billing features and other back-office features... + We provide a cloud-based, software-as-a-service platform where we help our customers with authentication, authorisation, user management, feature management, experimentation, advanced billing features, and other back-office features...
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx(4 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx
[uncategorized] ~13-~13: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...al Loss, any loss that is a result of a Third Party Service, or any loss or corruption of d...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[grammar] ~20-~20: The progressive verb “agree” is used incorrectly. Consider changing it to the simple tense.
Context: ...on or entity using the Platform. If you are agreeing to these Terms not as an individual but...
(PROGRESSIVE_VERB_AGREE)
[grammar] ~20-~20: The pronoun ‘you’ must be used with a non-third-person form of a verb.
Context: ...yee or governmental official), then you means your entity and you are binding your en...
(NON3PRS_VERB)
[uncategorized] ~20-~20: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...al official), then you means your entity and you are binding your entity to these Te...
(COMMA_COMPOUND_SENTENCE)
[typographical] ~37-~37: Consider adding a comma after this introductory phrase.
Context: ...atform available at all times. However, from time to time we may perform reasonable scheduled and...
(FROM_TIME_TO_TIME_COMMA)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...rm may be reliant on, or interface with third party systems that are not provided by us (fo...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ail clients, and internet providers) (Third Party Services). To the maximum extent perm...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...law, we shall have no Liability for any Third Party Services, or any unavailability of the ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...of the Platform due to a failure of the Third Party Services. 3. Without limiting clause...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~45-~45: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ided by the entity you are involved with or you may also sign up on the Platform. ...
(COMMA_COMPOUND_SENTENCE)
[style] ~46-~46: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...may also sign up on the Platform. 2. You must provide basic information when reg...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ding your contact name and email address and you may be asked to choose a password. ...
(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~48-~48: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...any other person. Your login is personal and you must not transfer or provide it to ...
(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~49-~49: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... your username and password confidential and you will be liable for all activity via...
(COMMA_COMPOUND_SENTENCE)
[style] ~53-~53: Consider using an alternative to avoid wordiness and strengthen your wording.
Context: ...urity Standards (as amended and updated from time to time) (PCI DSS) when we store, process, tran...
(FROM_TIME_TO_TIME)
[style] ~54-~54: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e are compliant with the PCI DSS. 2. We will notify you should we become aware ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~71-~71: The progressive verb “agree” is used incorrectly. Consider changing it to the simple tense.
Context: ...etes with our business; 2. if you are agreeing to these Terms not as an individual but...
(PROGRESSIVE_VERB_AGREE)
[style] ~74-~74: Consider shortening this phrase to just “whether”, or rephrase the sentence to avoid “as to”.
Context: ... in relation to the Platform (including as to whether the Platform is or will be fit or suita...
(WHETHER)
🔇 Additional comments (1)
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx (1)
111-111: Make contact details actionable and verify links
- Wrap the email in a mailto link for easier click-through.
- Confirm the ABN lookup URL resolves correctly.
- The last update date looks correct.
- Kinde Australia Pty Ltd ([ABN 11 655 096 263](https://abr.business.gov.au/ABN/View?abn=11655096263)) - Email: support@kinde.com - Last update: 5 June 2025 + Kinde Australia Pty Ltd ([ABN 11 655 096 263](https://abr.business.gov.au/ABN/View?abn=11655096263)) + Email: [support@kinde.com](mailto:support@kinde.com) + Last update: 5 June 2025Also applies to: 113-113, 115-115
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx
Outdated
Show resolved
Hide resolved
clairekinde11
left a comment
clairekinde11
left a comment
There was a problem hiding this comment.
A couple of copy edits to be US English
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (4)
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx (4)
8-8: Standardize heading formatting
The pattern1. ## **Our Disclosures**(and similar numbered list items preceding##) mixes list syntax with header markup. For clearer markdown, either remove the leading list numbers and use## Our Disclosures(etc.), or embed the number inside the heading like## 1. Our Disclosures.Also applies to: 16-16, 22-22, 35-35, 43-43, 51-51, 58-58, 67-67, 78-78, 84-84, 89-89, 101-101
19-19: Fix comma separation in feature list
The introduction reads “authentication, authorisation user management…”. Add a comma afterauthorisationso it becomes:authentication, authorisation, user management
53-54: Use “with” instead of “of” for non-compliance
Change “non-compliance of PCI DSS requirements” to “non-compliance with PCI DSS requirements”:- should we become aware of any actual or potential non-compliance of PCI DSS requirements + should we become aware of any actual or potential non-compliance with PCI DSS requirements🧰 Tools
🪛 LanguageTool
[style] ~53-~53: Consider using an alternative to avoid wordiness and strengthen your wording.
Context: ...urity Standards (as amended and updated from time to time) (PCI DSS) when we store, process, tran...(FROM_TIME_TO_TIME)
[style] ~54-~54: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e are compliant with the PCI DSS. 2. We will notify you should we become aware ...(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
111-115: Hyperlink support email for UX
Consider converting the plain email address into amailto:link:- Email: support@kinde.com + Email: [support@kinde.com](mailto:support@kinde.com)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx(4 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx
[uncategorized] ~13-~13: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...al Loss, any loss that is a result of a Third Party Service, or any loss or corruption of d...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[grammar] ~20-~20: The progressive verb “agree” is used incorrectly. Consider changing it to the simple tense.
Context: ...on or entity using the Platform. If you are agreeing to these Terms not as an individual but...
(PROGRESSIVE_VERB_AGREE)
[grammar] ~20-~20: The pronoun ‘you’ must be used with a non-third-person form of a verb.
Context: ...yee or governmental official), then you means your entity and you are binding your en...
(NON3PRS_VERB)
[uncategorized] ~20-~20: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...al official), then you means your entity and you are binding your entity to these Te...
(COMMA_COMPOUND_SENTENCE)
[typographical] ~37-~37: Consider adding a comma after this introductory phrase.
Context: ...atform available at all times. However, from time to time we may perform reasonable scheduled and...
(FROM_TIME_TO_TIME_COMMA)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...rm may be reliant on, or interface with third party systems that are not provided by us (fo...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ail clients, and internet providers) (Third Party Services). To the maximum extent perm...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...law, we shall have no Liability for any Third Party Services, or any unavailability of the ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...of the Platform due to a failure of the Third Party Services. 3. Without limiting clause...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~45-~45: Use a comma before ‘or’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ided by the entity you are involved with or you may also sign up on the Platform. ...
(COMMA_COMPOUND_SENTENCE)
[style] ~46-~46: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...may also sign up on the Platform. 2. You must provide basic information when reg...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[uncategorized] ~46-~46: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ding your contact name and email address and you may be asked to choose a password. ...
(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~48-~48: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...any other person. Your login is personal and you must not transfer or provide it to ...
(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~49-~49: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... your username and password confidential and you will be liable for all activity via...
(COMMA_COMPOUND_SENTENCE)
[style] ~53-~53: Consider using an alternative to avoid wordiness and strengthen your wording.
Context: ...urity Standards (as amended and updated from time to time) (PCI DSS) when we store, process, tran...
(FROM_TIME_TO_TIME)
[style] ~54-~54: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e are compliant with the PCI DSS. 2. We will notify you should we become aware ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~71-~71: The progressive verb “agree” is used incorrectly. Consider changing it to the simple tense.
Context: ...etes with our business; 2. if you are agreeing to these Terms not as an individual but...
(PROGRESSIVE_VERB_AGREE)
[style] ~74-~74: Consider shortening this phrase to just “whether”, or rephrase the sentence to avoid “as to”.
Context: ... in relation to the Platform (including as to whether the Platform is or will be fit or suita...
(WHETHER)
🔇 Additional comments (2)
src/content/docs/trust-center/agreements/end-user-licence-agreement.mdx (2)
39-41: New billing account clause looks good
The added sub-clause correctly references clause 4.2 and clarifies user responsibility for payment-processor accounts.
61-61: New IP clause is well-formed
The Intellectual Property clause and its wording align with the rest of the document. No changes needed here.
2 participants
Description (required)
Update EULA June 2025
Summary by CodeRabbit