Privacy policy

What is in use on this site

This section describes what is in place as of the last update date above, rather than the “we may use analytics” wording that makes it impossible for a visitor to know what is actually happening.

One page carries tracking, and only one. The Wispr Flow page carries nine outbound links, all pointing at the same destination, and it uses a click-tracking service called BeMob to count visits to that page and clicks on those links, so that activity originating on this page can be attributed to it. It loads as soon as that page opens. You are not asked first, there is no banner, and there is nothing on this site to switch it off with. It is described in full under click tracking below, including what it receives and what it stores, so that you can decide what to do with your own browser settings.

Everywhere else on this site: we do not use web analytics of any provider, including cookieless or so-called privacy-friendly analytics. We do not know how many people visit the rest of the site, which pages they read, or where they came from. We do not use advertising or conversion pixels — there is no Meta Pixel, no Google Ads tag, and no equivalent from any other advertising platform anywhere on this site, including the Wispr Flow page. Every page other than that one loads no third-party scripts, embeds or fonts at all: every byte comes from this site, the web font included. There are no accounts, no forms, no comment system and no newsletter.

Who is responsible

Workflow Vitals is operated from the Netherlands. The operator is the controller for any personal data processed through this website within the meaning of the General Data Protection Regulation (GDPR).

The controller’s legal identity and a contact address for data protection requests are published in this section before any commercial activity begins on the site. The processing described below is limited to what a hosting provider necessarily records in order to serve a page.

What data is processed

This site is a set of static pages. It has no accounts, no forms, no comments, and no login, so there is nothing to sign up for and nothing to fill in. With the single exception of the click tracking on the Wispr Flow page, which is described in its own section below and runs whenever that page is opened, nothing you do on this site is recorded.

As with any website, the hosting infrastructure that delivers these pages processes technical request data in order to serve them and to keep the service secure. That typically includes:

• your IP address;
• the date and time of the request;
• the page or file requested;
• the HTTP status returned and the amount of data transferred;
• your browser user-agent string and, where sent, the referring page.

This data is handled by the hosting provider as part of delivering and protecting the site. It is not used to build a profile of you, it is not combined with data from other sources, and it is not sold or shared for marketing purposes.

Click tracking on the Wispr Flow page

The Wispr Flow page carries outbound links to Wispr Flow’s own site, all pointing at the same destination. Visits to the page and clicks on those links are tracked so that they can be attributed to this page rather than arriving unaccounted for. This section covers what that involves for your data, in full.

What loads, and when

The service is BeMob, a click-tracking and attribution provider. It is reached at track.workflowvitals.com, an address that belongs to this site and points at BeMob’s servers. Two separate things use it:

• A page-visit request, on load. The Wispr Flow page carries a small script in its head that runs as the page opens and fetches a tracking script from that address, which records that the page was opened. This happens on every visit to that page, before you click anything and without anything being asked of you. It hands BeMob the information listed below and sets four cookies, including a one-year identifier for your browser. Opening the page is enough on its own; you do not have to click anything.
• The links themselves. The buttons on that page point at the tracker, which counts the click and forwards you to ref.wisprflow.ai and on to Wispr Flow. That redirect is what sets the cookies in the table below. The destination and the price you pay are the same as they would be if you went to the vendor directly.

Neither is limited to a first visit and neither waits for anything. If you would rather they did not happen, the practical options are browser-side and are set out under what you can do about it.

What BeMob receives

When the tracker is contacted, it necessarily receives the request data any web server receives, and it derives further information from it. Observed in the tracker’s own response: your IP address, an approximate location derived from it (country, region and city), your internet provider, your device type, operating system, browser and version, your browser language, and the address of the page you came from. It also assigns identifiers to the visit and the click.

This is used to attribute a signup to this site and to tell campaigns apart. It is not used to build an advertising profile of you here, it is not combined with data from other sources by us, and we do not receive your name, your email address or your payment details from it. What BeMob itself does with the data as a company is governed by its own terms, which is a limitation of this description rather than a reassurance.

Cookies and local storage

Outside the Wispr Flow page, this site sets no cookies of its own and writes nothing to local or session storage. This site stores no preference of any kind in your browser at all: there is no settings panel here, so there is nothing for it to remember. On the Wispr Flow page, cookies are set twice over — once when the page opens, and again if you follow the link.

Opening the Wispr Flow page

The page-visit request described above sets the following cookies on track.workflowvitals.com, before you click anything. Because that address is a subdomain of this site rather than a separate company’s domain, they are first-party cookies, which means browsers that block third-party cookies will generally keep them. Read from the tracker’s actual responses on 28 August 2026.

What the request itself tells BeMob, over and above these cookies, is under what BeMob receives.

Following an outbound link

Clicking any of them adds a second set, on the same address and on the same first-party basis. These are the ones attribution actually depends on, and they are what the click is for.

