Boolu privacy policy

Version of 13 November 2026.

Boolu (https://boolu.app) is a service for teams to leave notes about their websites on the page itself, and for Claude Code (Anthropic's coding assistant, used by each customer) to read them and fix them. This policy explains which personal data we process, what for, who we share it with, how long we keep it and what your rights are.

1. Who is the controller

Pitinvestment, S.L. (single-member company), tax id B70784723, address Calle Gasco Oliag, 6, entresuelo 10, 46010 València (Spain), registered in the Registro Mercantil (Companies Register) of Valencia, volume 11521, book 8799, folio 196, section 8, sheet V-216473, 1st entry, privacy contact hello@boolu.app.

Boolu processes personal data in two different ways:

• As controller: account data (who you are, how you sign in), billing, support and the security of the service. This policy is mostly about that.
• As processor, on behalf of our customers: what a team leaves in its notes (text, screenshots, videos, conversations) belongs to that team's workspace. The company that owns the workspace is the controller of that data, and Boolu processes it only to provide the service, under the data processing agreement. If you appear in a customer's screenshot or video, or want to exercise your rights over their content, contact that company; we will help it answer you.

2. What data we process

Your account

• Name, e-mail address and password (stored with a one-way hash; nobody can read it).
• The workspaces you belong to and your role in each (owner, admin, team or per project).
• Whether and when you accepted the terms, and whether you confirmed your e-mail.
• Your preferred language and your time zone, to write to you at a reasonable hour. The time zone comes from your browser when you sign up or sign in, and you can change it in “Profile”.
• Which e-mails you want to get and, if you accept news and offers, each time you say yes or no: when and where from (sign-up, an invitation, the panel or “Profile”).

How and where you sign in from

• Browser sessions: IP address, browser and operating system (the user agent) and last activity.
• The devices and connections you authorise: the extension, Claude Code or other MCP clients, and scripts with a token. For each, its name, when it was created and when it was last used. Tokens are stored with a one-way hash.

What your team leaves in Boolu (as processor; see section 1)

• Projects: name and website addresses.
• Notes: the page address; the text; the element pointed at (its selector and its text); drawings on the screenshot; screen size, scroll position and pixel density; the browser (user agent); and, if the team asks for them, design values of the page (“variables”).
• Files: the screenshot of the page at the moment of the note, its thumbnail, the “after” image once fixed and, if someone records, the video of the tab with the microphone and, if turned on, the camera.
• Each note's conversation: comments, mentions, assignments and status changes, with who and when.
• If the project asks for it, a project preview: a screenshot of the top of one of its pages.
• Who is looking at a project right now, to show the others.

Billing (once there are paid plans)

• Handled by Stripe. We keep the Stripe customer id, the plan, the subscription status and the card's brand and last four digits, as Stripe gives them to us. We never receive or store the full card number.
• Each payment you start in Stripe and whether it was completed or expired unpaid; the discount code of an offer, if your workspace gets one; and, if you cancel a subscription, the reason you choose in Stripe.

E-mails we send you

Each e-mail belongs to one of these four kinds. The kind decides whether you can turn it off, in “Profile” → “Emails”, and on which legal basis we send it (section 3):

• Service, always sent: invitations and links to come in and review a project; e-mail confirmation and change and password reset; exports ready; handovers, closing and deletion of workspaces and of the account; reminders of a project's deadline and of a note that has been waiting days for your review; the end of the free trial, the confirmation that you cancel a subscription, and notices about the service and its terms.
• Activity, each of which you can turn off: when someone mentions you, when a note of yours is ready for review, and the weekly summary of your projects, which is only sent when there is something to tell.
• First steps, which you can turn off: the welcome, a few e-mails with the next step while you get started (they stop once you have taken them) and the notice that the free trial is ending, 4 days before and the day before.
• News and offers, only if you say yes: when you sign up or accept an invitation, with a box that comes unticked, or later in the panel or in “Profile”. They are Boolu's news and, now and then, an offer: when your workspace on the free plan reaches a limit or has been in real use for a while, when you leave a payment half-done, or a month after your cancelled subscription moves to the free plan.

The first steps, the weekly summary and news and offers carry the link to unsubscribe from that kind without signing in, and the header to do it in one click from your e-mail program. Those same e-mails are never more than one a day or three a week, and go out between 9:00 and 20:00 in your time zone, never on Sunday (except the welcome, sent when you sign up).

We measure without following you. The e-mails carry no tracking pixels and no links that count clicks, and we send them from our own mail server, with no service measuring opens. We keep which e-mail we sent you and when, so we never send you the same one twice; and if within the next 30 days you did in Boolu what it suggested (for example, installing the extension or subscribing to a plan), we note it next to that e-mail. All of it stays in our database.

Bounces and complaints. Each e-mail carries, in a header, the address it goes to with our signature, to recognise the notice if it bounces or someone marks it as spam. If your address bounces for good (it does not exist or is closed) or you mark one of our e-mails as spam, we note why and stop sending that address mentions, notices of notes ready for review, the weekly summary, first steps, notices about the trial and the subscription, the notices we send to everyone, and news and offers. When you change your e-mail in “Profile”, the new address starts afresh.

We do not use analytics, advertising or tracking tools, on the website, in the extension or in the e-mails. The website's fonts and assets are served from our own server.

3. Purposes and legal basis

We take no automated decisions with legal effects on you and do no profiling. Which e-mails you get is decided by fixed rules on the state of your account and your workspaces: the steps you have taken, the trial days left, whether a limit of the plan has been reached.

4. Who we share data with

We do not sell personal data or hand it to third parties for their own purposes. Only the providers we need to run the service share it with us, as processors or sub-processors:

Integrations your team turns on. If an admin connects a project to Slack, Boolu posts to that Slack channel the title, text and author of new or fixed notes and a link to their images. The customer decides and controls it; from there Slack processes it under the customer's own terms with Slack.

Claude Code and other MCP clients. Boolu sends no data to Anthropic or to any artificial intelligence provider. A person of the team connects their own Claude Code (or another MCP client) to their Boolu account. That client reads the notes that person can see and sends them to its model under the terms that person or their company has with that provider. The connection can be revoked at any time in “Profile”.

We may also disclose data to authorities when a law requires it.

5. International transfers

Data is stored on servers in the European Union. Some providers are US companies (DigitalOcean, Laravel and, for part of the payments, Stripe) and could access or process it from there. When that happens, they do so with appropriate safeguards: the EU-US Data Privacy Framework, for certified companies, or the European Commission's standard contractual clauses, included in their data processing agreements.

6. The Chrome extension

Boolu's extension works only on the tab where you open it, with its button or its keyboard shortcut. It does not read the pages you visit or your browsing history, and does nothing in the background on other tabs.

What it sends when you open it on a page:

• the address of that page, to find which of your team's projects it belongs to. If it belongs to none, Boolu does not keep it;
• if the project asks for one and you may change it, a screenshot of the top of the page as the project's preview.

What it sends while it is open on a page of a project:

• every few seconds it asks what is new in the project and says which page you are on (its path within that website), so your team can see who is looking at it. No history is kept: you stop showing about 20 seconds after you close it.

What it sends when you leave a note:

• the address of that page, the element you point at (its selector and its text) and the window size;
• a screenshot of the visible part of that tab;
• if you press “Record”, a video of that tab with the microphone and, if you turn it on, the camera. Recording only starts on that click, and a recording bar is shown until it stops.

Where it goes: only to Boolu's server (or Boolu's file storage, through a signed address that expires), into your workspace, visible only to those with access to that project.

