MB REMOTE

Privacy policy

Updated 28 October 2026.

Who is responsible

Michael Bonard, trading as MB Tools, operates MB Remote and its connection service in the United Kingdom. He is the controller of the device-registration, service-management and support information described here. For privacy questions or requests, use the contact form, select MB Remote and begin your message with “Privacy request”. Include a reply email if you want a response. Never send passwords, private keys, sign-in tokens or invitation codes.

This policy covers MB Remote for Windows, its Android viewer, Quick Support and the supporting connection service. A person or organisation using remote access is separately responsible for the information they choose to access, share or retain on the connected devices.

Information used by the service

• Device registration: a device public key and derived PC number or phone ID, device name, online/last-seen information, app version and edition, and platform or operating-system version where reported. The service can also store a device description, preview-release membership and blocked status.
• Connections: participating device identifiers, temporary connection references, routing and availability information, and network information needed to deliver requests. Other connected devices can receive your device name, number, public key and availability when looking you up or communicating with you. Knowing a number does not itself grant screen access.
• Session history: the participating device numbers and names, reported start and end times, duration and disconnect reason. This is connection metadata, not a screen recording.
• Quick Support and security: invitation identifiers, code hashes, participating device identities, expiry/revocation state, authentication replay checks, short-lived request counters and administrative actions. Network addresses can be used for request limiting.
• Support: information you choose to submit through the contact form, including any optional email. The website feedback privacy notice explains that form's storage and retention.

Screens, input, clipboard, files and chat

MB Remote processes the screen, keyboard/mouse input, clipboard, files and chat needed for the features you use. These are delivered to the other device. Connections may use a direct local-network path or the relay service; relayed session traffic is encrypted between the apps. The connection database does not store screen recordings, file contents, clipboard contents or chat transcripts. Encryption does not prevent the receiving person or device from retaining what you share.

Remote screen access and control depend on approval or a saved access grant. File-transfer and chat permissions are managed separately. Optional Windows sign-in access must be enabled explicitly. Review Access permissions, revoke grants you no longer need, and share only with people you trust.

Why information is used

We use service information to identify devices, route requested connections, maintain saved-device discovery, deliver updates, troubleshoot failures, operate the service and prevent abuse. Our lawful basis for this service metadata is legitimate interests: providing a functioning remote-access service that users request, protecting that service and its users, and resolving technical problems. We limit the information to those purposes; an access approval in the app is a technical permission, not a blanket consent to unrelated use of personal information.

MB Tools does not sell this information or use it for advertising. There is no advertising profiling or automated decision-making with legal or similarly significant effects. Technical rate limits and device blocks may restrict service access; contact us if you believe a restriction is incorrect.

Who can access information and where it is processed

The restricted management console allows the operator to inspect device records and session history, manage preview updates, remove devices or block access. Connected recipients receive the content and device information needed for the features you use. Support information is available to the operator.

Cloudflare provides website, connection-service, database and download hosting and security. It may process network addresses, request details and operational information as part of those services. Processing can occur outside the UK, including in the United States. Cloudflare's Data Processing Addendum describes its international-transfer protections, including applicable contractual safeguards and Data Privacy Framework arrangements. You may contact us for information about the safeguards relevant to your data. See also Cloudflare's privacy policy. Information may also be disclosed where required by law.

How long information is kept

• Device records: remain until removed by the operator; there is currently no automatic inactivity expiry. Blocked records are retained to enforce the block. Contact us to request removal; we will explain if a limited security record must remain.
• Session history: is pruned at approximately 90 days from the session start, and may be removed sooner by the record limit. A record can remain briefly until the next cleanup runs.
• Quick Support: invitation expiry or revocation ends access, and ending temporary support removes the temporary device registration. Associated invitation records currently have no automatic deletion period and remain until administrative removal; expiry does not mean every related record has been erased.
• Administrative history: the service retains the latest 250 administrative actions rather than applying a fixed time limit.
• Temporary connection/security records: pending connection references expire after seconds, replay records after minutes and request counters after a few minutes; expired records are removed during service activity. Cloudflare's own operational records follow its applicable policies.

Deletion from the active database does not immediately remove provider recovery copies. Cloudflare's database recovery history may retain earlier data for up to a further 30 days. A request to remove a device does not automatically erase session records relating to other participants.

Information on your device

Device identity, saved devices, access permissions, settings, diagnostics, chat state and received files can be stored locally. Uninstalling the Windows app removes its service and unattended grants, but some identity and user data may remain for reinstallation. Files you received remain until you delete them. Copies held by another participant are under that participant's control. Do not send diagnostic logs to us unless needed for support; review them for personal information first.

Your choices and rights

You can stop sharing, change access permissions and stop using the service. Basic device and connection information is necessary to provide connections; the service cannot connect a device without it. Uninstalling alone does not delete its server registration.

Depending on the circumstances, you can request access to your personal information, correction, erasure or restriction, and object to processing based on legitimate interests. Portability applies where the law provides it. Use the contact form above; describe the request without supplying secrets. We may need proportionate information to verify that the records concern you. We normally respond within one month, subject to lawful extensions or exceptions, and explain any refusal.

You can complain to the UK's Information Commissioner's Office or your local data-protection authority. Please contact us first if you would like us to try to resolve a concern.

Changes

Updates to this policy will appear here with a revised date. Material changes affecting the use of personal information will be highlighted through an appropriate service or website notice.