SenseCrypt Docs

Changelog

Release notes for SenseCrypt — how the product is versioned and where notable changes are recorded.

Notable changes to SenseCrypt are recorded here.

How we version

SenseCrypt exposes a versioned HTTP API — the endpoint paths are prefixed (for example /v1/...), and the current surface is described in the API reference. Breaking changes to a released API version are avoided; where behavior needs to change incompatibly, it is introduced under a new version. Entries below are ordered newest first, each dated.

Releases

Passkeys and live-person sign-in (FIDO2/WebAuthn)

SenseCrypt sign-in is now built on real FIDO2/WebAuthn passkeys (ES256). Every sign-in pairs a device-bound passkey, which proves the device, with a live-face check, which proves the person. Three sign-in methods are available, all invisible to your OIDC/SAML integration:

  • Simple QR — scan an on-screen QR, then a face scan in the SenseCrypt Authenticator app, matched on the device.
  • Passkeys — a FIDO2/WebAuthn passkey through a roaming-authenticator app. This is the phishing-resistant path: WebAuthn binds each assertion to its origin, so a credential proven to one site can't be replayed against a look-alike.
  • Simple Webcam (enterprise only) — a webcam face scan on a trusted customer network, matched on the workstation rather than a phone. Available to enterprise customers; contact sales@seventhsense.ai.

SenseCrypt still never stores your face image or a biometric template, only a sealed, unlinkable, non-reversible token derived from your face that even we cannot reverse, and which contains no PII. See How SenseCrypt works and the Passkey entry in the glossary.

Initial documentation release

The first public release of the SenseCrypt documentation, covering:

On this page