Art. 1 Purpose
Data Riders hereby establishes, through this document, its public commitment to quality in the provision of professional, advisory, analytical, and technical services, ensuring that contracted deliverables will be 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 is intended to provide the market with transparency regarding how Data Riders ensures the quality of its deliverables, as well as the conditions under which it may perform revisions, corrections, and additions at no additional cost when there is objective non-conformity attributable to its execution.
Art. 2 Scope of services
Unless otherwise stated in a proposal, contract, or specific instrument, this guarantee applies to services provided by Data Riders, including, among others:
Assessments, studies, strategy, governance and process design.
Structuring indicators, dashboards and analytics.
Strategy, governance, evaluations and process redesign.
Projects involving data, automation and artificial intelligence.
Capacity building and knowledge transfer.
Support for audits, compliance and licensing.
Reports, presentations, models, playbooks, frameworks and others.
Art. 3 Warranty principles
The Data Riders warranty follows six foundational principles:
- Scope Alignment Quality is measured by the delivery's conformity with what was contracted and validated.
- Objectivity The warranty covers objective non-conformities, and does not cover implicit expectations or later unformalized changes.
- Assisted Correction When confirmed non-conformity exists, Data Riders will provide the additional hours and structure needed to correct the issue, at no additional cost to the client.
- Governance and Traceability Every warranty activation must follow a formal process of registration, classification, analysis, action plan, and final validation.
- Collaboration Between Parties The warranty assumes timely access to data, documents, key people, and necessary validations on the client's part.
- Separation Between Correction and Scope Change The warranty does not replace the change request process.
Art. 4 Definitions
Set of objectives, deliverables, activities, assumptions, limits, exclusions, schedule, and responsibilities set out in the proposal, contract, work plan, service order, or equivalent document.
Objective conditions defined between the parties to validate deliverables, milestones, reports, models, presentations, routines, artifacts, or other results included in the scope.
Objective and verifiable deviation between the delivered item and the contracted scope, the acceptance criteria, the formally approved assumptions, or the explicitly documented requirements.
The deliverable materially meets the scope, the acceptance criteria, and the intended use, even if residual non-material adjustments remain, with no relevant impact on the purpose of the work.
Request for enhancement, deepening, refinement, expansion, additional customization, change in preference, aesthetics, narrative, approach, or level of detail — not resulting from an objective failure to adhere to the originally approved scope.
Any new request, change in direction, inclusion of a requirement, modification of an assumption, increase in depth, expansion of analytical scope, broadening of coverage, or redefinition of deliverables after contract execution or milestone validation.
Any input, access, data, system, schedule, decision, validation, document, interview, authorization, or direction whose availability is necessary for service execution and acceptance.
Period granted to the client to formally review a deliverable and record any non-conformity, in accordance with this document or the applicable contractual instrument.
Art. 5 Warranty commitment
Data Riders guarantees that its services will be provided:
- With professional diligence consistent with market standards for specialized services;
- By a qualified and supervised team;
- In substantial adherence to the contracted scope and the agreed acceptance criteria;
- With the application of its methods, quality controls and internal delivery governance.
If the client identifies, within the applicable validation window, an objective non-conformity attributable to Data Riders' execution, we commit to provide — at no additional cost — the work hours, specialist allocation, and reasonably necessary corrective support 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 the issues are properly proven and attributable to Data Riders' execution:
- Material omission of content expressly included in the scope.
- Objective inadequacy of the deliverable relative to the agreed acceptance criteria.
- Methodological inconsistency — analytical or documentary — that compromises the contracted purpose.
- Consolidation error in interpretation or presentation arising from Data Riders' own execution.
- Misalignment with assumptions approved by the client, when correctly communicated and recorded.
- Adherence failures between modules, versions or artifacts when this compromises the final delivery as planned.
Art. 7 What the warranty does not cover
The warranty does not apply to:
- Changes to scope, priority, approach, format or expectations after contracting.
- Requests for deeper analysis, expansion, additional detail or customization not originally planned.
- Changes resulting from new information, new data, new rules or new decisions arising after validation of a prior milestone.
- Unavailability, delay, low 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 not related to a formally defined acceptance criterion.
- Use of the deliverable for a purpose different from that defined in the scope.
- Rework prompted by strategic redirection, sponsorship change, replacement of contacts or internal review not connected to an objective failure.
- Unavailability, policy changes, version changes, limitations or discontinuation of third-party tools, platforms or models.
- Approvals, licenses, consents, opinions or decisions from regulators, external auditors, stakeholders or third parties outside Data Riders' control, unless expressly contracted as an obligation of result.
Art. 8 Conditions for activating the warranty
The warranty may be activated by the client provided that:
- Written formalization The request is submitted in writing — by email, system, meeting minutes, or another contractually permitted channel.
- Objective identification The request objectively identifies the deliverable, the section, the requirement or the acceptance criterion allegedly not met.
- Validation window The statement is made within the validation window for the deliverable or, if no specific provision exists, within 10 business days after the delivery of milestones.
- Compliance with dependencies The client has fulfilled, within a reasonable timeframe, its critical dependencies for execution and validation.
- Does not constitute scope change The request is not an enhancement request, scope change or a later reorientation.
In the absence of a formal statement within the validation window, the deliverable may be considered accepted for project governance purposes, unless otherwise contractually agreed.
Art. 9 Review & correction process
Once the request is received, Data Riders will follow the process below:
- 9.1 Registration The request is recorded in formal quality control, with identification of the deliverable, date, requester, basis and reference to scope/criterion.
- 9.2 Triage (3 business days) Data Riders conducts the initial analysis and classifies the issue as: non-conformity; improvement request; scope change; pending customer dependency; or a combination of the above.
- 9.3 Diagnosis If non-conformity is indicated, Data Riders assesses cause, impact, need for revision, involved areas and estimated corrective effort.
- 9.4 Correction plan (5 business days after triage) Description of the adjustment; responsible parties; hours and profiles mobilized; estimated deadline; customer dependencies; revised deliverable or resubmission step.
- 9.5 Assisted correction Once confirmed, Data Riders carries out revisions, corrections, workshops, technical meetings, reconciliation of assumptions, reissues and any other activities necessary to remedy the deviation, at no additional cost to the client.
- 9.6 Revalidation After correction, the deliverable is resubmitted for a new client validation, observing a window proportionate and appropriate to the nature of the adjustment.
Art. 10 Remediation method
The primary remediation under this warranty is reperformance or assisted correction, which may include, at Data Riders' technical discretion:
- Content review — additional analysis, wording adjustments, structure or consolidation.
- Methodological review — reprocessing of data sets and evidence, updating materials and artifacts.
- Meetings and workshops — technical alignment meetings, reconciliation workshops and additional specialist hours.
- Additional support — short-term additional support to close out 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 reasonably necessary effort to correct confirmed non-conformities attributable to its performance, within the scope originally contracted.
Art. 11 Governance associated with the warranty
To ensure the effectiveness of this warranty, Data Riders adopts a quality governance structure composed — depending on project complexity — of the following roles and artifacts:
Responsible for scope, schedule, interface and overall execution of the work.
Responsible for consistency checks, methodological adherence and deliverable compliance.
Responsible for escalation, critical decisions and institutional alignment.
Scope, Assumptions, Dependencies and Acceptance Criteria matrix, actively maintained.
Formal log of non-conformities with associated action plans and owners.
Checkpoint, validation and alignment meetings with formal minutes.
Art. 12 Special conditions for AI deliverables
For deliverables involving AI — models, prompt libraries, agents, automations, analytical pipelines — the warranty additionally considers:
- Objective conformity with the agreed prompt structure, data schema and acceptance tests.
- Validation against the evaluation set and success criteria defined in the scope.
- Assisted correction for prompt, logic, data-grounding or output-format failures 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. If none is defined, a window of 10 business days applies from milestone delivery. Once the window closes without formal non-conformity statements, the deliverable is deemed accepted for governance purposes. The warranty closes upon revalidation of corrected deliverables or upon contractual closure of the engagement.
Art. 14 Limits of the warranty
This warranty:
- Does not guarantee external business results, regulatory approvals or third-party decisions.
- Does not replace change management, contractual amendments or formal scope-change requests.
- Does not cover items excluded from the scope, even if later deemed useful by the client.
- Does not extend the contract duration except as required to complete the corrective action.
Art. 15 Contact & escalation
To formalize a non-conformity or request escalation, write to [email protected] with the subject "Warranty — [project code] — [deliverable]". A human will acknowledge within 2 business days and open the formal triage defined in Article 9.