@intlayer/docs 5.5.11 → 5.5.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/blog/ar/intlayer_with_next-intl.md +0 -1
- package/blog/ar/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/ar/what_is_internationalization.md +2 -2
- package/blog/de/intlayer_with_next-intl.md +0 -1
- package/blog/de/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/de/what_is_internationalization.md +2 -2
- package/blog/en/intlayer_with_next-intl.md +0 -1
- package/blog/en/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/en/what_is_internationalization.md +2 -2
- package/blog/en-GB/intlayer_with_next-intl.md +0 -1
- package/blog/en-GB/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/en-GB/what_is_internationalization.md +2 -2
- package/blog/es/intlayer_with_next-intl.md +0 -1
- package/blog/es/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/es/what_is_internationalization.md +2 -2
- package/blog/fr/intlayer_with_next-intl.md +0 -1
- package/blog/fr/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/fr/what_is_internationalization.md +2 -2
- package/blog/hi/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/hi/what_is_internationalization.md +2 -2
- package/blog/it/intlayer_with_next-intl.md +0 -1
- package/blog/it/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/it/what_is_internationalization.md +2 -2
- package/blog/ja/intlayer_with_next-intl.md +0 -1
- package/blog/ja/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/ja/what_is_internationalization.md +2 -2
- package/blog/ko/intlayer_with_next-intl.md +0 -1
- package/blog/ko/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/pt/intlayer_with_next-intl.md +0 -1
- package/blog/pt/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/pt/what_is_internationalization.md +2 -2
- package/blog/ru/intlayer_with_next-intl.md +0 -1
- package/blog/ru/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/ru/what_is_internationalization.md +2 -2
- package/blog/zh/intlayer_with_next-intl.md +0 -1
- package/blog/zh/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/zh/what_is_internationalization.md +2 -2
- package/dist/cjs/blog.cjs +2 -2
- package/dist/cjs/blog.cjs.map +1 -1
- package/dist/cjs/common.cjs +17 -6
- package/dist/cjs/common.cjs.map +1 -1
- package/dist/cjs/doc.cjs +2 -2
- package/dist/cjs/doc.cjs.map +1 -1
- package/dist/cjs/frequentQuestions.cjs +2 -2
- package/dist/cjs/frequentQuestions.cjs.map +1 -1
- package/dist/cjs/generated/blog.entry.cjs +1152 -252
- package/dist/cjs/generated/blog.entry.cjs.map +1 -1
- package/dist/cjs/generated/docs.entry.cjs +3778 -1124
- package/dist/cjs/generated/docs.entry.cjs.map +1 -1
- package/dist/cjs/generated/frequentQuestions.entry.cjs +794 -161
- package/dist/cjs/generated/frequentQuestions.entry.cjs.map +1 -1
- package/dist/cjs/generated/legal.entry.cjs +32 -31
- package/dist/cjs/generated/legal.entry.cjs.map +1 -1
- package/dist/cjs/legal.cjs +2 -2
- package/dist/cjs/legal.cjs.map +1 -1
- package/dist/esm/blog.mjs +2 -2
- package/dist/esm/blog.mjs.map +1 -1
- package/dist/esm/common.mjs +17 -6
- package/dist/esm/common.mjs.map +1 -1
- package/dist/esm/doc.mjs +2 -2
- package/dist/esm/doc.mjs.map +1 -1
- package/dist/esm/frequentQuestions.mjs +2 -2
- package/dist/esm/frequentQuestions.mjs.map +1 -1
- package/dist/esm/generated/blog.entry.mjs +1151 -252
- package/dist/esm/generated/blog.entry.mjs.map +1 -1
- package/dist/esm/generated/docs.entry.mjs +3777 -1124
- package/dist/esm/generated/docs.entry.mjs.map +1 -1
- package/dist/esm/generated/frequentQuestions.entry.mjs +793 -161
- package/dist/esm/generated/frequentQuestions.entry.mjs.map +1 -1
- package/dist/esm/generated/legal.entry.mjs +31 -31
- package/dist/esm/generated/legal.entry.mjs.map +1 -1
- package/dist/esm/legal.mjs +2 -2
- package/dist/esm/legal.mjs.map +1 -1
- package/dist/types/blog.d.ts +2 -2
- package/dist/types/blog.d.ts.map +1 -1
- package/dist/types/common.d.ts +3 -2
- package/dist/types/common.d.ts.map +1 -1
- package/dist/types/doc.d.ts +2 -2
- package/dist/types/doc.d.ts.map +1 -1
- package/dist/types/frequentQuestions.d.ts +2 -2
- package/dist/types/frequentQuestions.d.ts.map +1 -1
- package/dist/types/generated/blog.entry.d.ts.map +1 -1
- package/dist/types/generated/docs.entry.d.ts.map +1 -1
- package/dist/types/generated/frequentQuestions.entry.d.ts +1 -0
- package/dist/types/generated/frequentQuestions.entry.d.ts.map +1 -1
- package/dist/types/generated/legal.entry.d.ts.map +1 -1
- package/dist/types/legal.d.ts +2 -2
- package/dist/types/legal.d.ts.map +1 -1
- package/docs/ar/intlayer_with_vite+react.md +100 -108
- package/docs/de/intlayer_with_vite+react.md +121 -142
- package/docs/en/CI_CD.md +3 -1
- package/docs/en/autoFill.md +3 -1
- package/docs/en/configuration.md +4 -1
- package/docs/en/dictionary/condition.md +3 -1
- package/docs/en/dictionary/content_extention_customization.md +3 -1
- package/docs/en/dictionary/enumeration.md +3 -1
- package/docs/en/dictionary/file.md +3 -1
- package/docs/en/dictionary/function_fetching.md +3 -1
- package/docs/en/dictionary/get_started.md +3 -1
- package/docs/en/dictionary/insertion.md +3 -1
- package/docs/en/dictionary/markdown.md +3 -1
- package/docs/en/dictionary/nesting.md +3 -1
- package/docs/en/dictionary/translation.md +3 -1
- package/docs/en/how_works_intlayer.md +3 -1
- package/docs/en/index.md +3 -1
- package/docs/en/interest_of_intlayer.md +3 -1
- package/docs/en/intlayer_CMS.md +3 -1
- package/docs/en/intlayer_cli.md +3 -1
- package/docs/en/intlayer_visual_editor.md +3 -1
- package/docs/en/intlayer_with_angular.md +3 -1
- package/docs/en/intlayer_with_create_react_app.md +3 -1
- package/docs/en/intlayer_with_express.md +3 -1
- package/docs/en/intlayer_with_lynx+react.md +3 -1
- package/docs/en/intlayer_with_nextjs_14.md +6 -1
- package/docs/en/intlayer_with_nextjs_15.md +5 -1
- package/docs/en/intlayer_with_nextjs_page_router.md +5 -1
- package/docs/en/intlayer_with_nuxt.md +3 -1
- package/docs/en/intlayer_with_react_native+expo.md +3 -1
- package/docs/en/intlayer_with_vite+preact.md +3 -1
- package/docs/en/intlayer_with_vite+react.md +9 -7
- package/docs/en/intlayer_with_vite+solid.md +3 -1
- package/docs/en/intlayer_with_vite+svelte.md +3 -1
- package/docs/en/intlayer_with_vite+vue.md +3 -1
- package/docs/en/introduction.md +3 -1
- package/docs/en/mcp_server.md +42 -1
- package/docs/en/packages/@intlayer/api/index.md +3 -1
- package/docs/en/packages/@intlayer/chokidar/index.md +3 -1
- package/docs/en/packages/@intlayer/cli/index.md +3 -1
- package/docs/en/packages/@intlayer/config/index.md +3 -1
- package/docs/en/packages/@intlayer/core/index.md +3 -1
- package/docs/en/packages/@intlayer/design-system/index.md +3 -1
- package/docs/en/packages/@intlayer/dictionary-entry/index.md +3 -1
- package/docs/en/packages/@intlayer/editor/index.md +3 -1
- package/docs/en/packages/@intlayer/editor-react/index.md +3 -1
- package/docs/en/packages/@intlayer/webpack/index.md +3 -1
- package/docs/en/packages/angular-intlayer/index.md +3 -1
- package/docs/en/packages/express-intlayer/index.md +3 -1
- package/docs/en/packages/express-intlayer/t.md +3 -1
- package/docs/en/packages/intlayer/getConfiguration.md +3 -1
- package/docs/en/packages/intlayer/getEnumeration.md +3 -1
- package/docs/en/packages/intlayer/getHTMLTextDir.md +3 -1
- package/docs/en/packages/intlayer/getLocaleLang.md +3 -1
- package/docs/en/packages/intlayer/getLocaleName.md +3 -1
- package/docs/en/packages/intlayer/getLocalizedUrl.md +3 -1
- package/docs/en/packages/intlayer/getMultilingualUrls.md +3 -1
- package/docs/en/packages/intlayer/getPathWithoutLocale.md +3 -1
- package/docs/en/packages/intlayer/getTranslation.md +3 -1
- package/docs/en/packages/intlayer/getTranslationContent.md +3 -1
- package/docs/en/packages/intlayer/index.md +3 -1
- package/docs/en/packages/intlayer-cli/index.md +3 -1
- package/docs/en/packages/intlayer-editor/index.md +3 -1
- package/docs/en/packages/lynx-intlayer/index.md +3 -1
- package/docs/en/packages/next-intlayer/index.md +3 -1
- package/docs/en/packages/next-intlayer/t.md +3 -1
- package/docs/en/packages/next-intlayer/useDictionary.md +3 -1
- package/docs/en/packages/next-intlayer/useIntlayer.md +3 -1
- package/docs/en/packages/next-intlayer/useIntlayerAsync.md +3 -1
- package/docs/en/packages/next-intlayer/useLocale.md +3 -1
- package/docs/en/packages/nuxt-intlayer/index.md +3 -1
- package/docs/en/packages/preact-intlayer/index.md +3 -1
- package/docs/en/packages/react-intlayer/index.md +3 -1
- package/docs/en/packages/react-intlayer/t.md +3 -1
- package/docs/en/packages/react-intlayer/useDictionary.md +3 -1
- package/docs/en/packages/react-intlayer/useIntlayer.md +3 -1
- package/docs/en/packages/react-intlayer/useIntlayerAsync.md +3 -1
- package/docs/en/packages/react-intlayer/useLocale.md +3 -1
- package/docs/en/packages/react-native-intlayer/index.md +3 -1
- package/docs/en/packages/react-scripts-intlayer/index.md +3 -1
- package/docs/en/packages/solid-intlayer/index.md +3 -1
- package/docs/en/packages/svelte-intlayer/index.md +3 -1
- package/docs/en/packages/vite-intlayer/index.md +3 -1
- package/docs/en/packages/vue-intlayer/index.md +3 -1
- package/docs/en/per_locale_file.md +3 -1
- package/docs/en/roadmap.md +5 -2
- package/docs/en/vs_code_extension.md +3 -1
- package/docs/en-GB/intlayer_with_vite+react.md +64 -83
- package/docs/es/intlayer_with_vite+react.md +91 -94
- package/docs/fr/intlayer_with_vite+react.md +73 -65
- package/docs/hi/intlayer_with_vite+react.md +107 -107
- package/docs/it/intlayer_with_vite+react.md +156 -112
- package/docs/ja/intlayer_with_vite+react.md +153 -218
- package/docs/ko/intlayer_with_vite+react.md +116 -148
- package/docs/ko/packages/intlayer/getLocalizedUrl.md +1 -23
- package/docs/pt/intlayer_with_vite+react.md +110 -132
- package/docs/ru/intlayer_with_vite+react.md +98 -83
- package/docs/zh/intlayer_with_vite+react.md +147 -184
- package/docs/zh/packages/intlayer/getLocalizedUrl.md +1 -23
- package/frequent_questions/ar/build_error_CI_CD.md +75 -0
- package/frequent_questions/de/build_error_CI_CD.md +75 -0
- package/frequent_questions/en/build_error_CI_CD.md +75 -0
- package/frequent_questions/en-GB/build_error_CI_CD.md +75 -0
- package/frequent_questions/es/build_error_CI_CD.md +75 -0
- package/frequent_questions/fr/build_error_CI_CD.md +75 -0
- package/frequent_questions/hi/build_error_CI_CD.md +75 -0
- package/frequent_questions/it/build_error_CI_CD.md +75 -0
- package/frequent_questions/ja/build_error_CI_CD.md +75 -0
- package/frequent_questions/ja/intlayer_command_undefined.md +3 -3
- package/frequent_questions/ko/build_error_CI_CD.md +75 -0
- package/frequent_questions/ko/intlayer_command_undefined.md +3 -3
- package/frequent_questions/pt/build_error_CI_CD.md +75 -0
- package/frequent_questions/ru/build_error_CI_CD.md +75 -0
- package/frequent_questions/zh/build_error_CI_CD.md +75 -0
- package/frequent_questions/zh/intlayer_command_undefined.md +3 -3
- package/legal/ar/privacy_notice.md +83 -0
- package/legal/ar/terms_of_service.md +55 -0
- package/legal/de/privacy_notice.md +83 -0
- package/legal/de/terms_of_service.md +55 -0
- package/legal/en/privacy_notice.md +83 -0
- package/legal/en/terms_of_service.md +55 -0
- package/legal/en-GB/privacy_notice.md +83 -0
- package/legal/en-GB/terms_of_service.md +55 -0
- package/legal/es/privacy_notice.md +83 -0
- package/legal/es/terms_of_service.md +55 -0
- package/legal/fr/privacy_notice.md +83 -0
- package/legal/fr/terms_of_service.md +55 -0
- package/legal/hi/privacy_notice.md +83 -0
- package/legal/hi/terms_of_service.md +55 -0
- package/legal/it/privacy_notice.md +83 -0
- package/legal/it/terms_of_service.md +55 -0
- package/legal/ja/privacy_notice.md +83 -0
- package/legal/ja/terms_of_service.md +55 -0
- package/legal/ko/privacy_notice.md +83 -0
- package/legal/ko/terms_of_service.md +55 -0
- package/legal/pt/privacy_notice.md +83 -0
- package/legal/pt/terms_of_service.md +55 -0
- package/legal/ru/privacy_notice.md +83 -0
- package/legal/ru/terms_of_service.md +55 -0
- package/legal/zh/privacy_notice.md +83 -0
- package/legal/zh/terms_of_service.md +55 -0
- package/package.json +7 -6
- package/src/blog.ts +6 -4
- package/src/common.ts +23 -7
- package/src/doc.ts +6 -4
- package/src/frequentQuestions.ts +6 -4
- package/src/generated/blog.entry.ts +1177 -280
- package/src/generated/docs.entry.ts +3868 -1217
- package/src/generated/frequentQuestions.entry.ts +808 -178
- package/src/generated/legal.entry.ts +34 -36
- package/src/legal.ts +6 -4
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Nutzungsbedingungen
|
|
5
|
+
description: Entdecken Sie, wie Intlayer Informationen verarbeitet, die über unsere Website und das CMS gesammelt werden. Folgen Sie der Dokumentation, um die verschiedenen Formate und Anwendungsfälle zu verstehen.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisierung
|
|
8
|
+
- Dokumentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Nutzungsbedingungen
|
|
11
|
+
- Dienstleistung
|
|
12
|
+
- Nutzung
|
|
13
|
+
- Lizenz
|
|
14
|
+
- Haftung
|
|
15
|
+
- Datenschutz
|
|
16
|
+
- Beiträge
|
|
17
|
+
- Urhebernennung
|
|
18
|
+
- Änderung der Bedingungen
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Nutzungsbedingungen
|
|
24
|
+
|
|
25
|
+
## 1. Annahme der Bedingungen
|
|
26
|
+
|
|
27
|
+
Durch die Nutzung von Intlayer erklären Sie sich mit diesen Nutzungsbedingungen einverstanden. Wenn Sie diesen Bedingungen nicht zustimmen, verwenden Sie das Tool bitte nicht.
|
|
28
|
+
|
|
29
|
+
## 2. Lizenz
|
|
30
|
+
|
|
31
|
+
Intlayer wird unter der **Apache 2.0 Lizenz** vertrieben, die die Nutzung, Modifikation und Verbreitung des Codes sowohl für Open-Source- als auch für kommerzielle Projekte erlaubt. Benutzer dürfen den Quellcode ändern und Beiträge über Pull Requests gemäß den Richtlinien in unserem [Beitragsleitfaden](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md) einreichen. Code-Diebstahl für kommerzielle Zwecke ist streng verboten.
|
|
32
|
+
|
|
33
|
+
## 3. Kommerzielle Nutzung
|
|
34
|
+
|
|
35
|
+
Sie dürfen Intlayer für kommerzielle Projekte verwenden. Die Wiederverwendung des Codes zur Erstellung direkter Konkurrenztools auf Basis von Intlayer ohne wesentliche Transformation oder erheblichen Mehrwert ist jedoch untersagt.
|
|
36
|
+
|
|
37
|
+
## 4. Haftung
|
|
38
|
+
|
|
39
|
+
Die Verantwortlichen von Intlayer bemühen sich, Fehler und Sicherheitsprobleme so schnell wie möglich zu beheben. Sie übernehmen jedoch keine Haftung für Schäden, die durch solche Probleme an der Infrastruktur der Nutzer entstehen. Wir empfehlen den Nutzern, Probleme über unser [Issue-Tracking-System](https://github.com/aymericzip/intlayer/issues) zu melden.
|
|
40
|
+
|
|
41
|
+
## 5. Datenschutz
|
|
42
|
+
|
|
43
|
+
Intlayer sammelt oder speichert keine personenbezogenen Daten der Nutzer.
|
|
44
|
+
|
|
45
|
+
## 6. Beiträge
|
|
46
|
+
|
|
47
|
+
Nutzer werden ermutigt, zu Intlayer beizutragen, indem sie den Richtlinien in unserem Beitragshandbuch folgen. Jeder eingereichte Code muss den festgelegten Qualitätsstandards entsprechen und wird vor der Integration von den Verantwortlichen überprüft.
|
|
48
|
+
|
|
49
|
+
## 7. Urhebernennung
|
|
50
|
+
|
|
51
|
+
Jedes Tool, das entwickelt wird, um den Intlayer-Code zu erweitern oder zu nutzen, muss Intlayer als Grundlage des Codes klar anerkennen. Diese Urhebernennung muss sowohl im Quellcode als auch in jeglicher Benutzer- oder Werbedokumentation sichtbar sein.
|
|
52
|
+
|
|
53
|
+
## 8. Änderung der Bedingungen
|
|
54
|
+
|
|
55
|
+
Diese Nutzungsbedingungen können jederzeit geändert werden. Die Nutzer werden über wesentliche Änderungen der Nutzungsbedingungen informiert und müssen den Änderungen zustimmen, um Intlayer weiterhin verwenden zu können.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Privacy Notice
|
|
5
|
+
description: Discover how Intlayer handles information collected through our website and CMS. Follow the documentation to understand the different formats and use cases.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalization
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Privacy
|
|
11
|
+
- Notice
|
|
12
|
+
- Cookies
|
|
13
|
+
- Tracking
|
|
14
|
+
- Analytics
|
|
15
|
+
- Google Analytics
|
|
16
|
+
- Meta (Facebook) Pixel
|
|
17
|
+
- Authentication
|
|
18
|
+
- User Data
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Privacy Notice
|
|
24
|
+
|
|
25
|
+
## Introduction
|
|
26
|
+
|
|
27
|
+
At Intlayer, we take privacy seriously. This notice explains how we handle information collected through our website and CMS.
|
|
28
|
+
|
|
29
|
+
## Contact
|
|
30
|
+
|
|
31
|
+
If you have any questions or concerns about privacy, please contact us at the following address: [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## Use of Cookies and Tracking Technologies
|
|
34
|
+
|
|
35
|
+
We use **Google Analytics** and the **Meta (Facebook) Pixel** to analyze the use of our website and improve our services. These tools generate statistics and other information about the website using cookies stored on users' devices.
|
|
36
|
+
|
|
37
|
+
For more information:
|
|
38
|
+
|
|
39
|
+
- [Google's privacy policy](https://policies.google.com/privacy)
|
|
40
|
+
- [Meta’s privacy policy](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## Authentication and User Data
|
|
43
|
+
|
|
44
|
+
Access to the Intlayer CMS requires user authentication. We offer both email/password authentication and third-party sign-in via **Google** and **GitHub**.
|
|
45
|
+
|
|
46
|
+
During the authentication process, we collect:
|
|
47
|
+
|
|
48
|
+
- Email address
|
|
49
|
+
- Display name (or chosen name)
|
|
50
|
+
|
|
51
|
+
Users may also access the CMS via access tokens linked to their account. These tokens are tied to the same authentication data.
|
|
52
|
+
|
|
53
|
+
## Data Storage and Security
|
|
54
|
+
|
|
55
|
+
User authentication data is stored in a **MongoDB database** hosted on **cloud.mongodb.com**:
|
|
56
|
+
|
|
57
|
+
- **Region:** AWS / Oregon (us-west-2)
|
|
58
|
+
- **Type:** Replica Set (3 nodes)
|
|
59
|
+
- **Password Security:** All passwords are hashed using industry-standard practices.
|
|
60
|
+
|
|
61
|
+
We do not store any unnecessary personal data beyond what is required for authentication and secure CMS access.
|
|
62
|
+
|
|
63
|
+
## Data Sharing with Third Parties
|
|
64
|
+
|
|
65
|
+
We do **not** sell or share your personal data with third parties, except as required for analytics (Google Analytics, Facebook Pixel) or as part of the authentication process (Google or GitHub sign-in).
|
|
66
|
+
|
|
67
|
+
## Users' Rights
|
|
68
|
+
|
|
69
|
+
As a user, you have the right to:
|
|
70
|
+
|
|
71
|
+
- Access the personal data we hold about you
|
|
72
|
+
- Request correction or deletion of your data
|
|
73
|
+
- Revoke access or delete your account
|
|
74
|
+
|
|
75
|
+
For any request regarding your data, contact us at [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## Changes to This Notice
|
|
78
|
+
|
|
79
|
+
We may update this privacy notice from time to time. Users are advised to regularly check this page to stay informed of any changes.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
Let me know if you'd like a more formal tone, add GDPR/CCPA mentions, or adapt it for a legal page on your site.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Terms of Service
|
|
5
|
+
description: Discover how Intlayer handles information collected through our website and CMS. Follow the documentation to understand the different formats and use cases.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalization
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Terms of Service
|
|
11
|
+
- Service
|
|
12
|
+
- Use
|
|
13
|
+
- License
|
|
14
|
+
- Liability
|
|
15
|
+
- Privacy
|
|
16
|
+
- Contributions
|
|
17
|
+
- Attribution
|
|
18
|
+
- Modification of Terms
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Terms of Use
|
|
24
|
+
|
|
25
|
+
## 1. Acceptance of Terms
|
|
26
|
+
|
|
27
|
+
By using Intlayer, you agree to be bound by these terms of use. If you do not accept these terms, please do not use the tool.
|
|
28
|
+
|
|
29
|
+
## 2. License
|
|
30
|
+
|
|
31
|
+
Intlayer is distributed under the **Apache 2.0 license** which allows the use, modification, and distribution of the code for both open-source and commercial projects. Users are allowed to modify the source code and submit contributions via pull requests in accordance with the guidelines established in our [contribution guide](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md). Code theft for commercial use is strictly prohibited.
|
|
32
|
+
|
|
33
|
+
## 3. Commercial Use
|
|
34
|
+
|
|
35
|
+
You are permitted to use Intlayer for commercial projects. However, reusing the code to create direct competitor tools based on Intlayer without significant transformation or substantial value addition is prohibited.
|
|
36
|
+
|
|
37
|
+
## 4. Liability
|
|
38
|
+
|
|
39
|
+
The maintainers of Intlayer strive to correct bugs and security issues as soon as they are discovered. However, they disclaim any responsibility for damages resulting from such issues on user infrastructures. We encourage users to report issues via our [issue tracking system](https://github.com/aymericzip/intlayer/issues).
|
|
40
|
+
|
|
41
|
+
## 5. Privacy
|
|
42
|
+
|
|
43
|
+
Intlayer does not collect or store any personal data of users.
|
|
44
|
+
|
|
45
|
+
## 6. Contributions
|
|
46
|
+
|
|
47
|
+
Users are encouraged to contribute to Intlayer by following the guidelines provided in our contribution guide. Any submitted code must adhere to the established quality standards and will be reviewed by the maintainers before integration.
|
|
48
|
+
|
|
49
|
+
## 7. Attribution
|
|
50
|
+
|
|
51
|
+
Any tool developed to extend or utilize Intlayer's code must clearly credit Intlayer as the basis of the code. This attribution must be visible in the source code as well as in any user or promotional documentation.
|
|
52
|
+
|
|
53
|
+
## 8. Modification of Terms
|
|
54
|
+
|
|
55
|
+
These terms of use may be modified at any time. Users will be informed of any significant changes in the terms of use and must accept the changes to continue using Intlayer.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Privacy Notice
|
|
5
|
+
description: Discover how Intlayer handles information collected through our website and CMS. Follow the documentation to understand the different formats and use cases.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisation
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Privacy
|
|
11
|
+
- Notice
|
|
12
|
+
- Cookies
|
|
13
|
+
- Tracking
|
|
14
|
+
- Analytics
|
|
15
|
+
- Google Analytics
|
|
16
|
+
- Meta (Facebook) Pixel
|
|
17
|
+
- Authentication
|
|
18
|
+
- User Data
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Privacy Notice
|
|
24
|
+
|
|
25
|
+
## Introduction
|
|
26
|
+
|
|
27
|
+
At Intlayer, we take privacy seriously. This notice explains how we handle information collected through our website and CMS.
|
|
28
|
+
|
|
29
|
+
## Contact
|
|
30
|
+
|
|
31
|
+
If you have any questions or concerns about privacy, please contact us at the following address: [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## Use of Cookies and Tracking Technologies
|
|
34
|
+
|
|
35
|
+
We use **Google Analytics** and the **Meta (Facebook) Pixel** to analyse the use of our website and improve our services. These tools generate statistics and other information about the website using cookies stored on users' devices.
|
|
36
|
+
|
|
37
|
+
For more information:
|
|
38
|
+
|
|
39
|
+
- [Google's privacy policy](https://policies.google.com/privacy)
|
|
40
|
+
- [Meta’s privacy policy](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## Authentication and User Data
|
|
43
|
+
|
|
44
|
+
Access to the Intlayer CMS requires user authentication. We offer both email/password authentication and third-party sign-in via **Google** and **GitHub**.
|
|
45
|
+
|
|
46
|
+
During the authentication process, we collect:
|
|
47
|
+
|
|
48
|
+
- Email address
|
|
49
|
+
- Display name (or chosen name)
|
|
50
|
+
|
|
51
|
+
Users may also access the CMS via access tokens linked to their account. These tokens are tied to the same authentication data.
|
|
52
|
+
|
|
53
|
+
## Data Storage and Security
|
|
54
|
+
|
|
55
|
+
User authentication data is stored in a **MongoDB database** hosted on **cloud.mongodb.com**:
|
|
56
|
+
|
|
57
|
+
- **Region:** AWS / Oregon (us-west-2)
|
|
58
|
+
- **Type:** Replica Set (3 nodes)
|
|
59
|
+
- **Password Security:** All passwords are hashed using industry-standard practices.
|
|
60
|
+
|
|
61
|
+
We do not store any unnecessary personal data beyond what is required for authentication and secure CMS access.
|
|
62
|
+
|
|
63
|
+
## Data Sharing with Third Parties
|
|
64
|
+
|
|
65
|
+
We do **not** sell or share your personal data with third parties, except as required for analytics (Google Analytics, Facebook Pixel) or as part of the authentication process (Google or GitHub sign-in).
|
|
66
|
+
|
|
67
|
+
## Users' Rights
|
|
68
|
+
|
|
69
|
+
As a user, you have the right to:
|
|
70
|
+
|
|
71
|
+
- Access the personal data we hold about you
|
|
72
|
+
- Request correction or deletion of your data
|
|
73
|
+
- Revoke access or delete your account
|
|
74
|
+
|
|
75
|
+
For any request regarding your data, contact us at [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## Changes to This Notice
|
|
78
|
+
|
|
79
|
+
We may update this privacy notice from time to time. Users are advised to regularly check this page to stay informed of any changes.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
Let me know if you'd like a more formal tone, add GDPR/CCPA mentions, or adapt it for a legal page on your site.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Terms of Service
|
|
5
|
+
description: Discover how Intlayer handles information collected through our website and CMS. Follow the documentation to understand the different formats and use cases.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisation
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Terms of Service
|
|
11
|
+
- Service
|
|
12
|
+
- Use
|
|
13
|
+
- Licence
|
|
14
|
+
- Liability
|
|
15
|
+
- Privacy
|
|
16
|
+
- Contributions
|
|
17
|
+
- Attribution
|
|
18
|
+
- Modification of Terms
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Terms of Use
|
|
24
|
+
|
|
25
|
+
## 1. Acceptance of Terms
|
|
26
|
+
|
|
27
|
+
By using Intlayer, you agree to be bound by these terms of use. If you do not accept these terms, please do not use the tool.
|
|
28
|
+
|
|
29
|
+
## 2. Licence
|
|
30
|
+
|
|
31
|
+
Intlayer is distributed under the **Apache 2.0 licence** which allows the use, modification, and distribution of the code for both open-source and commercial projects. Users are allowed to modify the source code and submit contributions via pull requests in accordance with the guidelines established in our [contribution guide](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md). Code theft for commercial use is strictly prohibited.
|
|
32
|
+
|
|
33
|
+
## 3. Commercial Use
|
|
34
|
+
|
|
35
|
+
You are permitted to use Intlayer for commercial projects. However, reusing the code to create direct competitor tools based on Intlayer without significant transformation or substantial value addition is prohibited.
|
|
36
|
+
|
|
37
|
+
## 4. Liability
|
|
38
|
+
|
|
39
|
+
The maintainers of Intlayer strive to correct bugs and security issues as soon as they are discovered. However, they disclaim any responsibility for damages resulting from such issues on user infrastructures. We encourage users to report issues via our [issue tracking system](https://github.com/aymericzip/intlayer/issues).
|
|
40
|
+
|
|
41
|
+
## 5. Privacy
|
|
42
|
+
|
|
43
|
+
Intlayer does not collect or store any personal data of users.
|
|
44
|
+
|
|
45
|
+
## 6. Contributions
|
|
46
|
+
|
|
47
|
+
Users are encouraged to contribute to Intlayer by following the guidelines provided in our contribution guide. Any submitted code must adhere to the established quality standards and will be reviewed by the maintainers before integration.
|
|
48
|
+
|
|
49
|
+
## 7. Attribution
|
|
50
|
+
|
|
51
|
+
Any tool developed to extend or utilise Intlayer's code must clearly credit Intlayer as the basis of the code. This attribution must be visible in the source code as well as in any user or promotional documentation.
|
|
52
|
+
|
|
53
|
+
## 8. Modification of Terms
|
|
54
|
+
|
|
55
|
+
These terms of use may be modified at any time. Users will be informed of any significant changes in the terms of use and must accept the changes to continue using Intlayer.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Aviso de Privacidad de Intlayer
|
|
5
|
+
description: Descubre cómo Intlayer maneja la información recopilada a través de nuestro sitio web y CMS. Sigue la documentación para entender los diferentes formatos y casos de uso.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internacionalización
|
|
8
|
+
- Documentación
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Privacidad
|
|
11
|
+
- Aviso
|
|
12
|
+
- Cookies
|
|
13
|
+
- Seguimiento
|
|
14
|
+
- Analítica
|
|
15
|
+
- Google Analytics
|
|
16
|
+
- Meta (Facebook) Pixel
|
|
17
|
+
- Autenticación
|
|
18
|
+
- Datos de Usuario
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Aviso de Privacidad de Intlayer
|
|
24
|
+
|
|
25
|
+
## Introducción
|
|
26
|
+
|
|
27
|
+
En Intlayer, tomamos la privacidad en serio. Este aviso explica cómo manejamos la información recopilada a través de nuestro sitio web y CMS.
|
|
28
|
+
|
|
29
|
+
## Contacto
|
|
30
|
+
|
|
31
|
+
Si tiene alguna pregunta o inquietud sobre la privacidad, por favor contáctenos en la siguiente dirección: [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## Uso de Cookies y Tecnologías de Seguimiento
|
|
34
|
+
|
|
35
|
+
Utilizamos **Google Analytics** y el **Meta (Facebook) Pixel** para analizar el uso de nuestro sitio web y mejorar nuestros servicios. Estas herramientas generan estadísticas y otra información sobre el sitio web utilizando cookies almacenadas en los dispositivos de los usuarios.
|
|
36
|
+
|
|
37
|
+
Para más información:
|
|
38
|
+
|
|
39
|
+
- [Política de privacidad de Google](https://policies.google.com/privacy)
|
|
40
|
+
- [Política de privacidad de Meta](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## Autenticación y Datos de Usuario
|
|
43
|
+
|
|
44
|
+
El acceso al CMS de Intlayer requiere autenticación de usuario. Ofrecemos tanto autenticación por correo electrónico/contraseña como inicio de sesión a través de terceros mediante **Google** y **GitHub**.
|
|
45
|
+
|
|
46
|
+
Durante el proceso de autenticación, recopilamos:
|
|
47
|
+
|
|
48
|
+
- Dirección de correo electrónico
|
|
49
|
+
- Nombre para mostrar (o nombre elegido)
|
|
50
|
+
|
|
51
|
+
Los usuarios también pueden acceder al CMS mediante tokens de acceso vinculados a su cuenta. Estos tokens están asociados con los mismos datos de autenticación.
|
|
52
|
+
|
|
53
|
+
## Almacenamiento y Seguridad de Datos
|
|
54
|
+
|
|
55
|
+
Los datos de autenticación de los usuarios se almacenan en una **base de datos MongoDB** alojada en **cloud.mongodb.com**:
|
|
56
|
+
|
|
57
|
+
- **Región:** AWS / Oregon (us-west-2)
|
|
58
|
+
- **Tipo:** Replica Set (3 nodos)
|
|
59
|
+
- **Seguridad de Contraseñas:** Todas las contraseñas están cifradas utilizando prácticas estándar de la industria.
|
|
60
|
+
|
|
61
|
+
No almacenamos datos personales innecesarios más allá de lo requerido para la autenticación y el acceso seguro al CMS.
|
|
62
|
+
|
|
63
|
+
## Compartición de Datos con Terceros
|
|
64
|
+
|
|
65
|
+
No vendemos ni compartimos sus datos personales con terceros, excepto cuando sea necesario para análisis (Google Analytics, Facebook Pixel) o como parte del proceso de autenticación (inicio de sesión con Google o GitHub).
|
|
66
|
+
|
|
67
|
+
## Derechos de los Usuarios
|
|
68
|
+
|
|
69
|
+
Como usuario, usted tiene el derecho a:
|
|
70
|
+
|
|
71
|
+
- Acceder a los datos personales que tenemos sobre usted
|
|
72
|
+
- Solicitar la corrección o eliminación de sus datos
|
|
73
|
+
- Revocar el acceso o eliminar su cuenta
|
|
74
|
+
|
|
75
|
+
Para cualquier solicitud relacionada con sus datos, contáctenos en [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## Cambios en este Aviso
|
|
78
|
+
|
|
79
|
+
Podemos actualizar este aviso de privacidad de vez en cuando. Se recomienda a los usuarios revisar esta página regularmente para mantenerse informados sobre cualquier cambio.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
Hágame saber si desea un tono más formal, agregar menciones de GDPR/CCPA o adaptarlo para una página legal en su sitio.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Términos de Servicio de Intlayer
|
|
5
|
+
description: Descubra cómo Intlayer maneja la información recopilada a través de nuestro sitio web y CMS. Siga la documentación para entender los diferentes formatos y casos de uso.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internacionalización
|
|
8
|
+
- Documentación
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Términos de Servicio
|
|
11
|
+
- Servicio
|
|
12
|
+
- Uso
|
|
13
|
+
- Licencia
|
|
14
|
+
- Responsabilidad
|
|
15
|
+
- Privacidad
|
|
16
|
+
- Contribuciones
|
|
17
|
+
- Atribución
|
|
18
|
+
- Modificación de Términos
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Términos de Uso de Intlayer
|
|
24
|
+
|
|
25
|
+
## 1. Aceptación de los Términos
|
|
26
|
+
|
|
27
|
+
Al usar Intlayer, usted acepta estar sujeto a estos términos de uso. Si no acepta estos términos, por favor no utilice la herramienta.
|
|
28
|
+
|
|
29
|
+
## 2. Licencia
|
|
30
|
+
|
|
31
|
+
Intlayer se distribuye bajo la **licencia Apache 2.0**, que permite el uso, modificación y distribución del código tanto para proyectos de código abierto como comerciales. Los usuarios pueden modificar el código fuente y enviar contribuciones mediante pull requests de acuerdo con las directrices establecidas en nuestra [guía de contribución](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md). El robo de código para uso comercial está estrictamente prohibido.
|
|
32
|
+
|
|
33
|
+
## 3. Uso Comercial
|
|
34
|
+
|
|
35
|
+
Se le permite usar Intlayer para proyectos comerciales. Sin embargo, está prohibido reutilizar el código para crear herramientas competidoras directas basadas en Intlayer sin una transformación significativa o una adición sustancial de valor.
|
|
36
|
+
|
|
37
|
+
## 4. Responsabilidad
|
|
38
|
+
|
|
39
|
+
Los mantenedores de Intlayer se esfuerzan por corregir errores y problemas de seguridad tan pronto como se descubren. Sin embargo, no se hacen responsables de los daños resultantes de dichos problemas en las infraestructuras de los usuarios. Animamos a los usuarios a reportar problemas a través de nuestro [sistema de seguimiento de incidencias](https://github.com/aymericzip/intlayer/issues).
|
|
40
|
+
|
|
41
|
+
## 5. Privacidad
|
|
42
|
+
|
|
43
|
+
Intlayer no recopila ni almacena ningún dato personal de los usuarios.
|
|
44
|
+
|
|
45
|
+
## 6. Contribuciones
|
|
46
|
+
|
|
47
|
+
Se anima a los usuarios a contribuir en Intlayer siguiendo las pautas proporcionadas en nuestra guía de contribución. Cualquier código enviado debe cumplir con los estándares de calidad establecidos y será revisado por los mantenedores antes de su integración.
|
|
48
|
+
|
|
49
|
+
## 7. Atribución
|
|
50
|
+
|
|
51
|
+
Cualquier herramienta desarrollada para extender o utilizar el código de Intlayer debe acreditar claramente a Intlayer como la base del código. Esta atribución debe ser visible tanto en el código fuente como en cualquier documentación de usuario o promocional.
|
|
52
|
+
|
|
53
|
+
## 8. Modificación de los Términos
|
|
54
|
+
|
|
55
|
+
Estos términos de uso pueden ser modificados en cualquier momento. Los usuarios serán informados de cualquier cambio significativo en los términos de uso y deberán aceptar los cambios para continuar utilizando Intlayer.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Avis de confidentialité Intlayer
|
|
5
|
+
description: Découvrez comment Intlayer gère les informations collectées via notre site web et CMS. Suivez la documentation pour comprendre les différents formats et cas d'utilisation.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisation
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Confidentialité
|
|
11
|
+
- Avis
|
|
12
|
+
- Cookies
|
|
13
|
+
- Suivi
|
|
14
|
+
- Analytique
|
|
15
|
+
- Google Analytics
|
|
16
|
+
- Meta (Facebook) Pixel
|
|
17
|
+
- Authentification
|
|
18
|
+
- Données Utilisateur
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Avis de confidentialité Intlayer
|
|
24
|
+
|
|
25
|
+
## Introduction
|
|
26
|
+
|
|
27
|
+
Chez Intlayer, nous prenons la confidentialité au sérieux. Cet avis explique comment nous traitons les informations collectées via notre site web et CMS.
|
|
28
|
+
|
|
29
|
+
## Contact
|
|
30
|
+
|
|
31
|
+
Si vous avez des questions ou des préoccupations concernant la confidentialité, veuillez nous contacter à l'adresse suivante : [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## Utilisation des cookies et des technologies de suivi
|
|
34
|
+
|
|
35
|
+
Nous utilisons **Google Analytics** et le **Meta (Facebook) Pixel** pour analyser l'utilisation de notre site web et améliorer nos services. Ces outils génèrent des statistiques et d'autres informations sur le site web en utilisant des cookies stockés sur les appareils des utilisateurs.
|
|
36
|
+
|
|
37
|
+
Pour plus d'informations :
|
|
38
|
+
|
|
39
|
+
- [Politique de confidentialité de Google](https://policies.google.com/privacy)
|
|
40
|
+
- [Politique de confidentialité de Meta](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## Authentification et données utilisateur
|
|
43
|
+
|
|
44
|
+
L'accès au CMS Intlayer nécessite une authentification utilisateur. Nous proposons à la fois une authentification par email/mot de passe et une connexion tierce via **Google** et **GitHub**.
|
|
45
|
+
|
|
46
|
+
Lors du processus d'authentification, nous collectons :
|
|
47
|
+
|
|
48
|
+
- Adresse e-mail
|
|
49
|
+
- Nom d'affichage (ou nom choisi)
|
|
50
|
+
|
|
51
|
+
Les utilisateurs peuvent également accéder au CMS via des jetons d'accès liés à leur compte. Ces jetons sont associés aux mêmes données d'authentification.
|
|
52
|
+
|
|
53
|
+
## Stockage et sécurité des données
|
|
54
|
+
|
|
55
|
+
Les données d'authentification des utilisateurs sont stockées dans une **base de données MongoDB** hébergée sur **cloud.mongodb.com** :
|
|
56
|
+
|
|
57
|
+
- **Région :** AWS / Oregon (us-west-2)
|
|
58
|
+
- **Type :** Replica Set (3 nœuds)
|
|
59
|
+
- **Sécurité des mots de passe :** Tous les mots de passe sont hachés selon les pratiques standards de l'industrie.
|
|
60
|
+
|
|
61
|
+
Nous ne stockons aucune donnée personnelle inutile au-delà de ce qui est requis pour l'authentification et l'accès sécurisé au CMS.
|
|
62
|
+
|
|
63
|
+
## Partage des données avec des tiers
|
|
64
|
+
|
|
65
|
+
Nous ne vendons ni ne partageons vos données personnelles avec des tiers, sauf si cela est nécessaire pour les analyses (Google Analytics, Facebook Pixel) ou dans le cadre du processus d'authentification (connexion via Google ou GitHub).
|
|
66
|
+
|
|
67
|
+
## Droits des utilisateurs
|
|
68
|
+
|
|
69
|
+
En tant qu'utilisateur, vous avez le droit de :
|
|
70
|
+
|
|
71
|
+
- Accéder aux données personnelles que nous détenons à votre sujet
|
|
72
|
+
- Demander la correction ou la suppression de vos données
|
|
73
|
+
- Révoquer l'accès ou supprimer votre compte
|
|
74
|
+
|
|
75
|
+
Pour toute demande concernant vos données, contactez-nous à [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## Modifications de cette notice
|
|
78
|
+
|
|
79
|
+
Nous pouvons mettre à jour cette notice de confidentialité de temps à autre. Il est conseillé aux utilisateurs de consulter régulièrement cette page pour rester informés de toute modification.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
Faites-nous savoir si vous souhaitez un ton plus formel, ajouter des mentions GDPR/CCPA, ou l'adapter pour une page légale sur votre site.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Conditions d'utilisation d'Intlayer
|
|
5
|
+
description: Découvrez comment Intlayer gère les informations collectées via notre site web et CMS. Suivez la documentation pour comprendre les différents formats et cas d'utilisation.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisation
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Conditions d'utilisation
|
|
11
|
+
- Service
|
|
12
|
+
- Utilisation
|
|
13
|
+
- Licence
|
|
14
|
+
- Responsabilité
|
|
15
|
+
- Confidentialité
|
|
16
|
+
- Contributions
|
|
17
|
+
- Attribution
|
|
18
|
+
- Modification des conditions
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Conditions d'utilisation d'Intlayer
|
|
24
|
+
|
|
25
|
+
## 1. Acceptation des conditions
|
|
26
|
+
|
|
27
|
+
En utilisant Intlayer, vous acceptez d'être lié par ces conditions d'utilisation. Si vous n'acceptez pas ces conditions, veuillez ne pas utiliser l'outil.
|
|
28
|
+
|
|
29
|
+
## 2. Licence
|
|
30
|
+
|
|
31
|
+
Intlayer est distribué sous la **licence Apache 2.0** qui permet l'utilisation, la modification et la distribution du code pour des projets open-source et commerciaux. Les utilisateurs sont autorisés à modifier le code source et à soumettre des contributions via des pull requests conformément aux directives établies dans notre [guide de contribution](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md). Le vol de code à des fins commerciales est strictement interdit.
|
|
32
|
+
|
|
33
|
+
## 3. Utilisation commerciale
|
|
34
|
+
|
|
35
|
+
Vous êtes autorisé à utiliser Intlayer pour des projets commerciaux. Cependant, la réutilisation du code pour créer des outils concurrents directs basés sur Intlayer sans transformation significative ou ajout de valeur substantiel est interdite.
|
|
36
|
+
|
|
37
|
+
## 4. Responsabilité
|
|
38
|
+
|
|
39
|
+
Les mainteneurs d'Intlayer s'efforcent de corriger les bugs et les problèmes de sécurité dès qu'ils sont découverts. Cependant, ils déclinent toute responsabilité pour les dommages résultant de tels problèmes sur les infrastructures des utilisateurs. Nous encourageons les utilisateurs à signaler les problèmes via notre [système de suivi des problèmes](https://github.com/aymericzip/intlayer/issues).
|
|
40
|
+
|
|
41
|
+
## 5. Confidentialité
|
|
42
|
+
|
|
43
|
+
Intlayer ne collecte ni ne stocke aucune donnée personnelle des utilisateurs.
|
|
44
|
+
|
|
45
|
+
## 6. Contributions
|
|
46
|
+
|
|
47
|
+
Les utilisateurs sont encouragés à contribuer à Intlayer en suivant les directives fournies dans notre guide de contribution. Tout code soumis doit respecter les normes de qualité établies et sera examiné par les mainteneurs avant intégration.
|
|
48
|
+
|
|
49
|
+
## 7. Attribution
|
|
50
|
+
|
|
51
|
+
Tout outil développé pour étendre ou utiliser le code d'Intlayer doit clairement créditer Intlayer comme base du code. Cette attribution doit être visible dans le code source ainsi que dans toute documentation utilisateur ou promotionnelle.
|
|
52
|
+
|
|
53
|
+
## 8. Modification des conditions
|
|
54
|
+
|
|
55
|
+
Ces conditions d'utilisation peuvent être modifiées à tout moment. Les utilisateurs seront informés de tout changement significatif dans les conditions d'utilisation et devront accepter ces changements pour continuer à utiliser Intlayer.
|