Back to Home
Legal Document

Service Level Agreement

Last Updated: February 12, 2026

1 Overview

This Service Level Agreement ("SLA") is part of the agreement between Oryn Systems LLC, a Michigan limited liability company ("we," "our," or "us"), and you ("Customer") for the Oryn Inventory Management System ("Service"). This SLA applies only to paid subscription plans and is incorporated by reference into our Terms of Service.

Free Tier Users: This SLA does not apply to free-tier accounts. Free-tier access is provided "AS IS" without any uptime guarantees or service credits.

2 Uptime Commitment

Oryn Systems LLC commits to the following monthly uptime targets for the Service:

Plan Monthly Uptime Target Max Monthly Downtime
Starter 99.5% ~3 hours 39 minutes
Professional 99.9% ~43 minutes
Enterprise 99.95% ~22 minutes

"Uptime" is calculated as the percentage of total minutes in a calendar month during which the Service's core functionality (login, inventory management, scanning, order processing) is available and responsive. Uptime is measured from our monitoring infrastructure, and our records shall be the sole basis for calculating uptime.

2.1 Uptime Calculation

Monthly Uptime Percentage = ((Total Minutes in Month − Downtime Minutes) / Total Minutes in Month) × 100%

3 Scheduled Maintenance

We perform scheduled maintenance to ensure the Service remains secure, up to date, and performant:

  • Maintenance Window — Scheduled maintenance is typically performed during low-traffic hours (Sundays 2:00 AM — 6:00 AM EST) when possible
  • Advance Notice — We will provide at least 48 hours' notice for planned maintenance via email and/or in-app notification
  • Emergency Maintenance — Critical security patches or urgent fixes may be deployed without advance notice; we will notify you as soon as practical

Note: Scheduled maintenance windows are excluded from downtime calculations for SLA purposes, provided adequate notice was given.

4 Incident Severity Levels

We classify service incidents by severity to prioritize our response:

Severity Definition Examples
Critical Complete service outage or data loss affecting all users Service unreachable; database corruption; security breach
High Major feature unavailable or severe performance degradation Login failures; scanning non-functional; order processing down
Medium Non-critical feature impaired with workaround available Report generation slow; search partially broken; exports failing
Low Minor issue with minimal business impact UI cosmetic issues; tooltip errors; non-critical notification delays

5 Response Time Commitments

We commit to the following initial response times based on your plan and the severity of the incident:

Severity Starter Professional Enterprise
Critical 4 hours 1 hour 30 minutes
High 8 hours 4 hours 2 hours
Medium 2 business days 1 business day 8 hours
Low 5 business days 3 business days 1 business day

Response times are measured from the time an incident is reported to us via the appropriate support channel. "Initial response" means an acknowledgment of receiving your report and the commencement of investigation, not necessarily a resolution.

5.1 Support Channels

  • Email: [email protected] (all plans)
  • Priority Email: [email protected] (Professional and Enterprise)
  • Dedicated Account Manager: Available for Enterprise plans

6 Service Credits

If we fail to meet the applicable uptime commitment, you may be eligible for service credits:

Monthly Uptime Service Credit
Below SLA target but ≥ 99.0% 10% of monthly subscription fee
Below 99.0% but ≥ 95.0% 25% of monthly subscription fee
Below 95.0% 50% of monthly subscription fee

6.1 Requesting Service Credits

To receive a service credit:

  • Submit a written request to [email protected] within 30 days of the end of the calendar month in which the SLA was not met
  • Include the dates and times of the downtime you experienced
  • Include any relevant logs, error messages, or screenshots

6.2 Credit Limitations

  • Service credits are issued as credits against future invoices only; no cash refunds will be issued
  • Total credits in any month shall not exceed 50% of the monthly subscription fee for that month
  • Credits cannot be transferred to other accounts or used for services outside the Service
  • Credits must be used within 12 months of issuance
  • Service credits are your sole and exclusive remedy for any failure to meet this SLA

7 SLA Exclusions

This SLA does not apply to performance issues or downtime caused by:

  • Free Tier — Accounts on the free tier are not covered by this SLA
  • Customer Actions — Downtime caused by your actions, configurations, or misuse of the Service
  • Force Majeure — Events beyond our reasonable control, including natural disasters, pandemics, government actions, war, terrorism, cyber attacks, power failures, or internet interruptions
  • Third-Party Services — Outages or issues caused by third-party infrastructure, hosting providers, ISPs, or integration partners
  • Scheduled Maintenance — Pre-announced maintenance performed within the designated maintenance windows
  • Alpha / Beta Features — Any features marked as beta, preview, or experimental
  • DNS / Network Issues — Issues with DNS propagation, network routing, or ISP problems outside our infrastructure
  • Account Suspension — Downtime resulting from suspension of your account due to violations of our Terms of Service or Acceptable Use Policy
  • API Abuse — Downtime caused by exceeding rate limits or making excessive API requests

8 Communication During Incidents

