Airdroidfy apps privacy policy
No account, no ads, no analytics of what you do in the app. The app does not ask for your name, email or phone number, and it has no usage-analytics, advertising, attribution or crash-reporting SDK. RevenueCat uses the phone-to-phone purchase details in the sales reports it shows us.
What is yours goes straight between your devices. Files, the screen, the camera, what you copy and your touches go from one device of yours to another over the local network or the cable, encrypted, and never pass through a server of ours.
The app only talks to our server for the phone-to-phone purchase, the 10-day trial and checking the time. For the purchase and the trial, it also talks to the device's store (Google Play or the App Store) and to RevenueCat. It carries identifiers drawn by the app or taken from the device, and never your name or your email. On Android, the pairing QR reader (ML Kit, by Google) sends Google technical operating data, never the camera picture or what the code says. It is all in The phone-to-phone purchase and the trial and in When the app uses the internet.
Who is responsible
The Airdroidfy apps are developed and maintained by Meigston Serviços Tech. For any privacy matter, write to support@airdroidfy.com.
What is never collected
We never receive or have access to: your files, the contents of your screen, the camera picture, what you copy or type, your notifications, your location, your contacts, your calendar, an advertising identifier or usage history. The third-party SDKs inside the app are RevenueCat's, which handles the phone-to-phone purchase, and, on Android only, Google Play's integrity library, used only to start the trial, and Google's ML Kit, which reads the pairing QR code on the device itself.
What stays on the device
Everything below lives in the app's private storage, on the device itself.
| What | Why |
|---|---|
| The device's private key and certificate | To identify this device on the encrypted connection. They are generated here, and the private key never leaves: only the public part of the certificate is seen by the paired device and, if you use the phone-to-phone purchase or trial, by our server. |
| Paired devices | To recognise your devices next time: the name, identifier and certificate fingerprint of each one. |
| Transfer history | To show what was sent and received: name, size and date, never the contents. You can clear it whenever you want. |
| Accessibility consent record | The date you authorised remote control and the version of the text you read. |
| The phone-to-phone purchase | The installation key (drawn by the app), the identifier drawn for the store, the pass, the trial's state and the latest time the app has seen. They live in an encrypted vault of the app on Android, or in this device's own Keychain on iPhone and iPad, and do not move to another device through a backup. |
On Android, uninstalling the app or clearing its data erases all of this. On iPhone and iPad, what is in the Keychain (the device certificate and the purchase state) may stay on the device after uninstalling, as is usual on iOS, and applies again if the app is installed again.
What goes straight between your devices
The files you send; the mirroring video, while it lasts; the camera picture, while you use it as a webcam; the picture and the touches, while the tablet or the iPad is a display; what you copy, when you send the clipboard; the notifications, if you turn on mirroring them; and, with remote control on, the taps and the text that reach the Android device. All of it is encrypted with TLS 1.3, straight from one device to the other, over the local network or the cable, and none of it is recorded by us anywhere.
The app announces on the local network the device name, an identifier and the certificate fingerprint: the minimum for your other device to find it and verify that it is the right one. Anyone on the same network can see that announcement, as they can see a printer's.
Between two phones, the pass. When one of the two has the purchase or the trial, it sends the other, over the same encrypted connection, a pass signed by our server. The pass says the device's identifier (a digest of its public certificate), an identifier of the activation on our server (the one it gave this device in the purchase, or the one for its trial), whether the device is Android or iOS, whether it is a purchase or a trial, when the pass was issued and until when it is valid, plus the pass version and which of our keys signed it. It carries no name, email or order number. The other phone uses it only on that connection, to know that one of the two is entitled, and does not keep it.
With the iPhone app closed. Only if you turn on Receive from phones with the app closed, in the iPhone's Settings: the paired phone that has something to deliver announces a fixed Airdroidfy code over Bluetooth, the iPhone proves with the pairing key that it is the right peer and receives, encrypted, the address to fetch the delivery over the network. The file then goes over Wi-Fi, on the usual encrypted connection.
The phone-to-phone purchase and the trial
Between two phones or tablets, sending files, dragging and the clipboard need one of the two to have the phone-to-phone purchase, made in the device's store, or the 10-day trial. The purchase, the trial and the time check (in When the app uses the internet) are the only parts of the app that talk to our server. For the purchase and the trial, these are the parties involved:
| Who | What they receive | What for |
|---|---|---|
| Google Play or the App Store | The payment, through your store account. We never see the card or the account. | To charge, send the receipt and restore the purchase on the devices of the same store account. |
| RevenueCat, which handles the purchase for us | An identifier drawn by the app (with nothing of yours in it) and the purchase details the store confirms: the product, the date, the order number, the country and the currency. Its SDK also carries the technical details of any request, such as the app and system versions. | To check the purchase with the store and tell the app and our server that it exists. From the same details, it builds the sales reports we see in its dashboard. |
| Google, on Android only | Google Play's integrity check request, when the trial starts. | To check that the request comes from the Play app on a device that passes basic integrity, so the trial does not start over for nothing. |
| Apple, on iPhone and iPad only | A temporary DeviceCheck token, when the trial starts. | To mark, in the two bits Apple keeps per device, that this device has already started the trial. The mark stays even if the app is deleted. |
| Our server | The public part of the installation key and of the device certificate, with the signatures that prove they belong to this device; a digest of a device identifier; and, depending on the request, the identifier drawn for the store, the device model (such as “SM-X510” or “iPhone16,1”) and the Google or Apple check token. | To check the purchase with RevenueCat, count the trial per device and issue the pass one phone shows the other. |
The digest of the device identifier is worked out on the device itself: on Android, from the identifier Android gives the app (the ANDROID_ID); on iPhone and iPad, from a number drawn by the app and kept only in the Keychain. Only the digest leaves, and the identifier cannot be worked back from it.
What our server keeps
| What | When |
|---|---|
| The purchase: the store order number, the date, whether it is a store test purchase and the drawn identifier that holds it now | When a device links the purchase to itself, after buying or restoring, or when RevenueCat reports a purchase, a refund or a transfer |
| Each device that used the purchase: its identifier (the certificate digest), the installation's public key, the digest of the device identifier, the model, whether it is Android or iOS, and the dates it joined, got its last pass and left | When the device links the purchase or renews the pass |
| The trial: the digest of the device identifier, whether it is Android or iOS, its start and end, the public key of the first and the latest installation, the device identifier and how it was checked | When the trial starts on this device |
| RevenueCat's notices: the notice identifier, its type and the drawn identifier | On each purchase, refund or transfer notice |
This is kept for as long as the service exists: it is what lets you restore the purchase, applies each purchase's device limit and stops the trial from starting over when the app is reinstalled. The server does not keep the device certificate, only the identifier worked out from it, and does not keep the Google or Apple check token, only that the device passed.
The IP address of each request is used to limit attempts, and that limit lives only in the server's memory. Like any web server, ours also writes each request to its access log: the IP address, the date and time, the address requested and the identification the device's system sends along. These records are deleted within 30 days: the server's file keeps 15 days, and the copy we use to watch the server for errors and slowness keeps 30.
The service also writes an operations log, and some of its lines carry purchase and trial details: the purchase's internal identifier, when it is recorded, changes state (on a refund, for instance) or hits the device limit; the store order number, when it is recorded and when it hits the limit; the activation identifier, when a device joins the purchase; the identifier of each RevenueCat notice; and, when a trial starts, whether the device is Android or iOS and the first 8 characters of the device identifier digest. This log is limited in size, not in days: the oldest records are deleted as new ones come in.
When the app uses the internet
- When you use the purchase or the trial: when you open the purchase sheet, buy, restore or start the trial. That is when RevenueCat's SDK starts for the first time, and from then on it also starts when the app opens. On iPhone and iPad it also starts on its own when the App Store already shows the purchase on your Apple Account, as on an iPad with the same Apple Account.
- To renew the pass of a device with the purchase or the trial: when the app opens, when it connects to another phone and, on Android, when the network comes back. The purchase pass is renewed every 7 days, and sooner in the first days after buying.
- To set the time right: if the device's clock goes back more than 5 minutes behind the latest time the app has seen, the app asks our server for the time until it gets an answer, and after that at most once an hour, even with no purchase and no trial. That request carries the same device identification details and, with no purchase and no trial, the server only reads it: it records nothing beyond the access log.
- On Android, when you use the QR reader: ML Kit, Google's library that reads the pairing QR code on the device itself, sends Google, over HTTPS, technical operating data: the device's maker, model and system, the app's name and version, performance measurements, error codes and a per-installation identifier that does not identify you or the device. Never the camera picture or what the code says. Google uses this data for the library's diagnostics and usage statistics, as the ML Kit documentation says. None of it goes through us.
Without the internet, the app keeps working over the local network, and a pass that has already arrived is valid until its date. Buying, restoring and starting the trial need the internet.
Deleting
To delete what the server kept about a purchase, write to support@airdroidfy.com with the order number the store sent on the receipt. Deleting does not cancel the purchase: it stays on your store account, and the record comes back if a device of yours links the purchase again. The operations log lines with the order number are not deleted one by one: they go away on their own as the log turns over. The trial record has nothing that lets us find you or your device without the device itself: it is the digest of a device identifier. If you want it gone anyway, write and we will work out how to find it. The payment and the receipt stay with the store, under its policy.
Permissions the app asks for, and why
On Android
| Permission | Why |
|---|---|
| Photos, video and audio | To list your files so you can choose what to send, and to write what arrives. Only what you select is read. |
| Camera | To read the pairing QR code, without storing the image. And, only when you accept the request, to act as a webcam: the picture goes to the paired device, over the local network, while it lasts. Video only: the app does not use the microphone. |
| Network, Wi-Fi and nearby Wi-Fi devices | To find your devices on the local network and connect. In Connect without Wi-Fi, to open a network just between the two devices. The app does not use Wi-Fi to work out where you are. |
| Internet | The phone-to-phone purchase, the trial and the time check, above. Your files do not go over the internet. |
| Bluetooth (nearby devices) | Only to call a paired iPhone whose app is closed and that has delivery with the app closed turned on: the announcement lasts while there is something to deliver and the app is open. The app does not scan for devices over Bluetooth. |
| Notifications | To announce an incoming file, its progress and a mirroring request and, during the phone-to-phone trial, to remind you once a day how many days are left. |
| Foreground service | To keep the connection alive with the app closed, always with the notification in view. Without it, Android suspends the app in the middle of a transfer. |
| Screen capture | To mirror the screen. Android asks for your confirmation every session. |
| Display over other apps | To show the glow of an incoming drag over whatever app is on screen. Only if you turn it on yourself; without it, the notification remains. |
| Notification access | To show Android's notifications on the paired device, only if you turn it on in Android Settings. |
| USB accessory | To use the tablet as a display by cable. The app only talks to the Airdroidfy Screen accessory, and only opens the picture of a paired device. |
| Accessibility | To perform on this device the taps and typing of remote control. See the section below. |
On iPhone and iPad
| Permission | Why |
|---|---|
| Local network | To find your devices and connect directly to them: to transfer files and, on iPad, to work as a display. Files and the screen never leave your network. |
| Camera | To read the pairing QR code. No image is stored or leaves the device. |
| Photos | To show your recent photos so you can take them to another device, and to save to Photos what arrived when you tap Save to Photos. Only what you send or drag leaves. |
| Notifications | To announce a file that arrived and, during the phone-to-phone trial, to remind you once a day how many days are left. |
| Bluetooth | Only with Receive from phones with the app closed turned on: a paired phone uses it to say it has something to deliver. |
Accessibility service, on Android
Remote control lets another paired device tap and type on the Android device while mirroring. For that the app uses Android's accessibility service, the only system API for reproducing taps.
- The service does not read the contents of your screen. It is declared without permission to retrieve window content and only gets told which field has focus, to know whether it can type.
- It only acts during a mirroring session you have authorised, and stops when it ends.
- It only works on the local network: the connection is refused outside a private network.
- Every gesture comes from an action of yours on the other device. The app decides and performs nothing on its own.
- Before taking you to Settings, the app shows a screen that explains this and asks for your authorisation. Nothing from this feature is collected, stored off the device or shared.
You can turn the service off whenever you like, in Android Settings, and control stops at once.
Who data is shared with
We do not sell, rent or hand over any data for anyone to use on their own account. These process data on our behalf, only for the phone-to-phone purchase and trial, and, on Android, Google receives the QR reader's technical data:
- RevenueCat, which checks the purchase with the store and builds the reports on those sales (its policy);
- Google, through Google Play, the integrity check and the QR reader's ML Kit, on Android (its policy);
- Apple, through the App Store and DeviceCheck, on iPhone and iPad (its policy).
Children
Airdroidfy is not made for children under 13 and does not knowingly collect children's data. If you notice that something from a child has reached us, write to support@airdroidfy.com and we will delete it.
Your rights
The LGPD, the GDPR and similar laws give you the right to access, correct and delete your data. What the app keeps is on the device itself. What our server keeps about the purchase and the trial is described above, and you can ask to see, correct or delete it at support@airdroidfy.com.
Changes to this policy
If anything changes, the date at the top changes with it, and the previous version stays in the project's history. If the change affects the accessibility service, the app asks for your consent again before carrying on.