Privacy Policy

Last updated: May 5, 2026

Plain-English summary

This is a TL;DR. The full text below is the legally binding version.

We are Bruno, based in Massachusetts, United States. Our service is an embeddable AI support assistant that runs on customer websites.
You are the customer if you signed up for a Bruno account. You are the visitor if you used a website that has Bruno installed.
For visitors, the customer is the data controller. Bruno is the data processor. Look at the customer's own privacy policy first.
For customers, Bruno is the controller. We collect what we need to run the service - account info, billing info, audit logs.
We do not sell personal data. We do not use your data to train AI models.
Email help@bruno.support for any privacy request.

1. Scope

This Privacy Policy explains how Bruno (referred to as "Bruno", "we", "us", or "our") collects, uses, and shares personal data when you:

Visit bruno.support or any subdomain (collectively, the "Marketing Site").
Sign up for and use the Bruno dashboard at app.bruno.support (the "Service").
Interact with the Bruno widget while visiting one of our customers' websites (a "Customer Site").
Email us, or otherwise communicate with us.

2. Our roles

Different activities give us different roles under data-protection laws like the EU/UK GDPR and similar regimes:

Marketing Site & Service. When you visit our pages or sign up for an account, we are the controller of your personal data.
Customer Sites. When you interact with the widget on a customer's site, that customer is the controller of any personal data they collect via the widget. We act as their processor under our Data Processing Agreement (DPA).

If you are a visitor with questions about how a specific customer uses Bruno on their site, please contact that customer first; their privacy policy applies. We will help them respond if they ask us to.

3. Data we collect

3.1 From customers (account holders)

Account info: name, email, hashed password, organisation name, role.
Configuration: websites you've added, embed keys, knowledge files you upload (PDFs, text, markdown).
Billing: plan, billing email, country, currency, last 4 digits of card, payment-processor customer / subscription IDs. Card data itself is held by our payment processor, not by us.
Usage data: dashboard logins and an internal audit log of administrative actions taken on the account (used for security and incident response, not exposed in the dashboard today).
Communications: emails to help@bruno.support, support tickets you open, optional product feedback.

3.2 From visitors (end-users of customer sites)

When the widget is loaded on a customer's site, we process the following on the customer's behalf:

Conversation content: messages typed by the visitor, replies returned by Bruno, and any consent decisions for hybrid actions.
Page context: a redacted summary of the current page (URL, title, headings, visible interactive elements, same-origin links). We do not extract form values.
Technical metadata: a session ID stored in localStorage, IP address (truncated), coarse user-agent for diagnostics, request timestamps.

Bruno does not read passwords, payment fields, or hidden inputs. The action runner refuses to fill, click, or interact with any input of type password.

3.3 From visitors of the Marketing Site

Logs: standard server logs - IP, user-agent, requested path, timestamp - retained briefly for security and debugging.
Cookies: see our Cookie Policy.

4. How we use it

To deliver the Service - host the dashboard, run the widget, generate replies, store conversations.
To support you - reply to help@bruno.support emails, debug issues, monitor uptime.
To bill - manage subscriptions and top-ups via Stripe, send invoices and receipts.
To secure the Service - detect abuse, rate-limit, log security events, investigate incidents.
To improve - measure aggregate usage trends and reliability. We do not use your conversation content or knowledge files to train AI models.
To comply with law - respond to lawful requests and meet our legal obligations.

5. Lawful bases (EEA / UK)

Under EU/UK GDPR we rely on the following lawful bases:

Performance of a contract - to provide the Service to customers and process payments.
Legitimate interests - to secure the Service, prevent abuse, and improve reliability. We balance our interests against your rights.
Consent - where required for non-essential cookies or specific marketing communications.
Legal obligation - to comply with tax, accounting, and other applicable laws.

6. Retention

Conversations and messages: retained while the customer's account and the corresponding website are active. They are deleted when the customer deletes the website or the account, or earlier on request to help@bruno.support.
Knowledge files: kept until the customer deletes the file or the website. Deletion removes the file and purges its embeddings.
Internal audit logs: retained for the period necessary to operate and secure the Service.
Account & billing records: retained while the account is active and for as long as legally required for tax and accounting compliance after closure.
Server logs: retained briefly for security and debugging, then aggregated or deleted.
Backups: provider-managed backups are encrypted and retained for disaster recovery only; data restored from a backup is removed again on the next normal cycle.

Self-service retention controls and dashboard exports are not currently available. If you need them sooner than we can ship them, contact help@bruno.support.

8. International transfers

Bruno is operated by a small team and uses subprocessors in multiple regions. Where personal data is transferred outside the EEA / UK / Switzerland, we rely on appropriate safeguards such as the EU Standard Contractual Clauses (SCCs) and the UK International Data Transfer Addendum, supplemented by technical measures including encryption in transit and at rest. The current data-processing locations are listed on the Subprocessors page.

9. Your rights

Depending on where you live, you may have rights to:

Access the personal data we hold about you.
Rectify inaccurate data.
Erase data, subject to legal retention obligations.
Restrict or object to processing.
Data portability.
Withdraw consent at any time, where processing is based on consent.
Lodge a complaint with your local data-protection authority. We'd appreciate the chance to address your concern first - email us at help@bruno.support.

If you are a visitor on a customer's site, please address requests to that customer first - they are the controller of your conversation with the widget on their site. Customers can in turn ask Bruno to fulfil access or deletion requests by emailing help@bruno.support.

10. Cookies and similar technologies

We use a minimal set of cookies and equivalent storage. See the Cookie Policy for the per-cookie table.

11. Children

The Service is not directed at children under 13 (or 16 in some jurisdictions) and we do not knowingly collect personal data from them. If you believe a child has provided us with personal data, contact help@bruno.support and we will delete it.

12. Changes to this policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top reflects the most recent change. For material changes, we will notify customers via email or dashboard banner. Continued use of the Service after a change constitutes acceptance of the updated policy.

13. Contact

For privacy questions or to exercise your rights, email help@bruno.support. The legal entity responsible for processing under this policy is Bruno, located in Massachusetts, United States. The applicable governing law is the Commonwealth of Massachusetts, United States.