Privacy

Files stay on your device

Files selected in Lalabb tools are read by browser APIs and processed in local memory. The conversion workflow does not send file bytes, filenames, creative contents, or generated outputs to a Lalabb server. Download links use temporary browser object URLs and are released after use.

Safe measurement

The analytics contract allows coarse events such as tool view, start, success, error code, locale, and result category. It prohibits filenames, file contents, full QR contents, project text, and direct personal data. No analytics provider is connected in this release.

Your choices

You can use every free tool without creating an account. Closing the page clears in-memory work that has not been downloaded.

Advertising and cookies

Guide pages use Google AdSense. When an ad page loads, the browser may contact Google and its advertising partners. They may use cookies, other local storage, and device information to deliver and measure ads. Ads may be personalised or non-personalised according to your choices and the applicable settings. Google Analytics is not installed on Lalabb.

For visitors in the EEA, the UK, and Switzerland, Google’s Privacy & messaging service presents choices to consent, decline, or manage options. You can later revisit your choice through the “Privacy and cookie settings” link that Google adds near the bottom of eligible ad pages. Declining personalised ads does not necessarily remove all ads.

Storage for tool functions

Book Studio saves project settings and progress in your browser’s IndexedDB; its autosave excludes the original file bytes and file handles. A Book Studio to Cover Studio handoff uses session storage. Creator Visual can save projects and templates in local storage. This browser storage is separate from AdSense storage and may remain until you remove it or clear site data.

Capture local storage

The v0.3.1 candidate keeps new originals and edits only in memory without a password. Choosing a separate password vault encrypts images, annotations, filenames and work records locally with AES-256-GCM. Extension and web vaults are independent; locking or restarting requires the password. Existing plaintext records may remain until consented migration completes. Records do not automatically expire after 30 minutes. Delete vault copies and downloaded files separately. Image content and passwords are not uploaded to a server. See the Lalabb Capture privacy notice for limitations.