This legal disclaimer applies to the blog post titled “Resolve incidents before your customers notice them” and to any related descriptions of Stitch’s incident detection, investigation, communication, automation, artificial intelligence, and postmortem capabilities.
The information provided in this blog post is for general informational and marketing purposes only. It is not intended to constitute legal, technical, operational, security, compliance, financial, or professional advice. Readers should not rely on this blog post as a substitute for advice from qualified legal, security, compliance, engineering, or operational professionals.
No Guarantee of Incident Prevention or Downtime Reduction
Stitch is designed to help teams detect, investigate, communicate about, and learn from incidents more efficiently. However, no software platform, artificial intelligence system, automation tool, monitoring solution, or incident management process can guarantee that all incidents, outages, degradations, bugs, security events, data loss events, or service disruptions will be prevented, detected, resolved, or communicated before customers are affected.
Statements such as “resolve incidents before your customers notice them,” “reduce downtime,” “AI-powered incident detection,” or similar descriptions are intended to describe product goals, use cases, or potential benefits. They should not be interpreted as a guarantee, warranty, service level commitment, or promise that Stitch will always detect incidents before customers are impacted or that downtime will always be reduced.
Actual outcomes may vary based on several factors, including but not limited to:
- the quality and completeness of connected observability data;
- the reliability of third-party services and integrations;
- the configuration of alerts, thresholds, workflows, and automation rules;
- the complexity of the customer’s infrastructure and application architecture;
- the maturity of the customer’s incident response processes;
- network availability and data latency;
- human review and operational decision-making;
- security, privacy, or compliance constraints;
- the availability of internal customer teams during incidents;
- and events outside Stitch’s reasonable control.
Customers remain responsible for maintaining appropriate monitoring, observability, escalation, backup, redundancy, disaster recovery, incident response, security, and business continuity practices.
Artificial Intelligence and Automation Limitations
Stitch may use artificial intelligence, machine learning, automation, or algorithmic systems to assist with incident detection, investigation, summarization, prioritization, communication, and postmortem generation. These systems are intended to support human teams and improve operational workflows, but they are not a substitute for professional judgment, engineering review, or security analysis.
AI-generated outputs may be incomplete, inaccurate, delayed, outdated, misleading, or inappropriate for a particular operational context. AI systems may also fail to detect relevant patterns, misclassify issues, overstate or understate severity, generate incorrect summaries, or omit important technical details.
Customers should review AI-assisted recommendations, summaries, communications, and postmortem drafts before relying on them or sharing them with internal teams, customers, regulators, partners, or the public. Stitch does not guarantee the accuracy, completeness, reliability, or suitability of AI-generated content.
Customers are solely responsible for determining whether and how to use AI-assisted outputs in their own incident response, customer communication, compliance reporting, or business decision-making processes.
Customer Communications
Stitch may assist teams in preparing, managing, or sending customer communications related to incidents, service disruptions, maintenance events, or post-incident updates. Any suggested or generated communication should be reviewed and approved by the customer before publication or distribution.
Customers are responsible for ensuring that all customer-facing communications are accurate, lawful, complete, timely, appropriate, and consistent with their contractual, regulatory, and business obligations.
Stitch does not guarantee that communications generated or managed through the platform will satisfy any legal notice requirement, regulatory reporting obligation, customer contract requirement, service level obligation, or public disclosure duty.
Postmortems and Incident Reports
Stitch may assist in generating postmortems, incident summaries, timelines, root cause analyses, remediation plans, or related reports. These materials are intended to support internal learning and operational improvement.
Any postmortem, root cause analysis, or incident report generated with the assistance of Stitch should be reviewed by qualified personnel before being finalized, shared, or relied upon. Incident reports may depend on incomplete logs, missing context, inaccurate timestamps, third-party data, or evolving facts.
Stitch does not guarantee that any generated postmortem or incident report will identify the definitive root cause of an incident or include every relevant contributing factor.
Third-Party Services and Integrations
The functionality of Stitch may depend on integrations with third-party services, including monitoring tools, logging platforms, communication systems, cloud providers, ticketing systems, status page providers, messaging applications, and other external platforms.
Stitch is not responsible for the availability, security, accuracy, performance, data handling, or reliability of third-party services. Failures, outages, latency, API changes, permission issues, rate limits, data errors, or service interruptions involving third-party systems may affect Stitch’s performance or availability.
Customers are responsible for reviewing and complying with the terms, policies, security requirements, and privacy practices of any third-party services they connect to Stitch.
Security and Compliance
Stitch may support security, operational, and compliance workflows, but the platform does not replace a customer’s own security program, compliance program, internal controls, audit processes, legal obligations, or governance requirements.
Customers are responsible for determining whether Stitch is appropriate for their specific regulatory, contractual, industry, and organizational requirements. This includes, where applicable, requirements relating to data protection, incident reporting, security monitoring, audit logging, access controls, confidentiality, data residency, retention, and regulated industry obligations.
No statement in the blog post should be interpreted as a representation that Stitch ensures compliance with any specific law, regulation, standard, framework, or contractual requirement.
Data Accuracy and Availability
Stitch’s ability to detect, investigate, summarize, or communicate incidents may depend on the availability, accuracy, timeliness, and completeness of data provided by the customer or third-party systems.
Incomplete logs, delayed metrics, incorrect alerts, missing telemetry, misconfigured integrations, network interruptions, permission restrictions, or inaccurate customer-provided data may affect the results produced by Stitch.
Stitch does not guarantee that all relevant data will be captured, processed, analyzed, retained, or displayed without error or delay.
No Service Level Commitment in Blog Content
Any references in the blog post to speed, uptime, response times, automation, detection, resolution, communication, or operational improvement are illustrative only. They do not create any contractual obligation, warranty, service level agreement, service credit, or performance guarantee.
Any legally binding service levels, warranties, support obligations, or remedies applicable to Stitch are governed solely by the customer’s written agreement with Stitch, including any applicable order form, master services agreement, service level agreement, data processing agreement, or other signed contractual document.
In the event of a conflict between this blog post and a written customer agreement, the written customer agreement will control.
Product Features and Availability
Product descriptions, screenshots, workflows, examples, feature names, integrations, user interfaces, and capabilities described in the blog post may be illustrative and may not reflect the exact product experience available to every customer.
Features may vary based on plan, region, configuration, permissions, integration availability, customer environment, beta access, or other factors. Stitch may modify, suspend, discontinue, or rename features at any time, subject to applicable contractual commitments.
Descriptions of future or planned functionality are provided for informational purposes only and should not be relied upon when making purchasing, operational, or investment decisions.
Beta, Preview, or Experimental Features
Some features described in the blog post may be beta, preview, experimental, limited-release, or otherwise not generally available. Such features may be incomplete, unstable, subject to change, or discontinued without notice.
Beta or experimental features may not be suitable for production use or for high-risk operational decisions. Customers should evaluate these features carefully and use appropriate human oversight and backup processes.
Unless otherwise stated in a written agreement, beta, preview, or experimental features may be provided without warranties, service level commitments, or support obligations.
High-Risk and Mission-Critical Use
Stitch is not intended to be used as the sole system for managing high-risk, safety-critical, life-critical, or mission-critical operations where failure could result in death, personal injury, severe environmental harm, major financial loss, or critical infrastructure failure.
Customers operating in highly regulated, safety-sensitive, or mission-critical environments should conduct their own risk assessments and maintain independent controls, escalation paths, manual overrides, backup systems, and professional review processes.
Customer Responsibilities
Customers are responsible for:
- configuring Stitch appropriately for their environment;
- connecting relevant and authorized data sources;
- maintaining accurate incident response procedures;
- reviewing AI-generated outputs before relying on them;
- validating customer communications before publication;
- controlling access permissions and user roles;
- protecting credentials, API keys, and integration permissions;
- maintaining backup, redundancy, and disaster recovery plans;
- complying with applicable laws, regulations, contracts, and internal policies;
- and training their teams on appropriate use of the platform.
Stitch is a tool to support incident operations. It does not assume responsibility for the customer’s systems, services, infrastructure, communications, compliance obligations, or business decisions.
Privacy and Data Protection
Use of Stitch may involve the processing of customer data, logs, metadata, communications, incident records, user information, and other operational data. Customers are responsible for ensuring that they have the necessary rights, consents, notices, permissions, and legal bases to provide such data to Stitch and to process it through the platform.
Customers should avoid submitting sensitive, confidential, regulated, or personal information to Stitch unless permitted by their agreement with Stitch and appropriate safeguards are in place.
Any processing of personal data by Stitch is governed by the applicable customer agreement, privacy policy, and any data processing agreement entered into between the parties.
Confidentiality
Incident data, logs, postmortems, security findings, internal communications, and customer communications may contain confidential or sensitive information. Customers are responsible for determining what information may be shared through Stitch and with whom.
Customers should review generated summaries, communications, and reports to ensure that confidential, privileged, sensitive, personal, or security-related information is not disclosed inappropriately.
Intellectual Property
The blog post and related materials may contain trademarks, product names, logos, screenshots, examples, text, designs, or other content owned by Stitch or third parties. Nothing in the blog post grants any license or right to use Stitch’s intellectual property or any third-party intellectual property except as expressly permitted by applicable law or written agreement.
Customer use of the Stitch platform is governed by the intellectual property terms contained in the applicable customer agreement.
Forward-Looking Statements
The blog post may contain forward-looking statements, including statements about planned features, future capabilities, expected product improvements, anticipated benefits, or strategic direction.
Forward-looking statements are subject to change and involve risks, uncertainties, and assumptions. Stitch undertakes no obligation to update such statements unless required by law. Customers should not rely on forward-looking statements as commitments or guarantees.
No Warranty
The blog post and the information contained in it are provided “as is” and “as available” without warranties of any kind, whether express, implied, statutory, or otherwise.
To the fullest extent permitted by applicable law, Stitch disclaims all warranties arising from or related to the blog post, including warranties of accuracy, completeness, reliability, merchantability, fitness for a particular purpose, non-infringement, availability, and suitability for any specific operational, technical, legal, or business purpose.
Limitation of Liability
To the fullest extent permitted by applicable law, Stitch will not be liable for any direct, indirect, incidental, consequential, special, exemplary, punitive, or other damages arising out of or relating to the blog post, reliance on the information contained in it, or use of Stitch’s products or services.
This includes, without limitation, damages for downtime, lost revenue, lost profits, lost business opportunities, reputational harm, loss of data, customer claims, service credits, security incidents, regulatory penalties, or business interruption.
Any liability relating to the use of Stitch’s products or services is governed exclusively by the applicable written agreement between Stitch and the customer.
External Links
The blog post may include links to third-party websites, tools, services, resources, or documentation. These links are provided for convenience only. Stitch does not control and is not responsible for third-party content, availability, accuracy, security, privacy practices, or terms of use.
The inclusion of any third-party link does not imply endorsement, sponsorship, approval, or recommendation by Stitch.
Changes to This Disclaimer
Stitch may update this disclaimer from time to time to reflect changes in its products, services, legal requirements, or business practices. The version posted with or linked from the blog post will apply to that blog post unless otherwise stated.
Contact
Questions about this disclaimer, Stitch’s legal terms, or the use of Stitch’s products and services should be directed to Stitch through the appropriate legal, support, or customer success contact channel.
This disclaimer should be read together with Stitch’s applicable Terms of Service, Privacy Policy, Data Processing Agreement, Service Level Agreement, Acceptable Use Policy, and any other written agreement between Stitch and the customer.
