Babilim

Babilim Privacy Policy

Last updated: 30 October 2026

This policy explains what the Babilim translation service ("the Service", operated by 鹿閣創意有限公司 (Kodeer Design Ltd.), "we") receives, why, how long it is kept, and who processes it. The Babilim WordPress plugin's readme lists, item by item, exactly what the plugin sends; this policy covers what the Service does with it.

1. Nothing before consent

The plugin sends nothing until a site administrator presses "Enable Babilim". "Disable Babilim" stops all further requests.

2. What we receive

About your site (at registration and on each sync): the site's URL; WordPress, PHP and plugin versions; the site's locales; a public key generated for the site; and, for every installed plugin and theme, its slug, version, text domains, whether it is listed on WordPress.org and which translations are installed; plus short diagnostic codes. We do not receive the content of your posts, pages, comments or media, user names, e-mail addresses or administrator accounts.

When you act: translation requests (component, version, locale), downloads (which build), and problem reports — including any original text, translation, suggestion, note and screen address you choose to fill in.

Source uploads (only after you confirm, for components not on WordPress.org): the whole plugin or theme directory as a zip. If it contains keys, logs or customer data, they are uploaded too; we remove common sensitive files but cannot guarantee we find everything.

Payments: Paddle, our merchant of record, processes payments under its own privacy policy (https://www.paddle.com/legal/privacy); we never see card or bank details. At checkout Paddle collects the buyer's name, e-mail address, billing country and payment details and handles them under Paddle's privacy policy. From Paddle we keep only the transaction id, the amount and currency, the payment status, and records of refunds and chargebacks, so that a license can be traced to its payment. We do not store the buyer's name or e-mail address. If processing a payment event fails, we record only the fields needed to diagnose it: the event id, type and time, the transaction id, the status, the order reference, the product price id, and the adjustment id, action and type. Restore codes are stored only as one-way hashes.

Technical data: like any web service, our servers and our network provider see the IP address of each request, and our server logs record requests for operation and security.

3. Why we use it

To verify that you control the site, provide compatible translation files, decide which translations a site may use (free allowance or license), translate components that have no translation yet, keep translations up to date, investigate reported problems, process licenses and payment reversals, and protect the Service from abuse.

We do not sell data, show advertising, or use it for profiling.

4. Sharing and processors

5. How long we keep it

6. Your choices and rights

You can stop all requests with "Disable Babilim". Uninstalling the plugin with "Delete all Babilim data on uninstall" ticked removes the plugin's data from your site. To ask what we hold about your site, to have it corrected or deleted, or to have an upload deleted, contact [email protected]. Deleting a site's data may end a paid license bound to it. Depending on where you live, you may also have the right to object, restrict processing, or complain to a data protection authority.

7. Security

Connections use HTTPS. Each site authenticates with its own access token; the site's private key never leaves the site. Restore codes and checkout links are stored only as hashes.

8. Changes and contact

We will update this page when what we collect changes; the date above shows the latest version. Questions: [email protected].