# Privacy and Data Handling

## Data categories visible in the product

Virusis may work with categories of data such as:

* account and session data
* token and cookie data for trial and share access
* device or tracking context (`device_hash`, `tracking_id`, `anon_id`)
* uploaded file, URL, and IP inputs
* scan metadata, checksums, and result records
* product and interaction telemetry

## Why this data is processed

* to start scans and display results
* to find existing samples again
* to manage trial and shared access
* to reduce abuse and overuse risk
* to monitor service quality and product reliability
* to power reporting and export flows

## Notable technical observations

* shared-result flows can extend access to a specific report
* some temporary client-side values can be stored for continuity
* analysis outputs can be represented as separate result layers

## Data minimization considerations

* share links should use the shortest viable lifetime
* sensitive access data should never land in logs
* retention periods should be defined by data type
* legal and security teams should agree on a shared retention matrix

## Contact note

No verified public privacy inbox is currently published in this help center. Before publication, an official data-subject channel and response window should be defined separately.


---

# 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/privacy-policy.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.
