ATROXIS
Privacy Policy

How ATROXIS handles submissions and public data.

ATROXIS is intended for security research and technical investigation. This page explains the types of information used by the public tools and the limits of the current disclosure.

What ATROXIS may receive

The website processes inputs needed to run a selected tool. These can include a URL and redirect destinations, a domain or public IP address, a file or file hash, a DNS name, a MAC address, a host and port, or text entered into local formatting tools. Requests to the site also expose normal connection information, such as an IP address and browser request metadata, to the hosting platform. The project does not publish a complete retention schedule for hosting or provider logs.

Third-party data sources

Data is sent to the services needed for the requested check. URL checks use ATROXIS to query the public Phishing.Database feed and to perform DNS, HTTP, and registration checks; the HTTP check requests the submitted public URL and follows a limited redirect chain, so the target site receives a request. DNS queries use Cloudflare DNS over HTTPS. WHOIS/RDAP checks consult the IANA bootstrap directory and the corresponding registry service; the .ae lookup uses the .ae registry's WHOIS service.

Domain, IP, and hash reputation searches use VirusTotal. For a file scan, ATROXIS calculates a SHA-256 hash and checks for an existing VirusTotal report; when no report is found, the file is uploaded for analysis. Files submitted to VirusTotal may be shared with its security partners under VirusTotal's own terms and policies. Public IP geolocation and MAC-vendor lookups use ipwho.is and macvendors.com respectively. Port testing attempts a network connection from the ATROXIS service to the specified public host and port.

Base64 conversion, JSON formatting, subnet calculation, and password generation run in the browser code and do not call the ATROXIS API. The My Public IP tool displays connection metadata available to the Worker from Cloudflare.

External providers process requests under their own terms, privacy policies, retention practices, and service limits. ATROXIS does not control those practices and does not claim that third-party data is never stored or shared.

Cookies, analytics, and ad scripts

The Google AdSense script is present on public pages. Google and its partners may process technical information, such as IP address, browser or device information, and cookies or similar identifiers, to provide, measure, and protect advertising. Whether ads are shown and whether they are personalized depends on the AdSense account settings and applicable consent choices. Review Google's privacy disclosures for details about its processing. The site owner must configure consent management where required for the audiences and jurisdictions served and keep this policy aligned with the actual AdSense settings. No separate analytics integration is configured in the current project.

Data retention and confidentiality

A full retention schedule is not currently published for hosting logs, submitted values, or third-party providers. The scanner keeps its displayed scan history in the current page session; the project does not implement an account-based scan history. This is not a promise about logs held by Cloudflare, Google, or external data providers. The site owner should confirm and publish the relevant retention details and review consent requirements against the actual AdSense configuration. Do not submit private, authenticated, proprietary, or otherwise confidential targets or files unless you have confirmed that doing so is appropriate and authorized.

Use only authorized data

Only submit URLs, domains, files, or network targets that you own or are authorized to investigate. Avoid uploading sensitive personal information or internal assets.

This policy is a practical disclosure for the current public site and should be reviewed by the owner before being treated as a final legal agreement for regulated or commercial use.