Who we are and what this covers
Tap4Dollars LLC operates Yuki Companion. This policy covers the mobile app and the pairing, connection and relay services it uses. Features depend on your platform and app version. The Yuki website, desktop account and other browser features also have a separate general privacy policy. Contact support@yuki-browser.com about this policy or your personal information.
Pairing and device information
Companion connects to a computer you authorize. The mobile app uses a limited pairing authorization rather than requiring you to enter your Yuki account password. Our services process the associated account and device identifiers, device name and platform, public keys, pairing status, authorization credentials and connection status to authenticate devices, route requests and revoke access. Private device keys and pairing secrets are protected in local device storage.
Files, photos, text and links
When you choose to send content, Companion accesses the selected files, photos, videos, text or links and the metadata needed to deliver them, such as file name, type and size. Camera access supports QR scanning and, where available, taking a photo to send. File and photo selection uses system pickers. Image processing happens on your device. The paired recipient can save or use received content; if you send a file to a website through the desktop browser, that website handles the resulting upload under its own policy.
Connections and encryption
Transfer content is encrypted between paired devices. Depending on connectivity and feature support, traffic can travel directly over a local or peer-to-peer connection or through relay infrastructure. Relays carry encrypted content; encryption does not hide connection metadata such as IP addresses, device identifiers, timing and traffic volume from the infrastructure handling the connection. Direct connections also expose network addresses to the peer. Our services process connection and authorization information to deliver the service, enforce limits and protect against misuse.
Verification codes and notification access
On Android, optional notification access lets Companion inspect notification text locally for a verification-code candidate while a request from your paired computer is active. This may include text from messaging or other apps. You must enable notification access in system settings and confirm a candidate on the phone before it is sent encrypted to the paired computer. Companion does not request permission to read your SMS inbox. Codes and pending code requests are kept in process memory, not the persistent inbox or transfer history. On iOS, you enter or paste and confirm the code yourself; Companion does not read other apps’ notifications. You can disable notification access in Android settings.
Screen sharing and Android accessibility
Starting screen sharing requires system authorization. Screen images, which may contain personal or sensitive information visible on your phone, are transmitted to the paired computer. Stop sharing before opening content you do not want that computer to see. On Android, optional remote gesture control uses the accessibility service only when you enable it; the service can perform gestures but is not configured to retrieve the window-content tree. You can disable it in system accessibility settings. iOS screen sharing is read-only. The current screen-sharing implementation does not transmit microphone audio.
Push delivery and service providers
Where enabled and configured, Android uses Google Firebase Cloud Messaging and iOS uses Apple Push Notification service. Push registration involves a delivery token and, for Firebase, an installation identifier. Our service associates the registration with the authorized device to send wake-up signals. These signals do not contain your files, text or verification codes. Google and Apple process push-related information under their own privacy policies. Hosting, network and relay providers process the information needed to operate those services on our behalf. Information may be processed outside your country, depending on the infrastructure involved.
Local storage, retention and deletion
Companion stores pairing credentials, preferences, pending content and limited transfer records on the device. Retention depends on the record and platform: temporary requests and queued messages expire; received files may remain until exported, deleted or cleaned up by the app. Android transfer history is limited to 500 records and 30 days and excludes file names, text, URLs and verification codes. You can clear that history in the app. Exported files and copies saved by recipients are separate and are not removed by uninstalling Companion. Service-side device, pairing and push records support authorization and delivery; revoking a link stops access but does not mean every service record or recipient copy is immediately erased. Contact us to request deletion of service-side personal information; information needed for security, disputes or legal obligations may need to be retained.
Your choices and requests
You can decline optional permissions, stop sharing or transfers, disable push where offered and revoke device pairing. Disabling a permission stops the feature that needs it. Removing a pairing or uninstalling the app does not delete your Yuki cloud account. You can request account deletion through Yuki account settings; active subscriptions must first be resolved. Email support@yuki-browser.com to request access, correction or deletion of personal information or ask about your privacy rights. We may need to verify your authority to prevent unauthorized disclosure or deletion. Do not send passwords, pairing secrets or verification codes with a request.
Other disclosures and policy changes
Companion does not use your transferred content for advertising, and we do not sell your personal information. We may disclose information when required by law or necessary to protect users and the service. This policy will be updated when our practices change; the date above identifies the current version. Material changes that require notice or consent will be presented through an appropriate channel.