Yuruka

Enterprise SLA

Effective date 24 June 2026

ENTERPRISE SERVICE LEVEL AGREEMENT

This Enterprise Service Level Agreement (“SLA”) forms part of the Enterprise Agreement and Terms of Service between Controlshift Talent Private Limited (“Controlshift”, “Yuruka”, “we”, “our”, or “us”) and the Enterprise Customer (“Customer”).

This SLA applies only to Customers who have purchased or entered into a valid Enterprise Agreement with Yuruka.

Customers using the Pay-as-you-go plan are not covered by this SLA unless expressly agreed in writing.

1. Purpose

The purpose of this SLA is to define:

  • Service availability commitments
  • Support response objectives
  • Incident severity levels
  • Planned maintenance procedures
  • Customer responsibilities
  • Service exclusions
  • Escalation procedures

2. Services Covered

This SLA applies to the following Enterprise Services:

  • Yuruka Platform
  • Applicant Tracking System (ATS)
  • Lead Bank
  • AI Candidate Sourcing
  • Resume Parsing
  • Resume Matching
  • AI Calling
  • Standard Calling
  • AI Interviews
  • AI Assessments
  • Offer Letter Generation
  • Employee Onboarding
  • Vendor Management
  • Enterprise Dashboard
  • Enterprise APIs
  • Administrative Portal

Third-party services integrated into Yuruka are not covered unless expressly agreed in writing.

3. Definitions

Business Day

A Business Day means Monday through Friday, excluding public holidays observed in Haryana, India, unless otherwise agreed in writing.

Business Hours

Business Hours are:

Monday – Friday

09:00 AM – 06:00 PM IST (Indian Standard Time)

Enterprise Customers with Premium Support may receive extended support hours under a separate written agreement.

Downtime

Downtime means the inability of Enterprise Customers to access the core Yuruka production platform due to an issue solely attributable to Yuruka.

Downtime begins when Yuruka confirms a qualifying production incident and ends once the affected Services are restored.

Downtime Does NOT Include

The following are excluded from downtime calculations:

  • Scheduled maintenance
  • Emergency maintenance
  • Beta or Preview Features
  • Internet outages
  • ISP failures
  • Customer device failures
  • Customer network issues
  • Browser incompatibility
  • Third-party integrations
  • Third-party telephony providers
  • Third-party cloud providers
  • Customer misconfiguration
  • Force majeure events
  • Cyberattacks directed at Customer infrastructure

4. Service Availability

Yuruka will use commercially reasonable efforts to maintain:

99.5% Monthly Uptime

Monthly uptime is calculated using:

\[(Total Minutes − Downtime Minutes) ÷ Total Minutes\] × 100

Only qualifying downtime counts toward this calculation.

5. Planned Maintenance

To maintain platform reliability, Yuruka may conduct scheduled maintenance.

Where reasonably practicable:

  • Customers will receive at least 48 hours’ prior notice.
  • Maintenance will be scheduled during periods of low expected usage whenever feasible.

Standard Maintenance Window

Sundays

01:00 AM – 05:00 AM IST

Maintenance performed during this window is excluded from uptime calculations.

6. Emergency Maintenance

Yuruka may perform emergency maintenance without prior notice to:

  • Address critical security vulnerabilities
  • Prevent platform instability
  • Protect Customer Data
  • Mitigate cyberattacks
  • Restore service availability
  • Comply with legal obligations

Emergency maintenance is excluded from uptime calculations.

7. Incident Severity Levels

Priority 1 – Critical

Examples include:

  • Complete platform outage
  • Login unavailable for all users
  • Critical production security incident
  • Widespread data corruption

Target Initial Response: Within 2 Business Hours

Status Updates: Every 4 Business Hours

Priority 2 – High

Examples include:

  • AI Interviews unavailable
  • Calling unavailable
  • ATS unavailable
  • Assessment platform unavailable
  • Major API outage

Target Initial Response: Within 4 Business Hours

Status Updates: At least once per Business Day

Priority 3 – Medium

Examples include:

  • Reporting issues
  • Performance degradation
  • Integration failures
  • Partial feature disruption

Target Initial Response: Within 1 Business Day

Priority 4 – Low

Examples include:

  • Cosmetic defects
  • General questions
  • Documentation requests
  • Feature requests

Target Initial Response: Within 2 Business Days

8. Support

Enterprise support requests may be submitted through:

Email: support@yuruka.com

Support requests should include:

  • Organization Name
  • User Name
  • Contact Information
  • Description of the issue
  • Time of occurrence
  • Screenshots (if applicable)
  • Error messages (if applicable)
  • Steps to reproduce

Providing complete information helps reduce resolution time.

9. Customer Responsibilities

To receive support under this SLA, Customers agree to:

  • Maintain accurate account information.
  • Cooperate with reasonable troubleshooting requests.
  • Use supported browsers and operating systems.
  • Maintain reliable internet connectivity.
  • Protect account credentials.
  • Assign appropriate internal administrators.
  • Promptly report production issues.

Failure to cooperate may affect response and resolution times.

10. Service Exclusions

This SLA does not apply to interruptions caused by:

  • Customer hardware
  • Customer software
  • Internet connectivity
  • Local firewalls
  • Customer misconfiguration
  • Third-party software
  • Third-party cloud providers
  • Third-party telephony providers
  • Browser extensions
  • Unsupported browsers
  • Beta Features
  • API misuse
  • Force majeure
  • Scheduled maintenance
  • Emergency maintenance

11. Security Incidents

Where Yuruka becomes aware of a confirmed security incident affecting Customer Data, Yuruka will:

  • Investigate the incident.
  • Take reasonable containment measures.
  • Notify affected Enterprise Customers without undue delay where required by applicable law or contract.
  • Cooperate with reasonable information requests relating to the incident.

12. Backups & Disaster Recovery

Yuruka maintains commercially reasonable backup and disaster recovery procedures designed to support service continuity.

Customers remain responsible for maintaining copies of business-critical information where appropriate.

13. Escalation Process

If an Enterprise Customer believes a production issue requires escalation, the Customer may request escalation through:

support@yuruka.com

Escalated incidents will receive additional internal review and priority based on business impact and technical severity.

14. Service Credits

Unless expressly stated in a separately executed Enterprise Agreement:

  • Yuruka does not provide automatic service credits.
  • Yuruka does not provide monetary compensation for downtime.
  • Any goodwill credits or commercial accommodations are granted solely at Yuruka’s discretion.

Nothing in this SLA creates an obligation to provide refunds, credits, or financial compensation.

15. Limitation of Liability

Nothing in this SLA modifies or expands the limitation of liability contained in the Yuruka Terms of Service.

All liability limitations contained in the Terms of Service remain fully applicable.

16. Changes to this SLA

Controlshift Talent Private Limited may update this SLA from time to time.

Material changes will be communicated to Enterprise Customers where required by applicable agreements or law.

17. Contact

For Enterprise Support:

Controlshift Talent Private Limited

Registered Office:

944, Block C Sushant Lok Phase 1 Gurugram, Haryana – 122001 India

Website: https://yuruka.com

Email: support@yuruka.com

© Controlshift Talent Private Limited. All Rights Reserved.