Privacy Policy
Last updated: September 2026
This policy explains what information is processed by NetEngine Receiver
for Android (package site.netengine.receiver) and by the
NetEngine service it connects to, including the NetEngine application for
Windows. The service is operated by NetEngine (“NetEngine”,
“we”, “us”).
NetEngine has no user accounts. You do not create a login, and we do not ask for your name, email address, phone number or payment details.
1. Information we process
Device and installation information
When the app first runs, it registers the installation with our server and we store:
- Installation identifier — a random identifier generated at first launch. It is not derived from your identity or from any hardware serial number.
- Device access token — a secret issued to your installation so it can authenticate. Only a hashed form (SHA-256) is stored on our server; we do not keep the token itself.
- Device code — the short numeric code the app displays, used to address transfers to your device. The app proposes this code by deriving digits from the Android device identifier (
ANDROID_ID) so that the same device keeps the same code; the server assigns a different code if the proposed one is already taken. The identifier itself is not sent to us or stored. - Device name — the device model name reported by Android (for example “Pixel 8”).
- Operating system and version, CPU architecture, and the NetEngine app version.
- Activity timestamps — when the installation first registered and when it was last seen, updated when the app contacts the server.
Network information
- IP address — the address your device connects from. It is stored with your installation record, and with transfer and download records, and is used only to operate the service, prevent abuse and investigate faults. We do not use it to determine your location.
- Our web server keeps standard request logs, as any web server does.
Transfer information
When a file or link is sent to your device code, we store a transfer record containing:
- the file name, size, content type and an integrity checksum (SHA-256);
- the destination device code;
- the IP address of the sending device;
- the optional short message the sender may attach;
- for link transfers, the web address (URL) the sender chose;
- status and timestamps (created, received).
Files held for delivery
For a file transfer, the file itself is stored on our server only long enough to deliver it to the destination device. We do not open, scan, index or analyse the contents of your files; they are processed only to compute the integrity checksum and to pass them on.
Download records
When a device downloads a file we publish through the service — for example a NetEngine application installer — we keep an operational record of which installation downloaded which file, the status, byte counts, timestamps and the IP address used. Downloads of a device-to-device transfer are recorded against the transfer itself rather than as a separate download record.
Information stored only on your device
Your device code, installation identifier, device token and your list of recently received files are stored locally on your phone. Received files are saved to your device’s Downloads (on Android 10 and newer) or to the app’s own folder. This local data is not sent to us beyond what is described above, and the app disables Android cloud backup of its data.
What we do not collect
- No advertising identifiers, analytics SDKs, crash-reporting SDKs or third-party trackers. The app contains no such libraries.
- No contacts, calendar, photos library, microphone, precise or approximate location, or browsing history.
- No name, email address, phone number or payment information.
2. How we use information
- To register your installation and authenticate it on later requests.
- To route a file or link to the device code it was addressed to, and to deliver it.
- To show you pending and received transfers, and to verify file integrity.
- To keep the service secure, prevent abuse and enforce rate limits.
- To diagnose technical faults and keep the service running.
We do not use your information for advertising or marketing, and we do not profile you.
3. How transfers work
Every installation is given a short numeric device code. Transfers are addressed using that code alone.
- There is no pairing step. NetEngine does not have a pairing handshake and no accept or decline prompt: anyone who knows your device code can send a file, a link and a short message to your device, and it will appear in your incoming list until you choose to download it or it expires. Nothing is downloaded to your device unless you tap Download.
- Any registered NetEngine installation can look up a device code, and doing so returns only that device’s name, operating system and whether it is currently online — so a person who already has your code can confirm it before sending. There is no public directory, feed, chat, profile or search, and no way to browse other users or discover codes.
- File transfers pass through our server, which holds the file only until it is delivered.
-
Link transfers do not pass through our server at all. The sender supplies a web
address, and we store only that address in the transfer record. Only
https://links are accepted.
4. Sharing and third parties
We do not sell or rent your information, and we do not share it for advertising.
- Link transfers connect you directly to someone else’s website. If you choose to download a transferred link, your device connects straight to the web address the sender chose. NetEngine does not fetch that file and is not involved in that connection. The operator of that website will see your request as an ordinary visit — including your IP address, and the usual information a browser or app sends — and their own privacy policy applies, not ours. Only download links from senders you trust.
- Devices you transfer with. The device you send to, or receive from, is shown your device name and device code as part of the transfer.
- Infrastructure. The service runs on hosting and network infrastructure operated by third-party providers, which necessarily process traffic in order to deliver it.
- We may disclose information where we are legally required to, or where it is necessary to investigate abuse of the service.
5. App updates and installing received apps
The version of NetEngine Receiver distributed on Google Play is updated only through Google Play.
The app requests Android’s REQUEST_INSTALL_PACKAGES permission for one purpose:
so that if someone sends you an Android app file (.apk) as a transfer, you can choose
to install it. Nothing is ever installed automatically — you tap to download, and Android then
shows its own installation confirmation. Transferred links are never treated as apps;
they are saved and opened as ordinary files.
6. Data security
- All communication between the app and our servers uses HTTPS (TLS), and link transfers are restricted to
https://addresses. - Device access tokens are stored only as a SHA-256 hash, never in plain form.
- Transferred files are checksum-verified (SHA-256) on your device before you open them.
- Stored files are not publicly browsable; delivery requires an authenticated request from the destination device.
- Administrative access to service data is restricted, authenticated and logged.
No online service can be guaranteed completely secure, and we cannot promise absolute security — but we aim to apply appropriate safeguards and to correct problems promptly.
7. How long we keep information
Different information is kept for different periods:
| Information | Retention |
|---|---|
| File contents awaiting delivery | Deleted as soon as the destination device confirms receipt, or if the sender cancels. Any file still undelivered is deleted when the transfer expires, 7 days after it was created. |
| File contents after delivery | Deleted on receipt. A periodic clean-up also removes the file contents of any delivered transfer. |
| Transfer record (file name, optional message, destination code, sender IP, link address) | Kept for up to 7 days from creation — including after the file has been received — and then permanently deleted automatically. |
| Installation/device record and download records | No automatic expiry. These are kept while the installation exists and until they are deleted on request (see below). |
| Server request logs | Kept for a limited period for security and troubleshooting, subject to normal server log rotation. |
We want to be precise here: deleting a transfer’s file contents and deleting its record are two different things. The file contents go as soon as the transfer is received; the record describing it remains for up to 7 days before it is removed.
8. Your choices, and deleting your data
Because NetEngine has no accounts, there is no account to delete — but the data tied to your installation can be deleted on request.
- Uninstalling the app removes the app’s local data from your device. It does not by itself remove your installation record from our server.
- To request deletion, email anoman003@gmail.com from any address and include the numeric device code shown on the app’s main screen. That is the identifier you can actually see; please do not send us anything else you are not comfortable sharing. We may ask one or two questions to confirm the request genuinely relates to your device before we act on it.
- Deletion removes the installation record, its transfer records and any files still held for it, and its download records. We currently handle these requests manually; there is no in-app delete button.
You may also ask us what information is held about your installation, or ask us to correct it, by writing to the same address.
9. Children
NetEngine Receiver is a general-purpose file-transfer utility intended for users aged 13 and over. It is not directed at or designed for children, and it is not enrolled in Google Play’s Designed for Families programme. We do not knowingly collect information from children. If you believe a child has used the service and you would like the associated data removed, contact us and we will delete it.
10. Changes to this policy
We may update this policy as the service changes. The date at the top of the page shows when it was last revised, and material changes will be reflected there. Continuing to use NetEngine after an update means the revised policy applies.
11. Contact
For privacy questions, data-access requests and deletion requests, contact the NetEngine developer at anoman003@gmail.com. This is the same contact address published on the app’s Google Play listing, and it is the fastest way to reach us — please use it in preference to any other address.
Application: NetEngine Receiver (site.netengine.receiver)
Service and publisher: NetEngine