Privacy Policy
Last updated November 21, 2026
Who is responsible
ArquiFlow operates https://arquiflow.es and is the controller of the personal data described on this page. Write to us about anything here at hola@arquiflow.es.
This policy is written under Regulation (EU) 2016/679 (the GDPR) and Spanish Organic Law 3/2018 on data protection and the guarantee of digital rights.
There are two relationships here and this policy only covers the first. For the data that makes you an account holder — your name, your sign-in, your studio membership, your subscription — ArquiFlow decides what happens to it and answers for it. For what a studio uploads about its own clients, sites and the people at a site visit — recordings, photographs, plans, documents — the studio decides, and ArquiFlow acts on its instructions. That second relationship is governed by the data processing agreement between the studio and ArquiFlow, not by this page.
What we hold, why, and on what legal basis
Every category the service holds, what we do with it, and the Article 6 basis that permits it.
| Data | What it covers | Why we hold it | Legal basis |
|---|---|---|---|
| Account | Your name, email address, a hash of your password, your interface language, your colegiado number and college if you give them, and — if you sign in with Google — the identity Google returns. | To create your account, sign you in and keep you signed in, and to identify you by your name and registration on the documents you sign or draft. | Contract, Art. 6(1)(b). |
| Activity | The last time you used the app while signed in, noted at most once an hour. It stops being noted once your account is deleted, and is kept until your account is erased. | To give support, and to spot accounts that have stopped using the service. | Legitimate interest, Art. 6(1)(f). |
| Studio | The studio name, its legal name, tax ID, address, phone and contact email, its seats, each member’s role, and invitations sent, accepted or revoked. | To run the shared workspace, decide who may do what inside it, and identify the studio on the actas and estimates it issues. | Contract, Art. 6(1)(b). |
| Meeting audio | Recordings a studio uploads from a site visit or a meeting, and the transcript produced from them. | To transcribe the recording and draft the acta from it. | Contract, Art. 6(1)(b), on the studio’s instructions. |
| Photographs | Site photographs a studio uploads, and the descriptions written from them, and the pages of a site notebook it photographs, with the text read from them. | To describe each photograph and place it in the acta, and to read the handwritten notes and draft the acta from them. | Contract, Art. 6(1)(b), on the studio’s instructions. |
| Report content | Drafted and issued actas, plans, technical documents, supplier quotes and the text extracted from them. | To produce the acta and the PDF the studio issues to the parties. | Contract, Art. 6(1)(b), on the studio’s instructions. |
| Cadastral lookups | Addresses a studio types when it looks up the cadastral reference of a site. | To query the Spanish Cadastre and return the reference for that address, or, in Álava, Bizkaia and Gipuzkoa, to look the street up in NORA, the Basque Government’s street directory. | Contract, Art. 6(1)(b), on the studio’s instructions. |
| Billing | Your name, email address, billing address, the state of your subscription and the invoices raised. Card details are typed into the payment provider’s own form and never reach our servers. | To sell you a subscription and to keep the accounting and tax records the law requires. | Contract, Art. 6(1)(b), and legal obligation, Art. 6(1)(c). |
| Public-site analytics | On the public pages only: the page address with its parameters, among them the campaign (`utm_`) parameters if you arrived through a campaign link; a coarse location derived from your IP address; your device and browser; and the notice that you sent an early-access request or asked for a downloadable template and which one, with nothing you wrote in either. | To see which public pages people read and which campaigns bring early-access requests and template requests. | Consent, Art. 6(1)(a). Nothing is collected until you accept, and refusing costs you nothing. |
| Session recordings and product analytics | On the public pages and inside the studio: a recording of the session (the structure and layout of the page, clicks, mouse movement, scrolling and navigation), usage events such as page views, clicks, sending an early-access request and asking for a downloadable template (with nothing you wrote in either), the page path without its query string or fragment, the campaign (`utm_`) parameters of the link you arrived through, a coarse location derived from your IP address, and your device and browser. Inside the studio the visible text is replaced by asterisks before it leaves the browser. It is not linked to your account, your name or your email. | To see how the product is used and where people get stuck, and to fix it. | Consent, Art. 6(1)(a), under the same analytics choice. Nothing is collected until you accept, and refusing costs you nothing. |
| Early-access requests | Your email and, if you give them, your name, your company and your profession (and, if you pick “Other”, the one you type); plus the form’s language, whether you want news and when you ticked it, when you sent the request and whether we have invited you; and, if you arrived through a campaign link or from another site, the campaign parameters (source, medium, campaign and content) of the link you came in through and the domain of the site that sent you, never its full address; those of the first request that carries them are kept, not those of later ones. | To review your request by hand, invite you if it fits, prepare the demo if you ask for one, write to you in your language and see which campaigns and sites bring requests; and, only if you tick the news box, send you news about ArquiFlow. | Your own request, Art. 6(1)(b): we review it because you ask us to. Without your email we cannot handle it. You can withdraw it, and we erase it, by writing to us at any time. News needs your consent, Art. 6(1)(a), in a separate, unticked and optional box; you withdraw it by writing to us or by sending the form again without ticking it. The campaign parameters and the referring domain are kept on the basis of legitimate interest, Art. 6(1)(f): to see which campaigns and sites bring requests, without combining them with anything else or using them to profile you. |
| Downloadable templates | Your email; the page’s language; which documents you asked for and when, when we sent each email, when you downloaded each file and how many times; when you ticked the privacy box; if you ticked the news box, the version of its wording, when you confirmed it from the email and, if you unsubscribe, when; and, if you arrived through a campaign link or from another site, the campaign parameters (source, medium, campaign and content) of the link you came in through and the domain of the site that sent you, never its full address; those of the first request that carries them are kept, not those of later ones. The pages the email’s links open collect nothing more: your IP address is used only to limit repeated attempts and is not stored with your request. | To send you the document you ask for; to see which campaigns and sites bring requests; and, only if you tick the news box and confirm it from the email, to send you commercial communications about ArquiFlow: product news and new templates. | For sending you the document, your request, Art. 6(1)(b). For commercial communications, your consent, Art. 6(1)(a): a separate, unticked and optional box that does not count until you press “Confirm subscription” in the email, and that you withdraw with the unsubscribe link in every email. The campaign parameters and the referring domain are kept on the basis of legitimate interest, Art. 6(1)(f): to see which campaigns and sites bring requests, without combining them with anything else or using them to profile you. |
| Only if you link your phone from your profile: your WhatsApp number and when you linked it; and, while you prepare an acta over WhatsApp, the project and the acta type you choose and the identifiers Meta gives your voice notes and photographs, and the written notes sent over WhatsApp. Those voice notes and photographs become the acta’s audio and photographs, and the written notes are kept with the acta, which ArquiFlow drafts from them. | To recognise your messages, prepare the acta from what you send ArquiFlow, and reply in the same chat. | Contract, Art. 6(1)(b). |
Analytics and session recording
The public site — this page, the home page, the pricing page — carries two analytics tools: Google Analytics 4 and PostHog. Both depend on the same choice. Neither is loaded, nor is its code even downloaded, until you accept analytics cookies; both stop the moment you refuse or change your mind; and both run only on the site’s production domain. The Google Analytics 4 tag denies advertising storage outright: the only advertising tool is the Meta pixel, described next, which depends on a separate choice.
The public site also carries the Meta pixel, to measure our ads on Instagram and Facebook. It loads only if you accept advertising cookies, only on the public pages and only on the production domain; never inside the studio. It sends Meta Platforms Ireland the public pages you visit, your IP address and browser, the identifier in its cookies and a notice when you submit an early-access request or ask for a template, without your email or anything you wrote. It does not read form fields. If you have an Instagram or Facebook account, Meta may link the visit to your account: that is how we learn how many requests each ad brought and can show our ads again to people who already visited the site. The legal basis is your consent. ArquiFlow and Meta Platforms Ireland are joint controllers for collecting and transmitting this data; what Meta does with it afterwards is Meta’s decision, under its Privacy Policy.
When you send an early-access request, both receive a notice that it was sent and nothing you wrote in it. Together with the campaign (`utm_`) parameters of the link you arrived through, that tells us which campaign brought the request. Asking for a downloadable template works the same way: Google Analytics 4 receives which template you asked for and PostHog that you asked for one, and neither receives your email.
Google Analytics 4 does not run on the authenticated studio pages. The tag is removed from the page as soon as you enter the application, rather than being left loaded and quiet, because Google Analytics 4 attaches the page address to what it reports by itself — and inside the application that address carries customer, project and report identifiers. They never reach Google.
PostHog, by contrast, also runs inside the studio and on the trade dashboard, so that we can see how the product is used. It records the session — the structure and layout of the page, clicks, mouse movement, scrolling and navigation — and logs usage events such as page views and clicks, together with the page path without its query string or fragment, the campaign (`utm_`) parameters of the link you arrived through, a coarse location derived from your IP address, and your device and browser. Inside the studio that path carries the internal customer, project and report identifiers, not their names.
This is what happens in your browser before anything leaves it. The value of every form field is masked on every page. Images, canvases and videos — and with them site photographs, drawn signatures, logos and plans shown as images — are replaced by an empty box, as are hidden fields and file-upload fields. Inside the studio all visible text is replaced by asterisks and the page title is dropped. In click events the text of the clicked element and its attributes are masked. Neither the body nor the headers of network requests are recorded. On the public pages visible text is recorded as it is, because it is the site’s public text.
PostHog does not run on the pages reached through a link that carries a code: resetting your password, accepting a studio invitation, verifying your email, a trade’s parte link, the link to sign an estimate and the links in a downloadable template’s email (the download, confirming the subscription and unsubscribing). On those pages the recording is paused and every event is dropped, and if the address of one of them appears in another event it is replaced by `/redacted`.
PostHog does not identify you: it receives neither your account, your name nor your email, only an anonymous identifier kept in your browser. The data is hosted in PostHog’s EU Cloud, in Frankfurt (Germany). PostHog, Inc. is a US company, and that transfer rests on what is described below.
Your choice is stored in your own browser, and you can change it at any time from the cookie settings on this page. The cookie policy on this site lists every cookie the application can cause to exist.
The pricing page loads the payment provider’s script so it can show you the price in your own currency, which means the provider reads your IP address to work out which country you are in. We treat that as strictly necessary to the price display you asked for, so it is not gated behind consent. It is disclosed here and in the cookie policy rather than left unsaid.
Who else receives it
These are the providers the service runs on. Each one receives only what its row describes. The last column links to the 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.
| Recipient | What it receives | Where | Their terms |
|---|---|---|---|
| Groq | Meeting audio and dictated clips (a report field, a building-code question, an incident or an estimate’s description), for transcription. | US | Privacy policy |
| OpenAI (transcription) | Only when Groq is unavailable for a request: the same audio as Groq’s row, for transcription. | US | Privacy policy |
| Anthropic | While a monthly allowance lasts, the first to receive: the transcript, the photo descriptions, the text read from handwritten notes, the studio’s supplier names and the report text, to draft the report and to title, categorise and summarise its observations and pinned plan pages; supplier-quote text, to read, compare and rank the quotes; an estimate draft (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); a phase file the studio imports, to turn it into a template; and site photographs, for description, and photographed notebook pages, to read the handwritten notes. | US and other countries (global processing) | Commercial terms and data processing addendum |
| Mistral AI | The same content as Anthropic’s row, except the photographs and notebook pages, when Anthropic fails, times out, is at its capacity limit or has used up its monthly allowance. And, as the first recipient: building-code questions, which routinely carry a street address, together with passages from the project’s own quotes, reports and documents when the question is about the project; a quote, with the project description and the other quotes, to point out the items it is missing; dictated incidents, with the studio’s supplier names, dictated observations and dictated new projects, to fill in their fields; and the pasted email or message text, or the dictation, of a trade report, to fill in its fields. | EU / EFTA | Data processing addendum |
| OpenAI (chat) | Only when Anthropic and Mistral AI both fail, or Mistral AI alone on the tasks that start with it: the same content as those two rows, except the photographs and notebook pages. 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. | US | Privacy 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: the same site photographs, for description, and the same photographed notebook pages, to read the handwritten notes. | US | Privacy policy |
| OpenAI (embeddings) | In production only: passages of every issued acta and every uploaded regulation, of project documents and of supplier quotes, and every question asked of them. | US | Privacy policy |
| Google (Analytics 4) | On public pages only, and only with your consent: the page path, a coarse location from your IP address, your device and your browser. Never on the authenticated studio pages. | IE / US | Privacy policy |
| PostHog (session recording and product analytics) | Only with your consent, on the public pages and inside the studio, never on the pages of a link that carries a code: the session recording, with form fields masked, images blocked and, inside the studio, all text replaced by asterisks; usage events; the page path; a coarse location from your IP; your device and browser. Neither your name nor your email. | DE — EU / US | Privacy policy |
| Paddle (payments) | Your name, email address, billing address and payment data. Paddle is the merchant of record: it is who sells you the subscription and who charges you. | UK / US | Privacy policy |
| Paddle.js (in your browser) | Your IP address, so the pricing page can show a price in your own currency. | UK / US | Privacy policy |
| Google Calendar | What you type on its booking page, and only if you book a demo. | US | Privacy policy |
| Google Identity | Your sign-in identity, and only if you choose to sign in with Google. | US | Privacy policy |
| Brevo (SMTP) | In production only: the recipient and the body of transactional email — studio invitations, address verification, password recovery, the acknowledgement and invitation for an early-access request, and the email carrying a template’s download link. | FR — EU | Privacy policy |
| Commercial campaign sending tool | Only for those who confirmed the news and have not unsubscribed: your email, your language, when you confirmed and with which version of the wording, which templates you asked for and your unsubscribe link. It receives only the list we export from this service, and before every send we replace it whole with a fresh export, so anyone who unsubscribes or is deleted does not receive the next send. | Not yet established | — |
| Hetzner Object Storage | In production only: every file uploaded or generated — audio, photographs, plans, documents and the issued PDFs. | DE — EU | Privacy policy |
| IONOS (the server) | Everything. The database, every application process and the ingress access logs run on one single-node k3s server. | ES — EU | Privacy policy |
| Catastro (Spanish Cadastre) | Addresses a studio types when looking up a cadastral reference. | ES — EU | Electronic office |
| NORA (Basque Government) | The street text a studio types when it looks up an address in Álava, Bizkaia or Gipuzkoa. No personal data. | ES — EU | geoEuskadi |
| Meta Platforms Ireland (WhatsApp) | Only if you link your phone: your WhatsApp number, what you send ArquiFlow over WhatsApp — voice notes, photographs and your replies — and the messages ArquiFlow answers with, which can carry the names of your projects and clients and the link to the acta. | IE — EU / US | WhatsApp Business data processing terms |
| Meta Platforms Ireland (Meta pixel) | Only if you accept advertising cookies: the public pages you visit, your IP address and browser, the identifier in the `_fbp` and `_fbc` cookies, and a notice when you submit an early-access request or ask for a template. | IE — EU / US | Meta Business Tools Terms |
The server host is the row a list like this most often leaves out and least can afford to: it is the infrastructure the whole product runs on, so every category above passes through it.
When an early-access request arrives, the notice we receive only says there is a request to review and, if you gave them to us, your name and your company. It travels through the same mail provider, Brevo.
Transfers outside the European Economic Area
Some of the recipients above are outside the EEA. This is what each transfer 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.
- The United States — Meta Platforms, Inc., for the Meta pixel. Meta Platforms Ireland Ltd also processes the data the pixel collects 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 into the Meta Business Tools Terms; where the provider is certified under the EU–US Data Privacy Framework, that certification applies instead.
Ask us at hola@arquiflow.es for the safeguard relied on for any single provider, and we will send you what we hold.
What the AI does, and what it does not decide
The transcription, the photograph descriptions, the reading of handwritten notes and the first draft of an acta are produced by the providers listed above. What comes back is a draft. A person at the studio reads it, edits it and issues it, and the professional who signs the acta remains responsible for what it says.
Nothing in this service takes a decision about you by automated means that produces legal effects concerning you or similarly significantly affects you, within the meaning of Article 22 GDPR.
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. That record exists so the service can be run and debugged, and it rests on our legitimate interest under Art. 6(1)(f).
What we do not claim: the material sent to those providers goes as the studio uploaded it. We do not strip personal data out of a recording, a photograph or a document before it is sent. If a recording should not leave the EEA, it should not be uploaded.
How long we keep it
We keep what a studio uploads, and what the service produces from it, for as long as the studio stays open.
The studio's owner can delete it from Settings. For the next 14 days the studio keeps working and the deletion can be cancelled; after that, it is erased. Every member gets an email when it is scheduled, another a few days before it is due, and another once it is done.
| What | What happens when the studio is erased |
|---|---|
| The studio's content | Deleted: customers and their contacts, each project's agents, projects and plans, actas with their recordings, transcripts, photographs and signatures, estimates, suppliers and quotes, site reports, incidents, documents, the regulations the studio uploaded with its questions, the subscription, and every file the studio holds, its logo included. |
| Members' accounts | Anonymised: the name, password, Google identity, professional registration, stored signature and linked WhatsApp number are deleted, and the email is replaced by a placeholder address, so the real address is free for a new account. |
| The studio's record | Left with the name «Estudio eliminado» and no legal name, tax id, address, phone, email or logo. |
| What is kept | The technical records of AI use — identifiers, counts and hashes, never the content — which, with the studio and the accounts anonymised, no longer point at anyone; the record that an early-access invitation was used; and, for 90 days, an internal list of the studio's and its members' identifiers that lets us repeat the erasure if a backup ever has to be restored. |
What that erasure does not reach: database backups hold a copy for up to 31 days, until they expire; the copies of the emails we sent stay with our outgoing mail provider; the application's technical logs expire on their own; and mail already delivered sits in its recipient's mailbox. Paddle keeps its own billing records as merchant of record.
An early-access request is deleted 12 months after its last submission or the invitation we sent you, whichever is later. Any unused invitation to your email is deleted with it. If you ask us to delete it sooner, we delete it then.
Someone who asks for a downloadable template is deleted, with their requests, 7 days after their last request if they never downloaded the file or confirmed anything from the email; the download link also expires after 7 days. If they downloaded it but never ticked the news box, they are deleted 30 days after their last request, because nothing is left to keep them for. In any other case — if they asked for the news, confirmed it or unsubscribed — 12 months after their last activity: a request, a download or a confirmation. So a contact that goes 12 months without any of them leaves the list. If you ask us to delete it sooner, we delete it then.
Your WhatsApp number is kept while it is linked, and deleted when you unlink it from your profile, when the studio removes you or when the studio is deleted. What you prepare for an acta over WhatsApp is deleted with the studio’s content, and the identifiers of the messages we receive over WhatsApp are deleted after 30 days.
Members the studio removed before the deletion are not part of it, and neither are the accounts of trades that filled in site reports for the studio: they are independent accounts, and only their link to the studio is deleted. Any of them can ask us in writing to erase their account.
Your rights, and how to use them
You have the right of access, rectification, erasure, restriction of processing, objection and portability, and the right to withdraw consent at any time — withdrawing it does not affect what was done while it was given.
Erasing a whole studio has a button: its owner deletes it from Settings, as described above.
Everything else is handled by hand: access, portability, the return of a copy of the material, and the erasure of a single account. Write to hola@arquiflow.es from the address on your account, say which right you are exercising, and we answer within one month of receiving the request, as Article 12(3) GDPR requires. We extend that by up to two further months only where the request is genuinely complex, and we tell you inside the first month if we do.
There is no button for access or portability. The service has no self-service way to download your data, and we would rather say so than imply one exists: a written request to the address above is the route, and it is a real one that a person answers.
If you are unhappy with how we handle it, you can complain to the Spanish supervisory authority, the Agencia Española de Protección de Datos (AEPD), at www.aepd.es, or to the authority of the country you live in.
What happens if a studio removes you from its team
A studio administrator can remove a member. 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 is written down here because it means an action by a studio administrator ends an account for which ArquiFlow is the controller. If it happens to you and you did not expect it, write to hola@arquiflow.es.
Changes to this policy
The date at the top of this page is the day it last changed. When something material changes — a new recipient, a new purpose, a different legal basis — we update this page, and where the change requires it we tell account holders by email before it takes effect.
Anything on this page, including a question you would rather ask before signing up, goes to hola@arquiflow.es.