Mouse control
Click, right-click, drag, and scroll with precise pointer control.
Cross-platform · Secure · Low latency
Control your computer with your phone
Turn your phone into a wireless mouse, trackpad, and keyboard for Windows and Mac computers.
Windows 10+ · macOS 12+ · iOS (coming soon)
Everything you need
Five core capabilities for couch, desk, and presentation use.
Trackpad experience
Multi-touch gestures and smooth pointer movement mapped to your desktop.
Keyboard input
Efficient typing with modifiers and shortcuts when you need them.
Low latency
Local network connection designed for real-time response on the same Wi‑Fi.
Secure & reliable
WSS encryption on your LAN. No cloud relay required for everyday control.
Connect in three steps
Desktop receivers are available now. The iOS app is not yet publicly released; Android is not available.
Mobile apps: iOS and Android are listed as coming soon. Pairing steps below describe the intended flow once the phone app is available.
-
1
Install AirsPad on your computer
Download the Windows or macOS receiver and run it on the PC you want to control.
-
2
Open the phone app and scan the QR code
When the mobile app is available, open AirsPad on your phone and scan the QR code shown on the desktop receiver.
-
3
Enter the pairing code
Confirm with the on-screen pairing code to establish a local WSS session, then use mouse, trackpad, and keyboard modes.
Try AirsPad now
Cross-platform wireless control. Desktop receivers are ready; mobile store releases are coming.
Windows
64-bit · Windows 10/11
AirsPad-Windows-v1.0.0-x64.exe
DownloadmacOS
Apple Silicon & Intel · macOS 12+
Developer preview — not Developer ID signed and not notarized. Gatekeeper may block this build. Do not disable system security to install it.
AirsPad-macOS-v1.0.0.zip
DownloadiOS Coming soon
App Store
Android Coming soon
Google Play
Quick guide
- Keep your phone and computer on the same Wi‑Fi / LAN for best latency. AirsPad does not provide public internet remote control.
- First launch on Windows or macOS: allow AirsPad through the firewall so the local WSS receiver can accept connections.
- Pairing uses a QR code and a short pairing code shown on the desktop app. After pairing, the phone authenticates with a stored token over WSS.
- Use trackpad or mouse mode for pointer control; switch to keyboard mode for typing. Multi-touch gestures are supported in the phone app.
- The iOS app is not yet publicly available in the App Store. Android is not released. Do not expect a store download for mobile today.
- macOS builds are developer preview only (unsigned / not notarized). Prefer the Windows package for a production-ready desktop install.
- If the computer sleeps, changes network, or the certificate pin changes, reconnect and re-pair from the phone app when available.
Changelog
Verified release notes from the current desktop packages.
Public desktop receivers for Windows (self-contained) and macOS (developer preview). Local WSS pairing with QR code and pairing code, mouse / trackpad / keyboard control over LAN.
Privacy policy
This policy describes how AirsPad handles data based on the current product source code and the public website as of the last update. It is not legal advice. Items that could not be verified are marked clearly.
1. Product and services
AirsPad is software that lets a phone control a Windows or Mac computer over the local network using encrypted WebSocket (WSS) sessions. The public website at airspad.com provides product information and desktop downloads. There is no cloud relay in the current product code for everyday control.
2. Data types we process
Depending on platform, AirsPad may process: device display name (iOS reads UIDevice name for pairing messages); locally generated device or host identifiers; LAN IP addresses used to form wss:// connection URLs and QR codes; pairing codes (short-lived); authentication tokens; TLS certificate / SPKI pinning material; lists of paired devices; user settings such as language and whether remote shutdown is allowed; and live pointer / keyboard / gesture events while a session is active.
3. Purposes of processing
Data is used to discover and connect devices on your LAN, complete pairing and authentication, encrypt the local session, apply input events on the computer, optionally allow remote shutdown when enabled, and remember language preference on the website.
4. Local network communication
Control traffic is sent between your phone and your computer on the local network. Input events are streamed for real-time control. AirsPad is not designed as a public-internet remote desktop service in the current codebase.
5. Pairing and authentication
First pairing uses an on-screen pairing code (and QR metadata). After pairing, the phone stores an auth token associated with that computer. Desktop receivers store token hashes (not plaintext tokens) for paired devices. Sessions use WSS with certificate pinning based on the receiver’s local TLS identity.
6. Local storage
iOS: device id, device name cache, auth tokens, SPKI pins, and saved endpoints are stored in app UserDefaults (not Keychain in the current iOS code). Windows: settings, DPAPI-protected device list and TLS identity under %LocalAppData%\AirPad, plus optional local log files. macOS: Application Support data including devices.json and TLS material; the TLS private key is stored in the Keychain. Website: language preference in localStorage (key airspad-locale). The website does not set first-party tracking cookies in the current source.
7. Website processing
Visiting airspad.com may cause the hosting provider or CDN to record standard HTTP access logs (IP address, user agent, requested URL, time). Exact log retention on the production host is outside this repository and is listed as not fully verified. Downloads are served as static files from the same site.
8. Third-party services
Current audited app and website source code do not include analytics SDKs, crash-reporting SDKs, advertising SDKs, or third-party tracking scripts. No Google Fonts or external marketing tags are loaded by the site source. App Store / Play / OS crash reports, if any, are outside AirsPad’s own code.
9. What we do not do (based on current code)
We do not operate a cloud control relay in the current product. We do not find evidence of uploading keystroke or mouse logs to AirsPad servers. We do not sell personal data. Input events are not persisted as a keystroke history in the app; they are applied live.
10. Remote shutdown
Desktop apps include an optional remote shutdown feature (can be disabled in settings) that requires an explicit prepare/confirm challenge from the phone. This can power off the computer when enabled.
11. Retention and deletion
Local pairing data remains until you remove paired devices or uninstall / clear app data. Website language preference remains until you clear site data. Hosting access logs, if any, follow the host’s retention policy (not verified here).
12. Controls you can use
Use the same Wi‑Fi only with devices you trust; remove paired devices in the apps; disable remote shutdown; uninstall apps to remove local stores; clear browser localStorage for language preference; and review firewall rules for the desktop receiver.
13. Security and limitations
LAN WSS encryption and pinning reduce exposure on the local network, but no product can claim absolute security. iOS currently stores tokens in UserDefaults rather than Keychain. macOS packages on the website are developer preview (unsigned / not notarized). Do not disable OS security features to install preview builds.
14. Policy updates
We may update this page when product behavior changes. The date of the website deployment reflects the latest published text.
15. Contact (pending confirmation)
A verified public operator contact email, company legal name, and registered address have not been confirmed in the project materials. Until those details are confirmed, please treat any previously shown placeholder addresses as unverified. This section will be updated when a real contact channel is provided.