During service incidents, we will communicate updates through:

  • Status Page — Real-time status updates at our service status page
  • Email Notifications — Direct email to affected account administrators
  • In-App Notifications — Banners and alerts within the Service (when accessible)

Post-incident, we will provide a root cause analysis report for Critical and High severity incidents affecting paid customers within 5 business days of resolution.

9 Data Protection During Incidents

During any service incident, we prioritize data protection:

  • Data Integrity — We maintain automated backups and will restore from the most recent clean backup if data corruption occurs
  • Recovery Point Objective (RPO) — Maximum data loss of 24 hours for standard plans; 1 hour for Enterprise plans
  • Recovery Time Objective (RTO) — Target restoration of service within 4 hours for Critical incidents
  • Transaction Integrity — We use ACID-compliant database transactions to ensure data consistency even during unexpected failures
  • Incident Logging — All actions taken during incident response are logged for audit and post-incident review

10 Data Durability and Backup

We implement comprehensive backup and data durability measures:

Backup Type Frequency Retention Plans
Automated Daily Backup Every 24 hours 30 days All paid plans
Point-in-Time Recovery Continuous 7 days Professional, Enterprise
Off-Site Replication Real-time N/A Enterprise
Weekly Full Backup Every 7 days 90 days Enterprise
  • Backups are encrypted at rest using AES-256 encryption
  • Backup integrity is verified automatically using checksums
  • Backup restoration is tested monthly to ensure recoverability
  • Customers may request a manual backup restoration by contacting support (subject to plan limitations)

11 Performance Benchmarks

In addition to uptime commitments, we target the following performance benchmarks for paid plans under normal operating conditions:

Metric Target (P95) Measurement
Page Load Time ≤ 2 seconds Time to first meaningful paint for authenticated pages
API Response Time ≤ 500ms Server-side processing time for standard API endpoints
Search Query Latency ≤ 1 second Time to return search results for inventory queries
Report Generation ≤ 30 seconds Time to generate standard reports (up to 10,000 records)
File Upload ≤ 5 seconds Time to process and confirm file uploads up to 10MB

Performance benchmarks are measured at the 95th percentile (P95) and exclude client-side network latency. These are targets, not guarantees, and are not eligible for service credits.

12 Customer Responsibilities

To receive the full benefit of this SLA, you agree to the following responsibilities:

  • Timely Reporting — Report incidents promptly through the appropriate support channels. Provide detailed information including steps to reproduce, screenshots, and affected user accounts
  • Maintenance Compliance — Keep your browser, operating system, and any integration software up to date with supported versions
  • Access Cooperation — Provide reasonable access and cooperation to our support team during incident investigation and resolution
  • Data Validation — Regularly verify the accuracy of your data and report any discrepancies promptly
  • Local Backup — Maintain independent backups of critical data using the Service's export functionality. We provide the tools, but the responsibility for maintaining local backups rests with you
  • Security Best Practices — Follow security best practices as outlined in our Acceptable Use Policy, including strong passwords, MFA, and principle of least privilege

13 Escalation Procedure

If you are not satisfied with the initial response to an incident, you may escalate using the following procedure:

Escalation Level Contact When to Escalate
Level 1 [email protected] Initial report; no response within committed timeframe
Level 2 [email protected] Unsatisfied with Level 1 response; issue persists beyond expected resolution time
Level 3 [email protected] Critical business impact; unresolved after Level 2 escalation for 24+ hours

Enterprise customers with a dedicated account manager may escalate directly through their account manager at any time.

14 Disaster Recovery

We maintain a disaster recovery plan to ensure business continuity in the event of a catastrophic failure:

  • Geographic Redundancy — Production data is replicated to geographically separate regions (Enterprise plans)
  • Failover Time — Automated failover to backup systems within 15 minutes of primary system failure detection
  • DR Testing — We conduct disaster recovery drills at least semi-annually and publish results to Enterprise customers upon request
  • Communication Plan — In the event of a disaster, customers will be notified within 1 hour via email and status page updates
  • Recovery Priority — In a disaster scenario, we prioritize restoration in the following order: (1) data integrity, (2) authentication, (3) core inventory operations, (4) reporting and analytics, (5) integrations

15 SLA Modifications

We may modify this SLA with at least 30 days' written notice. Changes will not apply retroactively to incidents that have already occurred. Continued use of the Service after SLA modifications take effect constitutes acceptance of the updated SLA. Material changes that reduce service commitments will be clearly highlighted in the notification.

16 Governing Law

This SLA is governed by the laws of the State of Michigan, United States of America, without regard to its conflict of law provisions. Disputes relating to this SLA shall be resolved in accordance with the dispute resolution procedures in our Terms of Service.

17 Contact

For SLA inquiries, incident reports, or service credit requests:

  • Email: [email protected]
© 2026 Oryn Systems LLC • Privacy Policy • Terms of Service • Acceptable Use • Cookie Policy • Disclaimer • SLA • DPA