ArquiFlowSign inRequest access

Legal

Data Processing Agreement

Last updated October 31, 2026

What this agreement is

This is the agreement Article 28(3) of Regulation (EU) 2016/679 (the GDPR) requires between a controller and its processor. It applies whenever a studio uses ArquiFlow to hold or work on personal data about other people — its clients, the people at a site visit, the people in a photograph. For that data the studio is the controller and ArquiFlow is the processor.

For the data that makes you an account holder — your name, your sign-in, your studio membership, your subscription — ArquiFlow is itself the controller, and the privacy policy covers it rather than this page.

It is concluded by using the service: it forms part of the terms of service and needs no signature. A studio that needs a signed copy asks at hola@arquiflow.es and we send one signed on our side.

It runs for as long as the studio uses the service. It begins the first time the studio uploads anything about another person, and the processing ends when the material is erased or returned, as the termination section below describes.

This agreement is published in English, Spanish and Catalan. The Spanish version is the authoritative one; the other two are translations offered for convenience.

Subject matter, nature and purpose of the processing

The subject matter is the production of an acta — a site-work report, an inspection visit, a meeting, a safety or quality report, an ITE/IEE, an expert opinion or a change request — from what a studio uploads about one of its projects, together with the project work around it: estimates, plans, supplier quotes, and questions asked of a project’s own documents.

These are the operations ArquiFlow carries out on the studio’s material.

  • Storing what the studio uploads, and what the service produces from it.
  • Transcribing a recording of a site visit or a meeting.
  • Describing a site photograph and placing it in the acta.
  • Reading the handwritten notes on photographed pages of a site notebook.
  • Drafting the text of the acta and generating the PDF the studio issues.
  • Sending the issued PDF to the parties the studio names on it.
  • Extracting the text of an uploaded plan, technical document or supplier quote, and comparing quotes.
  • Indexing an issued acta and answering questions asked over a project’s own documents.
  • Looking up the cadastral reference of an address the studio types.

ArquiFlow performs them for the studio and for no purpose of its own. Nothing a studio uploads is sold or made visible to another studio: every read is scoped to the studio that owns the row, and that scope is enforced underneath the features rather than left to each of them.

Categories of personal data and of data subjects

The categories are whatever the studio puts into the service. In practice they are these.

  • Identifying and contact data — names, roles, tax IDs, professional registration numbers and colleges, telephone numbers and email addresses, in a report, in a request to sign one, in a project's agents, or in a plan, technical document or supplier quote.
  • Voice — the recording of a site visit or a meeting and the transcript made from it, which carry whatever was said and whoever said it.
  • Images — site photographs, which can show the people who were on site, and the descriptions written from them; and photographed pages of a site notebook, with the text read from them.
  • Location — the address of a site and the cadastral reference looked up from it, which identifies a property and through it, often, whoever owns it.
  • Free text — everything else the studio writes or uploads: findings, decisions, instructions, incidents.

And the people the data is about.

  • The studio’s clients and the people who work for them.
  • Owners, occupiers and neighbours named in a report.
  • The people present at a site visit or a meeting whose voice the recording carries.
  • The people visible in a site photograph.
  • The contact people at a supplier whose quote the studio uploads.
  • The agents of a project the studio records: developer, designer, works and execution directors, health and safety coordinators, contractor and site manager.
  • Anyone else the studio names in something it uploads.

The service is not built for the special categories of data in Article 9 GDPR — health, trade-union membership, biometric data used to identify someone — and a studio must not enter them. A recording of a site visit is voice, not a biometric identifier: nothing in the service measures a voice in order to recognise a person.

Processing only on the studio’s instructions — Art. 28(3)(a)

ArquiFlow processes the data only on the studio’s documented instructions, including as regards a transfer to a third country. The documented instructions are this agreement, the terms of service, and the studio’s own use of the features: uploading a recording is the instruction to transcribe it, issuing an acta is the instruction to generate its PDF and send it to the parties named on it, and asking a question of a project is the instruction to search that project.

There is no other instruction channel and none is needed. A studio that wants something outside them writes to hola@arquiflow.es, and what we agree is documented in that exchange.

If we believe an instruction breaks EU or Spanish data-protection law, we say so and do not carry it out. Where EU or Spanish law obliges us to process the data for a reason of its own, we tell the studio before we do it unless the law itself forbids telling it.

Confidentiality — Art. 28(3)(b)

Everyone with access to the data is bound to keep it confidential, and that obligation outlives their work on the service.