Every cookie in both tables is set by the server and marked HttpOnly, Secure and SameSite=None, which means no script on this site can read them — or delete them. None of them carries your name, email address or payment information. What you can do about them is below.

What you can do about it

There is no tracking-preferences control on this site and no setting here that turns the tracking off. We would rather say that plainly than describe a switch that does not exist. What is available to you is what your own browser provides, and all of it works:

• Do not open the Wispr Flow page. It is the only page that contacts the tracker. Nothing else on this site does, so reading anything else here involves no tracking at all.
• Go to the vendor directly. Wispr Flow is reachable at wisprflow.ai without going through our link. You get the same product at the same price; we simply are not credited.
• Block or clear the cookies. The cookies above are set on track.workflowvitals.com. Clearing cookies and site data for workflowvitals.com in your browser settings removes them, and blocking cookies for this site prevents them.
• Use your browser’s tracking protection, or an extension. Content blockers and the built-in protections in Firefox, Safari and others can stop the tracking request outright. The page is written to remain fully readable when they do; nothing on it depends on the tracker loading.

To be exact about a limit rather than leave it implied: because the cookies are set by BeMob’s server on track.workflowvitals.com and are marked HttpOnly, no script on this site can read or delete them, and we will not claim to be able to remove them on your behalf. Your browser can; we cannot.

Legal basis

The technical request data that the hosting provider records in order to serve and protect these pages is processed on the basis of legitimate interests (GDPR Article 6(1)(f)): the interest in delivering the website reliably and protecting it from abuse.

For the click tracking, the legal basis has not yet been settled, and this page does not assert one. The tracking currently runs for every visitor to the Wispr Flow page without being asked for, so consent is not the basis — there is no consent to rely on. Whether it can properly rest on legitimate interests, and whether the cookies the click redirect sets require prior consent under the ePrivacy rules implemented in the Dutch Telecommunications Act, are open questions that have not been reviewed by a qualified person. They are being resolved before the site begins commercial activity. Stating that openly is more useful to you than naming a basis we cannot yet support, and nothing on this page should be read as a claim that the current arrangement is compliant.

Service providers

Cloudflare hosts and delivers this site through Cloudflare Pages, and provides the security layer in front of it. It acts as a service provider (processor) for that purpose and processes request data in that role. This is unchanged and applies to every page.

BeMob provides the click tracking described above. It acts as a service provider for that purpose and receives the data listed under click tracking — from visitors to the Wispr Flow page, and from that page only. No other third-party service is embedded in or loaded by any page on this site.

The contractual data-processing arrangements with these providers, the countries in which they process data, and any safeguards applied to transfers outside the European Economic Area, have not yet been confirmed and are therefore not stated here. They will be set out in this section before the site begins commercial activity rather than described speculatively.

Retention

Technical request data is retained by the hosting provider for a limited period for operational and security purposes and is then deleted or aggregated. This site keeps no separate copy and maintains no visitor database of its own.

The tracking cookies expire on their own after the periods in the tables above — one day, thirty days and one year, counted from the visit or the click that set them. How long BeMob retains the click and visit records on its own systems is set by BeMob and is not something this site controls or has verified, so no figure is given for it here.

Your rights

Where personal data relating to you is processed, the GDPR gives you the right to request access to it, to have inaccurate data corrected, to request erasure or restriction of processing, to object to processing based on legitimate interests, and to data portability where applicable.

Where processing is based on legitimate interests, you have the right to object to it. Because the legal basis for the click tracking is still being settled — see legal basis — the honest position today is that the effective controls available to you are the browser-side ones described under what you can do about it, and an objection sent to the contact address for this site once it is published.

This site holds no visitor database of its own, so there is generally nothing here to retrieve or delete on request. A request concerning the click-tracking records held by BeMob, or the request logs held by the hosting provider, can be made to the contact address for this site once it is published, and will be passed to the provider concerned. Contact details are listed on the about page.

You also have the right to lodge a complaint with a supervisory authority. In the Netherlands this is the Autoriteit Persoonsgegevens (Dutch Data Protection Authority).

Changes to this policy

This policy will change as the site develops, in particular if analytics or an advertising pixel is added, if click tracking reaches a page other than the Wispr Flow page, if a second provider joins BeMob, or if a consent mechanism is introduced. Any of those is a change to this page in the same revision, not afterwards. The “last updated” date at the top of this page reflects the most recent revision. Material changes will be described rather than made silently.

Scope and limitations

This policy covers workflowvitals.com only. It does not cover any external site you reach from a link here; those sites have their own policies and their own practices.

This document is a plain-language description of how the site currently works. It is provided for transparency and is not legal advice, and no guarantee is made that it satisfies every legal requirement that may apply to you or to this site. It is a working document that will be reviewed as the site takes on commercial activity.