NYTENew York Token ExchangeFor enterprise buyers

For enterprise buyers. For your customers.

Privacy secured.
Trust made visible.

NYTE requires confidential AI routes. Show your customers that privacy is built into your NYTE-powered AI, with a lock they recognize and evidence they can inspect.

Get the privacy seal
A familiar lock. Privacy with proof.
NYTE Privacy Secured — Confidential AINYTE Privacy Secured — Confidential AI
New York Token Exchange · By TrustedRouter
01

Confidential is required.

Privacy is the NYTE standard, not an optional tier. The lock identifies your NYTE-powered AI.

02

Easy to display.

A crisp, lightweight SVG. A simple link. No embedded script, tracking pixel, or cookie.

03

Backed by evidence.

Confidential compute, provider-side end-to-end encryption, and an explicit zero-retention policy are required on the same route.

Make it yours

Your customers.
Your privacy seal.

Choose a light or dark background for your NYTE-powered AI. See the confidential routing standard represented by the seal.

Appearance
NYTE Privacy Secured — Confidential AI
SVG · 320 × 88 · Scales cleanlyDownload SVG

Paste into your website

<a href="https://nytokenexchange.com/badge" aria-label="NYTE Privacy Secured: requirements and evidence">
  <img src="https://nytokenexchange.com/assets/badges/nyte-enterprise-dark.svg"
       alt="NYTE Privacy Secured — Confidential AI"
       width="320" height="88" loading="lazy" style="max-width:100%;height:auto">
</a>

All badge downloads
Privacy seal · dark SVGPrivacy seal · light SVG

What the lock means

The NYTE standard.
Confidential, by requirement.

NYTE requires every AI route to meet its confidential routing standard. This seal is exclusively for enterprise buyers to display to their customers on NYTE-powered AI features. It is not a supplier badge, and downloading the artwork does not verify your product.

The required data path uses TrustedRouter’s hardware-attested gateway and enforces model="trustedrouter/confidential", model="trustedrouter/e2e", or provider.min_privacy="confidential". The same route must have verified confidential compute, provider-side E2EE, and explicit zero data retention; requests must fail closed rather than fall back to an ineligible endpoint.

The encryption claim is route-specific: client TLS terminates inside the attested gateway, and provider-side end-to-end encryption is a separate verified property. The seal does not claim that the gateway cannot process plaintext, or that unrelated features on your website are end-to-end encrypted. Customer-side logging, processing location, and other systems require their own review.

This static image is not a live verification result, an independent security audit, or a product-wide certification. Review the confidential AI routing standard and the route-specific evidence; verify the live gateway to inspect the privacy claim.

Wear it well.

Keep it linked. Link to this page so customers can inspect the privacy claim and evidence. Place it beside the eligible AI feature, or clearly identify that feature in your trust center.

Keep it legible. Use the supplied colors and proportions, at least 240 pixels wide, with clear space around it. Do not crop or alter the words.

Keep it accurate. Display it only while the feature enforces every route requirement. Remove it if that changes. Do not present it as whole-company or whole-product certification.

Buy through the exchange

Your AI supply.
Your customers’ trust.