Last Updated: October 16, 2026
1. Scope
Aris Party LLC publishes TouchKVM for iOS and Android. This policy covers TouchKVM and its product pages on arisparty.org. Other Aris Party apps have their own privacy policies. You can connect to your KVM without creating a TouchKVM account.
2. Your KVM connections and local data
TouchKVM saves connection settings, hostnames or IP addresses, preferences, and connection history on your device. Saved KVM passwords and authentication secrets use platform secure storage. The app sends credentials and session commands to the KVM endpoint you choose to authenticate and operate it.
Ordinary remote video, audio, keyboard, and pointer sessions travel between your phone and your KVM through your configured network path. They are not uploaded to Aris Party as session recordings. The optional AI feature described below sends screen captures and related context to your selected provider.
LAN scanning checks reachable devices on your local network. Optional Tailscale import uses your access token to request device information from Tailscale. A saved import token uses platform secure storage. Importing does not itself create a VPN connection.
3. Advertising and consent
The free app uses Google AdMob banner advertising. Home-screen banners become eligible after 32 successful connections and depend on consent state and ad availability. Banner ads stay hidden while your TouchKVM Pro entitlement is active.
The Google Mobile Ads SDK may process your IP address (including approximate location derived from it), device and advertising identifiers, app and ad interactions, and diagnostic information to deliver and measure ads and prevent fraud. The app uses Google's User Messaging Platform to check consent status and show a consent form when required before requesting ads. These advertising choices do not control the app's separate Firebase Analytics collection.
Where required, an advertising privacy-options entry is available from the app's About screen. You can also manage advertising identifiers in your phone's privacy settings. Read Google's privacy policy and the Google Mobile Ads data disclosure for details.
4. Analytics and service configuration
TouchKVM uses Google Analytics for Firebase to understand app use and reliability. Events include screens and features used, connection outcomes and device family, stream settings, purchase flow outcomes, Pro status, and banner eligibility, loading, or failures. Firebase may also process app-instance identifiers and device, app, and usage information. Firebase Remote Config supplies app feature configuration and may process a Firebase installation identifier.
If you enable optional website analytics, our website measures page views, link clicks, device category, and referral source. Typed form values are not sent to website analytics. Manage this choice on the website privacy page. See Firebase privacy information for the provider's practices.
5. Purchases and creator attribution
Apple or Google processes in-app payments. We do not receive your payment-card details. To verify purchases and attribute eligible creator referrals, the app can send the signed Apple transaction or Google purchase token and product ID to our verification service, together with a creator code, campaign ID, click ID, or installation identifier retained for attribution. Purchase status is cached locally to restore access to paid features.
Manage recurring subscriptions through the store account used to subscribe. Removing the app does not cancel a store subscription.
6. Optional Agentic KVM
When you enable and run Agentic KVM, the app sends your task prompt, remote screen captures, action history, and connection context such as host and device family directly to the OpenAI, Anthropic, or Google Gemini provider you select. Your provider API key is stored using platform secure storage and is used to authenticate requests to that provider. Provider charges and data handling are governed by your provider account and its terms.
Screen captures can contain personal or confidential information visible on the remote computer. Only start a run when you are authorized to share that content with your chosen provider. The feature is optional; normal manual KVM control does not require it.
7. Permissions and transport security
Local-network access is used to discover and reach your KVM. Camera and microphone permissions are used for media features you activate, such as remote webcam or microphone passthrough. Availability depends on hardware, firmware, and your setup. You can revoke these permissions in phone settings.
Transport protection depends on your endpoint and network configuration. TouchKVM supports HTTP as well as HTTPS connections; HTTP traffic is not encrypted by HTTPS. The optional JetKVM audio bridge also uses HTTP. Use HTTPS where supported and keep KVM access and the audio bridge on a trusted private network or VPN. We do not claim that every connection path is encrypted.
8. Support, sharing, and retention
If you contact support, we receive your email address and the information you choose to include. We use this information to answer requests and diagnose problems. Avoid sending passwords, API keys, or confidential screen contents.
The providers described above process data to supply their services. We may also disclose information when required by law or to protect our services and users. Providers may process information in countries other than yours under their own data-handling terms.
Saved connections and settings remain on your device until removed or cleared. Provider data, purchase records, and support correspondence have separate retention requirements. Contact us to ask about access, correction, or deletion of information we hold; we may need to verify the request and retain records required for transactions or legal obligations. We cannot delete data held independently by your KVM, store, or selected AI provider.
9. Children and policy changes
TouchKVM is not directed to children under 13. Contact us if you believe a child has provided personal information. We update this policy when app practices change and show the revision date above.
10. Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us at: