This End User License Agreement (“EULA”) is a legally binding agreement between the entity or
organisation you represent, or if you do not designate an entity or an organisation in connection with a
license purchase or usage, you in your individual capacity on behalf of yourself (“you” or “your”) and ARIA
SPECTRE SDN BHD, (1288053-W) (The “Company”) in relation to the use of (“Docspe”) the
cloud-based web application. The terms and conditions (“Terms and Conditions”) below read together
with the Commercial Terms as annexed hereto ("Annex") shall form the End User License Agreement (“EULA”).
By paying the license fee for Docspe without promptly requesting a refund or otherwise using the cloud-based
web application, such acts indicate your acceptance and your agreement to be bound by this EULA.
You acknowledge and agree: (a) that you are a licensee, not an owner, of Docspe and any copies of Docspe
without any right to further transfer or distribute of Docspe or any copies of Docspe or provide access to
Docspe in any manner without ARIA Spectre’s prior written consent; (b) not to challenge the enforceability
or validity of this EULA; and (c) not to initiate any proceedings inconsistent with the terms of this EULA.
Severity Level | Description | Response Time | Resolution Time | Resolution Process |
---|---|---|---|---|
Severity 1 |
Critical business impact: A critical or key business function cannot be completed. No workaround exists. Business cannot continue without resolution. Could lead to significant revenue loss. Requires immediate attention from the technical team, potentially halting other development activities. Examples: Production server down, Application/Database crash, Critical module failure. |
1 hour Immediate escalation by phone or email to ensure prompt attention. |
2-8 hours | Continuous allocation of resources until resolution. Escalation to senior technical teams. Notification to senior executives if required. |
Severity 2 |
High business impact: Business functions can still be completed but with process or performance compromise. A workaround exists, but the issue impacts important processes. Business can continue temporarily with the workaround but requires urgent fixing. Examples: Major application slowdown, Key features inaccessible but not completely down. |
3 hours Escalation to the technical team. | 1-2 business day(s) | Appropriate resources will be allocated to resolve the issue. Continuous monitoring and updates until resolved. Notify senior management if required. |
Severity 3 | Medium business impact: Defects impacting key business functions but do not prevent completion. Manual workarounds exist, and the issue is tolerable until the next scheduled update or maintenance. Examples: Minor bugs, Non-essential features not functioning properly. |
8 hours Acknowledgement of the issue provided via email or ticketing system. |
5-8 business day(s) or next maintenance release | Plan resolution as part of next maintenance or scheduled release. Continuous communication with customer until resolved. |
Severity 4 | Low business impact: Cosmetic defects or minor issues that do not affect business processes or operations. These issues can be fixed during the next release cycle. Examples: UI glitches, text misalignment, minor visual bugs. |
1-2 business day(s) | 2 weeks or next maintenance release | Add to the maintenance schedule. Notify the customer of planned resolution timing. |