# Disclaimer

This page defines the limitations of liability and warranty exclusions that apply to the Virusis platform, its APIs, documentation, blog content, and all associated services. By accessing or using any part of the Virusis ecosystem, users acknowledge and accept the terms described below.

## Scope

This disclaimer applies to:

* the VirusProof web application and all its features
* the Virusis public API and any developer integrations
* all documentation, help center pages, and knowledge base articles
* blog posts, AI explainers, and educational content
* scan results, reports, threat intelligence outputs, and export files
* SDKs, libraries, code samples, and integration guides
* shared result links and any publicly accessible content
* trial access, free-tier services, and promotional features

## No warranty

All services, content, and outputs provided by Virusis are delivered on an **"as is"** and **"as available"** basis, without warranties of any kind, whether express, implied, or statutory.

Virusis explicitly disclaims all warranties including, but not limited to:

* **merchantability** — no guarantee that the service is fit for commercial use
* **fitness for a particular purpose** — no guarantee that the service meets any specific requirement
* **non-infringement** — no guarantee that the service does not infringe on third-party rights
* **accuracy or completeness** — no guarantee that scan results, threat data, or any output is correct, current, or exhaustive
* **uninterrupted or error-free operation** — no guarantee that the service will be continuously available or free from defects

## Limitation of liability

To the maximum extent permitted by applicable law:

* Virusis, its officers, directors, employees, affiliates, and agents shall not be liable for any **direct, indirect, incidental, special, consequential, or punitive damages** arising from or related to the use of, or inability to use, any part of the Virusis platform or its content.
* This includes, without limitation, damages related to:
  * loss of data, revenue, profits, or business opportunities
  * service interruptions or downtime
  * reliance on scan results, reports, or threat intelligence outputs
  * decisions made based on any content, documentation, or blog post
  * unauthorized access to or alteration of transmissions or data
  * third-party conduct or content accessed through the platform
  * integration failures, API errors, or SDK defects
* The total aggregate liability of Virusis for any claim shall not exceed the amount paid by the user for the specific service in the **twelve (12) months** preceding the event giving rise to the claim. For free-tier and trial users, this amount is zero.

## Scan results and threat intelligence

Virusis aggregates results from multiple third-party scanning engines and data sources. Users must understand and accept that:

* scan results represent **opinions from third-party engines**, not definitive security verdicts
* a clean scan does not guarantee that a file, URL, or IP address is safe
* a flagged result does not guarantee that a file, URL, or IP address is malicious
* detection rates vary across engines and change over time
* Virusis does not independently verify, validate, or endorse any individual engine result
* threat intelligence data is aggregated from external sources and may be incomplete, outdated, or inaccurate
* static analysis outputs are automated observations, not expert forensic conclusions

**Users must not rely solely on Virusis scan results or outputs for security decisions.** Independent verification through qualified security professionals is strongly recommended for any critical decision.

## API and developer integrations

Use of the Virusis API, SDKs, code samples, and developer tools is entirely at the user's own risk.

* API responses may change without prior notice
* rate limits, quotas, and availability are subject to change
* Virusis does not guarantee backward compatibility for any API version
* code samples and integration guides are provided for illustrative purposes only
* Virusis is not responsible for any damage caused by integrating its API into third-party systems
* developers are solely responsible for validating, handling, and securing API responses within their own applications

## Documentation, blog, and educational content

All written content published by Virusis — including documentation, help center articles, blog posts, AI explainers, and guides — is provided for **informational and educational purposes only**.

* content does not constitute professional security advice, legal advice, or consulting
* content may become outdated and is not guaranteed to reflect the current state of the platform
* content should not be used as the sole basis for any security, business, or legal decision
* Virusis is not responsible for actions taken based on published content

## Third-party services and links

The Virusis platform may reference, integrate with, or link to third-party services, tools, and websites.

* Virusis does not control, endorse, or assume responsibility for any third-party content or service
* third-party terms of service and privacy policies apply independently
* Virusis is not liable for any loss or damage resulting from the use of third-party services accessed through or referenced by the platform

## Indemnification

Users agree to indemnify, defend, and hold harmless Virusis and its officers, directors, employees, and agents from and against any claims, damages, obligations, losses, liabilities, costs, or expenses (including reasonable attorney's fees) arising from:

* the user's use of the platform, API, or any Virusis service
* the user's violation of any term or condition
* the user's violation of any applicable law or regulation
* the user's violation of any third-party right, including intellectual property rights
* any content or data the user submits, uploads, or transmits through the platform

## Force majeure

Virusis shall not be liable for any failure or delay in performing its obligations where such failure or delay is caused by circumstances beyond its reasonable control, including but not limited to:

* natural disasters, epidemics, or pandemics
* war, terrorism, or civil unrest
* government actions, sanctions, or regulatory changes
* power failures, internet outages, or infrastructure breakdowns
* cyberattacks, DDoS attacks, or security incidents
* third-party service failures or provider outages

## Modifications

Virusis reserves the right to modify this disclaimer at any time without prior notice. Continued use of any Virusis service after modifications constitutes acceptance of the updated terms.

Users are encouraged to review this page periodically.

## Severability

If any provision of this disclaimer is found to be unenforceable or invalid under applicable law, that provision shall be limited or eliminated to the minimum extent necessary, and the remaining provisions shall continue in full force and effect.

## Governing law

This disclaimer shall be governed by and construed in accordance with the laws of the Republic of Turkey. Any disputes arising from or related to the use of Virusis services shall be subject to the exclusive jurisdiction of the Istanbul Courts and Enforcement Offices.

For users subject to EU jurisdiction, nothing in this disclaimer limits any rights granted under the General Data Protection Regulation (GDPR) or other mandatory consumer protection laws.

## Contact

For questions regarding this disclaimer, contact <info@virusis.com>.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.virusis.com/legal/disclaimer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
