This agreement supplements the general Terms of Service and governs activation, installation, continuous operation, support, and operational continuity for purchased services.
Current version: March 11, 2026
The exact scope depends on the purchased plan, accepted proposal, and approved integrations. IreClaw operates the infrastructure, runtime, memory, automations, support, and monitoring within the contracted scope.
Activation requires confirmed payment and sufficient onboarding data to configure the service. IreClaw performs the installation and launch; only approvals required by external platforms or missing client data may affect timelines.
Integrations, channels, APIs, and automations are activated according to the plan, scope, and applicable approvals. IreClaw manages the technical and operational layer of the service. Sensitive changes or extraordinary spend may require additional internal validation before execution.
The IreClaw operational CRM acts as the system of record for notes, incidents, deployments, and follow-up. Support, renewals, recovery work, and expansions may generate new commercial or operational actions inside the system.
IreClaw does not control third-party outages, policy changes on external platforms, API blocks, vendor delays, or the quality of data provided by the client. Those factors may affect operations, timing, or outcomes.
By checking the acceptance box before payment or activation, the client accepts these conditions together with the general Terms of Service, the applicable commercial proposal, and the restrictions of the purchased plan.
This agreement supplements the general Terms of Service and governs activation, installation, continuous operation, support, and operational continuity for purchased services.
Current version: March 11, 2026
The exact scope depends on the purchased plan, accepted proposal, and approved integrations. IreClaw operates the infrastructure, runtime, memory, automations, support, and monitoring within the contracted scope.
Activation requires confirmed payment and sufficient onboarding data to configure the service. IreClaw performs the installation and launch; only approvals required by external platforms or missing client data may affect timelines.
Integrations, channels, APIs, and automations are activated according to the plan, scope, and applicable approvals. IreClaw manages the technical and operational layer of the service. Sensitive changes or extraordinary spend may require additional internal validation before execution.
The IreClaw operational CRM acts as the system of record for notes, incidents, deployments, and follow-up. Support, renewals, recovery work, and expansions may generate new commercial or operational actions inside the system.
IreClaw does not control third-party outages, policy changes on external platforms, API blocks, vendor delays, or the quality of data provided by the client. Those factors may affect operations, timing, or outcomes.
By checking the acceptance box before payment or activation, the client accepts these conditions together with the general Terms of Service, the applicable commercial proposal, and the restrictions of the purchased plan.
