Privacy Policy

Ladybird Privacy Policy

Ladybird is designed to keep your configuration local. This page explains what the extension stores, what it does not collect, and what you should know when exporting data.

Last updated: 2026-02-26

Summary

  • We do not collect, sell, or share personal data.
  • Configuration data is stored locally in chrome.storage.local.
  • Password Vault data is encrypted locally and only decrypted when you unlock the vault.
  • The extension does not upload your data to Ladybird servers. There is no telemetry backend.

1. Data collection

Ladybird does not collect analytics, telemetry, or usage data.

2. Local storage

  • Extension configuration and saved elements or flows are stored locally in chrome.storage.local.
  • Password Vault data is stored locally in encrypted form.

3. Export and import

  • If you choose to export your data, a JSON file is generated locally on your device.
  • Export can optionally include Password Vault data after vault-password confirmation.
  • You are responsible for handling exported files securely.

4. Permissions

Permissions are used to render user-defined UI on pages, operate the side panel, and run user-triggered automation flows.

5. Third parties

Ladybird does not sell or share your data with third parties.

6. Security notes

  • The extension uses packaged code only. It does not execute remote code.
  • Password Vault prompts and flow logs are designed to avoid storing or logging plain-text vault passwords.
  • If you forget the vault password, vault contents cannot be recovered and must be reset.

7. Contact

For privacy-related questions, please open an issue in this repository.