Accounts and sign-in

A Wrengle account is optional. You can download the desktop app, read all documentation, create or open a vault, and use every local-only desktop feature without signing in.

Where an account appears

• wrengle.com is the primary website and account portal. It hosts sign-up, sign-in, the account dashboard, profile and security settings, account deletion, and the public documentation you are reading now.
• The desktop app has an optional account entry in the status bar. It never prompts during first run and never blocks local vault work.

Wrengle uses Clerk for account identity and browser sessions. Available sign-in methods are the methods currently enabled for Wrengle in Clerk. Accounts are for individuals in this release; organizations and team workspaces are not included.

Website sign-up first asks you to confirm the 18+ account notice. The Clerk account form then separately requires express acceptance of Wrengle's current Terms and Privacy Notice before it creates the account; Clerk records that legal acceptance with the account. The local age acknowledgement is not a substitute for the document-consent record.

Browser sign-in

Choose Sign in anywhere on the website. A sign-in started from the documentation returns to the exact page you were reading. Sessions belong to wrengle.com alone; there is no separate documentation origin.

The docs are statically generated and do not contain a Clerk secret. When account support is configured, the static bundle contains only Clerk's publishable key. If Clerk is unavailable, blocked, or not configured, the documentation still renders and the account control remains a normal link to the website sign-in page.

The account menu provides Dashboard, Manage account, and Sign out. Signing out clears your browser session across the whole website, including this documentation.

Desktop sign-in

Desktop sign-in opens your system browser. The app uses an authorization-code flow with PKCE and a one-use loopback callback on 127.0.0.1; it does not embed the website or collect your password in the app. Access and refresh credentials stay in the operating-system keychain and are never returned to the React renderer, stored in the vault, or written to logs.

The desktop UI receives only a sanitized account summary such as display name, primary email, avatar URL, and last verification time. If the account service is offline, your local vault and local-only features remain available. Server-backed account actions wait until the service can be verified again.

When a saved desktop account grant exists, startup reads that build's Keychain bundle into the Rust-only, zeroizing session cache before the workspace opens. That access check does not refresh or verify the grant, contact Wrengle's account API, or return tokens to the renderer. Account verification can begin only after preflight settles. A cleanly missing bundle leaves the desktop signed out without changing the global startup state. A denied or locked configured bundle puts account-backed features in Limited mode without blocking local vault work.

The keychain bundle also caches the last verified name, email, and verification time so identity can be shown offline. The avatar is not persisted, and name or email can be omitted when a platform keychain has a smaller item-size limit. Development and release builds use separate stable account slots, so a debug session cannot replace or delete a release grant.

Browser and desktop sessions are separate grants. Signing out of the browser does not silently delete desktop credentials, and signing out of the desktop does not alter your browser session; sign out on each surface you no longer want connected.

Sign-out revokes the native session capability before attempting to delete the Keychain bundle. Runtime credential writes and deletion are non-interactive: if the operating system would require a new prompt, Wrengle fails closed and asks you to reconnect or recover at startup instead of showing a dialog over the workspace or reporting a change that was not safely stored.

The desktop identity endpoint requires an OAuth token for Wrengle's exact desktop client with both profile and email access. Sign-out still requires an authenticated OAuth token for that exact client, but intentionally does not depend on resource scopes so a malformed or reduced-scope grant can revoke itself. Browser session tokens and tokens for another client cannot use either desktop endpoint.

What an account does not enable

An account does not upload, sync, or copy your vault. Billing, licenses, gated downloads, organizations, cloud vault sync, hosted workflow execution, and private documentation are not enabled in this release. Jira's account-backed OAuth broker remains an internal foundation and is not a shipped workflow connection.

Checkout, customer-portal, and Polar-webhook routes are inactive non-cacheable 404s. No billing or entitlement webhook can change account access in v1.

Provider-specific connections such as Google Calendar or Gmail keep their own authorization and privacy boundaries. A Wrengle account does not replace those provider credentials.

Account data and deletion

Clerk stores the identity, authentication methods, and session data needed to operate your account. Wrengle mirrors the minimum account profile required by the dashboard and deletes that active mirror and its dependent server records when account deletion is confirmed. A keyed, pseudonymous deletion tombstone can remain to prevent a delayed webhook from recreating the deleted account.

Delete an account from the account dashboard on wrengle.com. Deletion invalidates browser sessions. A desktop session erases its local credential bundle the next time it verifies that deletion. Account deletion never deletes or changes vault files, local settings, or local backups.

Clerk uses essential authentication cookies and makes requests to Clerk services when the account UI is enabled. Those requests are for authentication, not site analytics. Wrengle does not attach your Clerk user ID or email address to its pseudonymous website or process-scoped desktop telemetry.

See AI and privacy for the separate boundaries around vault data, AI providers, connected services, and privacy-minimized desktop telemetry.