Skip to main content

ACCOUNT AND LICENSING

Access that follows the account, not a mystery key.

Side Whisper uses authenticated entitlement records, registered devices, revocation, protected downloads, and bounded offline grace. Public purchase fulfillment is the remaining launch connection.

Identity
Clerk browser sessions and dedicated desktop OTP sessions
Entitlements
Free, Early Access, and Pro states in Convex
Devices
Three active devices per account
Commerce
Not connected or charging users yet

THE ACCESS FLOW

Every access decision has a server-side source.

Authenticate

Sign in through the website or the dedicated desktop email-code flow. Session tokens are hashed server-side.

Resolve entitlement

The account’s plan, status, expiry, program state, and device identity determine effective access.

Register a device

A one-way device hash, label, platform, app version, and last-seen time are stored for up to three active devices.

Deliver a build

Protected download routes validate both the browser session and entitlement before returning the active build.

Use offline grace

A previously validated encrypted cache can keep access temporarily available during a service interruption.

Refresh or revoke

Periodic refresh catches expired access or a revoked current device and returns the app to sign-in.

TODAY

The backend is not a dummy.

User, consent, entitlement, device, desktop session, waitlist, invite, and build records already exist. Admin tools can grant, revoke, extend, upload, activate, and remove access and builds.

Side Whisper is not currently selling Pro access. Final pricing, Store transaction mapping, purchase restoration, refund handling, and production support procedures must be connected before paid launch.

DEVICE PRIVACY

Enough device information to enforce access, not inventory a PC.

The service receives a one-way device identifier hash, a human label that currently includes the computer hostname, platform, app version, registration time, activity time, and revocation state. The raw machine identifier is not sent.

  • Revoke a device from the website or desktop app
  • Current-device revocation signs out and exits the desktop app
  • Session and device records are separate from browser history
  • Authentication cache persists only with Electron secure storage