Service Level Agreement

### Purpose of This Agreement

This Service Level Agreement ("SLA") defines the service availability commitments, performance standards, support obligations, and remediation measures that CryptoMize ("Company," "we," "us," or "our") provides to clients ("Client," "you," or "your") utilizing the Perception X2 autonomous perception amplification engine and all associated tools, dashboards, APIs, and services (collectively, the "Platform"). This SLA forms an integral part of your service agreement and outlines the specific guarantees upon which you can rely when operating on the Platform.

### Scope of Commitments

The commitments contained in this SLA apply to all production environments, managed services, and core Platform functionality. They reflect CryptoMize's dedication to maintaining the highest standards of availability, reliability, and responsiveness in the perception intelligence industry. Whether you are leveraging Perception X2 for reputation monitoring, narrative engineering, crisis response, content intelligence, or analytics, this SLA ensures that your operations are backed by measurable, enforceable guarantees.

### Relationship to Other Agreements

This SLA should be read in conjunction with the Terms of Service, Privacy Policy, Security Policy, and any applicable service order forms or statements of work. In the event of a conflict between this SLA and the Terms of Service, the terms more favorable to the Client shall govern with respect to service availability and performance commitments. Any custom SLA terms negotiated in a master services agreement shall supersede the provisions of this SLA for the duration of that agreement.

### Commitment Philosophy

CryptoMize operates on the principle that trust is earned through accountability. This SLA is not a marketing document. It is a binding commitment backed by financial remedies, transparent reporting, and continuous improvement processes. We believe that the strength of our service guarantees directly reflects the confidence we have in our infrastructure, our engineering teams, and our operational excellence.

---

For the purposes of this Service Level Agreement, the following definitions apply:

**"Available"** means the Platform is operational and accessible via standard API calls and user interfaces, with all core functions responding within published performance thresholds. A period is considered Available even if intermittent errors occur, provided the error rate does not exceed the thresholds defined in Section 4.

**"Downtime"** means any period during which the Platform is not Available to the Client, excluding Scheduled Maintenance and the exclusions listed in Section 15. Downtime is measured from the moment a service disruption is confirmed by our monitoring systems to the moment full service is restored.

**"Scheduled Maintenance"** means pre-announced maintenance windows during which the Platform may be temporarily unavailable or operating in degraded mode. Scheduled Maintenance is planned in advance and communicated in accordance with Section 5.

**"Uptime Percentage"** means the total minutes in a measurement period minus Downtime minutes, divided by total minutes in the period, expressed as a percentage. The formula is detailed in Section 4.

**"Incident"** means any unplanned interruption, reduction in quality, or failure of a component of the Platform that affects Client operations and is not caused by Scheduled Maintenance or exclusions under Section 15.

**"Response Time"** means the elapsed time between an Incident being reported (or automatically detected) and the first substantive acknowledgment or action by CryptoMize support or engineering personnel.

**"Resolution Time"** means the elapsed time between Incident detection and the restoration of full service functionality.

**"Service Credit"** means a percentage-based credit applied to the Client's next invoice as compensation for failure to meet the uptime or response time commitments specified in this SLA.

**"Measurement Period"** means a calendar month unless otherwise specified, during which Platform performance is tracked and evaluated against SLA commitments.

**"Critical Path Functionality"** means core Platform features including API access, dashboard rendering, data ingestion pipelines, analytics processing, and alert delivery systems.

---

### Uptime Guarantee

CryptoMize guarantees that the Perception X2 Platform will maintain a minimum uptime of 99.9999% during each Measurement Period, equivalent to no more than 26 seconds of cumulative Downtime per calendar month. This guarantee applies to all Critical Path Functionality across all production environments and represents one of the most stringent availability commitments in the perception intelligence industry.

### Availability Targets by Service Component

| Component | Monthly Uptime Target | Max Downtime per Month | |---|---|---| | Core API Gateway | 99.9999% | ~26 seconds | | Dashboard & User Interface | 99.999% | ~2.6 minutes | | Data Ingestion Pipelines | 99.9999% | ~26 seconds | | Analytics Engine | 99.999% | ~2.6 minutes | | Alert & Notification System | 99.9999% | ~26 seconds | | Reporting Module | 99.999% | ~2.6 minutes | | Authentication & Access Control | 99.9999% | ~26 seconds |

### Multi-Region Redundancy

