Cancellation policy

Last Updated: June 24, 2026

At Vortex LLC, we dedicate significant engineering capacity, scheduling slots, and cloud infrastructure resources to each of our corporate engagements. This Cancellation Policy outlines the structured protocols and notice periods required to modify, pause, or terminate active projects and recurring technical services.

1. Recurring Managed Services & Support tiers

For clients utilizing our Technical Support, continuous security patching, or proactive infrastructure monitoring plans:

  • Notice Period: To terminate a recurring monthly support agreement, you must submit a formal written cancellation request at least 30 days prior to your subsequent scheduled billing cycle.

  • Final Month Delivery: Following your cancellation notice, your assigned support engineers will continue to manage your infrastructure, address ticket queues, and track system health until the end of the final, paid billing cycle.

  • Annual Contracts: Annual support agreements are committed for the full 12-month duration. Early cancellation requests during an active annual term will stop future automated renewals but are not eligible for a prorated refund of the remaining months.

2. Project-Based Engineering Contracts

For active software development sprints, API integration tracks, or custom CRM/Cloud deployments governed by a Statement of Work (SOW):

  • Termination for Convenience: Either party may opt to terminate an active project by providing written notice as specified in your Master Services Agreement (MSA)—typically 14 to 30 business days.

  • Invoicing upon Cancellation: Upon receipt of a project cancellation notice, Vortex LLC will immediately cease all forward-looking feature development. The client will be invoiced for all verified engineering hours logged, milestone tasks completed, and resource expenditures incurred up to the official termination date.

  • Offboarding Artifacts: Upon settlement of the final cancellation invoice, all partially completed source code, system configuration files, and architectural schematics built during the project will be pushed to your repository and turned over to your internal team.

3. Scheduled Strategy & Consulting Sessions

For dedicated architecture audits, technical consulting sessions, or engineering kickoff workshops:

  • Rescheduling: If your internal team needs to delay or reschedule a booked technical strategy session, you must notify your designated account lead at least 48 hours before the scheduled meeting time.

  • Late Cancellations: Consulting workshops or dedicated architecture reviews cancelled or rescheduled with less than 48 hours’ notice will incur a late cancellation fee equal to 50% of the session’s billable value, compensating for unutilized developer scheduling blocks.

4. Immediate Termination for Breach

Vortex maintains strict compliance, data security, and operational standards. We reserve the right to suspend development keys or terminate any service agreement immediately and without notice under exceptional circumstances, including:

  • Discovery of malicious software, structural vulnerabilities, or illegal materials knowingly hosted or introduced into the code repositories by client-side personnel.

  • Material breach of contract terms, including non-payment of undisputed invoices extending beyond 45 days.

  • Unauthorized attempts to reverse-engineer, compromise, or breach proprietary internal engineering infrastructure used by Vortex to monitor service layers.

5. How to Initiate a Cancellation

To officially request the cancellation or restructuring of an active project track, recurring maintenance tier, or dedicated developer retainer, your primary account holder must submit a request directly through our channels:

  • Email: support@vorteeex.com