Privacy, in plain language.
Effective date: July 29, 2026
Applies to: VeilSend for Android
1. Scope and service model
This Privacy Policy explains how VeilSend handles information when you use the Android application. VeilSend is offered as a free, advertising-supported service. Version 1.0.0 does not display in-app ads and contains no advertising SDK. Advertising-data terms for advertising-enabled distributions are stated in Section 6.
The application has no VeilSend account system, login, subscription, cloud file storage, remote transfer backend, analytics SDK, Firebase SDK or social feature.
2. Information the app processes
Files and transfer manifests
When you choose files, the app processes the selected file contents and related metadata—such as display name, media type, byte size and transfer status—to perform the transfer. The receiving device shows the sender's friendly device name and the file manifest before the receiver accepts.
Local device and network information
The app processes a randomly generated, editable friendly device name; local IP address and port; service-discovery records; session identifiers; protocol version; and temporary cryptographic material. These values are used to find the receiving device and establish the local transfer session. VeilSend does not read your account name to create the friendly name.
Preferences and task state
Language, theme, friendly device name, authorized receive folder, history-retention preference, first-run state and necessary transfer-task state are stored locally on the device.
Support communications
If you email support, we and the email service provider process the address, message and attachments you choose to send so we can respond, prevent abuse and keep necessary support records. Do not send file contents, session codes or other sensitive information unless it is necessary for your request.
3. How local transfer works
The core transfer occurs directly between two devices that can reach each other on the same local network. File contents are not routed through or stored by a VeilSend-operated cloud server. Internet access is not required for the core transfer, although the network itself may provide internet access independently.
A receiving session is visible only while the user actively opens Receive. A one-time QR code contains connection and temporary handshake data; it does not contain file contents or filenames. The receiving user reviews the device and manifest and must accept before file content is written. Transfer frames are encrypted in transit for the local session and files are checked for integrity before completion.
Other people who control either device or the local network infrastructure may affect connectivity. Guest Wi-Fi, VPNs, managed networks and access-point isolation can prevent local transfer.
4. Permissions and system access
- Camera: requested only when you choose to scan a VeilSend QR code. Camera frames are used on the device for code recognition and are not retained by VeilSend.
- Network access: used to discover peers and exchange encrypted data on the local network. A current Android release may grant local-network access through standard network permission behavior; later Android versions may present a separate local-network prompt.
- Notifications: requested when needed to keep a user-started transfer visible in the background. Notifications show file count and overall progress, not filenames, paths or the peer's friendly name.
- Files and folders: Android's system file picker provides access only to files you select. The system folder picker can grant access to a custom receive folder. On Android 8–9, legacy storage permission may be requested when required to save to the default public Downloads location.
The app does not request access to contacts, SMS, call logs, accessibility services, precise or background location, device administration, VPN control, all-files management or account identity.
5. Transfer history and diagnostic logs
Transfer history is stored only on your device and may include time, direction, the peer's friendly label, filenames, file count, total size, per-file outcome and overall result. History does not contain file copies, session keys, QR payloads or full system paths. Deleting history does not delete completed files saved outside App storage.
Operational logs are minimized and intended to diagnose local failures. They do not intentionally include file contents, cryptographic keys, QR payloads, complete filesystem paths or long-lived device identifiers. VeilSend does not transmit diagnostic logs automatically. If support asks for details, you choose what to share by email and should remove sensitive information first.
6. Advertising and advertising data
VeilSend's free-service model is advertising-supported. Advertising-enabled distributions process advertising-related data for ad delivery, measurement, fraud prevention, frequency control and compliance. This data can include device or advertising identifiers, approximate location inferred from network information, IP address, app interactions, ad impressions and clicks, diagnostics, and consent or privacy choices. Advertising providers act under their own privacy terms and applicable law.
Current distribution status: VeilSend for Android version 1.0.0 contains no advertising SDK, displays no in-app advertising and performs no advertising tracking. It therefore does not collect or share advertising data through the app in this version. Any Play Console Data safety disclosure must match the exact distributed binary.
7. Retention and deletion
- Temporary session keys and identifiers are discarded when the session completes, is declined, is cancelled, expires or fails.
- Incomplete cache files are deleted when the task terminates; crash remnants are cleaned on the next launch. Incomplete SAF, MediaStore and legacy-storage targets are rolled back when their write or verification fails.
- Completed files remain in the selected receive location until you delete them through Android or a file manager.
- Transfer-history metadata is retained for 30 days by default. You can select 7 days, 30 days or manual retention, delete an individual record, or clear all history.
- Preferences remain until you change them, clear App data or uninstall.
- Support messages are retained only as long as reasonably necessary to answer the request, maintain support records, prevent abuse and meet legal obligations.
8. Security
VeilSend uses temporary session identities, authenticated key agreement, encrypted transfer frames and per-file length and SHA-256 integrity checks to protect local transfers. A failed identity or integrity check does not fall back to an unencrypted transfer. Completed files are committed only after verification, and name conflicts are resolved without overwriting the existing file. The current release has not undergone an independent security audit or two-device adversarial test.
No security method is absolute. Device compromise, malicious network infrastructure, operating-system defects, user-approved malicious files or physical access to an unlocked device can create risks. Friendly device names and selected filenames are shown to the participating transfer peer, so verify the receiver and transfer only with people you trust.
9. Children
VeilSend is a general-purpose utility and is not directed to children under 13 or the minimum digital-consent age in their jurisdiction. The app does not knowingly create profiles of children. A parent or guardian who believes a child has provided personal information through a support interaction may contact us to request deletion.
10. International and cross-border use
The core file transfer stays between the participating devices on their local network; VeilSend does not operate a cloud relay for it. Support email and advertising services in advertising-enabled distributions can be processed in countries other than your own and under the service provider's safeguards and applicable legal requirements. Version 1.0.0 contains no advertising SDK.
11. Your choices and control
You can decline an incoming request; cancel a transfer; revoke camera, notification, storage or folder access in Android settings; edit your friendly device name; change the receive folder; change history retention; delete history; clear app data; or uninstall the app. Because version 1.0.0 has no account or cloud profile, most application data is controlled directly on your device. Revoking access may prevent the related feature from working.
12. Changes to this Policy
We may revise this Policy to reflect product, legal or operational changes. The effective date at the top will be updated. A materially different app distribution must be accompanied by matching in-app, store-listing and Data safety disclosures.
13. Contact
For privacy or support questions, contact: Avasprings91@gmail.com