Effective 16 November 2026
Security
How Mesa protects access and data today, what it does not claim, and how to report a problem.
Access
The app is behind a sign-in. The password is stored only as a salted scrypt hash. A session lasts twelve hours, its cookie cannot be read by page scripts and is sent only over HTTPS, and every change you make while signed in carries a token tied to your session, so another site cannot act in your name.
Repeated failed sign-ins are slowed down, per network address and overall.
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.
Rooms
A room is reached only with its link and its passcode. The link carries 32 random bytes; Mesa stores only its SHA-256 hash, so the link cannot be rebuilt from the database and is shown to the seller once, when it is made. The passcode has at least six characters and is stored only as a salted scrypt hash. Wrong passcodes are slowed down per network address and per room. Anyone who has both can open the room: Mesa does not tell people apart.
After a correct passcode the visitor gets a cookie that lasts twelve hours, is sent only to that room's address, only over HTTPS, and cannot be read by page scripts. A new link or a new passcode ends it. While a room is switched off it does not open; switched on again, a visit still within its twelve hours continues. An unknown link and a switched-off room give the same page, so one cannot be told from the other.
Documents are kept in Cloudflare R2, in its European Union jurisdiction, in a bucket with no public address; they are sent only through a room, after the visitor is let in. Mesa accepts only PDF, Word, Excel, PowerPoint, PNG, JPEG, text and CSV files, checks each file's first bytes against its extension, and sends it with its stored type and a rule that stops the browser from guessing another. Web pages (HTML) and SVG images are refused, so a file cannot run as a page on Mesa's address.
Room pages are kept out of search results, are never stored by a cache and send no referrer to other sites.
Data in transit and at rest
Everything travels over HTTPS, and browsers are told to use HTTPS only. The app and its database run on Cloudflare; the database is located in Western Europe, and uploaded documents are held in Cloudflare R2's European Union jurisdiction.
The keys for the model provider are held as secrets on the server. They are never sent to a browser and are not in the source code.
The pages themselves
Pages load scripts only from Mesa's own address, cannot be shown inside another site's frame, and send no referrer to other sites. Text that comes from a source or from a form is shown as text, never run as code.
Reading the web
Mesa reads only public pages, identifies itself as Mesa, follows each site's robots.txt (including its signal about use by AI), and does not work around sign-ins or paywalls. The one exception is a company's own documents, which you can ask Mesa to read despite a folder rule in that company's robots.txt; the brief says so. Each brief has a spending limit, after which Mesa stops reading.
What Mesa does not claim
Mesa has no security certification and has not had an independent security audit. It does not yet have separate accounts or separate storage per customer: all documents share one bucket, kept apart by the app. Mesa does not scan uploaded documents for malicious content. Cloudflare's operational logs record each request's address, which for a room includes its link; the passcode is still needed to open the room. When any of this changes, this page will say so.
Reporting a problem
If you find a weakness in Mesa, write to mesa@babete.pt with the steps to reproduce it. Please do not test against other people's data or disrupt the service. We answer every report.
Questions about this page: mesa@babete.pt