Skip to main content
PostQureCRYPTOGRAPHIC READINESS
PlatformCryptographic estateAI intelligenceCapabilitiesSecurity
Book a readiness session ↗

On this page

  1. Who may use PostQure
  2. Authority over every submitted asset
  3. Stay inside authorised scope
  4. No disruption, exploitation or unlawful access
  5. Protect credentials and connector configuration
  6. Cloud-provider policies
  7. Synthetic product views
  8. Refusal, suspension and limits
  9. Changes

Acceptable use

Acceptable Use

Last updated 26 August 2026

These rules apply to the public website, the launch enquiry form, and any use of PostQure to assess cryptographic assets. They exist so assessments stay lawful, authorised and non-disruptive.

Who may use PostQure

You may read the public pages and send a genuine launch enquiry if you represent an organisation that may want a briefing.

You may run or request an assessment only if you are authorised to do so for that organisation.

Authority over every submitted asset

You must own, or have written authority to assess, every hostname, certificate, cloud account, repository, cluster or other asset you submit or connect.

Do not submit third-party targets, customer environments, or supplier systems unless that third party has given written permission for the assessment.

Stay inside authorised scope

Configure collectors and connectors only for the assets and subscriptions that are in the agreed scope.

Do not use PostQure to expand a scan into neighbouring networks, shared tenancies or internet-wide discovery.

No disruption, exploitation or unlawful access

You must not use PostQure, the enquiry API or the console to:

  • disrupt, degrade or deny a service
  • exploit a vulnerability or attempt to gain unauthorised access
  • perform credential stuffing, password spraying or other credential attacks
  • intercept traffic, harvest secrets or extract private keys
  • bypass a bot check, flood the enquiry API, or probe the website except through a good-faith report to the published mailbox

Protect credentials and connector configuration

Keep console credentials, OAuth tokens, cloud roles and connector configuration confidential.

Use least-privilege roles. Do not embed long-lived secrets in places the product documentation does not require.

Revoke access when people leave or when a connector is no longer needed.

Cloud-provider policies

Follow the acceptable-use, scanning and security-assessment policies of each cloud provider, registrar and hosting platform in scope. Authorisation from your organisation does not override those providers’ rules.

Synthetic product views

Do not present the synthetic estate, scores or agent answers on the marketing site as a certified result, a customer case study or your own assessment.

Refusal, suspension and limits

PostQure may refuse, suspend or limit an enquiry or an assessment that appears unauthorised, out of scope, unsafe, automated abuse, or likely to disrupt a system.

Use the launch enquiry form if you believe a limit was applied in error.

Changes

These rules were last updated on 26 August 2026. They form part of the Terms of Use.

PostQureCRYPTOGRAPHIC READINESS

PostQure maps cryptographic estates, verifies quantum-vulnerable exposure and turns evidence into migration priorities.

Request an assessment

Product

  • Platform
  • Cryptographic estate
  • Intelligence
  • Capabilities

Resources

  • Security model
  • Request an assessment
  • PostQure home

Company

  • Contact

Legal

  • Privacy
  • Cookies
  • Terms
  • Acceptable use

© 2026 PostQure. Operated from the United Kingdom.

ApexWatch CSS Ltd is a company registered in England and Wales. Company number 14780291. Registered office: 86-90 Paul Street, 3rd Floor, London, England, EC2A 4NE.