Skip to policy
Lugescan

Effective 19 October 2026

Privacy Notice

Lugescan handles account information and potentially sensitive security findings to provide the service. This notice explains that processing and its limits so you can decide what to submit and who to give access to.

1. Information we process

  • Account information: your email, display name, password hash, verification and activation status, sessions, and the date and policy version accepted at registration.
  • Workspace information: membership, roles, invitations, plan, usage, and account activity records.
  • Scan information: target domains and URLs, ownership-verification details, selected settings, scan progress, findings, reports, and information observed on tested systems. Depending on the workflow, this may include headers, cookies, software versions, response excerpts, and supplied test credentials.
  • Operational information: request and security logs, errors, timestamps, connection information such as IP addresses where logged by the application or hosting infrastructure, and temporary scan files or failure evidence.
  • Correspondence you send when requesting access, support, or help with your information.

Avoid submitting personal or confidential information that the scan does not need. Information exposed by your target may enter scan evidence even if you did not enter it into Lugescan directly.

2. Why we use it

We use information to create and authenticate accounts, verify domain control, manage workspace access, run requested scans, deliver reports, enforce usage limits, send verification and password-reset emails, investigate errors and abuse, and respond to requests or legal obligations.

Where data protection law requires a legal basis, providing the requested service generally supports contract-related processing; securing and operating it supports legitimate interests, subject to applicable rights; and some records may be required by law. If a separate use requires consent, we will request it separately. Acknowledging this notice is not blanket consent to unrelated marketing or data use.

3. Encryption and access limits

Stored target domains, report target snapshots, and report markdown use application-level encryption with per-workspace keys. This protection does not cover every field: account details, membership, scan status, usage, and operational metadata may remain readable to the service. Passwords are stored as hashes rather than readable passwords. Temporary scan files and diagnostic evidence may contain readable scan information and are not covered by the report-blob encryption.

The backend decrypts protected information when needed to run scans and serve authorized requests. This is encryption at rest, not end-to-end encryption or a zero-knowledge service. Operators with sufficient access to the server and encryption keys can technically access protected information. We limit use of customer information to operating, securing, supporting, and meeting legal obligations for the service. No security measure eliminates all risk.

4. Who receives information

Authorized workspace members can access workspace data according to their roles. Hosting and infrastructure services process information needed to operate Lugescan; email delivery services receive addresses and messages needed for account emails.

When AI is used, it processes scan instructions and relevant target information, observations, and tool results. We use externally hosted models under zero data retention (ZDR) arrangements for scan inputs and outputs, local models with the encryption-at-rest protections described above, or sovereign models hosted in Guyana.

ZDR means the external AI provider does not retain the scan inputs and outputs covered by that arrangement after processing. It does not mean Lugescan keeps no data: we retain reports and operational records as described in this notice. Local hosting and encryption do not, by themselves, mean zero retention.

Guyana hosting applies to our sovereign model option; it does not mean every scan or every service provider processes data only in Guyana. Externally hosted models may process data outside Guyana. Contact us if you need to confirm which option applies to your scans, the current providers, processing locations, or the scope of a ZDR arrangement before submitting restricted information.

Scanning also sends traffic to your target and services involved in reaching it, such as DNS and hosting providers. Those services can record the traffic. We may disclose information when legally required or reasonably necessary to investigate misuse, protect rights, or address a security incident. We do not sell your personal information or use your scan reports for advertising.

5. Cookies and browser storage

Lugescan uses essential cookies for sign-in, the selected workspace, and protection against forged requests. The session cookie is inaccessible to page JavaScript; the workspace and request-protection cookies support browser functionality. Invitation information may be held temporarily in browser storage so you can finish joining a workspace. Signing out ends your application session; your browser also lets you clear cookies and site storage. Blocking essential storage may prevent sign-in or other features from working.

6. Retention and deletion

Report availability is limited by your plan and service retention settings; expired reports are removed by background cleanup. Temporary scan workspaces and retained failure evidence have separate cleanup rules. Account, security, usage, and activity records may be kept for service operation, abuse prevention, dispute resolution, or legal requirements. There is no promise that all categories expire with a report.

You can delete your account in account settings or contact us about deletion. Account deletion removes the account and schedules associated owned-workspace report files for cleanup. Reports in workspaces owned by others are not necessarily deleted when you leave or delete your own account. Deleting a target alone does not necessarily delete historical reports.

Deletion may take time to complete, and copies may remain temporarily in backups, logs, retained incident evidence, or non-model provider systems, such as hosting and email services, under their own retention rules. AI inputs and outputs processed under ZDR are subject to the commitment in section 4. We do not promise immediate erasure of every copy. Export needed reports before deletion or retention expiry.

7. Your choices and requests

You can update your display name, manage workspace access as your permissions allow, export available reports, stop submitting scans, and delete your account. Depending on applicable law, you may also have rights to access, correct, delete, restrict, object to processing, or receive a portable copy of personal information, and to complain to an appropriate data protection authority. Contact us to make a request; rights and exceptions depend on your circumstances and applicable law.

We may need to confirm your identity and authority over workspace information. Requests concerning data belonging to another organization may need to go through its workspace owner. We will explain any lawful reason we cannot fulfill a request.

8. Children and policy changes

Lugescan is intended for adults aged 18 or older. Contact us if you believe a child has provided personal information. We will update the effective date when this notice changes and communicate material changes through the service or account email where required. Any new processing requiring separate permission will be addressed before it begins.

Contact

Contact Lugescan at [email protected] with questions about these policies, your account, or your personal information. For privacy requests, include your account email and the request, but do not email passwords or sensitive scan reports. We may verify your identity before acting.