Tezcatl

Privacy Policy

English · 한국어

Effective date: September 18, 2026

This Privacy Policy applies to the Tezcatl mobile application (the “Application”), created by Mincheol Shin (the “Service Provider”). The Application is provided as is.

Information Collection and Use

The Application does not require an account and does not ask you to provide your name, phone number, address, or precise location.

The Application includes Google Analytics for Firebase and Firebase Crashlytics. Depending on your device and Firebase configuration, these services may automatically process information such as:

This information is used to understand Application usage, diagnose failures, and improve stability and performance. The Service Provider does not use this information for advertising or sell it to third parties.

The Application may download a TLS certificate from r2tezcatl.groovin.io. This happens when mirroring starts and the stored certificate is missing or close to expiry, and when you press Update in the certificate entry in settings. The hosting provider may process standard connection information such as your IP address, request time, and user agent in ordinary server logs.

The Application does not collect precise location information. It does not use artificial intelligence technologies to process your data or provide features.

Local Screen Mirroring and Remote Touch

When you start mirroring, screen video is transmitted directly from your Android device to a browser on the same local network. Screen video is not routed through or stored on the Service Provider’s servers.

Devices connected to the same local network can access the displayed connection address without separate user authentication while mirroring is active. You should use the Application only on a trusted private network and stop mirroring when it is not needed.

If Remote Touch is enabled, the Application receives touch coordinates and control commands from the connected browser over the local network and uses them only to perform the requested gestures. These touch inputs are not stored or transmitted to the Service Provider or other third parties.

AccessibilityService API

Remote Touch uses Android’s AccessibilityService API only to perform gestures requested by the user from the connected browser. The accessibility service is configured not to retrieve window content and the Application does not use it to read, collect, store, or share screen text, passwords, or accessibility events.

You can enable or disable this service at any time in Android accessibility settings. Remote Touch does not work while the service is disabled.

Fixed Local Addresses

When the optional fixed-address feature is enabled on a supported device, the bundled local helper uses Android’s TestNetworkManager to create a stable local address. A browser on the same local network can use the corresponding domain to connect directly to the Application.

This feature does not use VpnService, connect to a remote VPN server, or inspect or forward other applications’ traffic. No data is collected or shared through the address interface. The interface is released when mirroring stops or the helper connection closes. With the feature disabled or unavailable, the Application can be accessed through the device’s current hotspot IP address.

Wireless Debugging and Local ADB Identity

The optional virtual-display mode and fixed-address feature require Android developer options and wireless-debugging pairing initiated by the user to prepare the bundled local helper. The helper creates and controls the virtual display and, when requested, holds the fixed local address. Preparation is needed again after restarting the phone.

The Application also asks you to turn on USB debugging in developer options, because Android stops the debugging daemon when both USB and wireless debugging are off, which ends the helper as soon as the phone leaves Wi-Fi. The Application only reads whether these switches are on; it does not change them, and it does not connect to any computer on your behalf.

The ADB private key and certificate are generated and stored in the Application’s private device storage. They are excluded from Android cloud backup and device-to-device transfer. They are not transmitted to the Service Provider. You can revoke the pairing from Android wireless-debugging settings or reset it from the Application.

The helper executable is bundled with the Application. The Application does not download executable code from the Service Provider or another external source.

Optional Notification Access

If you enable notification access in Android settings, the Application reads active notifications to show a notification panel and app-icon badges on the virtual display. Tapping an item asks Android to run the notification's existing action, and dismissing an item removes that notification through Android's notification-listener API.

Notification titles, text, app identities, and actions are processed only in volatile device memory. The Application does not upload, persist, sell, or share notification content. You can revoke access at any time in Android notification-access settings, and mirroring continues to work without it.

Locally Stored Information

The Application stores settings, onboarding and terms acceptance status, selected Bluetooth-device information, launcher configuration, and other preferences in private application storage. A selected launcher wallpaper remains a local Android content reference and is not uploaded by the Application.

Sensitive device-specific material, including the local ADB identity, downloaded TLS certificate cache, and temporary display-restoration state, is excluded from Android backup and device transfer.

Third-Party Services

The Application uses third-party services that may process data under their own privacy policies:

The Service Provider may disclose information when required by law, to respond to lawful process, to protect the rights or safety of users or others, or to trusted service providers acting on the Service Provider’s behalf under appropriate obligations.

Opt-Out Rights

You can stop Firebase-related and other Application data processing by uninstalling the Application. You can stop local screen and touch transmission at any time by stopping mirroring. You can disable notification access, the accessibility service, fixed-address feature, Bluetooth automation, and wireless debugging through the Application or Android settings.

Data Retention and Deletion

Local settings and credentials remain on your device until you reset them, clear Application data, or uninstall the Application. Firebase and hosting-provider data are retained according to their applicable configurations and policies.

To request deletion of information associated with the Application or ask about retention, contact gaiuszzang@gmail.com. Because the Application does not provide accounts, the Service Provider may need reasonable technical information to identify data associated with a request.

Children

The Application is not directed to children under 13, and the Service Provider does not knowingly solicit personal information from children under 13. If you believe that a child has provided personal information through the Application, contact the Service Provider so appropriate action can be taken.

Security

The Service Provider uses reasonable technical and organizational safeguards appropriate to the information processed. Screen and remote-control traffic is intended to remain on the user’s local network. No method of electronic transmission or storage can be guaranteed to be completely secure.

Changes

This Privacy Policy may be updated from time to time. Changes will be published at https://groovin.io/tezcatl/privacy-policy with an updated effective date. You should review the policy periodically.

Contact Us

For privacy questions or requests, contact: