File Transfer (Android app com.lam2000.file_transfer, iOS and macOS app com.lam2000.fileTransfer, and the Windows app), made by Lam Nguyen Developer ("we").
Effective date: October 25, 2026
This policy explains what data the app accesses, collects and shares, why, and who receives it. In short:
Files you send go straight from your device to the device you pick, over your local Wi‑Fi network, a temporary Wi‑Fi network between the two devices, or Bluetooth. They never pass through our servers — we run none — and we never receive them.
The app has no accounts and never asks for your name, email address or phone number.
On Android and iOS the app shows ads from Google AdMob, and on every platform it uses Google Firebase or Google Analytics for usage statistics and crash reports. These Google services collect the data listed below.
Device or other IDs: collected by AdMob and Firebase, shared with Google through AdMob. Used for advertising, analytics and fraud prevention.
Approximate location (from your IP address): collected by AdMob and Firebase, shared with Google through AdMob. Used for advertising, analytics and fraud prevention.
App interactions: collected by AdMob and Firebase, shared with Google through AdMob. Used for advertising, analytics and fraud prevention.
Diagnostics: collected by AdMob and Firebase, shared with Google through AdMob. Used for advertising, analytics and fraud prevention.
Crash logs: collected by Firebase Crashlytics, not shared. Used for analytics (fixing crashes).
Purchase history (Android and iOS, only if you buy Premium): which plan you bought and when, recorded by Firebase Analytics, not shared. Used for analytics.
All of it is encrypted in transit. Details follow.
You choose what to send: files, photos, videos, music, apps, contacts or text. The app sends them directly to the device you pick:
On the same network, over your local Wi‑Fi using the open LocalSend protocol, so it also works with the LocalSend app.
When the two devices share no network, over a temporary Wi‑Fi network one of them creates (Wi‑Fi Direct or a hotspot), Apple's peer-to-peer Wi‑Fi between Apple devices, or, for small files, Bluetooth.
With "Send to a device without the app", a web page on your local network that other devices open in a browser after entering a 4-digit PIN. Sharing stops when you leave that screen.
Files received are saved only on the receiving device, in the folder chosen in the app's settings. Transfers stay on your local network or the direct link between the two devices and never cross the Internet. They are not end-to-end encrypted, so use networks you trust. Each device asks before accepting a transfer unless you have marked the sender as trusted or scanned its one-time QR code.
To be found by other devices, the app announces on your local network the device name you set in the app, the device model and type (phone, tablet, computer), and a random identifier created on first launch. Devices running File Transfer or LocalSend on the same network can see this. To wake a nearby device that has the app closed, the app sends a Bluetooth signal that carries only the app's own identifier, not your device name. None of this is sent to us.
The app asks for each permission only when the feature that needs it is used:
Local network, Wi‑Fi and nearby devices: to find devices and transfer files. On Android 12 and earlier, Android requires the location permission to show Wi‑Fi information and to create a hotspot. The app does not read, store or send your location.
Bluetooth: to find nearby devices, wake them when the app is closed, and carry small files when there is no Wi‑Fi path.
Camera: to scan the QR code shown on another device. Images are processed on the device and never saved or sent.
Photos, videos, music: to show your media so you can choose what to send, and on iOS to save received photos to the Photos app when you tap "Save to Photos".
Contacts: to show your contacts so you can send some of them as a vCard. Contacts leave your device only when you send them.
Notifications and background running: to show incoming transfers and transfer progress, and, if you turn on background mode, to stay ready to receive after a restart.
Install apps (Android): to install an APK you received, when you tap Install.
The app shows banner, interstitial and app open ads from Google AdMob. The Google Mobile Ads SDK collects the following data and shares it with Google for advertising, analytics and fraud prevention:
Device or other IDs: the Android Advertising ID and the app set ID, or on iOS the advertising identifier (IDFA, only if you allow tracking) and the identifier for vendors.
Approximate location: estimated from your IP address.
App interactions: for example app launches, taps, and ad and video views.
Diagnostics: app and SDK performance, such as launch time.
Google uses this data under its own privacy policy and may use it to show personalized ads unless you opt out (see "Your choices"). How Google uses data from apps that use its services: https://policies.google.com/technologies/partner-sites
The macOS and Windows apps show no ads.
Premium is an optional plan that removes ads; every transfer feature stays free. Google Play or the App Store handles the payment, and we never see your name, email address or payment details. The app asks the store which plan is active on this device to turn ads off, and Firebase Analytics records the purchase (plan, price, currency and time) so we can see which plans are bought. Manage or cancel a subscription in your Google Play or App Store account.
We use Firebase Analytics, Firebase Crashlytics and Firebase Remote Config, which Google runs for us as a data processor. On Windows, and in the iOS and macOS share extension, the same statistics go to Google Analytics directly. They collect:
App interactions: the screens you open and the buttons you tap, for example "Send" or a settings switch. Never file names, device names, IP addresses or anything you type.
Crash logs: technical details of crashes and unexpected errors, such as the stack trace and the error message. An error message can include the name of a file the app was working on.
Diagnostics: device model, operating system version, app version and language.
Device or other IDs: the Firebase installation ID and the Analytics app instance ID, or on Windows a random identifier created by the app. On Android, analytics does not collect the Advertising ID; on iOS, it can read the advertising identifier only if you allow tracking.
Approximate location: country or region, derived from your IP address.
We use this data to see which features are used, to fix crashes, and to adjust settings such as how often full-screen ads may appear.
In the EEA, the UK and Switzerland, the app asks for your consent with Google's consent message before showing ads, and you can change your choice at any time in Settings > Ad privacy. Residents of US states with privacy laws see Google's US state regulations message, where they can opt out of the sale or sharing of their data.
On iOS, the app asks through Apple's App Tracking Transparency prompt before AdMob can use your advertising identifier. You can change this at any time in Settings > Privacy & Security > Tracking.
On Android, reset or delete your Advertising ID, or opt out of personalized ads, in your phone's settings (Settings > Google > Ads, or Security & privacy > Privacy > Ads, depending on the device).
Uninstall the app to stop all further collection.
On your device: uninstalling the app, or clearing its storage, deletes everything the app keeps on the device, such as its settings, transfer history and trusted devices. Files you received stay in their folder until you delete them.
With Google: apart from emails you send us, the data we receive is tied only to the random identifiers listed above, not to your name or email address, so we cannot find or delete it for a specific person on request. It is deleted automatically as described below. Deleting your Advertising ID and uninstalling the app stop new data from being linked to those identifiers. Google's own controls for the data it keeps are at https://myaccount.google.com
We run no servers and keep no copies of this data ourselves. Firebase Crashlytics keeps crash reports for 90 days. Google Analytics keeps user-level event data for at most 14 months. Other data is kept as described in Google's policies: https://policies.google.com/technologies/retention and https://firebase.google.com/support/privacy
Data sent to Google is encrypted in transit (HTTPS/TLS). The app's settings and transfer history stay in its private storage on your device. The web page for devices without the app locks itself after repeated wrong PINs.
The app is not directed at children under 13, and we do not knowingly collect data from children.
If you email us (for example through Settings > Feedback & bug reports), the message opens in your own email app. We receive your email address, your message and, if you leave "Include device info" on, the app version, operating system, device model and app language. We use them only to reply to you and fix problems.
We will update this page when the app's data practices change, and update the effective date above.
Lam Nguyen Developer: lam29012000@gmail.com
Google Privacy Policy: https://policies.google.com/privacy