Privacy policy

Qingdao Weerocks Data Info. Tech. LLC. (hereinafter “Weerocks LLC”) operates the LanSender website. For privacy questions or requests about information you have sent us, contact lansender@weerocks.com.

No account is required. The LanSender apps have no advertising or analytics SDK and do not sell data or track users across apps. Message bodies and files travel directly between devices. Optional background reminders use the separate service described below; discovery announcements and content deliberately shared with a peer or support recipient also leave your device.

Your browser requests pages and assets from the site's hosting infrastructure. Those requests necessarily expose the IP address, requested path, time, ordinary HTTP headers and transport/security information needed to deliver and protect the service. Weerocks LLC does not use this information for advertising or cross-site analytics. Logs controlled by Weerocks LLC are ordinarily retained for no more than 30 days, except when longer retention is needed to investigate abuse, protect the service or comply with law. Infrastructure providers may process request data in the locations where they operate under their contractual and legal obligations.

The site stores your manually selected language and Light, Dark or System appearance setting in your current browser for future visits. Language-specific URLs always display the specified language; the homepage defaults to English when no choice is saved. These preferences are not used for tracking. Website analytics are described below. The site has no advertising, third-party fonts or a file-upload form. Clearing site storage removes the saved language and theme; browser controls may prevent them from being saved.

This website uses Google Analytics 4 to understand page visits, referral websites, approximate regions, browser and device categories, and clicks on published downloads. Google receives these events and network information, including your IP address, to process them. We do not send message content, transferred files, contact emails or URL query strings to Analytics. Download clicks do not prove a completed download or installation.

Google Analytics loads automatically when you visit the website. The site has no analytics prompt or switch. We use the statistics to improve the website and understand which downloads visitors choose. We do not enable Google Signals, advertising personalization or automatic form/search measurement. Your browser or content-blocking tools may restrict this collection.

First-party _ga cookies can be stored for up to 180 days to distinguish visits. Event-level and user-level Analytics data are retained for two months; aggregated standard reports may remain longer. Google may process data outside your country under its applicable terms and safeguards. See Google’s privacy policy at https://policies.google.com/privacy. Contact lansender@weerocks.com for privacy questions.

LanSender announces a device identifier, display name, platform, protocol capabilities, reachable address and port, temporary process identifier and public-key fingerprint on the local network. Other participants with compatible software can observe these announcements.

Messages, selected files, folders and transfer metadata travel directly to the selected peer over the client's encrypted connection. The publisher does not receive them through a LanSender server. You can compare safety codes for an additional identity check. The recipient controls the received copy after successful transfer.

The Windows, XP, macOS and iOS apps save message and attachment history locally in SQLite. Paging and memory-cache sizes do not delete saved history by count. Windows and Apple history has no additional application-level encryption at rest; iOS uses protected app storage and excludes history from system backup. Keys are stored separately; iOS may retain its Keychain identity after uninstall. Previously deleted or unsaved messages cannot be recovered.

The Android app stores encrypted history record bodies using Android Keystore AES-GCM in a private no-backup database. Its local indexes and received originals are not covered by that history-body encryption. Explicit open/export can give another app access or create a separate copy. Clearing a conversation on any client retains completed received originals and exported copies; deleting originals is a separate action. Consult Downloads for availability.

Mac notifications may show a peer name and generic event, without message text or filenames. iPhone/iPad and Android background alerts also omit peer names. Content requires the app to resume; an active-transfer notification does not guarantee transfer while suspended.

The Linux client protects local identity keys, saved peer trust and message payloads with AES-256-GCM, using a key stored in the desktop Secret Service. SQLite indexes, record identifiers, ordering and sizes are not encrypted. Received originals remain ordinary files in your chosen folder. Linux notifications show a generic event without message text, filenames or peer names. Closing the window keeps reception active only when a system tray is available; quitting or suspending the computer stops reception. Linux does not register for the Apple reminder service.

Pending messages are stored on the sending device and can survive restarts. Attachments use local staging or references to original files, which are checked again before sending. Cancelling removes the corresponding queue entry and app-created staging, not originals, and cannot recall content already received.

Enabling reminders on iPhone/iPad or an Android device with Google Play services sends an Apple APNs or Google FCM push token, provider and selected language to the LanSender notification service operated by Weerocks LLC. It stores random registration and route identifiers, authorization digests and short-lived event receipts. These records can be linked to the receiving device; no LanSender account is required.

A supported sender submits only an authorized route, random event identifier and message-or-file event type. Apple or Google receives the push token and a generic alert; Google also processes app installation identifiers and device information needed for Android push registration. Message text, filenames, attachments, safety codes, LAN identity keys and conversation history are not uploaded to the LanSender notification service. Data is used only for registration, authorization, delivery, deduplication and service protection, not advertising or tracking.

Registration and route authorization expire after at most 30 days without renewal; deduplication receipts expire within 24 hours. Cleanup runs during service activity or hourly. Tokens are encrypted and authorization secrets are stored as digests. Disabling reminders deletes registration and grants, or retries deletion on the next successful connection if offline. The service does not log request bodies, tokens or authorization secrets; operator-controlled request and security logs are ordinarily retained no more than 30 days.

Reminders require internet, notification permission and the relevant push service. After tapping, both apps must run and reach each other over LAN to deliver content from the sender. The server does not store queued messages or files. System restrictions, force-stopping or being offline may prevent alerts; immediate delivery is not guaranteed. Vendor push channels for Android devices without Google Play services are not yet available.

The iPhone/iPad support report is prepared only at your request. It contains app and OS versions, generation time, runtime status, peer count and transfer-state counts. It excludes message content, filenames, paths, device identifiers, keys and transfer tokens.

The iPhone/iPad selected-message report is separate. After selection and confirmation, it includes that message's text, identifier and time, the peer name and identifier, app and OS versions and report time. It excludes unrelated conversation history, file paths, local device identifiers, keys and transfer tokens. Review the report before choosing a sharing destination; it is not uploaded automatically.

If you email lansender@weerocks.com, Weerocks LLC and the providers that route and host the mailbox receive your address, message, attachments and normal email metadata. The mailbox is used for support, privacy, security and abuse reports. Case correspondence is ordinarily retained for 90 days after closure, with longer retention only when required by law or an active security investigation.

You can decline a transfer, stop the app, change system permissions, clear a conversation and delete stored files. Use peer blocking where the installed client provides it. These actions do not erase a recipient's independently retained copy or information you already emailed.

Contact lansender@weerocks.com to request access to, correction of or deletion of information you previously sent to Weerocks LLC, or to raise another privacy question. Provide only the information needed to locate the correspondence and verify the request; do not include a password or private key. We aim to acknowledge ordinary requests within two business days and escalate urgent safety or security reports within 24 hours.

This version replaces the earlier privacy policy from its effective date. Material changes will state a new version and date. Mandatory privacy rights under applicable law are not limited by this policy.