The Platform operates across geographically distributed infrastructure with automatic failover capabilities. Our architecture is designed so that no single point of failure can cause a breach of the availability commitment. Data replication occurs in real-time across multiple availability zones, and traffic is automatically rerouted in the event of a regional disruption. This multi-layered approach to redundancy is what enables us to offer near-zero downtime guarantees with confidence.

### Monitoring and Enforcement

Uptime is monitored continuously by independent monitoring systems that probe Platform endpoints from multiple global locations at sub-second intervals. These systems provide objective, verifiable measurement data that forms the basis for all SLA calculations. Clients receive real-time access to uptime dashboards, ensuring complete transparency into Platform availability at all times.

---

### Measurement Framework

Platform uptime is calculated using a comprehensive, transparent methodology designed to provide objective and verifiable results. The calculation begins at the start of each Measurement Period (the first second of the first day of each calendar month) and ends at the last second of the final day of that month. All times are referenced to Coordinated Universal Time (UTC) to eliminate ambiguity across time zones.

### The Uptime Formula

The Uptime Percentage for any given Measurement Period is calculated as follows:

**Uptime Percentage = ((Total Minutes - Downtime Minutes) / Total Minutes) x 100**

Where:

- **Total Minutes** equals the total number of minutes in the Measurement Period. - **Downtime Minutes** equals the cumulative number of minutes during which the Platform was not Available, as measured by our monitoring systems and confirmed through incident records.

### Measurement Methodology

Uptime is assessed through a combination of continuous synthetic monitoring and real-user telemetry. Synthetic monitors execute critical user workflows against production endpoints from multiple global vantage points every five seconds. Real-user telemetry captures actual API response times, error rates, and throughput metrics from live Client sessions. Both data streams feed into our SLA calculation engine, which produces a unified availability score for each Measurement Period.

### Excluded Time

The following periods are excluded from uptime calculations: Scheduled Maintenance windows announced in advance per Section 5, Downtime caused by Client actions or third-party systems outside CryptoMize's control, force majeure events under Section 16, and periods during which the Client has been notified of a configuration issue that CryptoMize has recommended resolving.

### Dispute Resolution

If a Client believes the Uptime Percentage has been miscalculated, they may submit a written dispute within thirty (30) days of receiving the monthly SLA report. CryptoMize will review all monitoring data, incident logs, and system records to resolve the dispute within fifteen (15) business days. If the dispute reveals a material miscalculation, the Client's account will be adjusted accordingly, including retroactive Service Credits where applicable.

---

### Maintenance Philosophy

CryptoMize performs Scheduled Maintenance to ensure the continued reliability, security, and performance of the Platform. We recognize that maintenance activities carry inherent risks to availability, and we have developed rigorous procedures to minimize impact on Client operations while maintaining the highest standards of Platform integrity.

### Notification Requirements

All Scheduled Maintenance must be announced at least seventy-two (72) hours in advance through the following channels: email notification to all registered account administrators, in-dashboard alert banners, API status endpoint updates, and direct notification to designated Client technical contacts for Enterprise-tier accounts. The notice will include the planned start and end times, expected impact on services, and any actions Clients should take.

### Standard Maintenance Windows

| Maintenance Type | Frequency | Maximum Duration | Notification Period | |---|---|---|---| | Security Patches | As needed | 30 minutes | 72 hours | | Infrastructure Upgrades | Monthly | 2 hours | 7 days | | Database Optimization | Monthly | 1 hour | 7 days | | Major Version Releases | Quarterly | 4 hours | 14 days | | Network Configuration | Quarterly | 2 hours | 14 days |

### Maintenance Execution

During Scheduled Maintenance, CryptoMize will: deploy maintenance activities within the declared window, monitor all services continuously throughout the process, provide real-time status updates via the status dashboard, and confirm completion through all notification channels. If maintenance extends beyond the declared window by more than fifteen (15) minutes, an additional notification will be issued immediately, and the extended period will be treated as unscheduled Downtime for SLA calculation purposes.

### Client Preparation

Clients are encouraged to review maintenance notices and adjust their workflows accordingly. For Enterprise-tier accounts, CryptoMize offers pre-maintenance consultation to assess potential impacts on custom integrations and mission-critical workflows. Documentation for all maintenance activities is published in the knowledge base within forty-eight (48) hours of completion.

---

### Incident Detection

