chore: add privacy policy and terms and conditions as new pages#172
Open
gonferreyra wants to merge 5 commits intodevelopfrom
Open
chore: add privacy policy and terms and conditions as new pages#172gonferreyra wants to merge 5 commits intodevelopfrom
gonferreyra wants to merge 5 commits intodevelopfrom
Conversation
WalkthroughSe agregaron nuevas páginas legales en español (política de privacidad y términos y condiciones) en dos ubicaciones; se añadieron páginas equivalentes en inglés bajo Changes
Sequence Diagram(s)(Sin diagramas — los cambios no introducen un nuevo flujo multi-componente que requiera visualización secuencial.) Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/pages/legal/privacy-policy.md`:
- Line 9: Update the main site link in privacy-policy.md: replace the markdown
link [www.sleakops.com](http://www.sleakops.com/) with an HTTPS URL so it reads
[www.sleakops.com](https://www.sleakops.com/); this change is in the Welcome
paragraph at the top of the file and ensures the privacy policy references a
secure URL without redirecting.
In `@src/pages/legal/terms-and-conditions.md`:
- Line 211: Replace the incorrect phrase in the terms contact line that
currently reads "If you have any questions about this Terms, please contact us:
[contact@sleakops.com](mailto:contact@sleakops.com)" with the grammatically
correct "If you have any questions about these Terms, please contact us:
[contact@sleakops.com](mailto:contact@sleakops.com)" so the document uses "these
Terms" consistently.
🪄 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: 91ef201b-4c0b-444f-b301-97644b7fa4c4
📒 Files selected for processing (6)
content/pages/es/legal/privacy-policy.mdcontent/pages/es/legal/terms-and-conditions.mddocusaurus.config.jssrc/pages/legal/privacy-policy.mdsrc/pages/legal/terms-and-conditions.mdsync_content.js
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (1)
content/pages/es/legal/privacy-policy.md (1)
151-151: Mejora editorial opcional: evitad “y/o” para una lectura más natural.No rompe nada, pero suena más limpio legalmente con una formulación directa (“productos o servicios de pago”, o separar casos si aplica).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/pages/es/legal/privacy-policy.md` at line 151, Replace the phrase "productos y/o servicios de pago" in the sentence that begins "Podemos proporcionar productos y/o servicios de pago dentro del Servicio." with a cleaner formulation such as "productos o servicios de pago" (or split into two sentences if you need to distinguish cases); update the markdown line containing that exact wording to remove "y/o" and use the chosen clearer phrasing.
🤖 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/pages/es/legal/privacy-policy.md`:
- Line 7: Replace the hardcoded date in the bold "Última actualización" line
("**Última actualización:** 15 de mayo de 2024") with the correct, current
approved revision date (e.g., "**Última actualización:** 22 de abril de 2026");
update the string exactly where that text appears in
content/pages/es/legal/privacy-policy.md so the published header matches the
latest legal-approved change.
In `@src/pages/legal/privacy-policy.md`:
- Line 171: Replace the ambiguous sentence "Our Service addresses only for those
who are at least 18 years of age. If you are under 18, do not use the Service."
with a clear, standard phrasing such as "The Service is intended only for
individuals who are at least 18 years old. If you are under 18, do not use the
Service." Locate the sentence in the privacy-policy.md content and update that
line to the proposed wording to remove the grammatical error and legal
ambiguity.
- Line 7: Update the "Last Updated" date in privacy-policy.md to the current
effective date confirmed by Legal/Compliance (replace the existing "May 15th,
2024"), and fix the grammatical error in the age restriction sentence (currently
containing "addresses only for") by replacing it with a clear legal phrasing
such as "is intended only for those who are at least 18 years of age" (locate
the sentence around the existing age-restriction paragraph and update
accordingly).
In `@src/pages/legal/terms-and-conditions.md`:
- Line 87: The anchor text "Terms and Conditions of SleakOps" linking to
"https://aws.amazon.com/legal/?nc1=f_cc" is misleading; update the markdown in
src/pages/legal/terms-and-conditions.md to change the link text to something
clear like "AWS Terms and Conditions" (or "AWS Terms and Conditions
(incorporated by reference)") so the anchor and URL match, and ensure
surrounding sentence reflects that AWS's terms are incorporated by reference.
- Around line 55-84: The document mixes direct card payments in the "Purchases"
section with AWS Marketplace billing in "Subscription Enrollment via AWS
Marketplace"/"Payment and Billing Information"/"AWS Account Billing", causing
legal ambiguity; remove or refactor the direct card/payment flow in the
"Purchases" section and explicitly state that all subscription and service
charges are processed exclusively via AWS Marketplace (update the "Purchases",
"Subscriptions", and "Payment and Billing Information" sections and remove
conflicting bullet points about supplying credit card details), ensuring
consistent language that SleakOps does not process payments directly and all
invoices appear on the customer's AWS account.
---
Nitpick comments:
In `@content/pages/es/legal/privacy-policy.md`:
- Line 151: Replace the phrase "productos y/o servicios de pago" in the sentence
that begins "Podemos proporcionar productos y/o servicios de pago dentro del
Servicio." with a cleaner formulation such as "productos o servicios de pago"
(or split into two sentences if you need to distinguish cases); update the
markdown line containing that exact wording to remove "y/o" and use the chosen
clearer phrasing.
🪄 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: 77d496eb-7ec9-4420-aa38-da4b1505d299
📒 Files selected for processing (3)
content/pages/es/legal/privacy-policy.mdsrc/pages/legal/privacy-policy.mdsrc/pages/legal/terms-and-conditions.md
|
|
||
| # Privacy Policy of SleakOps | ||
|
|
||
| **Last Updated:** May 15th, 2024 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n src/pages/legal/privacy-policy.md | head -20Repository: sleakops/docs
Length of output: 996
🏁 Script executed:
cat -n src/pages/legal/privacy-policy.md | sed -n '165,175p'Repository: sleakops/docs
Length of output: 750
Actualiza la fecha y corrige la gramática en restricción de edad.
La fecha "May 15th, 2024" está desactualizada (~1 año y 11 meses). Antes de mergear, confirmad con Legal/compliance la fecha efectiva actual y actualizadla. También, en línea 171, "addresses only for" tiene un error gramatical. Cambiad a "is intended only for those who are at least 18 years of age" o similar para que sea legalmente clara.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/legal/privacy-policy.md` at line 7, Update the "Last Updated" date
in privacy-policy.md to the current effective date confirmed by Legal/Compliance
(replace the existing "May 15th, 2024"), and fix the grammatical error in the
age restriction sentence (currently containing "addresses only for") by
replacing it with a clear legal phrasing such as "is intended only for those who
are at least 18 years of age" (locate the sentence around the existing
age-restriction paragraph and update accordingly).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
Novedades
Nuevas funcionalidades
Chores