Lalabb Capture privacy notice
Capture reads only the current webpage tab you explicitly invoke: its visible viewport or its scrollable page. OS screen/window selection is not provided.
Image pixels, filenames, job metadata and edit coordinates stay in local browser storage. Captured images and webpage contents are not uploaded to Lalabb, analytics services or third parties.
Saved screenshots and edited copies do not expire automatically after30minutes. Delete the capture, remove the extension, or clear its data. Handoff expiry is separate from original retention.
activeTab grants temporary access after invocation; scripting handles scrolling/restoration; offscreen stitches PNGs; downloads saves files; storage retains local work. No persistent all-sites access or background browsing-history collection.
Sensitive information visible on screen may appear in a screenshot. Hide it before capture and review an image before sharing it yourself. Full offline support is not promised.
Before Store submission, publisher/contact/support information, retention behavior and dashboard declarations must match the package. This policy covers the extension and web editor. The extension is not yet publicly available in the Chrome Web Store.
Capture
Publisher: Lalabb Studio · Support / 문의 · Existing site privacy
Extension-to-editor handoff uses browser messages after explicit Edit in Lalabb and Accept image clicks. Image pixels are never included in HTTP requests. Transfer is limited to a selected PNG part of 32MB and 16MP. Extension originals and web editor copies can be deleted separately and are isolated from Book storage.
Capture v0.3.1: data handling and password vaults
This notice describes the v0.3.1 release candidate; publication on the live website is a separate release step. Capture runs on the active tab only after your explicit action. Content suggestions temporarily read DOM region geometry such as main/article bounds, not OS window recognition or browsing-history tracking. The scripting permission supports region selection, existing scroll capture and page restoration.
Processed data include original images and split parts; source hostname, date, dimensions, format, filename and internal tab/window identifiers; crop, rotation and strip-removal coordinates; bubble text, numbered markers and annotations. Originals and reversible edits remain separate. Quick capture, editing and downloads work without a password, but new work stays only in memory. Closing or reloading a tab/browser, restarting the extension or memory reclamation may discard it. Download results you need to keep.
Local encrypted storage requires your choice to configure or unlock a vault and save. Images and work metadata are encrypted with AES-256-GCM. PBKDF2-SHA-256 with 600,000 iterations and a random salt derives a wrapping key from your password; it wraps a separate random 256-bit data key. Plaintext passwords and decryption keys are never persistently stored or sent to a server. Active keys exist only in memory. Locking or restarting requires the password again; Lalabb cannot recover a forgotten password. Extension and web vaults are independent and never exchange passwords or keys.
Existing plaintext records are not represented as already encrypted. With consent, migration reads originals one at a time, encrypts and verifies decryption, commits all linked records, then removes legacy data. Quota failures or interruption preserve the source for retry. Extra free space is required. Consent also upgrades only the old Capture database version to prevent older concurrent writers; downgrading to v0.3.0 then cannot directly reopen that library. Download needed files first. Unmigrated legacy data may remain plaintext.
Captures and vaults do not automatically expire after 30 minutes. Deleting a capture removes linked original/edit records. Deleting a vault removes that vault's encrypted records and configuration, not unmigrated legacy data, other vaults, Book/PDF records or downloaded files. Browser cleanup or extension removal may cause loss. Locking clears references to active decrypted work and keys, but cannot guarantee physical OS/RAM erasure or complete protection on a compromised device. Downloaded PNG/JPEG files are ordinary unencrypted files.
Files pass only after both Edit in Lalabb and Accept image are clicked, using the existing HTTPS origin, window and one-time nonce checks for the Capture editor on https://lalabb.net. A PNG original can accompany the edited PNG; a JPEG original remains in the extension while an edited PNG is passed. File objects include name, MIME type, size and last-modified time; names may contain a source reference. Source hostname, tab/window IDs and annotation operation lists are not separate transfer fields; annotation text can appear in exported pixels. Image bytes, passwords and annotation content are not uploaded to Lalabb servers or analytics. The extension has no advertising or tracking SDK. Website page, asset and advertising requests, cookies and CMP choices remain subject to the site policy.
Existing limits remain 16 megapixels and 32 MB per part, and 150 annotation edits. Large captures use split parts. Mosaic is a visual effect, not guaranteed secure redaction. User data are used only for the disclosed capture, editing, storage and export functions, not advertising targeting, sale or user profiling.