Terms of Service.

Acceptance of these Terms

By accessing the Loopbacs website, requesting our services, entering into a service engagement or otherwise using Loopbacs services, you acknowledge that you have read and understood these Terms of Service and agree to be bound by the terms applicable to your engagement.

If you are accepting these terms on behalf of a company or organization, you represent that you have authority to bind that organization.

What Loopbacs provides

Loopbacs provides infrastructure-focused technical services, which may include:

• Cloud and infrastructure management.
• Linux/Ubuntu server deployment, configuration, maintenance and troubleshooting.
• Infrastructure security, server hardening and security configuration.
• Firewall, WAF, SSL/TLS and security-monitoring implementation.
• Monitoring and managed infrastructure services.
• Application deployment and DevOps services, including Docker, Nginx and production environment configuration.
• Infrastructure assessment, optimization, migration and technical consulting.

The exact services, deliverables, timelines, support levels and exclusions will depend on the applicable proposal, quotation, statement of work or service agreement.

Your responsibilities

To allow Loopbacs to perform services effectively, the client is responsible for providing accurate information, timely approvals and appropriate access to systems that Loopbacs has been authorized to manage.

• Maintain ownership or lawful authorization for systems, domains, applications and data provided to Loopbacs.
• Provide accurate technical and business requirements.
• Maintain valid third-party subscriptions and licenses unless otherwise agreed.
• Provide timely access, approvals and decisions required for implementation.
• Maintain appropriate backups unless backup services are explicitly included in the engagement.
• Notify Loopbacs of material changes to infrastructure, credentials, applications or security requirements.

System access & credentials

Where infrastructure work requires administrative access, the client authorizes Loopbacs to access only the systems and resources necessary to perform the agreed services.

Clients should use secure credential-sharing methods whenever possible. Loopbacs may recommend SSH keys, restricted accounts, MFA, temporary credentials or other access controls depending on the engagement.

Loopbacs will not intentionally access systems outside the agreed scope without appropriate authorization, except where necessary to investigate a security or operational issue and such access is reasonably connected to the authorized service.

Security services & limitations

Loopbacs applies practical security controls intended to reduce risk, improve visibility and strengthen infrastructure security posture. These may include Linux hardening, SSH protection, firewall controls, WAF configuration, CrowdSec, Wazuh, SSL/TLS and monitoring.

Security services reduce risk but cannot guarantee that a system will never be compromised, attacked, unavailable or affected by vulnerabilities. Clients remain responsible for maintaining appropriate business continuity, backups, application security and access governance unless those responsibilities are explicitly included in the engagement.

Cloud platforms & third-party services

Loopbacs may configure or manage third-party services such as AWS, VPS providers, domain registrars, DNS providers, hosting providers, monitoring platforms, software repositories and other infrastructure tools.

Third-party services are subject to their own terms, pricing, availability, support policies and security practices. Unless expressly agreed otherwise, Loopbacs is not responsible for outages, policy changes, account restrictions, pricing changes or failures caused by third-party providers.

Fees & payment

Fees, payment schedules, recurring charges, taxes and payment terms will be specified in the applicable proposal, quotation, invoice or service agreement.

Unless otherwise agreed, third-party infrastructure, software licenses, domains, hosting, cloud usage and other external costs are separate from Loopbacs professional service fees.

Late or unpaid invoices may result in suspension of non-critical services or support after reasonable notice, subject to the applicable client agreement.

Changes, maintenance & suspension

Infrastructure environments may require maintenance, upgrades, configuration changes or emergency remediation. Loopbacs will make reasonable efforts to communicate planned changes when the engagement requires it.

Loopbacs may temporarily suspend a service where necessary to protect systems, respond to a security incident, address non-payment, comply with law, or prevent misuse of the service.

Intellectual property

Unless otherwise agreed in writing, clients retain ownership of their applications, data, domains, infrastructure accounts and other materials they provide to Loopbacs.

Subject to payment and the applicable agreement, client-specific deliverables created specifically for the client will be handled according to the ownership terms in the relevant proposal or service agreement.

Loopbacs retains ownership of its pre-existing know-how, reusable methods, templates, internal tools, processes, documentation frameworks and general technical expertise unless expressly assigned in writing.

Confidential information

Both parties should protect confidential business, technical and security information received from the other party and use it only for purposes related to the engagement.

Confidentiality obligations generally do not apply to information that is publicly available without breach, was already lawfully known, is independently developed, or must be disclosed by law or valid legal process.

Warranties & limitation of liability

Loopbacs will perform agreed professional services with reasonable care and skill. However, infrastructure and software environments involve inherent operational, security and availability risks, and no specific uptime, security outcome or uninterrupted operation is guaranteed unless expressly stated in a written service-level agreement.

To the maximum extent permitted by applicable law, Loopbacs will not be responsible for indirect, incidental, special, consequential or loss-of-profit damages arising from an engagement, except where such limitation is prohibited by law.

Any specific liability cap, warranty or service-level commitment should be stated in the applicable client agreement.

Ending a service engagement

Either party may terminate a service engagement according to the notice and termination provisions in the applicable agreement. Where no specific provision exists, the parties should provide reasonable written notice and cooperate to transition access, documentation and operational responsibilities.

Fees for services already performed and approved third-party costs incurred before termination remain payable unless otherwise agreed.

Governing law & disputes

The governing law, jurisdiction and dispute-resolution process should be defined in the applicable Loopbacs client agreement. If these Terms are used as a standalone agreement, the final version should identify the legal entity operating Loopbacs and the applicable jurisdiction after legal review.

Questions about these Terms?