Device & Network Security

Device security, remote-access authorization, and malicious-traffic filtering address different risks. Restricting who can control a device does not establish that every network connection from that device is inspected or blocked.

Our rules prohibit malware, phishing, unauthorized access, spam, attacks, and other harmful activity. A prohibition is not a guarantee that harmful activity will always be prevented or detected.

Do not assume that all traffic from a hosted device passes through a DroidDesk security gateway. Device connectivity can involve a host's Wi-Fi, a mobile carrier, or other permitted network arrangements. The remote-control connection and the device's outbound internet connection are separate aspects of the service.

Unless a specific protection is expressly documented for your device or plan, this service does not promise universal DNS or IP blocklists, content inspection, antivirus scanning of every installation, inspection of encrypted connections, or filtering of all applications and protocols. This page does not certify any of those controls as active across the entire device fleet.

Filtering provided by a host, router, operating system, carrier, or third-party application has its own coverage and limitations. Its presence must not be represented as a platform-wide DroidDesk control. A browser-level restriction should not be assumed to apply to other applications, and a Wi-Fi rule should not be assumed to protect a separate mobile-data connection.

Renters receive temporary access subject to the purchased plan, session limits, available features, and device restrictions. Attempting to bypass access controls, retain access after a rental ends, disable management controls, or obtain another user's credentials is prohibited.

Hosts must follow the approved setup instructions, maintain physical control of their devices, and protect the credentials used to manage them. Hosts must not share management access with renters or interfere with an active rental.

The availability of individual restrictions depends on the device, operating system, connection method, and plan. Do not assume a device is fully locked down merely because it is listed on the marketplace.

Hosts should use a dedicated device and a separate guest network or equivalent isolation for rental activity, where supported. Keep personal computers, storage devices, printers, administration interfaces, and other sensitive resources inaccessible from the rental network. A network name alone does not establish effective isolation.

Do not expose router administration, debugging ports, or device-management interfaces directly to the public internet. Keep relevant operating systems, router software, and management software updated. Follow your internet provider's and carrier's conditions.

These are host setup precautions. DroidDesk does not state that every host network has been inspected or that isolation is automatically configured by the Platform. If you cannot establish an appropriate setup, contact Support before making the device available.

Renters must not install malware, spyware, credential-stealing tools, or applications used to attack, deceive, or compromise other people or systems. They must not modify, root, flash, or disable device protections without explicit authorization for the relevant activity.

Hosts must not install surveillance tools or inspect renters' messages, credentials, files, or browsing activity. Suspected misuse should be reported to DroidDesk rather than investigated by accessing another user's private content.

Report suspected abuse through Contact Support. For an unresolved report or a formal complaint, use Complaints & Disputes. State that the matter concerns security and include the device ID, approximate incident time and time zone, a factual description, and relevant non-sensitive evidence.

Depending on the circumstances, DroidDesk may restrict an account or device, pause or end access, request clarification, remove a listing, or refer the matter to an appropriate provider or authority where permitted or required. These are available response measures, not a guarantee of automatic detection or a fixed response time.

If a host reasonably believes continued connectivity creates an immediate threat, the host should prioritize safety, stop making the affected device available, and notify support promptly. Preserve relevant information lawfully; do not open or copy renters' private files to collect evidence.

A security review may use the account, rental, device-status, transaction, and support information available to DroidDesk. A technical event or user report is an indicator for review, not necessarily proof of wrongdoing.

Our Privacy Policy explains the categories of personal information we process and the purposes for which we use them. This page does not claim that DroidDesk records every destination, decrypts every connection, or retains complete traffic content. Any additional monitoring must be accurately disclosed before it is described as an operating control.

The standard cleanup described in our Terms of Use removes applications installed during the rental and clears application and browser data. It is not a full factory reset after every rental. Files such as downloads, photos, documents, and APK files may remain.

Renters should delete their files and sign out before the rental ends. Hosts must not inspect or attempt to recover data left by a renter. Report a suspected cleanup failure to support and follow instructions before making the device available again. Cleanup is not a substitute for protection during an active session.

If you believe your legitimate activity was restricted incorrectly, contact support with the device or order reference and a description of the expected activity. Do not try to bypass the restriction while it is being reviewed. You can request further review through Complaints & Disputes.

Service compensation and reimbursement are handled under the Refund Policy. A security report does not automatically guarantee compensation.

No service can guarantee prevention of every attack, harmful application, abusive action, or network incident. Hosts and renters must follow the documented requirements and report suspected problems. A legal prohibition, manual review process, or suspension capability should not be understood as proof of comprehensive traffic filtering.