QAISS is building a neutral quantum-AI coordination layer. Follow the public roadmap and verify every claim.

Docs · Policy

Security model

How the site and connectors are designed to fail safely.

PublishedUpdated 2026-10-14

Website

  • Static site: no server-side code, accounts or database.
  • Content-Security-Policy: scripts only from the site’s own origin; network access limited to the listed read-only APIs.
  • No wallet connection, no transaction signing, no seed phrases — ever.
  • All user-supplied input (passports, share links, benchmark files) is size-limited, strictly parsed and rendered as text.

Connectors and future services

  • No credentials in the browser; provider secrets stay server-side.
  • Rate limits, abuse protection and audit logs on every endpoint.
  • Explicit per-job consent for anything that costs money.

Reporting a vulnerability

A security contact will be published in the Trust center. Until then, use the contact form with the topic "Security report".

Release notes

Engineering updates,
not hype.

Research drafts, releases, and every change to a public claim. No price talk.

Subscriptions open once the project publishes its privacy policy and mailing endpoint.