Comhlíonadh rialachán príobháideachta

Note

Anseo gheobhaidh tú faisnéis dlí éagsúla a d’fhéadfadh a bheith uait chun Weblate a oibriú i ndlínsí dlí áirithe. Cuirtear ar fáil é mar mhodh treorach, gan aon bharántas maidir le cruinneas nó cruinneas. Ar deireadh thiar is ortsa atá an fhreagracht a chinntiú go gcomhlíonann do úsáid a bhaint as Weblate le gach dlí agus rialachán is infheidhme.

Tip

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:

  • Rialachán Ginearálta maidir le Cosaint Sonraí an AE (GDPR)

  • Acht Príobháideachta Tomhaltóirí California (CCPA)

  • Lei Geral de Proteção de Dados na Brasaíle (LGPD)

  • Acht Cónaidhme na hEilvéise maidir le Cosaint Sonraí (nFADP)

  • Acht um Chosaint Faisnéise Pearsanta agus Doiciméid Leictreonacha Cheanada (PIPEDA)

  • Acht um Chosaint Sonraí Pearsanta Digiteacha na hIndia (DPDPA)

  • Dlí um Chosaint Faisnéise Pearsanta na Síne (PIPL)

Prionsabail phríobháideachta

Íoslaghdú sonraí

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.

Rochtain agus iniomparthacht sonraí

  • Users can download a JSON export of their user data from the Account tab in Próifíl an úsáideora; 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.

An ceart chun scriosadh agus ceartúcháin

  • 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.

Coinneáil agus scriosadh sonraí

  • 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.

Slándáil agus rúndacht

  • 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 Abhatáir.

Aistrithe idirnáisiúnta

  • 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.

Mapáil rialála

Creat

Supporting Weblate features

GDPR (AE)

Data export, correction, account removal, audit logs, privacy notices, configurable retention, self-hosting

CCPA (California)

Data access, deletion workflow, user control, no built-in sale of personal data

LGPD (An Bhrasaíl)

Transparency, access, correction, deletion workflow, operator-defined legal basis

nFADP (An Eilvéis)

Transparency, purpose limitation by configuration, account controls, auditability

PIPEDA (Ceanada)

Notice, consent workflow, access, correction, deletion

DPDPA (An India)

Notice, consent workflow, user rights handling, hosting locality controlled by operator

PIPL (An tSín)

Purpose limitation by configuration, data minimization, self-hosted locality controls

Moltaí maidir le comhlíonadh

  • Notices and consent: Provide privacy, cookie, subcontractor, and terms information through Modúl dlí, and update LEGAL_TOS_DATE when users must accept changed terms.

  • Policy links: Link external privacy and legal documents with PRIVACY_URL and LEGAL_URL when the documents are hosted outside Weblate.

  • Data subject requests: Define an operational process for user-data export, correction, account removal, backup handling, and historical contribution review.

  • Retention: Configure AUDITLOG_EXPIRY and document retention periods for database backups, log aggregation, mail systems, repositories, and external integrations.

  • External services: Review configured authentication providers, avatar providers, analytics, Sentry, GELF logging, machine translation, e-mail, and repository integrations for transfer and processor obligations.

  • Locality: Ensure application hosting, backups, logs, repositories, and external processors are located in permitted jurisdictions.