Operational policy
Acceptable use
Effective 23 August 2026
1. Approval before access
Phone-farm, cloud-device and related managed-device services require manual business approval before provisioning. We may request identity, company, ownership, billing and intended-use information as part of know-your-customer and risk checks. Approval is specific to the organisation and use case described; it is not transferable.
2. Permitted uses
Approved services may be used for legitimate social-media publishing and management across owned or authorised accounts, content scheduling and review, campaign monitoring, quality assurance, app and website testing, accessibility and localisation checks, controlled fleet staging, device-compatibility validation and closely related internal business workflows. Testing and automation must use accounts, content, networks and systems that you own or are authorised to use.
3. Prohibited conduct
You must not use the services for fake engagement or metrics, advertising fraud, account farming, spam or unsolicited messaging, credential theft or abuse, evasion of access controls or platform enforcement, malware, destructive activity or unauthorised surveillance. You must not impersonate another person, falsify provenance or coordinate deceptive activity.
4. Networks, SIMs and communications
You must not resell, share or broker SIM access, SMS or OTP receipt, mobile data, device connectivity or telecommunications capability. You must not alter, replace or edit supplied proxy or VPN settings, route third-party traffic through the service, or use the service to bypass geographic, identity, rate or security controls.
5. Law, rights and platform rules
You must not use the services for illegal activity or to infringe privacy, intellectual-property, contractual or other rights. You are responsible for ensuring your instructions, test materials and use of third-party platforms are authorised and comply with applicable platform rules.
6. Sessions and customer data
Use dedicated test accounts and the minimum data needed for the approved task. Do not enter production secrets, unrelated personal data or payment credentials unless the accepted quote expressly covers that controlled test. You are responsible for signing out and removing your test data at the end of a session. We may end sessions, isolate devices and reset or sanitise devices to protect customers and the service.
7. Monitoring and enforcement
We use account, device, session and security metadata to operate and protect the service; operational logs are designed to exclude screens, keystrokes and customer content. Where misuse is suspected, we may pause or suspend access, quarantine a device or session, preserve relevant security records, request more information, reject an order or terminate service. We may report activity where legally required.
8. Questions and policy status
This is an operational use policy incorporated into applicable VyrexCode orders and terms. It is not legal advice tailored to your organisation. Contact supportvyrexcode.com before ordering if a proposed workflow is unclear.