Account, Access and Security

Access boundaries in plain language

This page explains what Beaverly can do, what it cannot do, and how user authorization works in Chilla.

Article type: Concept + Reference Last reviewed: March 12, 2026

Plain-language summary

Chilla automates only within your approved instructions and connected environment scope. Beaverly does not hold your funds and does not provide financial advice.

Signing in and session basics

  • Use your registered account credentials.
  • Complete any verification steps prompted by the app.
  • Re-authenticate when session security requires it.

Consent and authorization basics

  • Automation requires explicit user authorization.
  • Instruction scope is user-defined and version-aware.
  • You can pause or revoke at any time from supported controls.

What Beaverly can and cannot do

Can do

  • Automate within your instructions.
  • Show activity in Flow.
  • Enforce guardrails and integrity checks.

Cannot do

  • Hold or custody your funds.
  • Act outside authorized instruction scope.
  • Provide personalized investment advice.

Security habits for users

  • Keep account credentials private and unique.
  • Review active environment links routinely.
  • Pause or revoke instructions if activity does not match your intent.
  • Use Flow history for audit-friendly reviews.