Acceptable Use Policy
Remote IT support depends on clear authority and legitimate business purpose. This policy identifies types of requests that fall outside the permitted service scope and explains why work may be refused when ownership, authorization, safety or legality is unclear.
This policy is designed to keep ordinary business IT work within authorized and lawful boundaries. It does not prevent legitimate account recovery, security configuration or administrative work where the client can establish appropriate authority.
1. Purpose
This Acceptable Use Policy defines the boundaries for requesting and using remote IT consulting and technical support. Services are intended for legitimate business administration, configuration, troubleshooting, productivity setup and workflow improvement.
2. Authorization requirement
A client must have lawful authority to request work on every device, account, domain, application, cloud environment, website, database or other system involved in an engagement. If authority is unclear, additional verification may be requested or the work may be declined.
3. Unauthorized access
Services may not be used to gain access to a third party’s account, device, network or data without permission. Requests to bypass ownership verification, defeat access controls or obtain another person’s credentials are prohibited.
4. Credential theft and phishing
Services may not be used to design or facilitate credential harvesting, deceptive login pages, phishing campaigns, impersonation schemes or other attempts to obtain authentication information through deception.
5. Malware and destructive activity
Requests involving malware creation, ransomware, destructive scripts, unauthorized data deletion, intentional service disruption or other malicious activity are prohibited.
6. Security control circumvention
Legitimate administrators may sometimes need help with account recovery or configuration changes, but services will not knowingly be provided to evade security controls where the client cannot demonstrate a legitimate administrative reason and authority.
7. Fraud and impersonation
Services may not be used to facilitate financial fraud, identity theft, deceptive impersonation, false account creation or other unlawful misrepresentation.
8. Surveillance and privacy
Services may not be used for unlawful surveillance, unauthorized interception of communications, covert monitoring without appropriate authority or collection of personal information in violation of applicable law or contractual obligations.
9. Intellectual property
Clients must not request assistance intended to distribute pirated software, bypass license controls, use unauthorized activation keys or infringe third-party intellectual property rights.
10. Abuse and harassment
Services may not be used to harass, threaten, stalk, intimidate or intentionally harm another person or business. Technical support may be discontinued if a requested setup presents a clear and material risk of abusive conduct.
11. Data handling
Clients are responsible for determining whether they have the legal right to access, process, move or disclose information contained in the systems they present for service. The fact that a client has technical access does not by itself establish legal authority to process the information.
12. Software licensing
Clients are responsible for maintaining valid licenses and subscriptions for software and cloud services used in an engagement. The service provider does not supply pirated software or methods intended to defeat licensing restrictions.
13. Provider terms
Work must be performed within the capabilities and legitimate account controls made available by relevant third-party providers. Requests that require violating a provider’s terms or circumventing platform restrictions may be refused.
14. Response to suspected misuse
If there is a reasonable basis to believe that an engagement violates this policy, work may be paused, access may be terminated, and relevant records may be preserved as reasonably necessary to protect systems, address a dispute or comply with legal obligations.
15. Client responsibility for users
The client remains responsible for the conduct of its employees, contractors, administrators and other users who operate systems configured through the service. Completion of a technical task does not transfer responsibility for the client’s later use of the system.
16. Annual review
This policy is scheduled for review once each year on August 9 and may be updated earlier if the service scope, risk environment or applicable legal requirements materially change.