Privacy policy
Last updated October 20, 2026
This policy explains what personal data FlowSight processes, including data from Google Analytics, why, and what you can do about it. FlowSight is run by Woodmont Digital.
Who we are
Woodmont Digital runs FlowSight and is responsible for the data described here. Questions or requests: contact@woodmontdigital.nl.
What we process
Your account: your e-mail address, your name, your language, and when you last used FlowSight. You sign in with a link sent to your e-mail address; there are no passwords.
Your projects: their names and websites, who is a member with which role, invitations, and the journeys you build — page titles, page paths, screenshots of pages you add, and how they connect.
The browser extension, if you use it: the screenshots you choose to add to a journey, with the page’s address and title, and a token that connects that browser to your account (FlowSight keeps only a scrambled form of it). The extension only takes a screenshot when you click its button, and sends nothing else; you can disconnect it on your account page.
Data from Google Analytics
When a project’s admin connects Google Analytics, FlowSight asks Google for read-only access to Google Analytics (the scope analytics.readonly), plus the e-mail address of the Google account that connects, to show which account is connected.
With that access FlowSight reads the list of Google Analytics properties the account can see, so the admin can choose one, and, from the chosen property, aggregate reports for the pages in the project’s journeys: numbers of users, sessions and page views per page path, page titles, how many users went from one page to the next, and which pages were viewed next. These are counts for groups of visitors; FlowSight doesn’t receive data about individual visitors.
FlowSight stores the connected Google account’s e-mail address, the chosen property, and the access tokens Google provides, encrypted. Report results are stored for at most {days} days after FlowSight last asked for them.
How we use it
Only to show the numbers on the journeys of the project they belong to, to that project’s members, and to keep those numbers up to date.
We don’t use Google user data for advertising, we don’t sell it, we don’t share it with third parties, we don’t transfer it to other apps, and we don’t use it to train AI or machine learning models. People don’t read it, except with your permission, to keep the service secure, or when the law requires it.
FlowSight’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Who can see what
A project’s journeys and numbers are visible to its members only: admins, editors and viewers. Only admins see and change the analytics connection.
The person who runs FlowSight has an overview with names, e-mail addresses and counts (projects, journeys, whether analytics is connected), to keep the service running. It doesn’t show journeys or Analytics numbers.
How we protect your data
We protect Google user data and the rest of your data with technical and organisational security measures, including encryption. Specifically:
Encryption in transit: all connections to FlowSight use HTTPS (TLS), and browsers are told to only use HTTPS (HSTS). FlowSight talks to Google’s APIs over TLS as well.
Encryption at rest: the access tokens Google provides are encrypted with AES-256 before they are stored. The encryption key is kept on the server, separate from the database and outside the source code. Tokens never leave the server: they are not sent to your browser and not written to logs.
Least privilege: FlowSight asks Google only for read-only access to Analytics, and only reads aggregate reports, never data about individual visitors. When an admin disconnects or the project is deleted, FlowSight deletes the tokens and asks Google to revoke the access right away.
Access control: every request is checked against the project’s members and their roles, so only a project’s members see its journeys and numbers, and only its admins manage the analytics connection.
Secure sign-in: there are no passwords that could leak. A sign-in link works once, expires after 15 minutes and is stored only as a hash, and sign-in attempts are rate-limited. Session cookies are only sent over HTTPS and can’t be read by scripts.
Infrastructure: FlowSight runs in isolated containers with minimal permissions and read-only file systems. The database can’t be reached from the internet; a firewall only lets web traffic and key-based administrator access through. Security updates for the server are installed automatically.
Incidents: if a data breach affects your data, we report it to the Dutch Data Protection Authority within 72 hours and inform the people affected when the GDPR requires it.
Where the data is
On a server of Hetzner in the European Union, with nightly backups in which the Google tokens stay encrypted. A copy of those backups is kept at Backblaze, in the European Union. E-mails (sign-in links and invitations) are sent through Brevo, in France. Google Analytics data comes from Google.
How long we keep it
Your account and projects stay until you delete them. Deleting your account (in Your account) also deletes the projects only you are in.
An analytics connection stays until an admin disconnects it or the project is deleted; FlowSight then deletes the tokens and asks Google to revoke the access. Stored report results disappear at most {days} days after FlowSight last asked for them. A screenshot no page uses any more is deleted after a week. Backups are kept for up to four weeks.
Your rights
Under the GDPR you can ask to see, correct, export or delete your data, and object to how we use it, at contact@woodmontdigital.nl. You can delete your account yourself in FlowSight.
You can also take away FlowSight’s access to Google Analytics at any time: disconnect it in the project’s settings, or remove FlowSight at myaccount.google.com/permissions. You can complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
Cookies
FlowSight only uses the cookies it needs to work: to keep you signed in and to protect forms. There is no tracking and no analytics on FlowSight itself.
Changes
When this policy changes, the date at the top changes too. For important changes we let users know by e-mail.
Privacy policy · Terms of service · Support · Woodmont Digital · contact@woodmontdigital.nl