ApertureData Support Policy
‍

‍‍“Urgent” means a catastrophic problem in Customer’s production systems. Examples include a complete loss of service, production systems that are crashed, a production system that hangs indefinitely, or when Customer cannot continue essential operations.

“High” means a high-impact problem in Customer’s production systems. Customer’s essential operations are seriously disrupted, but a workaround exists which allows for continued essential operations.

“Normal” means a lower impact problem on a production or non-production system that involves a partial or limited loss of non-critical functionality, or some other problem involving no loss in functionality. Customer can continue essential operations. Normal problems also include all problems on non-production systems, such as test and development systems.

“Low” means a general usage question. It also includes recommendations for requests for new products or features, and requests for enhancements or modifications. There is no impact on the quality, performance, or functionality of the product in a production or non-production system.

“Business hours” are from Monday - Friday, 5am to 6pm PT

“Business day” is a day from Monday - Friday PT excluding federal holidays.
‍

‍Support Details for Non Production Software Subscription (Basic Support)

‍During the Subscription Period, for issues at Priority Levels S3 and S4 as outlined in the Table 1 above, ApertureData shall provide technical support to address any questions, concerns, fixes necessary to use Software as follows: (i) email support (at support@aperturedata.io ), emails will be answered according to their specific priority level; and (ii) slack support on Aperture slack channel (aperturedata.slack.com), where messages will be answered according to their priority level.

Support coverage statement

‍As per support policy, if you are a licensed customer…


We support
‍

• Diagnosis and resolution of product defects
• Installation, configuration, and migration issues
• License issues
• How-to questions
• Delivery of updated documentation and software packages
• Installation/migration walkthroughs*
  
  
  
  * We support sharing best practices around installation/migration walkthroughs and pipeline and job design optimizations, and will try to support you. Where we feel that your question is too custom and would require more dedicated support, we may suggest alternative ways, which may incur additional costs.
  ‍
• ‍Customer Responsibilities
  
  Customer shall provide ApertureData with logs, sample data, process information, online access to the Supported Software, supporting analysis, and access to Customer’s Technical Contact as reasonably required to allow ApertureData to resolve reported Issues. Customer is responsible for the adequate duplication and documentation of all of its files and data for back-up purposes.
  ‍
• How to Escalate a Support Issue
  
  ApertureData Support is committed to providing accurate and timely solutions to technical support needs. If Customer has a critical or serious technical issue on its production system or is not satisfied with the response or resolution provided by ApertureData Technical Support, Customer may use one of the following escalation paths to have its concerns addressed:
  ‍
  1. For support issues where the business impact has changed or was not correctly stated initially, request to have the priority of the ticket increased according to the above service level definitions.
  2. For an existing issue that has become critical in nature where Customer’s production system is down, inaccessible, or Customer is dissatisfied with the ApertureData response or resolution, follow the procedure below for management review.
     
     
     1. Verify that the support email is up-to-date and all requested information and files have been provided and request an escalation.
     2. Contact support@aperturedata.io or call one of the escalation phone numbers found in the “Welcome to ApertureData” email. Customer’s Technical Contact will be asked for the Technical Contact’s name, company name, ticket number, contact number, and reason for the escalation.
     3. Once an escalation has been received, the Support Manager will contact Customer’s Technical Contact to acknowledge the escalation and determine the mode of communication and frequency of updates. The Support Manager will work to ensure that the appropriate resources are available to identify a solution or workaround.
• End of Life Policy
  
  Support covers (1) the current Major Release;and (2) the Major Release that was available immediately prior to the current Major Release only for security fixes; and (3) all Minor Releases under a supported Major Release. If none of the conditions in the preceding sentence are met, then the Supported Software has reached its End of Life (“EOL”).
  
  “Major Release” means a new version of the Supported Software made generally available by ApertureData with substantial improvements, enhancements and bug fixes, represented by a change in the number to the left (such as a version change from 1.1.0 to 2.0.0).
  
  “Minor Release” means a version change represented by a change in the number to the right of the last decimal point.
  
  The Supported Software will reach its End of Service Life (“EOSL”) 6 months after the EOL. Until the EOSL (and provided Customer has a current Subscription to Support), if Customer has identified a defect in a Major Release that has reached EOL, ApertureData will evaluate fixing the defect in a release that has not reached EOL. After the EOSL, ApertureData will not support, in any way, a Major Release and/or any Minor Releases of that Major Release.
  
  Support for other versions of the Supported Software is not provided under this Support Policy. Support only covers use of the Supported Software on the platform or operating system versions that are specified at www.ApertureData.co/product . Support does not cover use of the Supported Software on platforms or operating systems that are no longer supported by the original vendor.
  ‍
• Continuous Support
  
  In order to receive uninterrupted access to ApertureData Support from one subscription term to the next, Customer must renew their subscription to Software in a timely manner to avoid a lapse in Support
  ‍
• Amendments
  
  ‍Except as expressly provided herein, no modification of this Support Policy will be effective unless contained in writing and signed by an authorized representative of each party. From time to time, ApertureData may amend this Support Policy in its sole discretion. ApertureData will post the amended terms on the ApertureData website at www.apertureData.io/support-policy. ApertureData will also update the “Last Updated Date” at the top of this Support Policy. By continuing to access or use Support after ApertureData has provided Customer with such notice of a change, Customer is indicating that it agrees to be bound by the modified Support Policy. If the changes have a material adverse impact on and are not acceptable to Customer, then Customer must notify ApertureData within 30 days of the applicable Last Updated Date. If ApertureData cannot accommodate Customer’s objection, then the prior Support Policy shall govern until the expiration of the then-current subscription period. Any renewed subscription will be governed by the then-current Support Policy. No term or condition contained in Customer’s purchase order or similar document will apply unless specifically agreed to by ApertureData in writing, even if ApertureData has accepted the order set forth in such purchase order, and all such terms or conditions are otherwise hereby expressly rejected by ApertureData.