CryptoMize employs a multi-layered monitoring architecture that detects unscheduled Downtime and service disruptions through automated synthetic monitoring, real-time infrastructure health checks, Client-reported issues, and anomaly detection powered by machine learning. Our monitoring systems operate across all critical service components with sub-second detection intervals, ensuring that disruptions are identified within seconds of occurrence.

### Incident Response Framework

Upon detection of an Incident, the following response framework is activated:

1. **Automated Detection** (0-2 minutes): Monitoring systems detect anomalies and trigger automated alerts to the on-call engineering team. 2. **Triage and Acknowledgment** (2-15 minutes): On-call engineers assess severity, confirm the Incident, and begin response procedures. Clients are notified automatically through all registered communication channels. 3. **Containment** (15-60 minutes): Engineering teams isolate the affected components to prevent propagation and stabilize remaining services. 4. **Resolution** (Variable based on severity): Teams work to restore full service functionality, with progress updates provided at defined intervals based on severity classification. 5. **Post-Incident Review** (Within 48 hours): A comprehensive root cause analysis is completed and shared with affected Clients.

### Communication During Incidents

During any unscheduled Downtime event, CryptoMize commits to providing real-time status updates every fifteen (15) minutes for Severity 1 Incidents, every thirty (30) minutes for Severity 2 Incidents, and every sixty (60) minutes for Severity 3 Incidents. These updates are delivered through the status dashboard, email notifications, and the API status endpoint. A detailed post-incident report is provided within forty-eight (48) hours of resolution.

---

### Tier Overview

CryptoMize offers four distinct Service Level Tiers, each designed to align with different operational requirements, risk tolerances, and support expectations. Clients select their tier during onboarding and may upgrade at any time, with changes taking effect within twenty-four (24) hours.

### Tier Comparison

| Feature | Standard | Professional | Enterprise | Sovereign | |---|---|---|---|---| | Monthly Uptime Guarantee | 99.99% | 99.999% | 99.9999% | 99.9999% | | Max Monthly Downtime | ~4.3 minutes | ~26 seconds | ~26 seconds | ~26 seconds | | Response Time (Sev 1) | 30 minutes | 15 minutes | 5 minutes | Immediate | | Response Time (Sev 2) | 2 hours | 1 hour | 30 minutes | 15 minutes | | Response Time (Sev 3) | 8 hours | 4 hours | 2 hours | 1 hour | | Dedicated Account Manager | No | No | Yes | Yes | | 24/7 Support Access | No | Yes | Yes | Yes | | Dedicated Infrastructure | No | No | No | Yes | | Custom SLA Terms | No | No | Yes | Yes | | On-Site Support Available | No | No | No | Yes | | Service Credit Maximum | 10% | 15% | 25% | 30% |

### Tier Selection Guidance

Standard tier is designed for teams with flexible operational windows and moderate availability requirements. Professional tier serves organizations that require extended support hours and faster incident response. Enterprise tier delivers the highest standard of availability and support, with dedicated resources and customizable terms. Sovereign tier provides the ultimate level of protection, including dedicated infrastructure, custom SLA terms, and immediate response commitments for organizations with zero-tolerance operational requirements.

### Tier Upgrades

Clients may upgrade their Service Level Tier at any time by contacting their Account Manager or submitting a request through the Platform. Upgrades take effect within twenty-four (24) hours and are prorated for the remainder of the current billing cycle. Downgrades require thirty (30) days written notice and take effect at the start of the next billing cycle.

---

### Response Time Commitments

CryptoMize commits to specific response times based on the Client's Service Level Tier and the severity of the reported Incident. Response Time is measured from the moment an Incident is reported or automatically detected to the moment a qualified support or engineering professional provides a substantive initial response that acknowledges the issue and outlines the next steps.

### Response Time Matrix

| Severity | Standard | Professional | Enterprise | Sovereign | |---|---|---|---|---| | Severity 1 (Critical) | 30 minutes | 15 minutes | 5 minutes | Immediate | | Severity 2 (High) | 2 hours | 1 hour | 30 minutes | 15 minutes | | Severity 3 (Medium) | 8 hours | 4 hours | 2 hours | 1 hour | | Severity 4 (Low) | 24 hours | 12 hours | 8 hours | 4 hours |

### Response Quality Standards

An initial response must include: acknowledgment of the reported Incident, the assigned severity classification, the name or identifier of the assigned engineer, an initial assessment of scope and impact, and a commitment to the next update timeframe. Responses that do not meet these criteria do not count as substantive responses for SLA purposes.

