How Brea browses the web, signs in, and pays for you

Brea connects to more than 2,000 apps, and it still runs into websites with no integration at all. The dentist with an online booking form. A regional airline. A county permit portal. The supplier who only takes orders through their own site. When a task lands on one of those, Brea opens a web browser and works through the site itself.

We get two questions about this more than any other: where do my passwords go, and who controls my money? This post answers both.

How the browser works

You text Brea in iMessage, something like "book me a cleaning at Dr. Patel's office, any weekday after 4." Brea opens the site in a browser, finds the booking page, picks a slot that fits, and fills in the form. When it's done, it texts you what it booked.

Sometimes it gets stuck on something only you know: two open slots and no way to choose, or a verification code sent to your phone. Brea texts you the question and waits. You can answer an hour later and the task picks up from the same page.

Anything with real consequences still needs your OK. Before Brea sends, deletes, shares, or changes a setting, it asks in iMessage, and you reply allow, always, or deny.

Passwords never go in a text

Plenty of tasks need you signed in, and Brea will never ask you to text it a password. When it needs a login, it sends you a link to a secure Brea page where you save the username and password yourself.

• Saved logins are encrypted and kept in a vault, apart from the AI.
• The AI never sees the password. When the browser reaches a sign-in form, the vault types the login in directly. The model only knows a login exists for that site.
• A login saved for one site can only be used on that site.

Signups work the same way. Ask Brea to open a new account for you and it sends the secure link before it starts, asking you to pick the password. Brea fills your password into both the password and confirm fields. It won't invent a password you've never seen, because the account belongs to you and you should be able to log in without Brea.

For the technical details of how we store keys and tokens, see our security page.

Paying with Link by Stripe

Some tasks end at a checkout page, like concert tickets, a restock order, or a deposit on a rental. For these, Brea uses a wallet from Link by Stripe.

• You connect your Link wallet once, and your card details stay with Link.
• You approve every purchase in Link. If you haven't approved it, Brea can't pay for it.
• Each approved purchase gets its own one-time card number. Your real card number is never typed into the site.
• That one-time card only works with the seller you approved. The vault enters it at checkout, so the AI never sees the card number either.

If a site gets breached or a checkout goes sideways, what's exposed is a single-use card for a purchase you already said yes to.

Why we built it like this

We started Brea because most AI tools stop at advice, and we wanted one that would finish the task. That only works if people are comfortable letting it near their accounts and their cards. So we kept the AI away from the secrets. It can use a login or a card when you allow it, and it never holds either one.

Want to try it? Sign up free and text Brea something that lives on a website, like "find the cheapest flight to Denver next Friday and send me the options" or "book a haircut Saturday after 2pm."