Your device history stays local by default.

When you are online, Leadly sends barcode values, typed product searches, and label text extracted on your device from a photo or camera frame. The current matching flow does not send the source photo itself automatically.

Leadly may retain those inputs with the selected product, candidate scores, match explanation, and linked evidence in server scan-session records. These records support the match, traceability, and quality review and are separate from your local recent-history list.

A signed-in user can separately choose to save a package photo privately with an account-owned scan. Leadly requires an explicit confirmation before that upload. The photo remains an identity reference, is not treated as test evidence, and can be deleted from the report or through account deletion.

If you publish to Community, Leadly processes the account name, profile details, post text, selected topic and Leadly-provided cover, timestamps, and engagement needed to display and organize that content.

If you attach a product, the public post also includes the reviewed product name, brand, category, reviewed catalog image, evidence-status wording, source label, and the date Leadly created that frozen snapshot. It does not include the originating scan, report, barcode, household record, private photo, or internal product reference.

Approved Community posts and profile details are public. Other people may share or capture them outside Leadly, so do not post information you expect to remain private. Drafts that are expressly labeled as device-only remain on that device unless you submit them. Submitted posts remain private to their author until approved.

If telemetry is enabled in settings, Leadly stores a bounded log of structured events and errors on your device to help diagnose recent app behavior.

Telemetry turns off when you switch it off. Existing logs stay on-device until older entries are displaced, you clear them manually, or you reset local data. They are not included in the app's CSV or JSON history exports.

The public website may use privacy-oriented page analytics when that service is enabled. Leadly's servers may also send operational errors to a configured error reporting service. These services are separate from the app's on-device telemetry setting and do not receive source scan photos through the normal matching flow.

Beta feedback is another separate, user-initiated path. When you press Send feedback, Leadly receives the issue category, any note you choose to write, app, build, and catalog versions, and a persistent random app-install identifier used to associate repeat submissions during beta review. The random identifier is transmitted with the submission; the feedback database stores only its SHA-256 hash, not the original identifier or a Leadly account ID.

Attaching diagnostics to beta feedback is optional and off by default. If you select it, that submission can include up to 20 recent allow-listed app events or errors with coarse fields and minute-level times. Feedback rows, including a note or attached diagnostics, are marked to expire 90 days after submission and are physically removed during a later feedback-storage maintenance write. Physical deletion can occur after that date if no new beta feedback arrives. Because the row has no account ID, deleting an account does not identify or remove previously submitted feedback; it follows this expiry schedule. Clear data from this device removes the on-device random identifier, so the next feedback submission creates a new one, but it cannot recall feedback already sent. Browser or operating-system storage removal and uninstalling the app also remove the local identifier.