Compare commits
2 Commits
95746511f9
...
dd24396bd1
Author | SHA256 | Date | |
---|---|---|---|
dd24396bd1 | |||
9946375ce9 |
24
candidateprivacypolicy
Normal file
24
candidateprivacypolicy
Normal file
@ -0,0 +1,24 @@
|
||||
This policy outlines what happens with your personal data once you’ve applied to a job through our careers page.
|
||||
|
||||
Applicant Information: If you apply for a job at Lab6ix through our careers page we will ask you to provide some personal information, including:
|
||||
|
||||
Full name
|
||||
Home Address
|
||||
Phone number
|
||||
Email address
|
||||
Links to social media sites relevant to the job(s) you’re applying for
|
||||
Various basic questions to gain a high level understanding of your skills and interest in the job(s) you’re applying for
|
||||
|
||||
We also receive information via your shared social platforms like LinkedIn, as well as resumes cover letters. Your information gets stored in some of our IT platforms such as Greenhouse, Enboarder, Entelo, LinkedIn, and potentially any others we might use to evaluate your candidacy.
|
||||
|
||||
We use this personal information to gain an understanding of your skills, qualifications, and experience. If you’ve applied for jobs at Lab6ix in the past, we use the new information you’ve provided to sync and update the previous information so we have the most accurate and current view of you as an applicant. We hang on to your contact information for one year in order to communicate with you throughout the application process, keep you informed of any new fitting opportunities, and to report on and improve on our own recruitment process. After the end of that window, we will send you an email to see if you’d like us to keep your personal information on file so we can continue to consider you for new opportunities.
|
||||
|
||||
We may also request and collect additional information such as:
|
||||
|
||||
Desired salary or other compensation-related benefits
|
||||
Location you’ll plan to work from
|
||||
How you heard about Lab6ix
|
||||
Whether you are legally authorized to work in the country you are applying to work in
|
||||
Notes from interviews with Lab6ix team members
|
||||
|
||||
Please ensure that if you provide us with any referees or third party contact information, those parties have consented to you doing so and will be expecting us to contact them.
|
102
enterprisesla
Normal file
102
enterprisesla
Normal file
@ -0,0 +1,102 @@
|
||||
Lab6ix Enterprise Support SLA
|
||||
|
||||
Lab6ix warrants that it will use commercially reasonable efforts to deliver services and support substantially in accordance with the support levels (“Support Levels”) set forth in this SLA.
|
||||
|
||||
Technical Support Hours are 24/7/365 for all issues.
|
||||
Definitions
|
||||
|
||||
Supported Software is the list of Supported Software appearing in a specific Service Order.
|
||||
|
||||
Response Time is the target time our support team will give the first response to a customer for a particular Issue in a ticket, as defined in the attached schedule.
|
||||
|
||||
Issue is a specific problem or question from the Customer, opened via Ticket.
|
||||
|
||||
Issue Type is the severity of the issue as determined by the Customer based on the indicated Issue Qualification.
|
||||
|
||||
Tickets are communications regarding an Issue conducted using the provided ticketing application, which maintains a time-stamped transcript of communications and sends emails to stakeholders.
|
||||
SLA Details
|
||||
|
||||
ISSUE TYPE
|
||||
|
||||
|
||||
ISSUE QUALIFICATION
|
||||
|
||||
|
||||
FIRST RESPONSE TIME SLA
|
||||
|
||||
|
||||
INITIATION
|
||||
|
||||
Critical Issue
|
||||
|
||||
(SEV1/P1)
|
||||
|
||||
|
||||
Your system is down and unable to function AND no workaround is available;
|
||||
|
||||
OR
|
||||
|
||||
All or a substantial portion of your data is at significant risk of loss or corruption
|
||||
|
||||
OR
|
||||
|
||||
Your business operations have been severely disrupted
|
||||
|
||||
|
||||
2 HOURS
|
||||
|
||||
24x7x365
|
||||
|
||||
|
||||
TICKET ONLY
|
||||
|
||||
Production Issue
|
||||
|
||||
(SEV2/P2)
|
||||
|
||||
|
||||
Operations can continue in a restricted fashion, although long-term productivity might be adversely affected;
|
||||
|
||||
OR
|
||||
|
||||
A major milestone, project, or customer is at risk.
|
||||
|
||||
|
||||
4 HOURS
|
||||
|
||||
24x7x365
|
||||
|
||||
|
||||
TICKET ONLY
|
||||
|
||||
General Issue
|
||||
(SEV 3)
|
||||
|
||||
There is a problem with no notable impact or a minor impact on operations;
|
||||
|
||||
OR
|
||||
|
||||
There is a general question about functionality or features
|
||||
|
||||
|
||||
6 HOURS
|
||||
|
||||
24x7x365
|
||||
|
||||
|
||||
TICKET ONLY
|
||||
Exclusions
|
||||
|
||||
A particular Issue will not be eligible for this SLA, and Lab6ix may resolve a particular Issue as unresolvable if any of the following exclusions apply:
|
||||
|
||||
Customer has not paid all amounts due under any active SO by the respective Due Date.
|
||||
Customer is in breach of this MSA or the AUP.
|
||||
Customer is utilizing Supported Software that is more than 12 months older than the current production release.
|
||||
Customer is utilizing Supported Software in a manner not in line with recommended best practices.
|
||||
Customer is utilizing Supported Software at a scale inappropriate for the underlying infrastructure.
|
||||
Customer is unable or unwilling to provide the necessary access or information to troubleshoot.
|
||||
Customer utilizes Issue Types that do not reflect the Issue Qualification.
|
||||
|
||||
SLA Credits
|
||||
|
||||
In the event of a violation of this SLA, Customer will be issued a SLA credit of $5000 per incident. Requests for Invoice Credits must be made within 30 days of the Incident that triggered the credit. In no event shall Invoice Credits exceed the invoice value of the term in which they are accrued. A pending credit does not release Client from its obligation to pay Lab6ix’s submitted invoices in full when due. SLA Credits are the Customer’s sole and exclusive remedy to violations of this SLA.
|
@ -1,17 +1,10 @@
|
||||
Use of Lab6ix’s website, platform, or other online properties is governed by these Terms of Service. To the extent you provide any personally identifiable information while using the website, Lab6ix’s usage of such information is also governed by the Privacy Policy.
|
||||
|
||||
In addition to providing open source and proprietary software, Lab6ix provides a platform and an official catalog for the Lab6ix community to create and share a wide range of plugins (data sources, panels, apps) and dashboards, covering a wide range of interests.
|
||||
|
||||
If you are looking for licensing terms for your usage of Lab6ix’s proprietary software, the governing terms for such usage is the Master Services Agreement.
|
||||
|
||||
We believe that everyone should have the power to create and share plugins with minimal limits or restrictions. The key word in the preceding paragraph is minimal; in order to protect the experience and safety of our users, some “house rules” are required.
|
||||
USING PLUGINS
|
||||
|
||||
Plugins can be easily installed into your existing Grafana installation.
|
||||
|
||||
When you enable certain plugins that require an external account, you may be required to register or configure a third party account. Such accounts are subject to their own policies and we make no guarantees about any third party accounts.
|
||||
|
||||
When you install third party plugins that are not provided by or written by us, you are installing third party software on top of your Grafana installation. We make no guarantees about any plugin.
|
||||
When you install third party plugins that are not provided by or written by us, you are installing third party software on top of your software installation. We make no guarantees about any plugin.
|
||||
PUBLISHING PLUGINS
|
||||
|
||||
Please review our Plugins Policy if you are interested in publishing a plugin.
|
||||
|
Loading…
Reference in New Issue
Block a user