Cookie Policy
Last updated November 21, 2026
What this page lists
Every cookie ArquiFlow can set is named below, with what it is for, which category it belongs to, how long it lasts and who sets it. What it keeps in the browser’s own storage, beside cookies, is named further down. Nothing that is not on one of these lists is stored on your device by this site.
Only the analytics category is a choice. The essential cookies are what make signing in, remembering your language and remembering which welcome and help cards you have already seen or closed work at all, so they are not offered as an option — they are disclosed here instead. You can change the analytics choice at any time from the cookie settings at the foot of this page.
Essential cookies
| Cookie | Purpose | Lifetime | Party |
|---|---|---|---|
| at | Your access token — what keeps you signed in. Not readable by scripts. | Session | First-party |
| rt | Your refresh token — what renews the access token without asking you to sign in again. Not readable by scripts. | Session | First-party |
| NEXT_LOCALE | The language you chose, so the site keeps speaking it. | 1 year | First-party |
| cookie_consent | This decision itself: which categories you allowed, and when. Without it you would be asked on every page. | 180 days | First-party |
| onboarding | Which welcome and help cards you have already seen or closed, so they are not shown to you again. | 1 year | First-party |
| g_state | Guards the Google sign-in round trip against a forged callback. Set only if you use Google sign-in. | 15 minutes | First-party |
| g_nonce | Binds Google’s reply to the request that started it. Set only if you use Google sign-in. | 15 minutes | First-party |
| g_next | Where to send you after Google sign-in finishes. Set only if you use Google sign-in. | 15 minutes | First-party |
| g_eacode | The early-access code you sign up with through Google. Set only if you sign up with Google from a link that carries a code. | 15 minutes | First-party |
The four `g_` cookies are scoped to the `/api/auth/google` path and are gone within fifteen minutes. They exist for the length of one sign-in and no longer.
Analytics cookies — the one thing you decide
| Cookie | Purpose | Lifetime | Party |
|---|---|---|---|
| _ga | Google Analytics 4: tells one returning browser from another so visit counts are not inflated. | 2 years | First-party |
| _ga_DK8S1Y2D6N | Google Analytics 4: the same, for this specific property. | 2 years | First-party |
| ph_phc_BNRnYNGGgLyywoNriQuM6r3PjSfeWJiK2Sn754nGUpp6_posthog | PostHog: an anonymous identifier for your browser and your session, so the pages and the recording of one visit belong together. It carries neither your name nor your email. | Up to 1 year | First-party |
The first two are set by the Google Analytics 4 tag, and the tag loads only when three things are true together: you have allowed analytics, you are on a public page rather than inside the studio, and the site is being served from its production domain.
The third is set by PostHog, which records the session and logs usage events. It loads when you have allowed analytics and the site is being served from its production domain, on the public pages and inside the studio too, except on the pages reached through a link that carries a code: resetting your password, a studio invitation, email verification, a trade’s parte and signing an estimate. What it records and what it masks is set out in the privacy policy. PostHog also keeps entries in the browser’s local storage (localStorage) and session storage (sessionStorage) whose names begin with `ph_` or `__ph_`, holding the same anonymous identifier and the state of the session.
If you refuse analytics, none of these three is set. That is stronger than a cookieless mode: no script loads, so no request reaches Google or PostHog and there is nothing to store. Inside the studio the Google tag never loads, and one already loaded on a public page is disabled, whatever you allowed, so the addresses of your projects and actas are not sent to Google. PostHog does load inside the studio if you allow it, with all visible text replaced by asterisks.
Advertising cookies: also yours to decide
| Cookie | Purpose | Lifetime | Party |
|---|---|---|---|
| _fbp | Meta pixel: tells a returning browser from a new one, to learn whether someone who requests access came from one of our Instagram or Facebook ads. | 90 days | First-party (set by Meta’s script) |
| _fbc | Meta pixel: stores the click id of a Meta ad (`fbclid`) when you arrive from one. | 90 days | First-party (set by Meta’s script) |
Both are set by the Meta pixel, which loads only when three conditions hold at once: you have allowed advertising, you are on a public page and not inside the studio, and the site is served from its production domain. It sends Meta the public pages you visit and a notice when you submit an early-access request or ask for a template, with nothing you wrote in it. It does not read forms or record clicks on its own. In the consent record this choice is the `marketing` field. What Meta uses that data for is explained in the privacy policy.
If you refuse advertising, the pixel is not loaded and no request reaches Meta. Inside the studio it is not loaded, and if it had already loaded on a public page it is put on hold. Analytics and advertising are separate choices: under “Manage” you can accept one and refuse the other.
Paddle, on the pricing page
The pricing page loads Paddle.js from Paddle, the merchant of record that sells the subscriptions, so that prices can be shown in your own currency and a checkout can be opened. Paddle determines your country from your IP address to do it, and may set its own cookies on that page under its own policy.
This script is treated as strictly necessary and is not gated behind consent: showing you a price is the thing you asked for by opening the page. It is disclosed here and in the privacy policy rather than hidden behind a toggle.
No cookie is shared across subdomains
None of the cookies above sets a `Domain` attribute. Every one is therefore host-only: it is sent back to the exact host that set it and to nothing else, and no subdomain of this site can read another’s.
What is kept in the browser’s storage
Besides cookies, the studio keeps eight things in your browser’s own storage. None is sent with every request the way a cookie is, none is for analytics or advertising, and each is essential to the feature it names. The entries PostHog keeps, only if you allow analytics, are described in the analytics section.
| Name | Where | Purpose | Lifetime | Party |
|---|---|---|---|---|
| arquiflow-recordings | IndexedDB | The recordings of an acta that have not been uploaded yet, kept so they survive a browser crash or a lost connection. They are sent nowhere until you upload them. Recordings made with no connection in the installed field app move into `arquiflow-capture`. | Each is deleted once uploaded or discarded. A recording older than 7 days is deleted the next time a capture page opens on that device. | First-party |
| acta:drafted:{reportId} | sessionStorage | Remembers that an acta finished being written up in that tab, so the page refreshes only once. | Until you close the tab. | First-party |
| estimate-wizard:{projectId} | sessionStorage | The steps of the estimate wizard you have not finished, so reloading the page does not lose them. | Until you finish the wizard or close the tab. | First-party |
| field-static-* and field-offline-* | Cache Storage | A copy of the field app, only in studios with the field app turned on, in any browser. It keeps the application’s files (code and styles) and the “Offline” page, never any data of yours or of your projects. | Renewed with every release, and deleted when the field app is turned off or when you clear the site’s data. | First-party |
| arquiflow-field | IndexedDB | What the installed field app keeps for working offline: your studio’s recent projects with their addresses, their details and the contact details of their customers, of the suppliers and of the people who usually attend their actas. Only in studios with the field app turned on, and only in the installed app, never in a browser tab. | Until you sign out or the session ends, or up to 30 days without updating. Also deleted when another user or another studio signs in. | First-party |
| arquiflow-plans | Cache Storage | The pages of those projects’ plans, so they can be read while working offline in the installed field app. | Until you sign out or the session ends, or up to 30 days without updating. Also deleted when another user or another studio signs in. | First-party |
| arquiflow-capture | IndexedDB | The actas captured with no connection in the installed field app, until they are uploaded: their photos, the recordings, the notebook pages, the notes and the marks on the plans. Only in studios with the field app turned on. | Deleted once the acta is uploaded, when it is discarded, or when its author signs out and confirms. If another user signs in on the same phone, it is kept and hidden. The subject of an uploaded acta stays until it is generated or removed from the list. | First-party |
| arquiflow.fieldApp.installPromptSnoozedAt | localStorage | Remembers that you put off the invitation to install the app when creating an acta on a phone, so it is not shown again on that device for a while. Only in studios with the field app turned on. | 14 days. Deleted when you clear the site’s data. | First-party |
Pending recordings stay on the device until they are uploaded, discarded, or found by a capture page to be more than 7 days old: if no capture page is opened again on that device, they stay there. Signing out does not delete them. Clearing this site’s data from your browser does.
What the field app keeps for working offline is deleted the next time you open it after 30 days without updating: if you never open it again on that device, it stays there. On an iPhone the installed app keeps its own storage, separate from Safari’s, so signing out in Safari does not delete it: sign out in the app itself.
Changing your mind, and clearing what is stored
The cookie settings control at the foot of every page in this section reopens the choice, and saving it takes effect immediately — refusing analytics after having allowed it stops the Google tag and the PostHog recording on the spot, deletes the two Google Analytics cookies, and PostHog deletes its cookie and the identifiers it stored. It leaves only a `__ph_opt_in_out_…` entry in local storage that remembers you refused.
Refusing advertising after allowing it stops the Meta pixel and deletes its two cookies, `_fbp` and `_fbc`.
Your browser can also clear or block cookies for this site. Blocking the essential ones will stop sign-in from working. Anything else about this page can go to hola@arquiflow.es.