Access to production data is limited to the people who operate the service, is exercised through an administrative connection to the single server described below, and is used to keep the service running. Nobody at ArquiFlow reads a studio’s recording, report or document except where the studio asks in writing for help with a specific one, or where the law obliges us to.

Security measures — Art. 28(3)(c) and Art. 32(1)

These are the measures in place. They are described so that a studio can judge them, rather than summarised as an assurance.

  • Traffic between a browser and the service travels over TLS, on a certificate issued and renewed automatically at the edge.
  • Passwords are stored as a one-way hash and never in readable form. A signed-in session is carried by cookies that JavaScript in the browser cannot read and that, in production, are sent over HTTPS only.
  • Each studio’s rows are separated in the database by a filter applied to the queries that read them, which matches no row at all when no studio is in scope — so a query that forgets to name a studio returns nothing rather than everything.
  • Files live in a private object store, under keys the server generates rather than keys a client can guess. A file is served through the application, which checks which studio it belongs to first, and never from a public address.
  • What a member may do inside a studio follows the role the studio gave them, re-checked on the server for every action rather than only hidden in the interface.
  • Our own record of an AI call holds a digest — which model, which task, timings, token counts and a hash — and not the transcript or the document text. A test enforces that.

The database is dumped every night; the dump is encrypted before it leaves the server and stored in an object store under a 30-day retention lock that nobody can shorten. Older dumps are deleted, so a backup holds data for up to 31 days.

Subprocessors — Art. 28(2), Art. 28(3)(d) and Art. 28(4)

The studio gives general written authorisation, under Article 28(2) GDPR, for ArquiFlow to engage the subprocessors listed here. Each is engaged under a contract imposing the same data-protection obligations this agreement imposes on ArquiFlow, as Article 28(4) GDPR requires, and ArquiFlow answers to the studio for what a subprocessor does. The last column links to each provider’s own terms, because where a company processes data is a fact about that company and we will not assert it on its behalf.

SubprocessorWhat it doesWhereTheir terms
GroqTranscribes meeting and site-visit audio, and dictated clips (a report field, a building-code question, an incident or an estimate’s description).USPrivacy policy
OpenAI (transcription)Only when Groq is unavailable for a request: transcribes the same audio as Groq’s row.USPrivacy policy
AnthropicThe first provider for these tasks, within a monthly allowance: drafts the report from the transcript, the photo descriptions, the text read from handwritten notes and the studio’s supplier names, and then the titles and categories of its observations and a summary of each pinned plan page; reads, compares and ranks supplier quotes; drafts an estimate (from the description of the work, which can carry an address; the property’s details, which can come from the Catastro; the requested chapter titles; the supplier’s name for an imported quote that has no trade; the description, quantity and unit of the imported quote lines; and up to 150 descriptions from the studio’s price history, never a price); drafts a phase template from a file the studio imports; describes site photographs and reads photographed handwritten notes.US and other countries (global processing)Commercial terms and data processing addendum
Mistral AIDoes the tasks in Anthropic’s row, except the photographs and the handwritten notes, on the same content, when Anthropic fails, times out, is at its capacity limit or has used up its monthly allowance. It is also the first provider for these other tasks: answers building-code questions — which routinely carry a street address — with passages from the project’s own quotes, reports and documents when the question is about the project; reviews a quote for missing items against the project description and the other quotes; turns a dictated incident, with the studio’s supplier names, a dictated observation and a dictated new project into their fields; and drafts a trade report’s fields from pasted email or message text, or from a dictation.EU / EFTAData processing addendum
OpenAI (chat)Only when Anthropic and Mistral AI both fail, or Mistral AI alone on the tasks that start with it: does the text tasks in those two rows, on the same content. A provider fails when it returns an error, times out, is at its capacity limit or has recently been failing; Anthropic also when it has used up its monthly allowance. An estimate draft does not reach OpenAI: Anthropic drafts it and, when Anthropic cannot, Mistral AI.USPrivacy policy
OpenAI (vision)Only when Anthropic fails, times out, is at its capacity limit, has recently been failing or has used up its monthly allowance: describes the same site photographs and reads the same photographed handwritten notes.USPrivacy policy
OpenAI (embeddings)In production only: indexes passages of every issued acta and every uploaded regulation, of project documents and of supplier quotes, and every question asked of them.USPrivacy policy
Hetzner Object StorageIn production only: stores every file uploaded or generated — audio, photographs, plans, documents and the issued PDFs.DE — EUPrivacy policy
IONOS (the server)Runs everything: the database, every application process and the ingress access logs, on one single-node k3s server.ES — EUPrivacy policy
Catastro (Spanish Cadastre)Answers the cadastral lookup for an address the studio types.ES — EUElectronic office
NORA (Basque Government)Answers the street search for Álava, Bizkaia and Gipuzkoa with the street text the studio types. No personal data.ES — EUgeoEuskadi
Brevo (SMTP)In production only: delivers the transactional email the service sends — a request to sign an acta, a studio invitation, address verification, password recovery.FR — EUPrivacy policy
Paddle (payments)Account and billing data only, never the studio’s own material: it is the merchant of record that sells the subscription and charges for it.UK / USPrivacy policy
Paddle.js (in the browser)A visitor’s IP address on the public pricing page, so a price can be shown in their own currency.UK / USPrivacy policy
Google IdentityAccount data only: the sign-in identity of a member who chooses to sign in with Google.USPrivacy policy
Google Analytics 4Public-site visitors only, and only with their consent: never a studio’s material and never a page inside the application.IE / USPrivacy policy
PostHogOnly with each member’s consent, and never on the pages of a link that carries a code: records how the member uses the application — the structure and layout of the page, clicks, mouse movement, scrolling and navigation — and logs usage events with the page path, which carries the internal customer, project and report identifiers. Before anything leaves the browser, visible text is replaced by asterisks, form fields are masked, and images, canvases and videos — site photographs, signatures, plans shown as images — are replaced by an empty box. It receives neither the member’s name nor their email.DE — EU / USPrivacy policy
Meta Platforms Ireland (WhatsApp)Only for members who link their phone: carries what the member sends ArquiFlow over WhatsApp — voice notes from a site visit or a meeting, which record voices, and site photographs, which can show the people who were there — and the messages ArquiFlow answers with, which can carry project and client names.IE — EU / USWhatsApp Business data processing terms