### Support Channels

Clients may report Incidents through multiple channels: the Platform's built-in incident reporting system, dedicated support email, phone support (Professional tier and above), secure messaging portal (Enterprise and Sovereign tiers), and direct escalation to their named Account Manager (Enterprise and Sovereign tiers). All channels are monitored during the hours specified by the Client's Service Level Tier.

---

### Classification Framework

Incidents are classified into four severity levels based on their impact on Client operations, the breadth of affected users, and the criticality of the affected Platform components. Accurate classification ensures that resources are allocated proportionally and that response priorities align with Client business needs.

### Severity Definitions

| Severity | Definition | Impact | Example | |---|---|---|---| | Severity 1 (Critical) | Complete loss of Critical Path Functionality with no workaround available | Platform unusable for all or substantially all users | API gateway failure, authentication system outage, data ingestion pipeline complete stoppage | | Severity 2 (High) | Major degradation of Critical Path Functionality with limited workaround | Significant impact on core operations for a substantial portion of users | Dashboard rendering failures, analytics engine degradation, alert delivery delays exceeding 30 minutes | | Severity 3 (Medium) | Moderate impact on non-critical functionality or degraded performance of critical features | Noticeable but manageable impact on operations; workarounds available | Slow report generation, minor UI rendering issues, non-critical API endpoints returning errors | | Severity 4 (Low) | Minor issues with minimal impact on operations | Cosmetic or documentation issues; no functional impact | UI alignment issues, typographical errors in documentation, minor performance variances within normal ranges |

### Severity Override by Client

Enterprise and Sovereign tier Clients may request an escalation of severity classification for specific Incidents that they consider more impactful than the initial assessment indicates. CryptoMize will review such requests within thirty (30) minutes and adjust the classification if the Client's assessment is supported by the evidence. This override mechanism ensures that Client business context is factored into incident prioritization.

---

### Escalation Framework

CryptoMize employs a structured escalation framework designed to ensure that Incidents receive appropriate attention and resources as they progress. Escalation is both automatic, triggered by response time thresholds, and manual, initiated by the Client or support personnel based on evolving circumstances.

### Automatic Escalation Matrix

| Escalation Level | Trigger | Authority | Response | |---|---|---|---| | Level 1 | Initial response threshold breached | Support Manager | Immediate resource allocation | | Level 2 | 2x initial response threshold or no progress after 1 hour | Engineering Director | Dedicated engineering team assigned | | Level 3 | 4x response threshold or cross-service impact confirmed | VP of Engineering | Full engineering mobilization | | Level 4 | Sev 1 unresolved after 2 hours | Chief Technology Officer | Executive intervention, all resources |

### Client-Initiated Escalation

Clients may initiate an escalation at any time by contacting their Account Manager, calling the dedicated escalation hotline (available for Enterprise and Sovereign tiers), or submitting an escalation request through the Platform. All Client-initiated escalations are reviewed and actioned within fifteen (15) minutes during supported hours, and within thirty (30) minutes outside supported hours.

### Post-Escalation Review

Every escalation triggers a mandatory post-escalation review within forty-eight (48) hours of resolution. This review examines the root cause, the effectiveness of the escalation process, and any systemic improvements required to prevent recurrence. Findings are documented and, where material, incorporated into the Client's quarterly review reports.

---

### Credit Eligibility

Service Credits are the Client's exclusive financial remedy for CryptoMize's failure to meet the uptime or response time commitments specified in this SLA. Credits are automatically calculated and applied to the Client's next invoice when the applicable commitment is not met, provided the Downtime was not caused by exclusions listed in Section 15 or force majeure events under Section 16.

### Credit Calculation

| Monthly Uptime | Credit Percentage | |---|---| | 99.999% to 99.9999% | 5% of monthly service fees | | 99.99% to 99.999% | 10% of monthly service fees | | 99.9% to 99.99% | 15% of monthly service fees | | Below 99.9% | 25% of monthly service fees | | Below 99% | 30% of monthly service fees + Termination Right |

### Response Time Credit

| Severity | Missed Response Time | Credit | |---|---|---| | Severity 1 | Response exceeds 2x committed time | 10% of monthly service fees | | Severity 2 | Response exceeds 2x committed time | 5% of monthly service fees | | Severity 3 | Response exceeds 2x committed time | 2% of monthly service fees |

### Credit Limits and Procedures

