Last updated:
This policy explains how URLQuery handles information when you use the website, an account, or URL analysis. You can browse public reports without signing in. Technical, operational, and analytics information may still be processed when you do so.
Accounts and communications
When you use an account, the Service processes account information such as your email address, authentication information, team membership, permissions, API keys, and account settings to authenticate you and provide your authorized access.
If you contact us, we receive the information you provide, including your email address and request details, so we can respond and investigate your request.
Information associated with an account may come from you, your use of the Service, or team configuration that determines your access. Account and submission records can link activity to your account or team even when a report is not publicly attributed to you.
Submitted URLs and analysis data
URL analysis collects the submitted URL and evidence observed during the scan. This can include redirects, network requests and responses, domains, IPs, certificates, screenshots, page content, scripts, downloaded files, extracted artifacts, and detection results. Submission information may include the submitting account or team and the source IP address.
URLs and captured pages can contain personal or confidential information. Do not submit sensitive data, credentials, access tokens, or private links. Public reports are visible to all users; restricted and private reports require appropriate access. Select visibility deliberately before submission.
Analysis data can include information about people who do not have a URLQuery account, because the information was present on a submitted page or in captured traffic. You do not need an account to report a privacy concern.
Restricted and private settings control access to reports, but do not hide the submitter's identity from URLQuery. Public and restricted submissions may be shared with trusted security partners as described below. Private submissions and their analysis data are never shared with these partners.
Service operators may need to access relevant information to operate the analysis environment, investigate faults or abuse, or handle a review request.
Operational data and abuse response
Technical information is processed to operate, monitor, and protect the Service. This may include IP addresses, request metadata, timestamps, authentication events, service errors, and usage information. We may collect and review relevant information when investigating abuse, attacks, or attempts to damage the Service, and may block or suspend access.
Operational information is distinct from captured scan traffic: one describes use of URLQuery, while the other describes the browser's interaction with an analyzed website. A scan may also be recorded in the target website's own logs.
How information is used
- Provide the Service
- Authenticate accounts, apply permissions and report visibility, process submissions, deliver reports, support search and investigation, and manage account settings.
- Research and detection
- Analyze website behavior, correlate observed infrastructure, identify threats, and improve detection and the usefulness of report evidence.
- Reliability and protection
- Diagnose failures, understand service usage, manage capacity and limits, prevent unauthorized access, and investigate abuse.
- Communications and requests
- Respond to questions, handle account and report concerns, assess corrections or removal requests, and meet applicable legal obligations.
Cookies and local browser storage
The website uses an authentication cookie (urlquery-jwt) for signed-in sessions and a security cookie (urlquery-csrf) to help protect form submissions. Display preferences, including appearance and accessibility settings, are saved in your browser's local storage (uq-web-display-v1).
You can clear or block cookies and local storage through your browser settings. Doing so can sign you out or reset display preferences; blocking essential cookies may prevent account and form features from working.
The website and the documentation site (docs.urlquery.net) use Google Analytics to understand website usage. It loads Google's analytics script and sends page-view information, including the page URL and its query parameters, page title, and referrer. Google Analytics may use cookies, and requests to Google also expose technical information such as your IP address. Google's handling of this information is described in its Privacy Policy.
Cookies observed in a scan report belong to the analyzed website or its associated hosts. They are captured evidence, not cookies that URLQuery automatically installs in your own browser when you read a report.
Service providers and legal disclosures
Infrastructure and service providers may process information as needed to deliver URLQuery. This is separate from sharing analysis data with security partners. We may also disclose information when required by applicable law.
Retention
Analysis data is retained only for as long as necessary for analysis and operational stability, after which it is automatically deleted. Continued availability of reports and captured resources is not guaranteed.
Account, communication, and operational information is kept as needed to provide the Service, handle requests, protect against abuse, and meet applicable legal obligations. Stopping account use or clearing browser storage does not by itself delete server-side records or submitted reports.
Removal from public view, redaction of specific content, deletion of a report, and deletion of account information are different actions. If you request deletion, specify the information concerned. Some records may need to be retained to handle the request, meet legal obligations, or investigate abuse; we will consider applicable requirements when assessing the request.
Security and your responsibilities
The Service uses authentication, permission checks, report access controls, and form-submission protections to help limit unauthorized access. These measures do not eliminate every risk, and no online service can guarantee absolute security.
Protect passwords and API keys, review report visibility before submitting, and be careful when sharing exported evidence. Do not send credentials or unnecessary personal information in support messages. If you believe information has been exposed or an account compromised, contact us with enough context to investigate without repeating the sensitive information itself.
Analyzed websites and external links
Analyzing a URL causes the scan browser to contact the target and potentially other websites or services. Those operators can receive and log the scan requests under their own practices. URLQuery does not control their handling of information.
If you follow a link from the website or open a URL found in a report, you interact directly with that destination. Its privacy practices and terms apply independently of this policy. Capturing or linking to a website does not mean URLQuery endorses it.
Privacy concerns and review requests
Use Request review on a report page to request removal or private visibility. You can also contact us by email.
For concerns about exposed personal information, confidential content, removal, redaction, or account data, contact abuse@urlquery.net. Include the report link or ID when relevant and explain the concern without repeating sensitive information unnecessarily. See Contact for request guidance.
Depending on the law applicable to you and the information involved, you may have rights to request access to personal information, correction, deletion, restriction of processing, objection to certain processing, or a portable copy. You may also have a right to contact the relevant data-protection authority. These rights can be subject to conditions and exceptions.
Explain which information and action your request concerns and provide a way to contact you. We may ask for proportionate information to verify your identity or authority and locate the relevant records before disclosing or changing them. Do not send passwords, API keys, or identity documents unless a necessary, appropriate verification process has been agreed.
You can request review without having a URLQuery account. Account data requests and report-content requests are assessed separately; removal of an account does not automatically remove every report associated with it. We handle requests in accordance with applicable requirements and may explain when a requested action cannot be taken.
Policy updates and questions
We may update this policy as the Service and its practices change. Please review it periodically. For general privacy questions, contact contact@urlquery.net.