Privacy Policy

Plain language notes

How this page applies to SimpleRemote users

This section expands Privacy Policy with a practical explanation for customers and users evaluating SimpleRemote. The clauses above remain the legal reference; these notes help explain how they apply in daily use of remote control software.

In remote access, clarity matters because a session can show a screen, move files or allow actions on a Windows computer. The user or company using the service must therefore be authorized to connect and should inform employees, customers or third parties when required.

The SimpleRemote workflow separates authentication, subscription, device registration and remote-session signaling. That separation helps the service manage users and permissions without intentionally turning the server into a store for session content.

When a company adds users, it also takes responsibility for keeping the list current. If someone changes role, leaves the organization or no longer needs access, an administrator should remove permissions and review saved devices.

Billing and the business plan are intended for recurring professional use. Personal or light use can start without checkout, but continued commercial use, address-book management and team administration justify an active subscription.

External services such as Stripe, EmailJS, Cloudflare or Google reCAPTCHA are used for specific functions: payments, forms, human verification and security. Each provider may process the technical data needed to deliver that function.

Customers should also maintain their own controls: protect the email account receiving OTP messages, use strong endpoint passwords, avoid sharing credentials, review who has access to the company device book and document when a remote connection is allowed.

If an organization has internal, regulatory or sector-specific requirements, it should review these pages alongside its own policies. SimpleRemote provides tools to connect and manage access, but the customer remains responsible for the systems and data it chooses to display, copy or transfer during a session.

In practice, the customer controls the context of each session. SimpleRemote provides the technical tool, but it does not decide which computer is opened, which documents are visible or which file is transferred. That difference matters for privacy, security and internal compliance.

Technical logs may be necessary to diagnose errors, prevent abuse, review authentication or maintain availability. They should be understood as operational data, not as a complete recording of work performed on the remote computer.

Data minimization remains a good practice. Administrators should save only necessary devices, invite only users who genuinely need access and remove permissions when they no longer add value.

If a security incident occurs, the company should review users, devices, access email accounts, recent sessions and any shared credential. Contacting support can help, but the first internal response should protect affected computers.

Cancelling a subscription can affect business functions such as users, administration or managed access. Before cancelling, review which processes depend on those functions and communicate the change to people using the tool.

Data retention should be understood together with tax, contractual and security obligations. Some records may remain for legal periods even after an account is no longer active, especially when they relate to billing or abuse prevention.

These pages should be reviewed when the product, external providers, payment flow or applicable legal requirements change. Keeping them current helps users and search engines find a coherent explanation of the service.

For business customers, these pages also work as a reference point during rollout. Before inviting users, confirm who accepts the terms, who manages the subscription, who receives communications and who may make decisions about shared devices.

In an environment with employees or end customers, transparency should be part of the procedure. A short notice before starting support, an explanation of what will be done and a confirmation when the session ends can prevent misunderstandings and reinforce trust.

Using human-verification or payment tools does not mean all data passes through all providers. Each integration has a specific purpose. That is why the pages mention payments, forms, security and verification as separate categories.

When a customer acts as controller for its own users, it should combine SimpleRemote features with its internal obligations. That may include legal basis, employee notices, access records, support policies and rules for transferring files.

If a legal page is updated, the visible date helps readers understand which version is published. Keeping clear content, frequently asked questions and structured schema improves comprehension for people, search engines and systems that summarize web information.

This also gives future reviewers a stable place to check product, privacy and billing explanations before publishing changes.

Frequently asked questions