PRIVACY, SECURITY, & COMPLIANCE
RemoteToPC is committed to protecting customer data, account information, and remote-access sessions. We use technical and administrative safeguards designed to protect information from unauthorized access, misuse, alteration, or disclosure. This page summarizes our approach to privacy, security, and regulatory requirements.
PRIVACY
RemoteToPC collects and processes only the information needed to provide, maintain, support, and improve our services. Information is handled in accordance with our Privacy Policy and applicable data-protection requirements.
PCI COMPLIANCE
RemoteToPC does not directly store or process customer payment-card information. Subscription payments are processed by Stripe, a third-party payment provider responsible for securely handling payment-card data.
Because RemoteToPC does not store card numbers or sensitive payment credentials on its own systems, payment information remains within Stripe’s payment infrastructure.
GDPR COMPLIANCE
RemoteToPC supports customers subject to the European Union’s General Data Protection Regulation (GDPR). Our services are designed to limit the personal information required to provide remote access, monitoring, and management functionality.
Organizations using RemoteToPC remain responsible for determining how they use the service, what personal data they process, and what legal basis applies to that processing. Customers should ensure that their own use of RemoteToPC complies with applicable GDPR requirements..
LGPD COMPLIANCE
RemoteToPC supports customers subject to Brazil’s Lei Geral de Proteção de Dados (LGPD). Our services are designed to minimize the personal information required to provide remote access, monitoring, and management features.
Organizations using RemoteToPC remain responsible for determining how personal data is processed within their environment and for meeting their own obligations under the LGPD.
HIPAA Security Considerations
RemoteToPC includes security features that can support organizations operating in environments subject to HIPAA. However, using RemoteToPC does not by itself make an organization HIPAA compliant. Customers remain responsible for configuring and operating their systems, policies, access controls, and workflows in accordance with HIPAA requirements.
Security features relevant to protected environments include:
These security features can support organizations that use RemoteToPC as part of a broader HIPAA-compliant environment.
AGENTS AND SERVICE PROVIDERS
RemoteToPC uses selected third-party service providers to support certain business functions. For example, Stripe processes subscription payments, and Google Analytics may be used to understand website usage and traffic.
These providers operate under their own security and privacy policies and are used only where appropriate to support RemoteToPC services.
SECURITY
RemoteToPC uses multiple safeguards to protect accounts, remote sessions, and service infrastructure.
LINKS
