SparkOS · 2.0

Support and Incident Response Policy

Channels and coverage

The approved Service Schedule identifies ticket and emergency channels, coverage hours, languages and escalation contacts for each plan and is displayed before acceptance. Round-the-clock support is not assumed unless specified. The Clinic supplies impact, start time and a redacted example without unnecessary patient data.

Incident classification

Critical incidents include total outage, data loss, unauthorised access or material disruption without a workaround. High incidents affect a core function with a limited workaround. Medium incidents have limited impact and a practical workaround. Low incidents are inquiries or improvements. When classification is disputed and data is at risk, the higher level applies provisionally pending the service owner’s documented determination.

Response, resolution and updates

Response, update and containment times for each severity are specified in the Service Schedule. Timing starts at Company detection or receipt of the report, whichever occurs first, and uses disclosed coverage hours. Response means a specialist taking ownership, not an automated reply. The Schedule distinguishes binding commitments from estimated restoration targets. Data-breach notification deadlines do not pause for customer responses or office closure. Genuine customer-dependent delays are documented together with mitigation.

Availability and maintenance

Where a plan includes an availability commitment, monthly availability equals eligible minutes less downtime, divided by eligible minutes. Downtime includes documented login or core-function failure. The Schedule defines the excluded maintenance allowance, notice, measurement and credits. Hosting failures are not excluded merely because the provider is external. Emergency or excess maintenance is not excluded unless expressly and lawfully agreed in the accepted Schedule.

Escalation and remedies

Incidents escalate when deadlines are missed or impact increases through the approved escalation contacts. The Company reports material-incident causes, correction and prevention. Plan credits apply where specified and are not the sole remedy for data breaches or liability that cannot lawfully be restricted. A support ticket does not replace a separate privacy incident notification.