Updated September 20, 2026. This notice applies to the mobile companion and browser app distributed by the app publisher.
The app is local-first. It does not include advertising, third-party analytics, or cross-app tracking. Core pairing, capture, and local tools work without an account. You may optionally create a publisher-operated account with Google or Apple to carry approved app data between devices.
The app can process text that you enter, assistant history, reminders, memory notes, a location label that you type, device connection and diagnostic state, and photos, videos, or audio that you choose to capture or import. This information stays in app-specific storage unless you explicitly submit it to an endpoint or export it.
You can enable a backend URL and submit an assistant prompt or a tool-session request. A request can include the text you submit, language, a random local conversation or session identifier, selected capability, timestamps, and related interaction metadata. The app does not send these requests until you enable the backend or explicitly choose to share. The destination and its retention terms depend on the URL you configure. Do not use an endpoint that you do not trust.
Tools > Studio connects to LazyEdit Studio only after you approve account linking. The app uses scoped access and refresh credentials, not your Studio password. Native clients protect credentials with Android Keystore or Apple Keychain. The PWA companion keeps them server-side and uses a protected session cookie; browser storage contains upload receipts and retry identifiers, not Studio access tokens.
When you explicitly choose to upload, Studio receives that video's bytes (including any audio and embedded metadata), filename, size, content hash, and optional title. Processing receives the editing context or subtitle corrections you submit. These are linked to your Studio account and retained by your selected Studio service. No automatic gallery-wide upload occurs. Do not upload private or bystander recordings without appropriate consent.
Publication requires separate permission and your explicit review and confirmation. The chosen social platform then receives the reviewed video and publication metadata under its own terms. Uploading, linking or capturing does not automatically publish. Unlinking revokes the device grant but does not cancel accepted jobs, erase uploaded Studio media, or remove existing social posts. Manage those records in Studio and the selected platform, or contact their operator for deletion. Native source snapshots and pending-operation history remain locally for resumable work until app data is removed; do not erase unresolved jobs merely to retry.
If you choose Google or Apple sign-in, that provider authenticates you and returns a short-lived identity token to the app. The app sends that token and a one-time security challenge to the publisher account service for validation. Depending on what the provider supplies, the service can store the provider name, provider-specific account identifier, email address and verification status, display name, and profile image URL. It uses the provider-specific identifier, not the email address, as the account identity.
The app never receives your Google or Apple password. After validation, the service issues an app-specific session token. Android protects it with Android Keystore, Apple platforms store it in Keychain, and the browser stores it only in the current browser session. Google and Apple process sign-in under their own privacy notices and account settings.
Capture and recording start only after a user action and show an operating-system or in-app recording state. The Android companion requests Bluetooth and nearby-device access to connect to supported hardware-provider glasses. Android 11 and earlier may require location permission for Bluetooth discovery; the app does not use that permission to collect GPS location. Network and Wi-Fi permissions support local device and optional backend communication.
The app publisher does not sell personal information. The app does not share information for advertising or cross-app tracking. Information leaves the device only for a connection or sign-in you initiate, when you export it, or when you explicitly submit it to a backend that you select.
Local records remain until you delete them with available product controls, clear app or browser storage, or uninstall the app. App session tokens are not included in job data. Data sent to a backend is governed by that endpoint's operator and retention policy.
If you create an account, the in-app Delete account control removes the publisher account record, linked provider identity, and all app sessions for that product. It does not delete local captures or device pairing. You can also use your Google or Apple account settings to review or revoke the provider connection.
The account service requires HTTPS; development builds permit plain HTTP only on the same device. Paired glasses media transfer uses HTTPS with a certificate pin delivered through the paired control channel. Use HTTPS for any internet-accessible or user-configured tool backend. Plain HTTP on a trusted local network does not protect data in transit. If you choose an endpoint in another country or region, your submitted information may be processed there under that endpoint's terms.
The app is not directed to children under 13, does not knowingly collect children's personal information for the publisher, and should not be used to record another person without appropriate notice and consent.
Material changes to data collection, cloud services, advertising, analytics, or account features will be reflected in this notice and the applicable store disclosures before release.
Controller: the app publisher, company website.
Privacy questions: privacy contact
Last updated: 2026-09-20