Hybytes

Acceptable Use Policy

Rules for using Hybytes-provided or Hybytes-managed systems

Last updated:

27 August 2026

Introduction

This Acceptable Use Policy sets out the rules that apply when you or your users access any system, tool, environment, or portal that Hybytes Ltd provides or manages as part of an engagement, including our support ticketing system, shared Git repositories and CI/CD pipelines (for example, GitLab), monitoring dashboards, and any AWS account, Kubernetes cluster, or other production environment where Hybytes personnel operate with access credentials you have granted. It forms part of our Terms of Business.

1. Who this applies to

This policy applies to the Client, its employees, contractors, and any other person the Client authorises to interact with Hybytes-provided systems or with environments Hybytes manages on the Client's behalf ("Users"). The Client is responsible for its Users' compliance with this policy.

2. Acceptable use

  • Systems and access provided as part of an engagement must be used only for purposes connected to that engagement. Users must not:
    • Use any system to store, transmit, or process unlawful content, or content that infringes a third party's rights.
    • Attempt to gain unauthorised access to any system, account, or data outside the scope of the engagement.
    • Probe, scan, or test the vulnerability of any Hybytes or client system without prior written agreement, except as part of agreed security testing work.
    • Introduce malware, or knowingly transmit any code designed to disrupt, damage, or gain unauthorised access to a system.
    • Share access credentials with anyone not authorised under the engagement, or circumvent access controls.
    • Use the access provided to compete with Hybytes or to solicit Hybytes personnel outside the terms agreed between the parties.

3. Access to production and client environments

Where Hybytes personnel are granted access to a Client's AWS accounts, Kubernetes clusters, databases, or CI/CD systems as part of Managed Services, DevOps Support, SRE, or migration work, that access is used strictly for the purposes described in the applicable Statement of Work.

Hybytes follows the principle of least-privilege access, uses temporary or role-based credentials (for example, AWS IAM roles) in preference to long-lived keys wherever the environment supports it, and will remove or rotate credentials at the end of an engagement, or sooner on request.

4. Meetings and media

These rules apply to meetings and calls between the Client and Hybytes personnel during an engagement.

  • Recording: The Client will not record a meeting without the explicit consent of Hybytes; Hybytes personnel may decline to have a meeting recorded.
  • Cameras: Hybytes personnel are not obliged to turn on their cameras during meetings; this is at their discretion.
  • Photographs: The Client will not request or use a photograph of Hybytes personnel, including on social media or any other public or private platform, without their explicit consent.
  • Screen sharing: Hybytes personnel are not obliged to share their screen where doing so would display personal or professional data, or systems that could be vulnerable to exploitation, and may decline to do so to protect sensitive information.

5. Reporting misuse or security issues

If you become aware of misuse of a Hybytes-managed system, or of a security vulnerability, please report it promptly through our contact form. See our Vulnerability Disclosure Policy in the Security Overview for how we handle reports.

6. Enforcement

Hybytes may suspend or restrict access for a User who breaches this policy, and will notify the Client promptly where practical. Serious or repeated breaches may be treated as a material breach of the Terms of Business.