Account access
Private routes require an authenticated account, and user-facing data is scoped to the signed-in account.
Security
Slice uses authenticated sessions, server-side authorization, and controlled financial and ownership authorities for supported account actions.
Private routes require an authenticated account, and user-facing data is scoped to the signed-in account.
Financial, ownership, and trading operations are validated and recorded through server-side services rather than browser-managed balances.
Provider-backed flows remain distinct from account data and are only available when the relevant integration is configured.