READINESSOS

Policy: Service Availability (SLA) Policy

Version: 1.0

Effective Date: 06/06/2026

Last Updated: 06/06/2026

Contact: ReadinessOS@proton.me

1. Document Purpose

This Service Availability (SLA) Policy establishes the service availability objectives, maintenance practices, operational expectations, and service limitations applicable to the ReadinessOS platform.

The objective of this policy is to provide transparency regarding platform availability while recognizing that cloud-based software services may occasionally experience maintenance, upgrades, interruptions, or unforeseen outages.

This policy describes service objectives only and does not constitute a contractual uptime guarantee unless expressly stated in a separate written agreement.

2. Scope

This policy applies to:

• Professional user accounts
• Vessel accounts
• Future fleet accounts
• Readiness Passport services
• AI-assisted services
• Authentication systems
• Mobile applications
• Web applications
• APIs
• Enterprise integrations
• Future marketplace services

3. Service Philosophy

ReadinessOS is designed to provide reliable, highly available cloud-based operational readiness services.

The platform architecture is intended to support continuous access while maintaining security, stability, and ongoing product improvements.

Reasonable efforts are made to maximize availability while balancing maintenance and platform evolution.

4. Service Availability Objective

ReadinessOS targets high operational availability for production services.

Availability objectives are internal operational goals and should not be interpreted as legally binding uptime guarantees unless otherwise agreed through a separate enterprise agreement.

Availability measurements may exclude scheduled maintenance and force majeure events.

5. Scheduled Maintenance

ReadinessOS may periodically perform scheduled maintenance including:

• Platform updates
• Security patches
• Infrastructure upgrades
• Database optimization
• Performance improvements
• AI model updates
• Feature deployment
• Backup validation

Scheduled maintenance may temporarily affect platform availability.

Reasonable efforts will be made to minimize disruption.

6. Emergency Maintenance

Emergency maintenance may be performed without prior notice where necessary to:

• Protect platform security
• Prevent data loss
• Address critical vulnerabilities
• Restore platform stability
• Protect users
• Protect infrastructure
• Resolve major service failures

Emergency maintenance may temporarily interrupt service availability.

7. Planned Downtime

ReadinessOS may schedule maintenance windows during periods expected to have lower platform utilization whenever reasonably practical.

Planned downtime may include:

• Infrastructure migration
• Database migration
• Major feature releases
• Security upgrades
• Disaster recovery testing

Advance notice may be provided where practical but is not guaranteed.

8. Unplanned Interruptions

Platform interruptions may occur due to:

• Infrastructure failure
• Internet disruption
• Cloud provider outage
• Cybersecurity incidents
• Software defects
• Third-party service failures
• Network instability
• Force majeure events

ReadinessOS will make reasonable efforts to restore service as quickly as practical.

9. Third-Party Dependencies

Platform availability may depend upon external providers including:

• Cloud infrastructure providers
• Authentication providers
• AI service providers
• Email providers
• CDN providers
• DNS providers
• Payment providers
• Internet service providers

ReadinessOS cannot guarantee uninterrupted availability of third-party services.

10. Beta and Experimental Features

Experimental functionality may:

• Be unavailable
• Be modified
• Be discontinued
• Experience instability
• Generate inconsistent results

Beta services are provided on an "as available" basis without guaranteed availability.

11. AI Service Availability

AI-assisted features may depend upon external AI providers and computational resources.

AI functionality may become temporarily unavailable due to:

• Capacity limitations
• Provider outages
• Maintenance
• Rate limiting
• Infrastructure changes
• Platform updates

Temporary AI service interruption does not necessarily affect core platform functionality.

12. Data Availability

ReadinessOS implements reasonable backup and recovery procedures to preserve user and vessel data.

However, users acknowledge that:

• Temporary delays may occur
• Synchronization delays may occur
• Cached information may differ temporarily
• Disaster recovery procedures may require restoration time

No system can guarantee absolute prevention of data loss.

13. User Responsibilities

Users should maintain reasonable operational procedures independent of platform availability.

Users should avoid relying exclusively upon ReadinessOS for:

• Emergency response
• Navigation
• Engineering diagnosis
• Medical treatment
• Regulatory compliance
• Safety-critical decision making

Independent operational procedures should always remain available onboard.

14. Service Notifications

Where practical, ReadinessOS may communicate:

• Planned maintenance
• Service interruptions
• Major incidents
• Security events
• Infrastructure upgrades
• Feature deployments

Notification methods may include:

• Email
• Platform notifications
• Administrative announcements
• Future status pages

Immediate notification cannot be guaranteed in all circumstances.

15. Enterprise Agreements

Enterprise customers may receive separate written service commitments that supersede portions of this policy.

Where separate contractual service levels exist, those agreements shall govern the applicable enterprise relationship.

16. Limitation of Liability

To the maximum extent permitted by applicable law, ReadinessOS shall not be liable for losses arising from:

• Platform downtime
• Scheduled maintenance
• Emergency maintenance
• Third-party outages
• Internet failures
• AI service interruption
• Infrastructure failure
• Force majeure events

Users remain responsible for maintaining independent operational readiness procedures.

17. Relationship to Other Policies

This policy should be interpreted together with:

• Terms of Service
• Platform Security Policy
• Operational Disclaimer Policy
• AI Usage & Responsible AI Policy
• Privacy Policy
• API & Third-Party Integration Policy

Where conflicts exist regarding personal information processing, the Privacy Policy shall govern.

18. Policy Updates

ReadinessOS may revise this policy as infrastructure architecture, cloud providers, enterprise services, or operational practices evolve.

Updated versions become effective upon publication unless otherwise specified.

19. Revision History

END OF DOCUMENT