What it keeps in your browser: your account access (a token), your name, whether you allowed the microphone and the camera and which one you chose, whether you want sounds, and the notes that could not be sent yet, to send them when the connection is back. Signing out of the extension deletes the access.

Signing in uses “Sign in with Boolu” (OAuth 2.0 with PKCE, through Chrome's sign-in window). It does not read or store your Google account.

Limited Use. Boolu's use of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements:

• we use it only for the extension's single purpose, leaving notes about a website for your team, as described in its listing and its interface;
• we do not sell it or transfer it to third parties, except to provide that service, to comply with the law, or in a merger or acquisition, with notice;
• we do not use or transfer it for advertising, to determine creditworthiness or for lending;
• nobody reads it except with your explicit consent for specific cases (for example, support you ask for), for security, to investigate abuse, or to comply with the law.

7. How long we keep it

What cannot be deleted from Boolu: e-mails and Slack messages already sent, and invoices issued by Stripe.

8. Your rights

You can ask for access, rectification, erasure, restriction and portability of your data, and object to its processing, by writing to hello@boolu.app. You can do many of these yourself in Boolu:

• Rectify: your name and e-mail, in “Profile”. An e-mail change is confirmed from the new address.
• Object and withdraw consent: in “Profile” → “Emails” you turn off each kind of e-mail that is not the service's and say no to news and offers. Also with the unsubscribe link in the first steps, the weekly summary and news and offers, in one click and without signing in.
• Take it with you (portability): “Profile” → export. You get a zip file with your account, your workspaces and roles, the notes and comments you wrote in the projects you can still see, with their files, and your devices and connections, in JSON and CSV. A workspace's owner can export the whole workspace in “Workspace”.
• Erase: “Profile” → delete account, with your password. Your sessions, access, exports and invitations are deleted at once, and so are the workspaces where you are alone. What you wrote in other teams' projects belongs to those teams and stays, but signed “Deleted account”, without your name or e-mail; where you were mentioned it reads “@Deleted account”. If you own a workspace with other people, you must hand it over or delete it first.

If you believe we have not handled your data properly, you can complain to the Spanish Data Protection Agency (www.aepd.es) or to the authority of your country.

9. Cookies

The website only uses technical cookies, needed for it to work:

We use no analytics, advertising or third-party cookies. As they are all technical and needed for the service you ask for, your consent is not required (art. 22.2 of Spain's LSSI).

10. Security

Everything is encrypted in transit (HTTPS). Passwords and tokens are stored with a one-way hash, and integrations' secrets (such as the Slack webhook address) encrypted. Files are private: served only to those with access, through signed links that expire. Each workspace is isolated from the others, and automated tests check it. Actions that cannot be undone (deleting, handing over, exporting) ask for the password again. If a security breach affected your data, we would notify the authority and, where required, you, within the legal deadlines.

11. Children

Boolu is a service for work teams. You must be at least 18 to create an account.

12. Changes

If we change this policy in a relevant way, we will tell you by e-mail or in the panel before it applies. The date of the version in force is at the top.

This text exists in Spanish and in English. If the two versions differ, the Spanish version prevails.