Your work.
Handled with care.

What we collect, and why

• Application: name, email, agent setup, platform, task idea and contact permission, to review your request and contact you about this beta. Applying does not grant access or subscribe you to a marketing newsletter.
• Account: email, a salted password hash, hashed one-use recovery codes and their expiry, workspace memberships and invitation/session records, to sign you in and control access. Passwords are hashed rather than stored as readable text.
• Workspace: world appearance, agent definitions, prompts, conversations, task activity, command acknowledgements, usage summaries, saved jobs, schedules, approval decisions, results and feedback, to provide the workspace and help investigate problems.
• Technical operation: time-limited hashed rate-limit identifiers and necessary hosting/network diagnostics. The app avoids raw URL access logs and does not intentionally record passwords or provider keys in logs. Hosting/network providers may keep their own security and request records.

The installed-agent connector does not bulk-upload your project folder. Prompts and returned content are sent to Forgebrio, so any file contents or secrets included by you or your agent may become part of stored work. There is no reliable automatic secret-removal guarantee. Use non-sensitive tasks.

Where information goes

The dashboard runs on Render; its hosted database uses Supabase. Cloudflare provides network delivery/security for the public site. These services process information needed to host and deliver the beta. Your connected runtime receives task inputs and uses the model/tool providers you configure. The optional cloud starter processes supported tasks in your own Cloudflare account. Those providers have their own terms and retention practices.

Authorized members of your workspace can view its work. Owners manage connections and invitations; operators can perform supported work; viewers have read-only access. The beta operator has administrative access to operate and support the service. Workspace content is not end-to-end encrypted or private from the operator and infrastructure providers. Do not assume data remains in a particular country; ask before using data with location requirements.

We do not sell application or workspace content, use it for advertising, or use it to train our own models. The site has no advertising or third-party analytics trackers. Browser scripts are served from Forgebrio itself. This does not control what your chosen runtime or model provider does with its requests.

Retention and your choices

Beta applications are eligible for removal after 90 days; cleanup runs when the service starts and when a new application is processed. You can request earlier withdrawal or deletion. An accepted account and its workspace records are separate from the application.

Workspace work, accounts and feedback remain until removal is arranged; there is currently no automatic workspace-retention schedule. Use Your data & agents to disconnect, delete a world or delete your account. World deletion removes its saved work and credentials from the active database. Account deletion removes the account, sessions, application, feedback, memberships and sole-member owned workspaces; it is blocked while you own a workspace with other members. Work in other people’s workspaces can remain. Deletions require your current password and explicit confirmation. Expired sessions and rate-limit records are cleaned during normal use. Disconnecting an agent or signing out does not erase saved work.

You can save reports and, as a workspace owner, export workspace data through the account export endpoint. To request a copy, correction, application withdrawal or account/workspace removal, email Billy@ku13sh.com or use your existing invitation conversation. Identify your account email and the relevant workspace without including secrets. We verify ownership and scope before acting, and confirm what was completed. Shared-workspace records may involve other members. Runtime, provider, exported or backup copies require separate handling; we cannot promise immediate removal from provider backups.

Recovery codes are private account credentials. Only their hashes are stored; generated plaintext is shown once and is not saved in browser storage. A successful recovery revokes all existing sessions and codes. Temporary host-issued codes require ownership verification through an existing trusted conversation. No automatic recovery email is sent.

A necessary sign-in cookie keeps your session; it is not used for advertising. Your browser also saves interface preferences and return-to-work state. Use a separate browser profile on shared computers and sign out when finished. Clearing browser data does not delete server records.

Protections and remaining limits

The beta uses HTTPS, secure HTTP-only sign-in cookies, request-origin and anti-forgery checks, workspace/role authorization, scoped revocable runtime credentials, one-use expiring pairing codes, and bounded requests. The hosted database connection verifies TLS. Validation errors omit submitted values, and browser policies restrict resource loading. These are safeguards, not a guarantee of complete security or an independent security certification.

The full app is a hosted private beta, not currently an open-source or supported self-hosted release. The downloadable connector can be inspected before use. An installed agent runs with its existing local permissions; the chosen folder is not a security sandbox. Give it only the tools and files you are comfortable exposing. A stop request is cooperative and a call already running may finish. No operator model account or credits are supplied to testers; your own provider terms and usage costs apply.

Please report a suspected vulnerability privately to Billy@ku13sh.com, with a brief description and redacted reproduction steps. Do not access another user’s information or include credentials. No paid bounty is promised. If an incident is confirmed, we will assess it, contain access where possible, and communicate material findings and necessary actions to affected users as appropriate.

This beta has not had an independent penetration test or legal compliance review. It is not offered for confidential, regulated or safety-critical work. Material changes to these practices will be reflected here; a date change alone does not grant new permissions to use your data.