DropLAN · Your data

Privacy Policy

Draft updated October 22, 2026 · English

Publication draft. Developer identity and contact details are pending. This document describes the current build with online collection disabled.

Your files stay on your chosen devices. DropLAN shares selected files over a local network. You do not need a DropLAN account, an internet connection, or a receiver app for local transfers.

1. Scope

This policy describes the current DropLAN Android app and its local browser receiver. It covers information used to provide local file sharing, preferences, and temporary transfer state.

2. Information processed locally

Selected files: file contents, names, sizes, and available metadata are read through Android’s system file picker with your permission. Selected folder paths may be used to preserve archive structure.
Connection and transfer information: local network addresses, pairing credentials, browser sessions, download requests, progress, and measured transfer performance are used to authorize and operate a sharing session.
Preferences: appearance, language, concurrency, keep-screen-on, and connection preferences may be stored on your device.
Temporary files: when you choose archive preparation or compression, DropLAN may create a local archive in app-controlled storage.

3. Who receives your files

Browsers you authorize can access the files included in the current share. DropLAN does not upload those files to a developer-operated cloud relay. A recipient can keep, copy, or redistribute a downloaded file; ending a share cannot recall those copies.

4. Permissions and security

File access is limited to what you select through Android. Network, nearby-device or Wi-Fi permissions support local connectivity where required. Notifications support the active sharing service. Availability depends on your Android version and chosen connection method.

Pairing and session access controls limit access to the active share. Plain HTTP and WS traffic is not encrypted. HTTPS and WSS use TLS when configured; certificate trust must be checked on the receiving device. Use a network and recipients you trust.

5. DevHub and external services

This build includes DevHub integration with its collection master switch disabled. Optional country/region and device statistics are configured but are not currently sent. No DevHub account, Google sign-in, purchases, campaign requests, or event reporting is enabled by DropLAN. Local file sharing does not depend on DevHub. Enabling any online service in a future version requires an updated notice and any applicable consent before collection begins.

Optional country and device statistics: after collection is enabled with the required notice and authorization, DevHub is configured to process device manufacturer, model, Android version, country/region code, and language tag for device compatibility and regional usage analysis. Country comes from the device’s default locale settings, not GPS, and may differ from your physical location. Installation registration also uses an installation identifier, first-open time, and app version. Requests go to devhub.wukuiqing0409.workers.dev; its hosting infrastructure receives connection information such as IP addresses. Shared file contents are not included in these statistics.

No collection enablement control is currently available. Consent, withdrawal, server retention, and server deletion arrangements must be completed before activation. Declining optional statistics must not prevent local sharing.

Android, your file provider, browser, and device backup services operate under their own settings and privacy policies. App data may be included in system backups when enabled. If these pages are published on a website, the hosting provider may process connection information such as IP addresses to serve them. The HTML pages themselves contain no analytics, external fonts, scripts, or tracking pixels.

6. Retention and deletion

Active share authorization and transfer state are held for the sharing session. Ending sharing invalidates access; restarting the app does not automatically restore the share. Preferences remain until changed or app storage is cleared. Temporary archives may remain until cleanup or removal of app cache/storage. No fixed automatic retention period is promised.

See the Data Deletion Policy for steps to remove local app data, browser data, and downloaded copies.

7. Your choices

You choose what to share, which browsers to approve, and when to stop sharing. You may revoke permissions through Android settings or remove the app. These actions do not remove files held by recipients or by your storage and backup providers.

8. Contact and policy changes

The developer’s legal name and privacy contact must be supplied before this policy is published. This draft does not yet provide a privacy request channel. Material changes will be reflected in an updated policy date.