FAQ

Direct answers about the current closed beta.

Accounts, credentials, and trust #

Does uncapped receive my Claude password or API key? #

No.

In the current path, you sign in through Claude Code and your session connects to uncapped with a separate revocable uncapped token.

What can that connection reach? #

It receives queued task context within your uncapped account permissions.

It cannot read your private journal, another user's ungranted work, or uncapped's internal prompt and orchestration corpus.

How do I disconnect? #

Contact beta support to revoke the connection token and stop using the private workspace that contains it.

Self-service connection management is not yet a beta claim.

AI execution #

Can crew work while my computer is closed? #

No.

The current beta path runs inside a Claude Code session you start.

Scheduled, server-held BYOK, and unattended managed execution are not live.

Does AI approve its own work? #

No.

AI results return as drafts.

A human must approve or reject the result before it becomes an accepted outcome.

Privacy and data rights #

Who can read my journal? #

The journal is scoped to its account owner.

Only a task the user explicitly confirms moves into the shared work graph.

Is all production data encrypted at rest? #

Not yet.

TLS protects data in transit and backup archives are encrypted, but the production working set is not currently represented as fully encrypted at rest.

Can I export or delete my complete account myself? #

Not through a complete self-service workflow today.

Email beta support to request access revocation, available exports, or deletion.

Support will explain any current backup-retention limitation before confirming completion.

FAQ