PRIVACY
POLICY

At TimXSoft, we engineered Mouse Keyboard around a single non-negotiable principle: your data is your property. In a landscape saturated with surveillance capitalism and cloud data harvesting, we built our entire remote control ecosystem to function without a single byte of user data ever leaving your local network.

This document is not just a legal requirement—it is a technical blueprint of our privacy commitments. By using any component of the Mouse Keyboard ecosystem (Mobile Controller, Android TV Server, or Desktop Server), you are entering an architecture where privacy is not an optional setting. It is the system.

Mouse Keyboard is a Local Network Protocol (LNP) application. We do not operate any cloud infrastructure, relay servers, or data aggregation pipelines. When you move your finger across the touchpad or type a password via the virtual keyboard, that data travels exclusively via your private Wi-Fi or LAN—it never touches the public internet.

As a direct consequence of this architecture:

• No Account Required: We never request your name, email, phone number, or any personally identifying information. You are a permanent anonymous user of your own local hardware.
• No Keylogging: Keystrokes entered via the remote keyboard are raw HID events transmitted to your local server. They are never logged, buffered, or recorded by any component of our stack.
• No Behavioral Analytics: We do not track how often you use the app, which modes you prefer, or what apps you control. This data simply does not exist in our system.
• No External Storage: Your pairing history, network configuration, and control patterns are stored only in your device's local storage, under your full control.

The Mouse Keyboard application requires specific sensitive permissions to function. Below is a detailed, transparent disclosure of how and why these permissions are used, as required by Google Play Developer policies.

A. Camera Access (android.permission.CAMERA)

Strict Use Case: The camera is used exclusively to scan the QR code displayed on the Server application to establish a secure local connection.
Data Handling: Camera access is only active while the scanner is open. We do not take photos, record videos, or capture image data. The visual stream is processed locally on-device to decode the QR text and then immediately discarded. No image data is ever stored on your device or transmitted over any network.

B. Location & Bluetooth (android.permission.ACCESS_FINE_LOCATION)

Strict Use Case: On certain Android versions, the application requires location permissions to perform Bluetooth and Wi-Fi scans to discover nearby servers.
Data Handling: This app does NOT track your physical location, record your GPS coordinates, or build a location history. The permission is used solely as a system requirement for local network discovery. We do not collect or share any location-derived data with third parties.

C. Accessibility Service (Android TV Server)

Strict Use Case: This permission enables the server to translate incoming network commands (e.g., {"cmd":"CLICK_LEFT"}) into real UI interactions on your Android TV or Tablet.
Data Handling: Our implementation is strictly Input-Only. It does not read screen content, monitor other apps, or capture text. It is dormant until a command is received from your authenticated mobile controller.

To sustain the free tier of Mouse Keyboard, we integrate Google AdMob for advertisement delivery in the Mobile Controller app. AdMob may collect non-personally-identifiable identifiers such as your Android Advertising ID (GAID) to serve contextually relevant ads.

Critical Distinction: AdMob operates as a sandboxed SDK with zero access to Mouse Keyboard's internal data streams. Specifically, AdMob cannot access:

• Your control inputs, keystrokes, or cursor movements
• The identity of devices you pair with
• Your local network topology or IP addresses
• Any data processed by the Accessibility or Overlay services

Users who upgrade to our Pro tier have AdMob completely removed at the SDK level. No ad code executes in the Pro build. For details on how Google processes advertising data, refer to the Google Privacy Policy.

While all Mouse Keyboard traffic is local, your local network security directly impacts the integrity of your control sessions. We strongly recommend the following configuration:

• Use WPA3 or WPA2-Personal encryption on your Wi-Fi network
• Set a strong, unique network passphrase (12+ characters, mixed character types)
• Avoid using Mouse Keyboard on unsecured or public Wi-Fi networks
• Enable your router's client isolation for guest networks (our app will not work on isolated networks by design)

Our QR pairing mechanism provides a first-layer of session authentication, ensuring that only devices that physically scan the QR code are granted access to the control stream.

Because we collect no user data, there is nothing to delete from our end. All application state (paired devices, preferences, logs) exists exclusively in your device's local storage, which you control completely.

To perform a full data reset:

• Mobile App: Clear app storage via your phone's Settings → Apps → Mouse Keyboard → Storage → Clear Data
• Desktop Server: Delete the %APPDATA%\MouseKeyboard\ directory (Windows) or equivalent on macOS/Linux
• Android TV Server: Clear app data from your TV's app management settings

This policy may be revised to reflect new features or regulatory requirements. Significant changes will be communicated via an in-app notification. Continued use after an update constitutes acceptance of the revised terms.

For privacy inquiries, technical transparency requests, or protocol audits, contact us at: [email protected]

// WE BUILD TOOLS FOR OURSELVES. WE PROTECT YOUR PRIVACY AS OUR OWN. //