Effective Date: July 21, 2026
This Privacy Policy explains how Pikcn Technologies (OPC) Private Limited ("Pikcn," "we," "us," or "our") handles information when you use Remote VNC Server (the "App"), package com.pranayc.remotevncserver. The App provides direct, user-initiated screen sharing between your Android device and a client you select. Pikcn does not operate an account, analytics, advertising, telemetry, or relay service for the App.
-
Introduction
Remote VNC Server captures an Android display with the operating system's MediaProjection API and sends it over the Remote Framebuffer protocol to a compatible client chosen by the user. The App can optionally receive remote touch and keyboard input and synchronize plain-text clipboard content during an active sharing session.
The App does not require an account and does not include advertising, analytics, tracking, crash-reporting, or developer-operated cloud-relay SDKs. Pikcn does not receive a copy of your screen, remote input, clipboard text, connection password, or connection history.
-
Screen Capture and Sharing
Android displays its own screen-capture consent prompt each time a new sharing session starts. The App cannot start MediaProjection without this user approval. During an approved session, display frames are processed in memory and transmitted directly to authenticated clients that connect to the device, or to a listening client address configured by the user.
Pikcn does not receive, store, inspect, or retain captured screen content. The App does not record the screen to a file. Android may blank protected or security-sensitive content and may stop screen projection when the device locks. The App does not attempt to bypass those protections.
-
Network Connections and Encryption
Connections are made directly over a network path selected by the user. The Play-distributed release requires RA2-256 authenticated encryption. The App fails closed when a client does not support the required security type and does not silently downgrade to plaintext. A persistent public-key identity is generated in Android Keystore, and the App shows a fingerprint that users can compare with the client's first-connection prompt.
Source-built debug variants may expose a legacy compatibility mode for protocol testing. That mode is not enabled in the Play-distributed release. Anyone who independently builds and uses the debug variant should understand that classic VNC authentication does not encrypt screen pixels, remote input, or clipboard text and should use it only through a trusted encrypted tunnel.
Reverse connections change which endpoint opens the TCP socket. They do not by themselves add encryption. The App applies the same selected security mode to incoming and reverse connections.When incoming mode is enabled, the server listens on the Android device's available network interfaces. Depending on the device, router, VPN, and firewall configuration, that can make the selected port reachable beyond the immediate Wi-Fi network. Users are responsible for limiting network exposure to the clients they intend to allow.
-
Optional Remote Control and Accessibility Access
Remote control is disabled by default. If the user chooses to configure it, the App first shows a prominent disclosure explaining why Android Accessibility access is needed, what data it can access, and how it is used. Only after the user chooses Open settings does Android show its separate system screen for enabling the service.
While screen sharing is active, the Accessibility service can perform the touch gestures requested by an authenticated client and can inspect the currently focused field when necessary to enter requested text. It does not autonomously initiate actions or make decisions. Accessibility data is not collected, stored, sold, used for advertising, or uploaded to Pikcn. When sharing stops, the App rejects new remote input and discards gestures that Android has not begun; a gesture already being delivered by Android may finish while the stop request is processed. Screen sharing remains available in view-only mode without enabling the service.
-
Optional Clipboard Synchronization
Clipboard synchronization is disabled by default. When enabled during an active sharing session, the App can read current plain-text clipboard content after an Android clipboard change and send a bounded text value to connected clients. It can also place plain text received from an authenticated client onto Android's system clipboard.
Clipboard text is processed in memory for this feature and is not sent to Pikcn or stored in a developer-operated service. Once text is placed on Android's system clipboard, Android and other apps with authorized clipboard access may handle it under their own behavior and privacy practices.
-
Connection and Device Information
The App processes limited technical information needed to provide direct connections:
- Local network addresses: enumerated on the device so the App can display connection endpoints.
- Client network address: held in memory while a client is connected and shown in session status.
- Reverse destination: a host name or IP address and port entered by the user and stored in local App settings.
- Protocol details: negotiated security, pixel format, encoding, frame dimensions, and connected-client count used to operate and diagnose the current session.
This information is not uploaded to Pikcn, used for tracking, or combined with an advertising or analytics identifier. Release builds do not contain a developer telemetry or remote log-upload service.
-
Information Stored on the Device
The App stores non-secret configuration values in its private application storage, including ports, selected connection methods, reverse destination, and feature switches. The configured server password is session-only: it is kept in memory for authentication during the active sharing session, released when that session stops, and never persisted in App preferences. Android's application sandbox limits ordinary access to stored preferences. The persistent server identity's private key is generated and retained through Android Keystore.
App-data cloud backup and device-to-device transfer are disabled. Pikcn does not maintain a remote copy of preferences, passwords, identity keys, or session content.
-
Permissions and Special Access
The App uses the following Android permissions or system-controlled access:
- Internet and local network: accept direct connections and create user-configured reverse connections.
- MediaProjection and foreground service: capture the approved display and keep an active session visible and user-stoppable.
- Notifications: display the active screen-sharing service and its Stop action.
- Accessibility service: optional remote gestures and focused-field text entry as described above.
- Clipboard interface: optional synchronization while sharing is active.
The App does not request access to location, contacts, phone calls, SMS, microphone, camera, accounts, advertising identifiers, or general file storage.
-
Data Collection, Sharing, and Sale
Pikcn does not collect, sell, rent, or use user data from the App for analytics, profiling, advertising, marketing, or machine-learning training. There is no developer-operated backend to receive session content.
Screen frames and optional clipboard text leave the Android device only as part of the specific sharing session initiated and configured by the user. They go directly to the client or endpoint the user selected. A recipient, client application, network operator, VPN provider, or tunnel provider may process traffic under its own terms and privacy policy. Pikcn does not control a third-party client chosen by the user.
-
Retention and Deletion
Captured frames, queued remote-input requests, clipboard bridge values, and connected-client details are retained in memory only as needed for the active session and are discarded as buffers are replaced or the session ends. The App does not create a recording or server-side history.
Locally stored preferences and the server identity remain until the user clears the App's storage in Android settings or uninstalls the App. Stopping sharing immediately closes active and pending network connections and stops capture, remote input acceptance, and clipboard synchronization.
The App does not create user accounts and Pikcn stores no server-side App data. Therefore, there is no App account or remotely stored user profile for Pikcn to delete.
-
Data Security
The App minimizes permissions, requires encrypted connections, defaults remote control and clipboard synchronization to off, protects identity keys with Android Keystore, disables backup and device transfer, and keeps active screen sharing visible through Android's foreground-service and projection indicators.
No security measure is perfect. Users should verify the server fingerprint, use a strong unique password, keep Android and client software current, limit network exposure, and stop sharing when finished.
-
Software Components and Third-Party Services
The production App has no runtime third-party library dependency. It relies on Android platform APIs and its own Java RFB implementation. A standards-compatible client selected by the user is a separate product and is not operated by Pikcn through this App.
The App does not integrate an advertising network, analytics service, crash-reporting service, social login, payment processor, cloud-storage service, or developer-operated relay.
-
Children's Privacy
Remote VNC Server is a general-purpose network administration and screen-sharing utility intended for adults. It is not directed to children and Pikcn does not knowingly collect personal information from children or other users through the App.
-
Changes to This Privacy Policy
We may update this policy when App features, permissions, dependencies, security modes, data practices, or legal and platform requirements change. The revised policy will be posted at this URL with a new effective date. Material changes to data handling will be disclosed before the changed version is distributed.
-
Contact Us
For privacy questions or concerns about Remote VNC Server, contact:
Pikcn Technologies (OPC) Private Limited
Bengaluru, Karnataka, India
Email: info@pikcn.com
Website: www.pikcn.com