Total Service Credits in any Measurement Period shall not exceed thirty percent (30%) of the Client's monthly service fees for that period, except for Sovereign-tier accounts where no cap applies. Credits must be claimed within sixty (60) days of the Incident by submitting a credit request through the Platform or to the designated Account Manager. Credits are non-transferable and have no cash value. Unused credits do not accumulate or roll forward to subsequent periods.

---

### Monitoring Infrastructure

CryptoMize maintains a comprehensive monitoring infrastructure that provides real-time visibility into Platform performance across all service components. Our monitoring stack encompasses synthetic transaction monitoring, application performance monitoring, infrastructure health checks, database performance tracking, network latency measurement, and end-user experience monitoring. This multi-dimensional approach ensures that performance degradation is detected and addressed before it impacts Client operations.

### Key Performance Indicators

| Metric | Target | Measurement Frequency | |---|---|---| | API Response Time (p50) | < 100ms | Continuous | | API Response Time (p99) | < 500ms | Continuous | | API Response Time (p99.9) | < 1000ms | Continuous | | Dashboard Load Time | < 2 seconds | Continuous | | Data Ingestion Latency | < 30 seconds | Continuous | | Alert Delivery Latency | < 60 seconds | Continuous | | Error Rate (API) | < 0.01% | Hourly | | Throughput Capacity | > 10,000 req/sec | Daily |

### Client-Facing Dashboards

All monitoring data is accessible to Clients through the Platform's performance dashboard, which provides real-time and historical views of all KPIs. Clients can configure custom alerts based on performance thresholds, generate performance reports, and export data for internal analysis. Enterprise and Sovereign tier Clients receive access to enhanced dashboards with granular per-endpoint metrics and custom metric tracking.

### Continuous Improvement

Performance data is analyzed monthly by our engineering team to identify optimization opportunities, capacity planning requirements, and architectural improvements. Insights from this analysis are incorporated into the Platform's development roadmap and shared with Clients during quarterly business reviews. This commitment to continuous improvement ensures that Platform performance consistently exceeds published targets.

---

### Backup Architecture

CryptoMize employs a multi-tiered backup architecture designed to protect Client data against loss, corruption, and disaster. All Client Data is backed up continuously using a combination of real-time replication, incremental snapshots, and full backups. Our backup infrastructure is geographically distributed, ensuring that Client data remains available even in the event of a regional catastrophe.

### Recovery Objectives

| Metric | Target | Measurement | |---|---|---| | Recovery Point Objective (RPO) | < 5 minutes | Maximum data loss in failure event | | Recovery Time Objective (RTO) | < 15 minutes | Maximum time to restore service | | Backup Retention | 90 days | Rolling retention window | | Backup Integrity Verification | Daily | Automated checksum validation |

### Disaster Recovery

CryptoMize maintains a comprehensive disaster recovery plan that is tested quarterly through full-scale simulations. The disaster recovery plan covers all service components and includes failover procedures, data restoration processes, communication protocols, and return-to-normal operations. Test results are documented and reviewed by senior leadership, with any identified gaps addressed before the next test cycle.

### Data Sovereignty

Client Data is stored in the geographic regions specified in the Client's service agreement. CryptoMize does not transfer Client Data across jurisdictional boundaries without explicit Client authorization. All backup data is encrypted at rest using AES-256 encryption and in transit using TLS 1.3, with encryption keys managed through a hardware security module (HSM) infrastructure that meets FIPS 140-2 Level 3 standards.

---

### Status Dashboard

CryptoMize maintains a publicly accessible status dashboard that provides real-time information on Platform availability, performance, and ongoing incidents. The status dashboard is updated continuously by automated monitoring systems and supplemented by human updates during active Incidents. It serves as the single source of truth for Platform health status and is hosted independently from the Platform to remain accessible during any service disruption.

### Communication Channels

| Channel | Purpose | Availability | |---|---|---| | Status Dashboard | Real-time Platform status | 24/7/365 | | Email Notifications | Incident alerts, maintenance notices | 24/7/365 | | API Status Endpoint | Programmatic status checks | 24/7/365 | | In-Dashboard Banners | Active incident notifications | 24/7/365 | | Account Manager (Enterprise) | Direct communication | Business hours + on-call | | Quarterly Business Reviews | Performance reviews, roadmap | Per schedule |

### Monthly SLA Reports

