Private dashboard access
Public pages explain the product, but dashboards, generation routes, notes, and exports stay behind authentication.
Levida security: account-scoped data, tokens, and exposed-credential response
Levida keeps dashboard data private to each account, uses bearer tokens for API access, and expects HTTPS for live environments.
Bearer tokens
API tokens should stay private, should not be committed into scripts or docs, and should be rotated if they are exposed.
HTTPS
Use HTTPS for live traffic so credentials and tokens are not transmitted over plain HTTP.
Exposed password or token
Manual security action recommended: rotate any password or API token exposed in terminal logs or shared conversations.