1. Quality & Scope Adherence, Data Riders Commitments

• Objective
• Scope of services
• Warranty principles
• Definitions
• Warranty commitment
• What is covered
• What is not covered
• Invocation conditions
• Analysis & correction process
• Remediation method
• Governance
• AI deliverables
• Validation window & closure
• Warranty limitations
• Contact & escalation

Art. 1 Objective

Through this document, Data Riders establishes its public commitment to quality in the provision of professional, advisory, analytical, and technical services, ensuring that contracted deliverables are executed with professional diligence, methodological consistency, and substantial adherence to the scope, assumptions, acceptance criteria, and formal validation milestones agreed upon with the client.

This commitment aims to provide market transparency regarding how Data Riders guarantees the quality of its deliverables, as well as the conditions under which it performs revisions, corrections, and supplementations at no additional cost when there is an objective non-conformity attributable to its execution.

Art. 2 Scope of services

Unless otherwise provided in a proposal, contract, or specific instrument, this warranty applies to services provided by Data Riders, including, but not limited to:

Assessments, studies, strategy, governance, and process design.

Structuring of metrics, dashboards, and analytics.

Strategy, governance, assessments, and process redesign.

Projects involving data, automation, and artificial intelligence.

Training and knowledge transfer.

Support for audits, compliance, and licensing.

Reports, presentations, models, playbooks, frameworks, and related artifacts.

Art. 3 Warranty principles

The Data Riders warranty follows six fundamental principles:

• Scope alignment: Quality is measured by the deliverable's conformity with what was contracted and validated.
• Objectivity: The warranty covers objective non-conformities; it does not cover implicit expectations or subsequent unformalized changes.
• Assisted Correction: Once non-conformity is confirmed, Data Riders allocates additional hours and resources to correct it at no cost to the client.
• Governance and traceability: Every claim follows a formal process: logging, classification, analysis, action plan, and final validation.
• Collaboration between parties: The warranty presupposes timely client access to data, documents, key personnel, and required validations.
• Separation between correction and scope change: The warranty does not replace the change request process.

Art. 4 Definitions

The set of objectives, deliverables, activities, assumptions, boundaries, exclusions, timeline, and responsibilities set forth in a proposal, contract, work plan, statement of work, or equivalent document.

Objective conditions defined between the parties to validate deliverables, milestones, reports, models, presentations, routines, artifacts, or other outcomes included in the scope.

Objective and verifiable deviation between what was delivered and the contracted scope, acceptance criteria, formally approved assumptions, or documented requirements.

The deliverable materially meets the scope, acceptance criteria, and purpose, even if minor adjustments without material impact remain.

A request for further depth, refinement, expansion, additional customization, change of preference, aesthetics, narrative, approach, or level of detail, not arising from an objective failure of scope adherence.

Any new request, change of direction, addition of requirements, change of assumptions, increase in depth, analytical expansion, broadened coverage, or redefinition of deliverables following contracting or milestone validation.

Any input, access, data, system, schedule, decision, validation, document, interview, authorization, or direction required for service execution and acceptance.

Period granted to the client to formally review a deliverable and log any non-conformity, pursuant to this document or the applicable contractual instrument.

Art. 5 Warranty commitment

Data Riders warrants that its services will be performed:

• With professional diligence consistent with market standards for specialized services;
• By qualified and supervised personnel;
• In substantial adherence to the contracted scope and agreed acceptance criteria;
• Applying its methodologies, quality controls, and internal delivery governance.

If the client identifies, within the applicable validation window, an objective non-conformity attributable to Data Riders execution, the company commits to providing, at no additional cost, the working hours, specialist allocation, and corrective support reasonably necessary to review, correct, supplement, and resubmit the deliverable until substantial conformity with the originally contracted scope is achieved.

Art. 6 What the warranty covers

The warranty covers, provided they are duly substantiated and attributable to Data Riders execution:

• Material omission of content expressly included in the scope.
• Objective inadequacy of the deliverable regarding the agreed acceptance criteria.
• Methodological, analytical, or documentation inconsistency that impairs the contracted purpose.
• Consolidation, interpretation, or presentation errors resulting from execution itself.
• Misalignment with client-approved assumptions, when properly communicated and recorded.
• Gaps in alignment between modules, versions, or artifacts that compromise the planned final deliverable.

Art. 7 What the warranty does NOT cover

The warranty does not apply to:

