Beta privacy notice

What we collect

The waitlist stores your email address once, with your join time and invitation status. A hidden form field detects bots. Submissions that fill this field are discarded before storage.

Our hosting platform keeps standard request logs. This site sets no cookies.

The app collects the following data to run the service:

• The app collects your account details and sign-in records.
• It collects the GitHub repositories you connect.
• It collects the agent-provider credentials you add.
• It collects your tasks, prompts, and chat messages.
• It collects session and command logs, and their results.
• It collects workspace artifacts, including uploaded local-handoff archives.
• It collects usage, including worker hours counted against your beta allowance.

How we use it

• Your waitlist address holds your place. We use it only to email access updates, including a confirmation and a later invitation.
• The app uses your data to start your disposable cloud worker and run your configured agent.
• Your data also lets the app show progress and logs, and open draft pull requests in your chosen repository.
• We use your data to enforce beta limits and keep the service secure.
• We do not sell personal data. We do not use your repository or task content for advertising.

Who receives it

These providers help run the beta. Each handles only the data it needs, under its own terms:

• Cloudflare hosts this site, stores the waitlist database, and rate-limits the join form.
• Resend delivers the waitlist confirmation email. The app sends beta invitation emails through its own outbox.
• PostHog receives analytics events from this site and product analytics from the app. See the Analytics and cookies section below.
• GitHub is where the app reads the repositories you connect and creates branches, commits, and draft pull requests.
• The agent provider you connect receives the repository and task content needed to run your tasks. Only providers you choose receive that content. Connecting an integration does not send your code to every supported provider.

Credentials and access

Barge stores connected provider credentials encrypted at rest. A running worker receives only the scoped credentials it needs. Local handoff archives are scanned for secrets and encrypted at rest.

Only the operator can access stored data. The operator may inspect accounts and sessions to run and support the beta.

Removing a credential from Barge deletes our copy. It does not revoke the underlying provider key. Revoke that key at the provider.

Analytics and cookies

This site sends PostHog page views, page leaves, tagged-link clicks, and JavaScript errors. Tagged-link clicks carry only a location label as custom click data. Analytics collection is anonymous, without cookies, browser storage, or person profiles. Analytics events contain no form content. Your email address travels only in the join form.

Before sending events, the loader removes query strings and fragments from URL and referrer properties. It removes campaign properties except utm_source, utm_medium, and utm_campaign. These three properties remain as campaign attribution data. It also removes their initial-value variants from person properties.

Session replay is disabled for this site, regardless of the PostHog project setting. If your browser sends Do Not Track or Global Privacy Control, the analytics script does not load or report events.

This site stores only your light or dark theme choice in your browser. It stores that choice only when you use the footer switch.

The app sends product analytics to the same PostHog project, with session replay disabled. The app also sets cookies to keep you signed in.

How long we keep it

We keep waitlist addresses while the beta invitation program runs. We keep app data while your account exists. Email and hosting providers keep their own delivery and request logs under their own retention policies.

Account deletion removes your data from our active systems. Backup copies expire as those backups cycle out. A restore does not reactivate a deleted account or make its data accessible again.

Deleting your account and data

In the app, select Delete my account in Settings. Confirm with a recent sign-in. Confirmation immediately signs you out everywhere and revokes CLI tokens. It blocks new sessions and queued work, and stops running workers.

Deletion then removes your account, profile, and connected provider and GitHub credentials. It removes tasks, prompts, chat, session logs and results, and workspace artifacts. It also removes linked waitlist and invitation records. It removes identifiable analytics records where the provider supports deletion.

A cleanup step that cannot finish stays pending and retries. Barge reports cleanup complete only after all cleanup steps finish.

If you have only a waitlist entry and no account, email us to remove your address.

Account deletion does not remove external copies. Pull requests, commits, comments, and branches that Barge created stay in your GitHub account. You can manage or delete them there. Third-party copies, including delivered emails and agent-provider logs, follow their own policies.

Barge may keep a minimal deletion record to prevent a restored backup from bringing the account back.

Changes and contact

We update this notice as the beta changes. The date at the top identifies the latest version. The notice always lives at getbarge.io/privacy.

Contact Barge with questions about this notice or your data, including help with access, correction, or deletion:

info@getbarge.io