LanBridge privacy policy

Scope and contact

This policy describes data processing for the LanBridge international website, accounts, remote connections and LanMate tasks. The operator is Hangzhou Jianlan Zhiwei Technology Co., Ltd. Contact support@lanbridge.cc for personal-data requests.

Account and service records

We process login emails, verification delivery and checking status, account, device and session information for authentication, service connections and security. The service may also retain connection history, errors and audit records, task usage and membership transaction status. Some identity and verification fields are stored as hashes or masked values.

When you choose Sign in with Google, we use the account identifier, email address, email verification status and, where provided, Google Workspace domain information returned by Google to authenticate you and link your LanBridge account. Our server stores a keyed hash of the Google identifier and its account link; account email is identified by a keyed hash and masked email address, with the verified full contact email separately encrypted for authorized support staff handling account issues, troubleshooting and usage feedback. Temporary sign-in information is held in service memory. After issuing a LanBridge session, we clear the raw Google identifier, email and domain information from that temporary flow. This Google sign-in flow does not retain Google access or refresh tokens. The Google sign-in link is removed when your account is deleted. Google processes sign-in data under its privacy policy.

We store verified contact email addresses in encrypted form for account support, troubleshooting and individual usage follow-up. Authorized support staff can view an address and manually send a message. Sending shares the recipient address and message with Amazon SES; replies go to support@lanbridge.cc. The stored contact address is removed when the account is deleted.

When you check out through Dodo Payments, Dodo Payments processes buyer data needed for payment, tax, compliance and fraud prevention. We receive order, payment, subscription and notification status needed to provide membership and reconcile billing. Dodo Payments independently processes the relevant data under its privacy policy.

Task content and remote display

Data needed for a task may include the goal, text, file content, browser pages, application information, images, screenshots and operation results. Processing follows the selected task, device, materials and authorized scope. Check sensitive information and access scope before approving.

Remote connections transmit data needed for authorized display and control. Task materials, results and diagnostics may be stored on devices or the service. Remote display and file content should not be assumed never to be stored or uploaded.

The current client stores task audit screenshots locally on the executing device. Server audit-screenshot uploads are disabled by default. An online model may separately receive images or screenshots needed for the task; that is a different data path from audit-screenshot uploads.

Models and service providers

With official models, the LanBridge service processes requests and forwards them to the model service bound to the task. With a custom model, content is sent to the provider and API address you configure; cross-device calls may be relayed by LanBridge. Necessary content may include text, images, file content and context.

The model recipient is determined by the model bound to the task or the model settings you select. Each task is not sent to every provider. Providers may process data in their service regions; their contracts, account settings and policies govern retention and subsequent processing. Review the selected provider's policy before use.

Our infrastructure uses Contabo hosting, Cloudflare R2 object storage and AWS SES email delivery. Verification delivery, software downloads and encrypted backups involve these services, separately from model requests.

Authorized actions may also submit content to target websites or recipients. Those third parties process received data under their own rules.

Task-record retention and deletion

Deleting a conversation from client history hides it and does not immediately erase server records. By default, the server cleans up completed, failed or cancelled tasks after 30 days, and tasks waiting for a user response after 30 days of inactivity, with checks every six hours.

Cleanup removes server task bodies and related process data while retaining a minimal receipt without task content. Daily usage totals without task bodies may remain for allowance control. Deployment settings may differ; contact support to confirm them or request deletion.

Local task audits and screenshots are not automatically deleted when server records expire. The default local audit capacity is 512 MiB; when full, new records pause without automatically removing older ones. Downloaded files and data submitted to third parties are not automatically deleted by stopping tasks, signing out or uninstalling.

Backups, account and security records, and billing information required by law may have different retention requirements. Deleting an online record does not immediately erase backup copies or data already processed by a third party.

First-party website statistics

We aggregate anonymous counts of visible visits and product-button clicks on our websites. We do not use cookies, browser identifiers or fingerprinting, or collect input content, task bodies, file paths or remote-control input for these counts. Referrers are classified only in the browser. The server may infer countries or regions offline. Aggregates contain no raw referrer addresses, query parameters, IP addresses or account identifiers and are retained for 90 days by default.

Do Not Track or Global Privacy Control disables these browser statistics. Ordinary service requests, security records and server-side HTTP totals are unaffected. Download clicks, download-address requests and bytes sent do not prove a completed download or installation.

Advertising measurement

The advertising-measurement section of this privacy policy was updated on October 30, 2026.

For Reddit campaigns, LanBridge records only the campaign source in a promotional link and, with your consent, uses it for its own download, sign-up, sign-in and displayed-frame statistics. We do not collect Reddit click identifiers, load Reddit advertising-measurement code or report these source conversions to Reddit or Google. Promotional links may be shared, so a campaign-source record alone does not verify a paid click.

Only on the lanbridge.cc international production site, and only with your permission, we use Google Ads to measure web download clicks, new accounts and displayed remote frames. We may also import native sign-ups and displayed remote frames using ad-click IDs. Google may receive ad-click IDs, cookies, IP addresses, simplified page addresses, event times and deduplication references without raw account identifiers. We do not send login emails or email hashes, raw LanBridge account or device IDs, tasks, files or remote-screen content, or enable personalized ads or enhanced conversions.

LanBridge uses browser storage and a random first-party cookie to link a consented ad source to download-address preparation, web sign-in, native Google sign-in through the same system browser, and remote frames subsequently displayed for that account, for up to 30 days. Ad-click IDs and account associations are used only for this measurement. We do not infer identity from IP addresses, browser fingerprints or nearby timestamps.

A download click means a download address was obtained, not that downloading or installation finished. The server confirms new accounts; a native first frame is recorded only after an updated client confirms it was displayed. Direct native email registration, another browser, an older client or declining measurement may leave parts of the journey unattributed. Without an ad-click ID, we count only the campaign source and cannot confirm a specific paid click.

Decline or withdraw measurement in Privacy choices in the website footer, sign-in page or workspace account menu. No Google tag loads before consent and earlier events are not replayed. An older choice does not automatically permit the new Reddit campaign measurement. Withdrawal immediately stops this browser’s reports and clears Google first-party advertising cookies. When the server receives the withdrawal, it deletes the source and account association and stops subsequent native attribution. A network outage can delay delivery; the next site visit tries again. Data already received by Google is governed by its privacy policy. Essential sign-in, device authorization and free remote desktop are unaffected.

Google privacy policy

Choices, support and personal-data requests

You can refuse authorization, stop tasks, disconnect and sign out of sessions. Stopping does not undo completed actions. To request access, correction, export or deletion of account or personal data, contact support@lanbridge.cc with the scope of your request. We need to verify that the request belongs to the account.

When you send support email or diagnostics, we process the contact information, description and attachments you provide to address the request. Avoid sending unrelated passwords, tokens or other sensitive information.

This website stores appearance and display-language preferences in the browser. Visits also involve ordinary network requests and server logs. Preferences affect presentation only and do not grant device, task or payment permission.

support@lanbridge.cc