We tell studios by email about any intended addition or replacement of a subprocessor before it takes effect. A studio may object on reasonable data-protection grounds and, where we cannot meet its objection, it may end its subscription without penalty and with nothing further to pay.

The server host is the row a list like this most often leaves out and least can afford to: every category above passes through it.

Transfers outside the European Economic Area — Art. 46(2)(c)

Some of the subprocessors above are outside the EEA, and the studio’s general authorisation covers those transfers. This is what each one rests on.

  • The United States — Groq, OpenAI, Google, PostHog and Paddle’s US operations. PostHog hosts the data in Frankfurt, but PostHog, Inc. is a US company. OpenAI also receives the content Anthropic and Mistral AI receive, for a request neither of them serves, the photographs and handwritten notes Anthropic receives, for a request Anthropic does not serve, and the audio Groq receives, for a request Groq does not answer. The safeguard is the European Commission’s standard contractual clauses under Article 46(2)(c) GDPR, incorporated in each provider’s data processing terms; where a provider is certified under the EU–US Data Privacy Framework, that certification applies instead.
  • The United States and other countries — Anthropic. As we use it, Anthropic processes the data globally, in the United States and in other countries. The safeguard is the European Commission’s standard contractual clauses under Article 46(2)(c) GDPR, incorporated in the data processing addendum that forms part of its commercial terms.
  • The United States — Meta Platforms, Inc., for WhatsApp. ArquiFlow uses the WhatsApp Business platform of Meta Platforms Ireland Ltd, which also processes the messages and files in the United States through Meta Platforms, Inc. The safeguard is the European Commission’s standard contractual clauses under Article 46(2)(c) GDPR, incorporated in the WhatsApp Business data processing terms; where the provider is certified under the EU–US Data Privacy Framework, that certification applies instead.

No AI task has an EEA-only mode to switch to, and no task’s data is guaranteed to stay in the EU. By default, drafting the report and its notes, reading, comparing and ranking quotes, the estimate draft, the imported phase template, photo description and the reading of handwritten notes go to Anthropic, outside the EEA (US and other countries); only when Anthropic fails or has used up its monthly allowance do they go to Mistral AI (EU / EFTA) or, for photographs and handwritten notes, to OpenAI (US). Requests for the tasks in Anthropic’s and Mistral AI’s rows go to OpenAI (US) when neither of them serves them, except those for an estimate draft. Transcription (Groq, US, and OpenAI, US, when Groq is unavailable for a request) and, in production only, the search index (OpenAI, US: passages of every issued acta and every uploaded regulation, of project documents and of supplier quotes, and every question asked of them) leave the EEA too. A studio that cannot accept a transfer outside the EEA cannot use these features as they are built today. That is worth reading before a recording is uploaded rather than after, because the studio chooses what goes into a recording or a document in the first place.

