Privacy policy
The apps collect no personal data. There is no account, no analytics of what you do in the app and no advertising. Your files go from one device of yours to another device of yours, over your local network, without passing through any system of ours.
There are two exceptions. Buying the computer licence needs an email to send you the key and a payment to process: see If you buy the computer licence. And, in the phone apps, the phone-to-phone purchase and the 10-day trial go through the device's store, RevenueCat and our server, with identifiers drawn by the app or taken from the device, and no name or email: see The phone-to-phone purchase.
Who is responsible
Airdroidfy is developed and maintained by Meigston Serviços Tech. For any privacy matter, contact support@airdroidfy.com.
What is not collected
Never, under any circumstance, do we collect, receive or have access to: your files, the contents of your screen, the picture from your camera, what you type, your location, your contacts, your calendar, advertising identifiers or usage history. We use no usage-analytics, attribution or crash-reporting tools in any of the apps. The only third-party SDK in the phone apps is RevenueCat's, which handles the phone-to-phone purchase and, from its details, builds the sales reports we see in its dashboard.
There is no infrastructure for it: the transfer is peer to peer. The two devices talk directly over the local network, and no system of ours sits in the path for anything to be sent to. Not even the licence server sees that traffic: what reaches it is only what is described below, and never a file, a screen, a touch or what you copy.
What stays on your device
Everything below lives in the app's private storage, on the device itself. On Android, uninstalling the app or clearing its data erases all of it. On iPhone, iPad and Mac, what goes into the Keychain may stay on the device after uninstalling, as is usual on those systems.
| What | Why |
|---|---|
| The device's private key and certificate | To identify this device over TLS. Generated on the device, and the private key never leaves it — only the public part of the certificate is seen by the peer and, for the phone-to-phone purchase, by our server. |
| List of 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. Stores name, size and date — never 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. |
| Display choices (on the Mac) | For each tablet used as a display: the mode, the position, whether it starts on its own when the cable goes in, and the USB serial number that links that cable to the paired tablet. Forget this cable, in the app's Settings on the Mac, erases the serial number and the "starts on its own" choice; forgetting the tablet (Forget, in the same Settings) also erases the mode and the position. |
| 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. |
What travels between your devices
The files you send, the mirroring video while a session lasts, the camera picture while you are using it as the Mac's webcam, the display picture and the touches on the tablet or the iPad while it is the Mac's or the PC's display, what you copy when you send the clipboard and, when remote control is active, the coordinates of taps and the text you type on the computer. All of it is encrypted with TLS 1.3, straight from one device to the other — over the local network or, for the display, over the USB cable too — and none of it is recorded by us anywhere.
Between two phones, 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, whether the device is Android or iOS, whether it is a purchase or a trial, when it was issued and until when it is valid: no name, email or order number.
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. That announcement is visible to anyone on the same network, as with any printer or local network service.
Permissions the app asks for, and why
The table below is Android's. The full list, with iPhone's and iPad's and those for Bluetooth and Connect without Wi-Fi, is in the phone apps privacy policy, the one they open from Settings.
| 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 — in that use the image is not stored and never leaves the device. And, only when you accept the Mac's request, to act as its webcam: while it lasts, the camera picture goes to the paired Mac, over the local network, and is not recorded. Video only — the app does not use the microphone. |
| Network and Wi-Fi | To find your devices on the local network and open the connection. Over the network, the app refuses to connect outside a private network. The display's USB cable is not a network: over it the connection goes straight to the Mac at the other end, with the same encryption and the same certificate check. |
| 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. Without it, Android suspends the process in the middle of a transfer. |
| Screen capture | To mirror the screen on the Mac. Android asks for your confirmation on its own, every session, and the app cannot skip that prompt. |
| USB accessory | To use the tablet as a display for the Mac by cable. When the Mac presents itself as the Airdroidfy Screen accessory, Android asks whether the app may open. The app talks only to that accessory, and only shows the picture for a paired Mac. |
| Accessibility | To perform on this device the taps and typing you make from the computer. See the section below. |
Accessibility service
Airdroidfy for Android lets the computer tap and type on the Android device during mirroring. It uses Android's accessibility service for that, which is the only API the system offers for reproducing touches.
In it:
- The service does not read your screen contents. It is declared without content-reading permission and receives only the notification of which field has focus, so it knows whether it may type. Nothing written on the screen is read, stored or transmitted.
- It acts only during a mirroring session you authorised, and stops the moment that session ends.
- It works only on the local network. The connection is refused if the other side is not on the same private network — this is a check on the socket itself, not a configuration option.
- Every gesture originates from an action of yours on the computer. The app does not decide, plan or perform anything on its own.
- Before sending you to Android's Settings, the app shows a screen explaining all of this and requires you to tick the authorisation. No data from this feature is collected, stored off the device or shared with third parties.
You can turn the service off at any time in Android's Settings, and control stops immediately.
Your tablet or iPad as a display
When you use an Android tablet (or phone) as a display for the Mac — Airdroidfy Screen —, the two devices exchange only what that needs:
- From the Mac to the tablet, the picture. When extending, only what is on the tablet's display; when mirroring, the Mac's main screen. It is shown and discarded: neither the Mac, nor the tablet, nor we record the video.
- From the tablet to the Mac, the touches. The position of your finger or pen, to move the pointer, click and scroll. Nothing on the tablet's screen is read.
- Screen Recording, on the Mac. It is the macOS permission that lets the app capture the picture that goes to the tablet. It is used only while the display is on, and the picture only goes to the paired tablet.
- Accessibility, on the Mac. It is the permission that turns the tablet's touches into clicks and pointer movement. It only applies during a session you accepted and with the Mac unlocked, and the Touching the tablet controls the Mac setting turns it off.
- USB accessory. By cable, the Mac presents itself to Android as an accessory. The connection running over it is the same encrypted, certificate-checked one the two use over the network. Always on this tablet covers only the paired tablet on that cable; any other device gets the question.
- No thumbnail in Recents. Android keeps no image of the Mac's screen in the tablet's recent apps list.
- Diagnostics only when you ask. On the Mac, Export display diagnostics saves a text file on the device itself, with performance figures and the state of the permissions — no image of the screen at all. It only reaches us if you send it.
On a Windows PC, with an Android tablet or an iPad, the same applies: the picture goes from the PC to the display and the touches come back, straight between the two, and nothing is recorded. By cable, the iPad talks to the PC through Apple's device service installed on the PC (the Apple Devices app), and the connection running over it is the same encrypted, certificate-checked one. The virtual display Airdroidfy creates on Windows is a driver installed on the PC itself, with your permission.
If you buy the computer licence
The Mac and Windows apps have a three-day trial and then ask for a lifetime licence, paid once, on the website. With the computer, the phone apps buy and check nothing: the computer is the one that checks the licence. It is worth being specific about what the licence involves.
| What | Where it lives | Why |
|---|---|---|
| Your email | On our licence server, and at Stripe | To send you the key, and to send it again if you lose it. It is also how you prove the licence is yours, in My devices and to support. |
| Card details | At Stripe only. They never reach us. | To charge you. Payment happens on Stripe's own page; we receive only a "paid" notice and the transaction and customer identifiers at Stripe. |
| A fingerprint of the key | On our licence server | To check a key without storing it. We keep the hash, not the key — someone who breached the database would not walk away with usable licences. |
| One public key per installation | On our licence server | To know how many computers the licence was activated on. It is a key the app generates itself, not an identifier of your computer: it says nothing about the model, the name or the serial number of the machine. |
| The licence's computers | On our licence server | To show in My devices where the licence is active: the name the computer has in the system (such as "Ana's MacBook"), whether it is a Mac or Windows and when it last checked the licence. Alongside goes an opaque identifier of the computer — a cryptographic digest that does not reveal the serial number —, to recognise the same computer when the app is reinstalled, without using up a swap. |
| Purchase and activation dates | On our licence server | To apply the activation and swap limits and to answer a support request. |
The computer apps do not talk to our server day to day. They talk at activation, and work offline after that: what they keep is a certificate signed by us, which they verify on their own without internet. Every so often they revalidate in the background — and if they cannot, they keep working. No check can switch the app off because your network went down. They also fetch updates and each version's what's new from airdroidfy.com, like any visit to the website.
In My devices, you see and free up the licence's computers with the purchase email and the key. Nothing is kept in the browser, and the attempt limit lives only in the server's memory.
We keep that record for as long as the licence exists, because it is what lets us reissue the key to you. If you want it deleted, ask at support@airdroidfy.com: we delete it, and the licence can no longer be activated on another computer.
The phone-to-phone purchase
Between two phones or tablets, sending files, dragging and the clipboard need one of the two to have the phone-to-phone purchase, made inside the app through the device's store (Google Play or the App Store), or the 10-day trial. It is a separate purchase from the computer licence. It has no account and no email: the app draws an identifier for the store, and the purchase is known only by it, and by the device.
| Who | What they receive |
|---|---|
| Google Play or the App Store | The payment, through your store account. We never see the card or the account. |
| RevenueCat, which handles the purchase for us | The identifier drawn by the app and the purchase details the store confirms, which it also uses for the sales reports we see in its dashboard. |
| Google (on Android) or Apple (on iPhone and iPad) | Only when the trial starts: Google Play's integrity check, or Apple's DeviceCheck, which marks that the device has already started the trial. |
| Our licence server | The public part of the installation key and of the device certificate, a digest of a device identifier and, when the purchase is linked, the drawn identifier and the device model. It keeps the purchase (the store order number, the date and the drawn identifier), the devices that used it and each device's trial, for as long as the service exists, and issues the pass one phone shows the other. |
The detail — what goes in each request, when the app uses the internet and how to ask for deletion — is in the phone apps privacy policy.
The website
airdroidfy.com has no visitor analytics and no advertising. It sets a single
cookie, idioma, to remember whether you chose Portuguese or
English. Like any web server, ours writes each request to its access log:
the IP address, the date and time, the page requested and the browser's
identification. 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.
Sharing with third parties
We do not sell, rent or hand over any data for anyone to use on their own account. These services handle your data on our behalf:
- Stripe — processes the payment for the computer licence. They are the ones who see the card details; we do not.
- Resend — delivers the email with the licence key, and receives the messages sent to support@airdroidfy.com, which are forwarded to the support mailbox, on Gmail.
- RevenueCat — checks the phone-to-phone purchase with the store and builds the reports on those sales.
- Google and Apple — through the stores, Google Play's integrity check and DeviceCheck, only for the phone-to-phone purchase and trial.
Each one has its own privacy policy. Beyond that, the obvious exceptions are services you choose to use separately: if you download the app from the App Store or Google Play, those companies see the download under their own policies.
Children
Airdroidfy is not directed at children under 13 and does not knowingly collect data from children. The purchases assume someone able to enter into a contract. If you notice that a child's data reached us, write to support@airdroidfy.com and we will delete it.
Your rights
GDPR, Brazil's LGPD and similar laws give you rights of access, correction and deletion of your personal data. For everything the apps keep, those rights are exercised on the device itself: what exists is there.
If you bought the computer licence, or used the phone-to-phone purchase or trial, a record of ours exists, described above. Write to support@airdroidfy.com and we will show you what is there, correct it or delete it. Deleting the computer licence removes the ability to activate it on another computer. Deleting the record of the phone-to-phone purchase does not cancel it: it stays on your store account, and the record comes back if a device of yours links the purchase again.
Changes to this policy
If anything changes, the date at the top changes with it and the previous version stays in the project's public history. If a change affects the accessibility service, the app asks for your consent again before continuing.