Security & compliance
Built for local government: what we do with the data, where it is processed and who decides what gets published.
The red line: fe pública stays yours
EnaScribe writes drafts; it never certifies. Every generated text carries a visible AI label until you review it, and the only official minutes are the ones you sign. No feature of the product suggests otherwise: that is our design commitment, in writing.
Nothing is published without review
The public page shows nothing until a secretary or an editor reviews the session, marks the secret items and confirms publication. A published session can be unpublished.
Where the data is processed
Audio is transcribed on our own servers, with speech-recognition models we run ourselves. To draft titles, summaries and minutes, the transcript text is sent to Google (Gemini API), acting as a sub-processor.
GDPR and data processing
The town is the controller and we are the processor (GDPR art. 28). We sign a data-processing agreement that lists the sub-processors, Google included.
Secret items (art. 70.1 LBRL)
Items marked secret never appear on the public page or in public audio clips. In the exported minutes, the town chooses whether they are excluded, shown by title only, or included in full for the official internal minutes.
AI transparency
All automatically generated content carries an 'AI-generated' label until a human reviews it, including on the citizen-facing public page.
Access control and traceability
Role-based access (contributor, editor, secretary) and a history of every edit with its author. We are working towards Spain's ENS basic level; the conformity statement is still pending.
Cookie-free public page
The public session page uses no cookies and no tracking identifier. The language is chosen through the address and remembered in the browser.
Accessibility
Public pages are designed to meet WCAG 2.1 AA (EN 301 549). They have not had an external audit yet.