ULAK does not collect, store, or share personal data. Files go directly between your devices and are never stored on any server.
ULAK ("the App") is a Fast File Transfer application developed by ALGSoft (Fatih ÖNDER). On the same local network or via Wi-Fi Direct it works entirely offline, transferring files directly between devices. With the optional Remote Transfer feature, paired devices on different networks can also exchange files over the internet; this is end-to-end encrypted and files are never stored on any server (see section 4).
This Privacy Policy describes what information ULAK accesses, how it is used, and the protections in place. This policy applies to all versions of ULAK across all supported platforms: iOS (Apple App Store), Android (Google Play Store), Windows (Microsoft Store & direct download), macOS (Mac App Store & direct download), and Linux (direct download, Flatpak, Snap).
ULAK does not collect, transmit, or store any of the following on any platform:
No third-party analytics SDKs, advertising networks, or telemetry tools are included in the application on any platform.
The permissions ULAK requests depend on the operating system. All permissions are used exclusively for core file-transfer functionality. No permission data is sent to external servers.
Purpose: Discovers other ULAK-enabled devices on the same Wi-Fi network using Bonjour/mDNS service discovery and establishes direct TCP connections for file transfers.
Data handling: Device discovery and local transfers stay on your local network. Optional Remote Transfer between different networks is described in section 4.
Purpose: Allows you to select photos and media files from your gallery to send to other devices. Triggered only when you use the gallery picker inside the app.
Data handling: Selected photos are transferred directly to the recipient device on your local network. Photos are never uploaded to any server or cloud service.
Purpose: Sends local device notifications when an incoming transfer arrives or when a transfer completes. No remote push tokens are collected or transmitted.
Purpose: Detects connected Wi-Fi networks, enables peer discovery via mDNS/Bonjour, and establishes direct TCP socket connections between devices on the local network. The INTERNET permission on Android is required for any socket communication, including purely local connections.
Data handling: Local traffic stays within your local network. Optional Remote Transfer between different networks is described in section 4.
Purpose: Required on Android 13+ to scan for nearby Wi-Fi peers without needing precise location access. CHANGE_WIFI_MULTICAST_STATE enables multicast packets required by the mDNS discovery protocol.
Data handling: No location data is collected or stored. These permissions are used only for local device discovery.
Purpose: Allows you to select files, photos, videos, and audio from your device to send to other devices. On Android 13+, scoped media permissions are used (READ_MEDIA_*). On older Android versions, READ_EXTERNAL_STORAGE is used instead.
Data handling: Files are read only at the moment of transfer and sent directly to the recipient device. Nothing is uploaded externally.
Purpose: Required on Android 13+ to display local notifications for incoming transfer requests and completed transfers. No FCM (Firebase Cloud Messaging) tokens are used or collected.
Purpose: Declared in the app's APPX manifest for Microsoft Store packages. Grants permission to communicate over private (local) networks only. Required to discover peers via mDNS and transfer files over TCP on the LAN.
Data handling: Local traffic is confined to your local network segment. Optional Remote Transfer between different networks is described in section 4.
Purpose: Allows you to select files from your device to send. The app uses the standard Windows file picker dialog; no background file scanning occurs.
Data handling: Files are read only when you explicitly select them for transfer.
Purpose: Displays local toast notifications for incoming transfers and completion events. No WNS (Windows Push Notification Services) tokens are registered or sent.
Purpose: Sandboxed Mac App Store builds require explicit entitlements to listen for incoming TCP connections (network.server) and to initiate outgoing connections (network.client). NSLocalNetworkUsageDescription is required on macOS 14+ for mDNS/Bonjour discovery.
Data handling: Local connections stay on your local network. Optional Remote Transfer between different networks is described in section 4.
Purpose: Sandboxed builds use this entitlement to read files you explicitly select via the standard macOS Open/Save panel for transfer, and to write received files to the Downloads folder.
Data handling: Files are accessed only when you explicitly select them. No background file system scanning occurs.
Purpose: Sends local user notifications for incoming and completed transfers. No APNs push tokens are collected or transmitted.
Purpose: The system kernel handles network access directly. No explicit permission declaration is required. ULAK opens TCP sockets and performs mDNS peer discovery on the local network.
Data handling: Local traffic stays within your local network. Optional Remote Transfer between different networks is described in section 4.
Purpose: Allows reading files you select for transfer and writing received files to your home/Downloads directory. No background file system scanning occurs.
Purpose: Uses the standard freedesktop.org notification interface (via libnotify or D-Bus) to display local desktop notifications for transfer events.
On the local network, ULAK communicates directly between devices using:
Local transfers never traverse the public internet.
When Remote connection is enabled in the app (Remote Devices screen; it can be turned off at any time), ULAK connects to ULAK's own signaling and relay server relay.algsoft.net.tr, operated by ALGSoft and hosted in Germany (EU), so that paired devices on different networks can find each other:
Update checks (if applicable) are performed by the respective platform store (App Store, Google Play, Microsoft Store) and are governed by that store's own privacy policy.
All data processed by ULAK remains locally on your device:
Transfer history is stored locally in the app's private container on all platforms. No data is automatically synced to any cloud service by ULAK. (Device-level backup services such as iCloud, Google Drive backup, or OneDrive may back up app data independently, subject to the user's device settings.)
Uninstalling the app permanently removes all locally stored ULAK data.
All file transfers are protected with AES-256 encryption. Users may additionally set an optional transfer password to provide an extra layer of security for sensitive content. Local transfers stay on your LAN. Remote Transfer is end-to-end encrypted with WebRTC (DTLS); the connection is authenticated with a key established during code pairing, so neither the relay server nor anyone on the network can read or alter the data.
ULAK does not integrate with any third-party services on any platform. There are no embedded SDKs for:
ULAK does not knowingly collect personal information from children under the age of 13 (or the applicable minimum age in the user's jurisdiction). The app does not target children and has no features that require user registration or personal data entry. If you believe a child has used the app and you have concerns, please contact us using the information below.
You can revoke ULAK's permissions at any time using your operating system's settings. Revoking a permission limits the corresponding feature but does not result in data loss.
iOS:
Android:
Windows:
macOS:
Linux:
ULAK is distributed through the following channels. Each store's own privacy policy governs data collected during the download, purchase, and review processes — not ULAK.
ULAK complies with the review guidelines and privacy data-safety requirements of each distribution channel. The data practices disclosed in each store's privacy questionnaire accurately reflect the practices described in this policy.
We may update this Privacy Policy from time to time. Significant changes will be reflected by updating the "Effective" date at the top of this policy. Continued use of the app after the effective date constitutes acceptance of the updated policy. We encourage you to review this page periodically.
Questions about this privacy policy or ULAK's data practices? Reach us through any of the following: