Effective 16 November 2026
Privacy notice
What Mesa stores when you use it, which outside services receive data, what your browser keeps, and the rights the EU General Data Protection Regulation (GDPR) gives you.
Who is responsible
Mesa is operated by Babete (babete.pt). Babete's registered legal name and postal address will be added to this page before Mesa opens beyond its private preview. Until then, write to mesa@babete.pt for anything about your data.
Mesa is in private preview. Access is by one password that Babete gives to the people it invites. There are no self-service accounts, no payments and no separate workspace per customer.
What Mesa stores
Mesa keeps what it needs to write a brief, and nothing about you as a visitor of the public pages:
- Your company's context: the name and website you give, and the profile Mesa drafts from that website and you review and edit (who you sell to, the problems you solve, what you offer, the people involved in buying, results you cite, objections and limits).
- The companies you ask about: the name you typed, the candidates found for it, and each company's name, website, country and what the company registers say about it.
- The public sources Mesa reads for a brief: the text of pages and documents on the company's own site and in the press, and of any PDF you upload for a brief, with its file name.
- The evidence of a brief: short quotes from those sources, with the source, its date and, when the source names the speaker, the person's name and role.
- The brief itself as generated, your edits to it beside it, what the brief cost to produce, and any error that stopped it.
- The progress of work in hand (drafting your context, finding a company): its steps and result, kept for the fifty most recent pieces of work.
- Your Mesas: for each opportunity with a company, its name, whether it is open, won or lost, and the dates it was made and closed.
- A room, if you make one for a Mesa: its headline and message, its colour, whether it is on, the date its link was made, how many times it was opened and when it was last opened. The room's link and passcode are kept only as hashes (a link or passcode cannot be recovered from them).
- The documents you share in a room: each file (PDF, Word, Excel, PowerPoint, PNG, JPEG, text or CSV), its name, title, description, category and size, how many times it was viewed and downloaded and when it was last viewed.
- Sign-in attempts and attempts to open a room: the network address and a count per fifteen-minute window, used to slow down password guessing. Counts from earlier windows are deleted the next time anyone tries to sign in, and an address's count is deleted when it signs in successfully. Attempts to open a room are counted the same way, per address and per room.
People named in a brief
A brief can name people who work at the company it is about, with what they said in public: in an annual report, a press release, an interview. Mesa takes this only from published sources, keeps the quote word for word with its source, and does not infer anything about a person's character or private life.
If you are named in a brief and want to know what is stored, or want it corrected or removed, write to mesa@babete.pt.
Who receives data
Mesa sends data to these services, and to no advertising or analytics service:
- Cloudflare runs the app and holds its database, which is located in Western Europe. Cloudflare R2 holds the documents you share in rooms, in Cloudflare's European Union jurisdiction. Cloudflare also keeps the app's operational logs, which include the websites and addresses of the companies you ask about and the address of each request to the app, which for a room includes the room's link, and resolves the internet addresses of the sites Mesa reads.
- OpenAI receives the text Mesa asks a model to read or write (source text, your company's context, the company's name) and runs the web searches for press coverage. Mesa asks OpenAI not to store its requests to read, write and search; to size a document, its text is also sent to OpenAI's token-counting service. OpenAI is based in the United States, so this is a transfer outside the European Economic Area, made under the terms OpenAI applies to its API.
- GLEIF and Wikidata, two public company registers, receive the company name you type (and GLEIF the country, if you give one), to find the company you mean.
- The websites Mesa reads receive an ordinary page request that identifies itself as Mesa. Mesa follows each site's robots.txt and does not read a site that refuses automated readers altogether. If you ask for a company's own documents to be read, Mesa can open pages that a folder rule in that company's robots.txt excludes; the brief says when it did.
What your browser keeps
Mesa sets no advertising or tracking cookies. Your browser keeps only what the app needs to work:
- session: a cookie that keeps you signed in, for twelve hours.
- login_csrf: a cookie that protects the sign-in form, for one hour.
- room_ followed by eight letters or digits (for example room_1a2b3c4d): a cookie that keeps a person inside the room they opened with its passcode, for twelve hours. It is sent only for that room's address, only over HTTPS, and page scripts cannot read it. It is set only after a correct passcode.
- mesa-theme: your choice of light or dark, in the browser's local storage.
- mesa-start: where you are in the onboarding, in the browser's session storage, gone when you close the tab.
- mesa-lang: your choice of language, in a cookie that lasts one year. Page scripts cannot read it.
Why Mesa may process this, and for how long
Under the GDPR, Mesa processes data to provide the service you asked for (your company's context, your briefs) and on the basis of legitimate interest (reading public business sources to prepare a sales conversation, keeping the service secure).
Briefs and company contexts are kept until they are deleted. A brief can be deleted from the list of briefs, with its sources, their text and its evidence. A document is deleted, with its file, when you remove it, and a Mesa is deleted with its room, its documents and their files when you delete it. None of that removes the company's record, your company's context or the names you typed: those, and anything else, are deleted on request.
Mesa makes no decision about a person and builds no profile of one.
If you open a room someone shared with you
A room is made and filled by a person who uses Mesa, who chooses what is in it and sends you its link and a passcode. You need no account.
When you enter the passcode, Mesa adds one to the number of times the room was opened. When you open or download a document, it adds one to that document's count and notes the time. Mesa does not record who you are: no name, no email, no network address, no browser details and no time spent on the page are stored with a visit. The person who shared the room sees only the counts.
To slow down guessing, Mesa counts passcode attempts by network address for fifteen minutes, as it does for sign-in attempts; your address's count is deleted when you enter the right passcode. Cloudflare's operational logs record each request's address, which includes the room's link. Your browser keeps one cookie for the room, named above, for twelve hours. If you choose a language, it also keeps the mesa-lang cookie, for one year.
Documents in a room come from the person who shared it. If something in one concerns you, write to mesa@babete.pt.
Your rights
You may ask for access to your personal data, for a copy, for its correction or deletion, for its processing to be restricted and, where it applies, to receive it in a portable form, and you may object to processing based on legitimate interest. Write to mesa@babete.pt.
You may also complain to a data protection authority. In Portugal this is the Comissão Nacional de Proteção de Dados (CNPD).
Questions about this page: mesa@babete.pt