Beta privacy notice
JisrDesk is designed for visible, consent-based remote support. This notice explains the technical data handled during the supervised beta.
The beta is for testing with people you know and trust. It is not intended for regulated, confidential, or high-risk support environments.
Data stored by the service
The device registry stores your JisrDesk numeric ID, the public half of the device identity key, your chosen device name, approval status, and first and last connection times. The private identity key stays on your computer.
Data handled during a connection
The signaling service temporarily handles network addresses, online presence, consent requests, session routing information, encrypted connection setup messages, and a salted verifier for the temporary session password. Active routing information is not designed to remain after a service restart.
Screen and input data
Screen media and remote-control messages normally travel directly between the two computers or through an encrypted relay when a direct connection is unavailable. JisrDesk’s signaling and relay services are not designed to record screen content, keystrokes, or mouse input. Infrastructure providers can still observe operational details such as network addresses, timestamps, and traffic volume.
Data on your computer
The Windows app keeps the local device identity, preferences, and a local activity history. The local history is controlled by the user of that computer and is not a tamper-proof compliance record.
Your choices
- You can reject any support request before screen sharing begins.
- You can end an active session at any time.
- You can ask the beta administrator to revoke or delete a registered device.
- You can uninstall JisrDesk and remove its local application data.
Questions and deletion requests
Contact support@usaimisoft.com. Do not email temporary passwords, private keys, screen captures, or other sensitive session content.