Account & Security

Account & Security contains owner-level settings only. Console destination links belong in the horizontal workspace navigation, not the avatar menu.

Profile

Editable display and full-name fields are presentation data. Updating them does not change provider identity, Page ownership or scoring facts.

Wallets

Wallet connection requires a server-issued challenge and signed ownership proof before storage. Never accept a client-submitted address alone as proof.

Destructive actions

Sign-out, disconnect and account removal use explicit confirmation. Disconnecting a provider must not silently delete canonical Pages or evidence history owned under a separate relation.

Profile settings

The profile route accepts only documented editable fields and validates them server-side. Display name, company and presentation preferences can change account presentation; they cannot change canonical provider IDs, ownership verification or scores.

await fetch('/api/clawdbase/profile', {
  method: 'PATCH',
  headers: {
    Authorization: `Bearer ${session.access_token}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ display_name: 'Clawdbase Builder' }),
})

Use the documented fields only. Validation appears beside the affected field, and a successful update is reflected in the account menu.

Wallet proof

Session and credential hygiene

• Keep Clawdbase Access Keys server-side.
• Rotate compromised Access Keys from Developer Access.
• Revoke provider connections independently of the primary session.
• Do not treat editable profile text as proof of provider ownership.
• Require recent reauthentication before account deletion or other high-impact changes when implemented.

Account removal

Document which private account data is deleted, which public canonical evidence remains, and which billing records must be retained. Cancellation, provider disconnection and account deletion are separate operations and should never be combined behind one ambiguous control.