At the end of each Measurement Period, CryptoMize generates a comprehensive SLA report for each Client. This report includes: detailed uptime statistics for all service components, response time performance against committed targets, incident summaries with root cause analyses, Service Credit calculations (if applicable), and recommendations for operational improvements. Reports are delivered electronically and archived in the Client's account portal for historical reference.

### Proactive Communication

Beyond reactive incident communication, CryptoMize proactively communicates with Clients regarding: upcoming maintenance windows and their expected impact, platform improvements and new feature releases, security advisories and recommended actions, capacity planning updates and scaling recommendations, and changes to SLA terms with appropriate advance notice.

---

### General Exclusions

The following events and conditions are excluded from SLA calculations and do not give rise to Service Credit obligations:

**Client-Caused Downtime:** Downtime resulting from Client actions, including but not limited to: misconfiguration of the Platform, exceeding allocated resource limits, using the Platform in a manner inconsistent with documentation, or failure to implement recommended security practices.

**Third-Party Dependencies:** Downtime caused by failures in third-party services, internet service providers, domain name system (DNS) providers, content delivery networks, or other external systems outside CryptoMize's reasonable control.

**Pre-Authorized Maintenance:** Downtime occurring during Scheduled Maintenance windows announced in accordance with Section 5, provided the maintenance was completed within the declared window.

**Beta and Preview Features:** Any downtime or performance degradation affecting features designated as "Beta," "Preview," or "Experimental" in the Platform, as these features are provided without SLA guarantees.

**Force Majeure Events:** Downtime caused by events listed in Section 16, including natural disasters, government actions, and other events beyond CryptoMize's reasonable control.

### Limitations

Exclusions are applied narrowly and in good faith. CryptoMize will not invoke exclusions to avoid legitimate SLA obligations. Any disputed exclusion will be resolved through the dispute process outlined in Section 4. CryptoMize commits to maintaining detailed records that substantiate any exclusion claim, and these records will be made available to Clients upon request within a reasonable timeframe.

---

### Definition

A Force Majeure event is any circumstance beyond the reasonable control of CryptoMize that prevents or delays the performance of its obligations under this SLA. Force Majeure events include, but are not limited to: natural disasters such as earthquakes, hurricanes, floods, and volcanic activity; pandemic or epidemic conditions; war, terrorism, civil unrest, or insurrection; government actions, sanctions, embargoes, or regulatory changes; widespread internet or telecommunications failures not attributable to CryptoMize; cyberattacks of a scale and sophistication that could not reasonably be anticipated or prevented; and utility failures beyond the control of CryptoMize's infrastructure providers.

### Obligations During Force Majeure

When a Force Majeure event occurs, CryptoMize will: use commercially reasonable efforts to mitigate the impact on Client services, provide prompt notification of the Force Majeure event and its expected duration, resume performance as soon as reasonably practicable, and provide regular updates on restoration progress. CryptoMize will not be liable for Service Credits during a confirmed Force Majeure event, but will apply best efforts to minimize disruption.

### Notification and Duration

CryptoMize will notify affected Clients within twenty-four (24) hours of determining that a Force Majeure event is affecting Platform availability. If a Force Majeure event continues for more than thirty (30) consecutive days, either party may terminate the affected services without penalty, provided that thirty (30) days written notice is given.

---

### Right to Modify

CryptoMize reserves the right to modify, update, or enhance the Platform and its associated services to improve performance, security, functionality, and compliance. Such modifications may include infrastructure changes, software updates, feature additions or removals, and changes to service architecture.

### Notification of Material Modifications

For modifications that materially affect the Client's use of the Platform or the service levels specified in this SLA, CryptoMize will provide: at least sixty (60) days advance notice for changes to uptime commitments, at least thirty (30) days advance notice for changes to support response times, at least thirty (30) days advance notice for changes to monitoring or reporting systems, and at least fourteen (14) days advance notice for changes to API endpoints or data formats.

### Client Options

When a material modification is proposed, Clients will have the option to: accept the modification and continue using the Platform under the updated terms, request a transition period to adjust to the modification, or terminate the affected service without penalty if the modification materially impairs the Client's use of the Platform. These options ensure that Clients retain control over their relationship with the Platform.

### Backward Compatibility

CryptoMize is committed to maintaining backward compatibility wherever practicable. Deprecated features will be supported for a minimum transition period of ninety (90) days following announcement. During this transition period, both the legacy and updated functionality will be available, and Clients will receive detailed migration documentation and support.

