Privacy

Short version: your chats stay in your browser, but the things you ask about leave it. Below is exactly what goes where. If a line here ever stops matching the code, the line is the bug.

Voice mode sends your microphone audio to a third party

This is the one that matters most, so it goes first.

Voice mode uses your browser's built-in speech recognition. In most browsers that is notprocessed on your device — your microphone audio is streamed to the browser vendor's servers and text comes back. In Chrome that vendor is Google. In Safari it is Apple. In Edge it is Microsoft. Bugglo never receives your raw audio, and never stores it, but we are the reason it is sent, so we are telling you.

The reply is spoken back using your operating system's voices. Some of those voices are also synthesised remotely by the browser vendor, which means the assistant's reply text can be sent to them as well.

If you do not want any of that, do not use voice mode. Typing the same question sends nothing to Google, Apple, or Microsoft.

What stays in your browser

Chat history and interface preferences (theme, language, mode) are stored in your browser's localStorage. They are not uploaded to us. Clearing site data removes them permanently — we cannot restore them, because we never had them.

What is sent when you ask a question

Your message, the recent messages in that conversation, and any file you attach are sent to the chat backend, and from there to the language-model engine that answers. Attached images are sent as image data; attached documents are sent as extracted text.

To answer questions about a token, the engine calls tools. Those tools reach outside services — the Robinhood Chain RPC, DexScreener for market data, and the analysis servers configured for this deployment. They receive whatever the question requires, which is typically a contract address or a ticker. They do not receive your conversation.

Your IP address is used to rate-limit requests and to enforce spending caps. That is the only thing it is used for.

Incognito chats

An incognito chat is not written to your browser's stored history. That is what the setting does, and it does it completely.

It does not make the request private. The message is still sent to the backend and still sent to the engine, exactly as a normal chat is. We do not control whether the engine provider retains or trains on what it receives, and incognito mode does not change what they receive. Treat incognito as "not saved on this device", not as "not seen by anyone".

Signing in

Signing in with Google gives us the email address on that account, and nothing else. Signing in with a wallet asks you to sign a login message — a plain text string proving you hold the key. It is not a transaction, it cannot move funds, and Bugglo never asks you to approve one.

Never paste a secret

Never enter private keys, recovery phrases, passwords, or seed words into the chat. No part of this product will ever ask you for one, and anything that does is not us.