Ask us at hola@arquiflow.es for the safeguard relied on for any single provider, and we send what we hold.

Helping with a data subject’s request — Art. 28(3)(e)

If someone whose data a studio uploaded exercises a right — access, rectification, erasure, restriction of processing, objection or portability — the studio answers them: the studio is the controller and holds the relationship. ArquiFlow assists, taking into account the nature of the processing, so the studio can answer within the month Article 12(3) GDPR allows it.

The assistance is given by hand. Write to hola@arquiflow.es from an address on the studio’s account, name the project and the person, and say what the request asks for. We find the material, tell the studio where it is — a recording, a transcript, an acta, a photograph, an index entry — and then either erase it or send the studio a copy of it, within ten working days of a clear request, which leaves the studio the rest of its month.

There is no button for answering a data subject: the service has no self-service mechanism for access to, erasure of or portability of one person's data, and a written request is the only route, answered by a person. The only self-service erasure is of the whole studio, described in the erasure-or-return clause.

If a data subject writes to us directly, we do not answer for the studio: we tell them to contact the studio, and we tell the studio it happened, unless the law requires otherwise.

Security, breaches and impact assessments — Art. 28(3)(f)

ArquiFlow assists the studio in meeting its own obligations under Articles 32 to 36 GDPR, given the nature of the processing and what we hold.

  • A personal data breach — we notify the studio without undue delay after becoming aware of one, as Article 33(2) GDPR requires, with what we know: what happened, which categories and roughly how many people and records are involved, the likely consequences, and what we are doing about it. Whether the AEPD or the people affected are notified is the studio’s decision, and we give it what it needs to take it.
  • A data protection impact assessment — we answer written questions about how the processing works, what goes where, and on what safeguard, so the studio can carry one out. A studio that records people who do not know this service exists is the case for doing one.
  • Prior consultation with a supervisory authority — we provide the same information.

None of this makes ArquiFlow the studio’s data protection officer, and none of it is legal advice.

Erasure or return when the processing ends — Art. 28(3)(g)

When the processing ends, the studio's material is erased in one of two ways. The owner deletes the studio from Settings and, 14 days later, everything the studio uploaded and everything the service produced from it is erased, its files included; or the studio asks us in writing at hola@arquiflow.es and we do it within 30 days of a clear request.

Return is asked for in writing at the same address, before the studio is deleted: we send a copy within 30 days of a clear request and, if asked, erase the material afterwards. The studio keeps working during those 14 days, so it can also download the PDFs of its actas and estimates itself.

The studio's members' accounts are anonymised in the same erasure. Database backups hold a copy for up to 31 days, until they expire, and if one ever has to be restored the erasure is repeated on it.

After that we keep only what European or Spanish law obliges us to keep: the accounting and tax records of the subscription, which are account data and belong to the privacy policy, not to this agreement. Paddle keeps its own billing records as merchant of record.

Information and audit — Art. 28(3)(h)

ArquiFlow makes available the information needed to show that this agreement is being met, and submits to audits and inspections by the studio or by an auditor it mandates.

In practice that is written questions answered in writing, and this page: each section names the files in our own source tree that back what it says, and a test resolves every one of those paths and fails the build when one of them moves.

An audit that reaches the systems themselves is arranged in advance, at a reasonable time, under confidentiality, and no more than once a year unless a breach or a supervisory authority’s request makes another one necessary. It cannot extend to another studio’s data, which is the one thing we refuse.

One boundary worth naming: removing a member

A studio administrator can remove a member from the studio. That does two things at once: it ends the membership, and it closes that person’s whole platform account — not only their access to that one studio.

It belongs in this agreement because it is the one place where an instruction from the controller reaches a data subject for whom ArquiFlow is itself the controller: the account holder. We carry it out, because the studio decides who is on its team; what the person affected can do about their own account is in the privacy policy. An administrator who only means to end someone’s access to one project should know that this is what the action does.

Changes to this agreement

The date at the top of this page is the day it last changed. A change that affects a studio’s obligations, or the list of subprocessors, is announced by email before it takes effect. A change that only makes the same thing clearer is published here.

Anything about this agreement, including a request for a copy signed on our side, goes to hola@arquiflow.es.

Back home