Terms ofService.

Orvatos provides guided engineering consultations, technical diagnosis, architecture and security reviews, performance analysis, deployment guidance, and troubleshooting for software applications. Our standard service is consultation-led: clients retain control of their code and implement proposed changes in their own environments.

The specific deliverables, scope, fees, and acceptance criteria are agreed in writing before work begins. Any work outside the agreed written scope requires a separate estimate, timeline, and written approval.

Before scheduling formal advisory sessions or committing engineering resources, Orvatos reviews your technical intake and provides a written statement of scope, estimated session requirements, deliverables, and fees.

Consultation work officially commences only after the client approves the written scope, pricing, and applicable milestone schedule in writing or via electronic confirmation.

Clients retain ownership of their existing source code, proprietary algorithms, database schemas, and other intellectual property. Orvatos does not acquire ownership of client intellectual property through a consultation.

Ownership and permitted use of any separately created deliverables, documentation, tailored AI prompt templates, or advisory reports will be specified in the applicable engagement terms. Clients receive a perpetual, non-exclusive license to use all customized guidance provided during their engagement.

We document findings and perform validation appropriate to the agreed scope. Results depend on the information available, the client's environment, third-party services, and the tests performed. We will communicate known limitations and any remaining issues identified during the engagement.

Because production environments interact with fluctuating external dependencies, load patterns, and third-party APIs, our advisory recommendations are structured with documented operational boundaries and testing criteria.

Clients generally retain control of their repositories, hosting accounts, and development environments. Orvatos does not require repository access or a full-codebase upload for its standard guided consultations.

Clients are responsible for applying changes, managing their credentials, and maintaining appropriate backups. Any exception involving additional environment access must be agreed upon separately in writing with specific security parameters.

Unless an alternate schedule is agreed in writing, engagements follow our proposed structured milestone plan:

Refunds & Cancellations: Initial commencement fees cover preparatory architecture diagnosis and engineer reservation and are non-refundable once technical work has begun. Subsequent milestones are payable only upon delivery of the agreed stage. If a milestone is disputed in good faith, both parties agree to review test outcomes against the agreed acceptance criteria before funds release.

Changes are evaluated against written acceptance criteria agreed upon prior to commencement. Following completion of the implementation consultation, a defined validation window (standard 3 business days, or as confirmed in writing) begins.

Defect Reporting: If the documented issue persists or an immediate defect related directly to the recommended fix is identified during the validation window, Orvatos will re-examine the problem under the original scope at no additional charge. Issues arising from subsequent unapproved code modifications, unrelated subsystems, or new third-party outages are outside scope and will require a separate quote.

To ensure safe advisory and avoid production incidents, clients acknowledge and agree to:

• Maintain Reliable Backups: Take complete, verified snapshots or backups of source repositories, database state, and environment configurations before applying any recommended changes.
• Review AI-Generated Changes: Independently review, test in staging, and validate all AI prompt instructions or script snippets before applying them to production systems.
• Safeguard Secrets & Keys: Mask or rotate credentials before screen sharing and avoid disclosing API keys, database secrets, or sensitive production telemetry.
• Supervise Live Sessions: Supervise all screen-sharing calls and retain sole authority over commands executed in local or cloud environments.

Modern software systems depend on external services including AI coding tools (e.g. Cursor, Claude, GitHub Copilot, OpenAI), hosting platforms, managed databases, third-party authentication services, and package registries.

Orvatos provides advisory guidance on best practices for these platforms but is not liable for service outages, upstream breaking changes, model deprecations, or pricing modifications imposed by third-party providers.

To the maximum extent permitted by applicable law, neither Orvatos nor its consultants shall be liable for indirect, incidental, special, consequential, or punitive damages, including loss of profits, data corruption, business interruption, or system downtime resulting from client implementation decisions.

In all circumstances, Orvatos' aggregate total liability arising out of or related to an engagement, whether in contract, tort, or otherwise, shall be strictly capped at the total fees actually received by Orvatos from the client for the specific engagement giving rise to the claim during the three (3) months preceding the event.

These terms and any consultation agreements shall be governed by and construed in accordance with the laws of India. In the event of a dispute, the parties agree to first attempt informal, good-faith executive escalation for at least thirty (30) business days.

If unresolved, competent courts in Bengaluru (Bangalore), Karnataka, India shall have exclusive jurisdiction over any formal legal proceedings.

To request custom enterprise agreements or discuss customized milestone terms, contact our engineering team: