Terms of Service

Effective date: 24 June 2026 These Terms govern access to and use of AZTCO RDP MFA, including the administration portal, authenticator PWA, enrollment flows, email approval flows, Windows connector installers, NPS extension, Credential Provider connector, AD/local sync agent, audit logs, support tickets, documentation, and related services. 1. Roles and responsibility AZTCO RDP MFA is a multi-factor authentication and access approval platform. Each customer or tenant remains responsible for its own users, administrators, servers, licenses, policies, connector deployment, Windows/RDP configuration, backups, legal basis for processing, and compliance obligations. Tenant administrators must only enroll users, devices, servers, domains, IP ranges, and connectors that they are authorized to manage. 2. Authorized use You may use the platform only for lawful business authentication, RDP/RD Gateway/NPS/Credential Provider protection, user enrollment, audit review, AD/local user synchronization, support, and related security operations. You must not misuse the service, attempt unauthorized access, bypass tenant isolation, reverse engineer hosted services, upload malicious files, share service keys or activation tokens outside authorized personnel, or use the service to violate privacy, employment, surveillance, export control, or computer misuse laws. 3. Tenant isolation and administrators Tenant data is designed to be isolated by tenant. Global administrators manage platform-wide configuration, license types, connector builds, global email templates, documentation, legal text, and operational support. Tenant administrators manage their own tenant users, devices, enrollments, servers, MFA policy, AD/local sync, audit forwarding, support tickets, and tenant settings. Customers are responsible for selecting trusted administrators and promptly removing access that is no longer required. 4. MFA behavior and availability The platform can require, bypass, or deny MFA according to tenant/server policy, user/device status, subscription status, connector availability, push notification delivery, email approval settings, lockout rules, and fail-open/fail-closed configuration. MFA does not guarantee uninterrupted access, complete prevention of compromise, or successful delivery of third-party push/email notifications. If a connector, network, browser, phone, email system, or Windows service fails, access may be delayed, denied, or handled according to the configured fail policy. 5. Connectors, installers, and local systems Windows connectors run in the customer environment and interact with Microsoft Windows, NPS, RD Gateway, Credential Provider, local users, or Active Directory. Customers are responsible for testing connectors in a non-production environment, validating hashes and installer sources, keeping Windows and runtime dependencies patched, protecting configuration files and service keys, and confirming that policies are synchronized before enforcing production access. 6. Accounts, devices, and credentials Users and administrators must protect passwords, trusted devices, enrolled devices, email accounts, authenticator profiles, service API keys, activation tokens, registration keys, and recovery channels. A tenant may limit users by license, suspend expired subscriptions, revoke devices, delete enrollment records, and lock users after repeated failed or unapproved authentication attempts. 7. Audit logs, monitoring, and forwarding The platform records security and operational events such as login attempts, approvals, denials, email delivery, enrollment, device changes, policy changes, server registration, connector health, sync status, support activity, and administrative actions. Customers may configure forwarding to secure syslog or SNMPv3 authPriv collectors. Customers are responsible for collector security, retention rules, access controls, and lawful monitoring notices. 8. Subscriptions, billing, and suspension Access to paid features may depend on active subscription status, license quantity, billing approval, trial terms, and payment status. If a subscription expires, is suspended, or exceeds allowed use, users or features may be disabled until renewal or correction. Deleting users or tenants may be restricted where needed for billing, audit, security, or legal retention. 9. Customer content and support attachments Customers are responsible for content submitted to the platform, including support ticket text, attachments, documentation edits, templates, legal text, branding, SMTP settings, certificates, log destinations, and uploaded connector builds. Do not upload secrets or regulated data unless it is necessary and authorized. 10. Security commitments and limits AZTCO RDP MFA is built with tenant scoping, role-based access, audit logging, MFA workflows, policy controls, trusted device controls, encrypted secret storage where supported, and secure connector registration. No system is perfect. Customers must maintain their own endpoint security, Windows hardening, network security, backups, monitoring, incident response, and administrative controls. 11. Data deletion and retention Tenant administrators may request or perform deletion of tenant data where supported. Deletion may remove users, devices, enrollments, servers, licenses, support records, and related tenant records, subject to backups, logs, billing records, fraud prevention, dispute handling, legal obligations, and security retention. 12. Warranties and liability To the maximum extent permitted by law, the service is provided without warranties of uninterrupted operation, error-free operation, fitness for a particular purpose, or complete security. AZTCO is not liable for customer misconfiguration, unauthorized administrator activity, lost credentials, third-party outages, Windows/RDP/NPS behavior, email or push provider failures, or business interruption caused by customer-selected policies. 13. Changes AZTCO may update the service, connectors, policies, documentation, templates, and these Terms. Continued use after an update means acceptance of the updated Terms unless a separate written agreement states otherwise. 14. Contact Questions about these Terms, security, privacy, or data requests should be sent to [email protected] or the support channel provided in the platform.