---

### Monthly SLA Reports

CryptoMize generates comprehensive SLA performance reports at the conclusion of each Measurement Period. These reports are delivered to all active Clients within five (5) business days of the period's end. Each report includes detailed uptime statistics, response time performance metrics, incident summaries, Service Credit calculations (where applicable), and trend analysis comparing current performance against historical baselines.

### Quarterly Business Reviews

Enterprise and Sovereign tier Clients receive quarterly business reviews conducted by their dedicated Account Manager and a senior member of the engineering team. These reviews cover: comprehensive SLA performance analysis, Platform utilization trends and optimization recommendations, roadmap preview of upcoming features and improvements, feedback collection and action item tracking, and strategic alignment discussions.

### Annual SLA Review

CryptoMize conducts a formal annual review of this SLA to ensure that commitments remain aligned with industry best practices, technological capabilities, and Client expectations. The annual review considers: performance data from the preceding twelve months, Client feedback and satisfaction surveys, industry benchmarking and competitive analysis, infrastructure investment and capacity planning, and regulatory and compliance developments.

### Transparency Commitment

CryptoMize is committed to full transparency in SLA reporting and review. All performance data, incident records, and monitoring metrics are available to Clients upon request. CryptoMize does not selectively report or obscure data that would affect a Client's understanding of Platform performance. This commitment to transparency is foundational to the trust relationship between CryptoMize and its Clients.

---

### Effective Period

This SLA is effective from the date specified on the first page of this document and remains in force for so long as the Client maintains an active subscription to the Perception X2 Platform. The SLA automatically renews with each successive Measurement Period unless terminated in accordance with this section.

### Termination for SLA Failure

If CryptoMize fails to meet the uptime commitment for three (3) consecutive Measurement Periods, or if the cumulative Downtime in any twelve (12) month period exceeds the equivalent of two (2) full calendar days, the Client may terminate the affected service agreement without penalty and receive a prorated refund of any prepaid fees for the unused portion of the current billing period.

### Termination for Convenience

Either party may terminate this SLA with thirty (30) days written notice. Upon termination, all Service Credit obligations for completed Measurement Periods will be honored, and any accrued but unused credits will be applied to the Client's final invoice or refunded at CryptoMize's discretion.

### Survival

The following provisions survive termination of this SLA: Section 11 (Service Credits) for Incidents occurring prior to termination, Section 13 (Data Recovery and Backup Guarantees) for a period of ninety (90) days following termination, Section 2 (Definitions) for the purpose of interpreting surviving provisions, and any other provision that by its nature is intended to survive termination.

---

### General Inquiries

For questions about this Service Level Agreement, contact the CryptoMize Legal and Compliance team through the following channels:

- **Email:** legal@cryptomize.com - **Platform Support:** Available through the Platform's built-in support system - **Web:** [perception.ac/contact](https://perception.ac/contact)

### Incident Reporting

To report an Incident or service disruption:

- **Standard and Professional Tiers:** Submit an incident report through the Platform's support portal - **Enterprise and Sovereign Tiers:** Contact your dedicated Account Manager or call the priority support line - **Status Dashboard:** [status.perception.ac](https://status.perception.ac)

### Escalation Contact

For escalation of unresolved Incidents:

- **Email:** escalation@cryptomize.com - **Phone:** Available for Enterprise and Sovereign tier Clients upon request

### Account Management

Enterprise and Sovereign tier Clients have a dedicated Account Manager whose contact details are provided during onboarding. For all other tiers, account-related inquiries can be directed to accounts@cryptomize.com.

### Legal Notices

Formal legal notices related to this SLA should be sent to:

- **Email:** legal-notices@cryptomize.com - **Postal:** Available upon request through the legal team

CryptoMize responds to all inquiries within the timeframes specified by the Client's Service Level Tier. Urgent matters related to active Incidents are prioritized accordingly.

---

### Related Legal Documents

- [Terms of Service](/legal/terms) -- Platform usage terms and conditions - [Privacy Policy](/legal/privacy) -- How we collect, use, and protect your data - [Security](/legal/security) -- Our security architecture and practices - [Compliance](/legal/compliance) -- Regulatory compliance and certifications - [Cookie Policy](/legal/cookies) -- How we use cookies and tracking technologies

---

**CryptoMize** | Perception X2 Platform Global operations across multiple continents 15+ years of operational excellence | 300+ elite clients | Zero security incidents