Controlled customer access
Customer workspaces, records, technical tools, and real product operations require authenticated, entitlement- and organization-scoped access.
YQ Series Trust Center
Security boundaries that buyers and engineers can review together.
This page describes current public product and evaluation safeguards. Contracted deployment, retention, residency, availability, incident response, and sector requirements are defined during diligence. We do not claim certifications or authorizations that have not been completed.
Common control plane
A consistent trust model across the product family
Synthetic public experiences
Public demos use synthetic selections and expose no customer keys, secrets, topology, proprietary decision logic, or production systems.
Protected implementation boundary
Private keys, signing seeds, shared secrets, service credentials, and restricted operating details remain server-side or in dedicated service boundaries.
Authenticator assurance
Interactive accounts require a password plus a time-based authenticator (NIST 800-63B AAL2), idle session limits, and durable lockout after repeated failed sign-in attempts.
Reviewable evidence
Where the product requires it, records carry opaque identifiers, timestamps, versions, fingerprints, status, and verification outcomes.
Product-specific posture
What each product protects
Government, defense & critical infrastructure
YQ Line
- Shared secrets are confirmed but are not returned to the browser or stored as customer records.
- Customer records and endpoint operations are authenticated, organization-scoped, and access-tier controlled.
- Production activation requires customer-approved architecture, downgrade behavior, monitoring, and rollback controls.
Financial services & high-value workflows
YQ Trust
- Signing seeds and private-key material remain server-side and are never exposed by the public experience.
- Trust records are persisted with opaque identifiers, fingerprints, timestamps, and verification outcomes.
- Access is entitlement-gated and scoped to the authenticated customer organization.
Telecommunications & network operations
YQ Net
- Tenant and environment boundaries scope inventory, policy, rollouts, alerts, and evidence.
- Policy changes are versioned and signed; rollback targets an approved prior version.
- Customer-facing evidence can omit restricted topology while retaining reviewable control outcomes.
Universities, laboratories & research partners
YQ Research
- The runner uses a dedicated Research account, token, key, datastore, and deployment identity.
- Tenant and operator identifiers sent to the runner are SHA-256 fingerprints rather than raw identifiers.
- Synthetic, mock, candidate-algorithm, and deterministic-seed work is explicitly labeled non-production.
Standards posture
Standards-referenced. Claims disciplined.
The products reference standardized post-quantum algorithms where implemented. Algorithm use is distinct from module validation, deployment authorization, or sector certification.
FIPS 203
ML-KEM-768
Key-establishment profile used by YQ Line and benchmarked in YQ Research.
FIPS 204
ML-DSA-65
Signature profile used by YQ Trust, signed-policy workflows, and Research benchmarking.
FIPS 205
SLH-DSA seam
An attestation algorithm seam exists; availability and approval are deployment-specific.
OpenAPI 3.1
Versioned API contract
Authorized YQ integration paths have a canonical machine-readable contract after access is granted. Request API access
Available now
Evaluation and product safeguards
- Authenticated customer and technical workspaces
- Organization- and entitlement-scoped product routes
- Synthetic, non-production public demonstrations
- Server-side secret and credential boundaries
- Reviewable errors and product evidence where implemented
Defined per engagement
Production assurance and deployment scope
Data handling, retention, residency, availability, incident response, customer-managed environments, cryptographic-module requirements, export-control handling, and sector-specific compliance are documented for the actual pilot and production boundary.
Do not submit classified, export-controlled, regulated, or customer-confidential technical data through public demos or initial contact messages.
Contracting party
Yoon Laboratories Inc. is the party to YQ Series
Yoon Laboratories Inc. is the only party to YQ Series products, the YQ Series API, and this website's customer terms, except where a document names another party.
Intellectual property
Patents pending across the product family and API
Each YQ Series product and the YQ Series API as a whole are covered by one or more patents pending. The notice is a status statement, not a claim of grant, claim scope, or enforceability in any particular jurisdiction.
- YQ Line is covered by one or more patents pending as part of the YQ Series.
- YQ Trust is covered by one or more patents pending as part of the YQ Series.
- YQ Net is covered by one or more patents pending as part of the YQ Series.
- YQ Research is covered by one or more patents pending as part of the YQ Series.
Bring security into the first product conversation.
We can scope access, deployment, data handling, evidence, and review requirements before a production connection is activated.