Дотримання правил конфіденційності¶

Примітка

Тут ви знайдете різноманітні юридичні відомості, які можуть знадобитися вам для роботи з Weblate у певних юрисдикціях. Їх надано для орієнтування, без жодних гарантій точності або правильності. Уся відповідальність щодо забезпечення повної відповідності законодавству користування вами Weblate покладається на вас.

Порада

Weblate provides features that help organizations operate within privacy frameworks such as GDPR, DPDPA, PIPL, and others. Hosting, legal basis, retention, notices, and compliance responsibilities remain under the deploying organization’s control.

This document outlines Weblate features that can support compliance with:

Загальний регламент ЄС про захист даних (GDPR)
Закон Каліфорнії про захист прав споживачів (CCPA)
Загальний закон Бразилії про захист даних (LGPD)
Швейцарський федеральний закон про захист даних (nFADP)
Закон Канади про захист персональної інформації та електронних документів (PIPEDA)
Закон Індії про захист цифрових персональних даних (DPDPA)
Закон Китаю про захист персональних даних (PIPL)

Принципи конфіденційності¶

Мінімізація даних¶

Weblate processes account and activity data needed to provide translation workflows, authentication, notifications, access control, and auditability. Depending on enabled features, the following personal data can be stored or processed:

Account identifiers such as username, full name, primary e-mail address, verified e-mail addresses, and social-authentication associations.
Optional profile fields such as public e-mail, website, profile links, location, company, language preferences, and dashboard preferences.
Translation activity, suggestions, comments, watched projects, notification settings, and contribution statistics.
Operational records such as audit-log entries, IP addresses, user agents, timestamps, and security-related events.

External analytics, crash reporting, remote logging, and avatar providers are optional integrations controlled by the site operator.

Доступ до даних та їх портативність¶

Users can download a JSON export of their user data from the Account tab in Профіль користувача; the export format is documented in Weblate user data export.
Administrators can export active non-bot user data with dumpuserdata.
Project translations and translation files can be exported separately using Weblate’s project and file export features.

Право на видалення та виправлення¶

Users can correct account and profile information from the profile interface.
Users can request account removal from the Account tab. The removal flow requires confirmation and then deactivates and anonymizes the account.
Account removal clears private profile fields, API tokens, social-auth associations, group memberships, notification subscriptions, watched projects, and user translation memory.
Historical project records can remain associated with an anonymized deleted account where needed to preserve translation history and auditability.

Зберігання та видалення даних¶

Audit-log retention is configured using AUDITLOG_EXPIRY.
Backups, reverse-proxy logs, mail server logs, and database retention are controlled by the site operator.
Third-party services receive data only when configured or used by the operator, for example external authentication providers, avatar providers, Matomo, Sentry, remote logging, machine translation services, or repository integrations.

Безпека та конфіденційність¶

Weblate supports HTTPS deployments and secure cookie settings; operators should configure TLS and trusted proxy headers correctly.
Failed sign-ins, permission changes, two-factor changes, account removal requests, and other security events are recorded in the audit log.
Optional GELF logging can forward logs to systems such as Graylog.
Access control is enforced through users, teams, roles, project access settings, and component permissions.
Commit identity privacy can be improved with PRIVATE_COMMIT_EMAIL_OPT_IN, PRIVATE_COMMIT_EMAIL_TEMPLATE, PRIVATE_COMMIT_NAME_OPT_IN, and PRIVATE_COMMIT_NAME_TEMPLATE.
Avatar fetching can be disabled with ENABLE_AVATARS; when enabled, avatars are downloaded and cached server-side as described in Аватари.

Міжнародні перекази¶

Weblate itself does not require a specific hosting region.
Hosting location, backups, e-mail delivery, repository hosting, external authentication, analytics, error reporting, and machine translation services determine where data is processed.
Organizations can self-host Weblate in the required jurisdiction, or use a dedicated deployment with suitable infrastructure controls.

Нормативне картографування¶

Рамка	Supporting Weblate features
GDPR (EU)	Data export, correction, account removal, audit logs, privacy notices, configurable retention, self-hosting
CCPA (Каліфорнія)	Data access, deletion workflow, user control, no built-in sale of personal data
LGPD (Бразилія)	Transparency, access, correction, deletion workflow, operator-defined legal basis
nFADP (Швейцарія)	Transparency, purpose limitation by configuration, account controls, auditability
PIPEDA (Канада)	Notice, consent workflow, access, correction, deletion
DPDPA (Індія)	Notice, consent workflow, user rights handling, hosting locality controlled by operator
PIPL (Китай)	Purpose limitation by configuration, data minimization, self-hosted locality controls