Know what is checked.
Know what is kept.
A factual guide to the public reference desk, the separate protected workspace and how each handles your data.
PUBLIC SITE UPDATE · 2 NOVEMBER 2026
Public guidance and a separate protected workspace
This public website provides articles, checklists, search, a guided security review and a clearly labelled synthetic sample report. It does not host scanner APIs, collect provider API keys or store private assessment records.
Live checks, domain verification, scanner connections, reports and action notes remain in the existing protected CyberScan workspace. It retains owner-private access through the ChatGPT Sites sign-in gateway. Existing authorised access is required; publishing these guides does not grant access to that workspace.
Saved domains, reports and action notes stay scoped to the signed-in workspace identity. A domain entered in the homepage form is passed to the protected workspace only when you choose to continue. No check starts from this public site.
This describes the implemented application and its current deployment setting. It is not a statement of independent security certification or a completed legal privacy review.
Provider API keys are transient
A key entered for HostedScan or Pentest-Tools.com is held for the current connection session in the protected workspace. It is sent over HTTPS to that workspace’s server for the requested operation and then to the selected provider’s fixed API endpoint. It is not sent to this public website and is not a browser-only provider connection.
CyberScan does not persist provider API keys in its database, reports or browser storage, and the application does not log them. Reloading or leaving the workspace requires you to supply the key again. Disconnect when you finish; rotate or revoke a key in the provider’s own account if necessary.
What the public pages and protected workspace store
| Record | Purpose and contents | Current lifecycle |
|---|---|---|
| User identifier | The platform’s user identifier associates domain and report records with the correct workspace. The session may display the signed-in email. | The identifier remains with the records it owns. Provider credentials are separate. |
| Domains | Hostname, owner identifier, verification challenge and creation, challenge-expiry and verification dates. | A challenge expires after 24 hours. Successful verification is valid for 30 days. Expiry does not delete the record. |
| Reports and actions | Target, scan mode, dates, observed or provider-reported findings, coverage, provider scan reference, action status and notes. | Stored until deleted from the workspace. This version has no automatic age-based report purge. |
| Rate-limit counters | User-associated operation counts used to limit requests. | Counters expire after their short operating window and are removed by bounded housekeeping during later requests. |
| Saved reading | The identifiers of articles you choose to save. | Kept in this browser on this device, separately for each website origin. Clear the reading list to remove them. They do not move between this public site and your workspace. |
| Article checklist progress | The step numbers you mark while reading an implementation article. | Page-only by default. If you choose “Remember progress on this device”, the selected steps are saved in local browser storage. Turn off that option to remove the stored record. It is not saved with a report. |
| Guided review answers | Your Yes, No or Not sure answers and the plan created from them. | Held only in the open page's memory. They are not sent to the server or saved in browser storage. Leaving or reloading clears them; a downloaded or printed plan is a copy you keep. |
User identifiers, domain records, assessment reports and rate-limit counters in this table belong to the protected workspace, not this public host. Domain records currently have no removal control or automatic purge. Verification must be renewed after its 30-day validity period before a new public check can run. Keep credentials, personal data and other unnecessary sensitive information out of action notes.
Deleting a report
The workspace’s delete action removes the selected report and its action notes from the active CyberScan database. It does not delete a scan from your provider account, copies you have exported or records held independently by a service provider.
No claim is made that application deletion immediately erases infrastructure logs or backups. Their handling is governed by the relevant hosting and provider arrangements.
Where requests go
Optional analytics on public pages
Optional Google Analytics is disabled unless this website has a configured measurement service and you explicitly accept its analytics option. No Google Analytics request is made before that choice. Where the option is available, use Analytics preferences in the footer to change or withdraw consent. Measurement is limited to eligible public page visits and does not include query strings, searched terms, entered domains, review answers, credentials or assessment contents.
Reading-list and checklist storage are activated by the choices described above. Hosting and sign-in services can still process technical requests under their own arrangements; this statement is not a claim that either hosting platform is cookie-free.
Checks run from the protected workspace use Cloudflare’s DNS-over-HTTPS resolver for public records and make ordinary HTTP or HTTPS requests to the authorised hostname. DNS lookups and web requests can be visible to those services. The scanner does not log in to the target or collect its page body as report evidence.
Connected operations send the required account requests to HostedScan or Pentest-Tools.com. The application stores bounded, normalised findings. Raw scanner output, detailed HTTP request and response evidence, cookies and target authentication settings remain in the provider account.
Permission and technical limits
A public check requires permission confirmation and proof of domain control through a DNS TXT record or a verification file served over HTTPS. Verification covers the entered hostname; it does not establish permission to test shared infrastructure or unrelated systems.
Public checks reject unsupported hostnames and observed private or reserved addresses, constrain redirects, and use request and rate limits. The supported baseline uses DNS and web observations. It does not perform port scans, exploit attempts, full TLS analysis or authenticated application testing.
Connected scans require your confirmation of permission and an existing target in the selected provider account. Provider errors, skipped tests and partial finding imports remain visible. A successful connection or zero findings does not establish complete security.
Checks run on demand. This release has no continuous monitoring, scheduled news publishing, breach notification or managed incident-response service.