← Back to Home

Service Level Agreement (SLA)

Last updated: January 2025

1. Overview

This Service Level Agreement ("SLA") describes our service level objectives for the JobScamScore service ("Service"). JobScamScore is currently in BETA; there is no paid version. This SLA applies to all users and reflects our commitment to service quality. It does not create legally binding uptime guarantees or financial remedies.

This SLA is part of and incorporated into our Terms of Service. Capitalized terms not defined in this SLA have the meanings given in the Terms of Service.

2. Service Availability

2.1 Uptime Objective

We aim to maintain high availability for the Service, with a target of 99.9% uptime measured on a monthly basis. During BETA this is an objective, not a guarantee.

2.2 Calculation Method

Uptime is calculated as follows:

Uptime % = ((Total Minutes in Month - Downtime Minutes) / Total Minutes in Month) × 100

2.3 What Counts as Downtime

Downtime is defined as any period when the Service is unavailable due to:

  • Server errors (HTTP 500, 502, 503, 504)
  • Service unavailability caused by our infrastructure
  • Database connection failures
  • API endpoint failures affecting core functionality

2.4 Exclusions from Downtime

The following do not count as downtime:

  • Scheduled maintenance (with advance notice)
  • Emergency maintenance (with notice when possible)
  • User errors or misuse
  • Third-party service failures (e.g. AI providers, hosting)
  • Force majeure events (natural disasters, war, etc.)
  • DDoS attacks or security incidents
  • Issues caused by user's network or device
  • Beta or experimental features

3. Response Times

3.1 Support Response Times

We aim to respond to support requests within the following timeframes:

Issue TypeResponse Time
Critical (Service Down)4 hours
High (Major Feature Broken)24 hours
Medium (Feature Issue)48 hours
Low (General Inquiry)72 hours

3.2 Response Time Definition

"Response time" means our acknowledgment of your support request, not resolution time. Resolution times depend on the complexity of the issue.

4. Maintenance Windows

4.1 Scheduled Maintenance

We may perform scheduled maintenance during off-peak hours. We will provide at least 48 hours' notice for scheduled maintenance that may cause service interruption.

4.2 Emergency Maintenance

We may perform emergency maintenance without advance notice to address critical security issues or prevent service degradation. We will notify users as soon as possible.

4.3 Maintenance Notifications

Maintenance notifications will be sent via:

  • Email to your registered account
  • In-app notifications (when possible)
  • Status page updates

5. Performance Standards

5.1 Scan Processing Time

We aim to process job scans within 30 seconds under normal conditions. Processing time may vary based on:

  • Complexity of the job posting
  • Third-party API response times (OpenAI)
  • Current system load

5.2 API Response Times

We target API response times of:

  • Authentication endpoints: < 500ms
  • Scan history endpoints: < 1 second

These are targets, not guarantees, and may vary based on network conditions and system load.

6. Monitoring and Reporting

6.1 Service Monitoring

We continuously monitor the Service for availability and performance. Our monitoring systems track:

  • Server uptime and response times
  • API endpoint availability
  • Database performance
  • Third-party service status

6.2 Status Page

We maintain a status page (when available) to provide real-time information about service health and incidents.

6.3 Reporting

We may provide status or incident updates via email or a status page when available.

7. Limitations and Exclusions

7.1 Third-Party Services

This SLA does not cover downtime or issues caused by third-party services, including:

  • AI provider (e.g. xAI, OpenAI) API outages or rate limits
  • MongoDB Atlas service interruptions
  • Vercel hosting platform issues
  • Internet service provider outages

7.2 User-Caused Issues

This SLA does not apply to issues caused by:

  • User errors or misuse
  • Violation of Terms of Service
  • User's network or device problems
  • Invalid or malformed input data

8. Changes to SLA

We may modify this SLA from time to time. Material changes will be communicated by posting the updated SLA on this page and updating the "Last updated" date. Continued use of the Service after changes take effect constitutes acceptance of the updated SLA.

9. Contact

For questions about this SLA, please contact us: