Mesa

Effective 16 November 2026

Data processing and subprocessors

How Babete processes data on behalf of a business that uses Mesa, under Article 28 of the EU GDPR, and the other companies involved.

Status

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.

This page describes the processing as it is today. A business that is given access and needs a signed data processing agreement can ask for one at mesa@babete.pt.

Roles

For the content a business puts into Mesa (its company context, the documents it uploads, its edits), the business is the controller and Babete is the processor, acting on the business's instructions given through the app.

For the reading of public sources that Mesa does to write a brief, and for operating the service, Babete is the controller, as set out in the privacy notice.

What is processed

Processing is limited to what a brief needs:

Subprocessors

Babete uses these companies to provide Mesa:

Transfers outside the European Economic Area

The database stays in Western Europe and uploaded documents stay in Cloudflare R2's European Union jurisdiction. Text sent to OpenAI for a model to read or write is processed in the United States, under the terms OpenAI applies to its API. Cloudflare serves requests from its network worldwide.

Measures, deletion and changes

The technical measures are described on the security page. 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 it is removed, and a Mesa with its room, documents and files when it is deleted. A room's link and passcode are stored only as hashes. All of a business's data is deleted on request.

If a subprocessor is added or replaced, this page is updated before the change takes effect.

Questions about this page: mesa@babete.pt