• Changes in scope, priority, approach, format, or expectations after contracting.
• Requests for deeper analysis, expansion, further detail, or customization not originally planned.
• Changes arising from new information, new data, new rules, or new decisions that emerge after the validation of a prior milestone.
• Unavailability, delay, poor quality, inconsistency, or incompleteness of data, systems, access, documents, or information provided by the client or third parties.
• Delays or gaps in validation, decision-making, or feedback by the client.
• Modifications made by the client or third parties to deliverables already issued by Data Riders.
• Purely subjective disagreements that do not relate to a formally defined acceptance criterion.
• Use of the deliverable for a purpose other than that specified in the scope.
• Rework driven by strategic realignment, change in sponsorship, turnover of contact personnel, or internal review unrelated to an objective failure.
• Unavailability, policy changes, version changes, limitations, or discontinuation of third-party tools, platforms, or models.
• Approvals, licenses, opinions, or decisions from regulators, external auditors, stakeholders, or third parties outside Data Riders' control, unless an obligation of result is expressly contracted.

Art. 8 Warranty Claim Conditions

The warranty may be claimed by the client provided that:

• Written formalization The request is submitted in writing, via email, system, meeting minutes, or another contractually approved channel.
• Objective identification The request objectively identifies the deliverable, section, requirement, or acceptance criterion allegedly not met.
• Validation window Notice is provided within the window specified for the deliverable or, in the absence of a specific provision, within 10 business days of milestone delivery.
• Fulfillment of dependencies The client has fulfilled, within a reasonable timeframe, its critical execution and validation dependencies.
• No scope change The request is not an enhancement request, scope change, or subsequent reorientation.

In the absence of formal notice within the validation window, the deliverable may be deemed accepted for project governance purposes, unless contractually agreed otherwise.

Art. 9 Review & Remediation Process

Upon receiving the request, Data Riders follows the process below:

• 9.1 Logging The request is logged in formal quality control, identifying the deliverable, date, requester, rationale, and reference to the scope/criterion.
• 9.2 Triage (3 business days) Initial analysis classifying the issue as: non-conformance; enhancement request; scope change; pending client dependency; or a combination of the above.
• 9.3 Diagnosis If there is an indication of non-conformance, the cause, impact, need for revision, areas involved, and estimated corrective effort are evaluated.
• 9.4 Corrective Plan (5 business days after triage) Description of the adjustment; owners; hours and profiles assigned; estimated timeline; client dependencies; revised deliverable or resubmission step.
• 9.5 Assisted Remediation Once non-conformance is confirmed, Data Riders conducts reviews, corrections, workshops, technical meetings, assumption reconciliations, reissuances, and other necessary activities at no additional cost.
• 9.6 Revalidation Following correction, the deliverable is resubmitted for client revalidation, subject to a window proportional to the adjustment.

Art. 10 Remediation Method

The primary remediation is re-execution or assisted correction, which may include, at Data Riders' technical discretion:

• Content review, additional analysis, adjustments to wording, structure, or consolidation.
• Methodological review, reprocessing of datasets and evidence, updating materials and artifacts.
• Meetings and workshops, technical alignments, reconciliation workshops, and additional specialist hours.
• Additional support, short-term ad hoc support to achieve compliance.

Data Riders does not promise, under this document, unrestricted subjective satisfaction or unlimited delivery of hours; the commitment is to provide, at no additional cost, the effort reasonably necessary to correct confirmed non-conformances within the originally contracted scope.

Art. 11 Warranty Governance

To ensure warranty effectiveness, Data Riders adopts the following governance structure, according to project complexity:

Responsible for scope, schedule, interface, and overall project execution.

Checks for consistency, methodological alignment, and deliverable compliance.

Escalation, critical decisions, and institutional alignment.

Scope, assumptions, dependencies, and acceptance criteria matrix, actively maintained.

Formal log with action plans and assignees.

Checkpoints, validations, and alignment meetings with formal minutes.

Art. 12 Special Conditions for AI Deliveries

For deliverables involving AI, models, prompt libraries, agents, automations, and analytical pipelines, the warranty additionally considers:

• Objective compliance with agreed prompt structures, data schemas, and acceptance tests.
• Validation against the evaluation dataset and success criteria defined in the scope.
• Assisted correction for failures in prompts, logic, data grounding, or output format attributable to Data Riders' execution.

Known limitations of underlying models (hallucination, latency, pricing, availability) outside Data Riders' control are not covered, but we remain responsible for flagging and mitigating them during delivery.

Art. 13 Validation Window & Warranty Closure

Each milestone has a validation window defined in the scope document. In the absence of a definition, 10 business days from delivery apply. Once the window closes without formal notice, the deliverable is deemed accepted for governance purposes. The warranty ends upon revalidation of corrected deliverables or upon contractual project closure.

Art. 14 Warranty Limitations

This warranty:

• Does not guarantee external business outcomes, regulatory approvals, or third-party decisions.
• Does not replace change management, contract amendments, or formal scope change requests.
• Does not cover items excluded from scope, even if subsequently deemed useful by the client.
• Does not extend contract duration, except as necessary to complete corrective action.

Art. 15 Contact & Escalation

To formally report a non-conformance or request escalation, email hi@datariders.com.br with the subject "Warranty, [project code], [deliverable]". A team member will acknowledge receipt within 2 business days and initiate the formal triage process under Article 9.