Cookies Policy
ProcessMind Cookies Policy
Effective date: October 28, 2026
Introduction
ProcessMind uses cookies and similar technologies across our websites and services to enhance your experience, understand service usage, and tailor advertisements.
Our use of these technologies helps us improve our websites and services, make them user-friendly, and deliver targeted advertisements across our websites, services and third-party platforms. You have control over your cookie settings and can customize your preferences at any time.
If you wish to modify your cookie settings on ProcessMind, you can do so by clicking on Cookie preferences
Cookie preferencesFrequently Asked Questions
What is a cookie?
Cookies are small text files stored by your browser that enable a website to recognize your browser. They may be session cookies (deleted when you close the browser) or persistent cookies (stored until they expire or you delete them), and may be set by us (first-party cookies) or by third parties.
What cookies do we use?
We use session cookies and persistent cookies. Depending on the purposes for which they are used cookies can be:
Essential – used to efficiently and quickly load the pages and offer features by distributing the workload across several computers, to authenticate you and to ensure your secure connection and prevent fraudulent use of your account or detect other malicious activity on the website.
Functionality cookies – these cookies are used in order to enhance your user experience and to remember your preferences such as your language preference and cookies which are necessary for the playback of media content or which can autofill a form for you.
Analytical/Performance - used by us to count the number of users on our website, to recognize you when you visit the website again and to help us improve your experience on our website depending on how it is used. These cookies also help us understand how our services are doing and improve them by developing new features.
Targeting and advertising – these cookies are used to record your behavior online and can be used to provide you with offers and services you might be interested in.
What are third party cookies?
Depending on the website or domain placing the cookie, a cookie is “first” or “third” party. A first party cookie is set by a website visited by you directly. Third party cookies are set by third parties domains or websites which can place cookies through the website you visit, hence their name “third party cookies”. These third parties are other entities than ProcessMind and they can be session or persistent cookies.
We use YouTube to display the videos we have on our website.
How can I stop cookies?
You may withdraw your consent for the use of cookies or change the cookie settings for this website at any time by clicking on the “Cookie preferences” button at the top of this page or by configuring your browser settings (please refer to your browser’s help function to learn more about cookie controls). If your browser sends a Global Privacy Control (GPC) opt-out signal, ProcessMind automatically disables analytics and marketing cookies and applies the signal to your saved preferences; the anonymous, cookie-less page measurement described under Analytics Cookies in the Cookie List below is not a sale or sharing and is not switched off by the signal.
This policy may change from time to time so if we make any material changes we will post a notice on our website. You can find out more information on cookies by accessing www.allaboutcookies.org or by contacting us at privacy@processmind.com or through our contact page.
Cookie List
A cookie is a small piece of data (text file) that a website—when visited by a user—asks your browser to store on your device in order to remember information about you, such as your language preference or login information. Those cookies are set by us and called first-party cookies. We also use third-party cookies—which are cookies from a domain different than the domain of the website you are visiting—for our advertising and marketing efforts. More specifically, we use cookies and other tracking technologies for the following purposes:
Strictly Necessary Cookies
These cookies are essential for the website to operate properly and are automatically enabled in our system. They are typically activated by your interactions, such as setting privacy options, logging in, or completing forms. While you can adjust your browser settings to block or notify you about these cookies, certain features of the site may not function correctly without them. Some of these cookies hold an identifier for your signed-in session; they are not used to track you across other websites.
| Cookie Name | Origin | Description | Content | Expiry |
|---|---|---|---|---|
| cookie_consent | ProcessMind | Stores your cookie consent preferences to remember your choices across visits. | JSON object containing consent status for each cookie category (necessary, analytics, marketing, preferences) | 1 year |
| auth-token | ProcessMind | Authenticates your session in the ProcessMind application. Set only after you sign in; HttpOnly and Secure. | Signed session token | 7 days (or until you sign out) |
| auth-state / auth-nonce | ProcessMind | Temporary values that protect the sign-in redirect when you sign in with a third-party provider. Set only while you are signing in; HttpOnly and Secure. | Random state and nonce values | 15 minutes |
| original-url / login-as-tenant-id / login-as-user-id | ProcessMind | Remembers where to return you after sign-in and, for authorized ProcessMind support staff only, enables temporary impersonation for troubleshooting. HttpOnly and Secure. | URL and internal identifiers | 15 minutes |
| userid / tenantid / organizationid | ProcessMind | Operational context used to attribute your activity to your account in ProcessMind logs when you use the application. HttpOnly and Secure. | Internal identifiers | 1 year |
| processmind_trial_variant | ProcessMind | Set when you open a page we are testing (for example the free-trial landing page) and stores which version of that page you were shown, so later visits keep showing the same version. It holds only the variant number, no identifier, is not used to track you across websites and is never shared. | Variant number (1-4) | 1 year |
| processmind_navbar_cta_variant | ProcessMind | Set when you open our website and stores which wording of the free-trial button in the page header you were shown (for example “Start now” or “Free trial”, in your language), so later visits keep showing the same wording. It holds only the variant number, no identifier, is not used to track you across websites and is never shared. | Variant number (1-4) | 1 year |
| processmind_cta_banner_small_variant | ProcessMind | Set when you open a page that shows our small free-trial banner and stores which design of that banner you were shown, so later visits keep showing the same design. It holds only the variant number, no identifier, is not used to track you across websites and is never shared. | Variant number (1-2) | 1 year |
Analytics Cookies
These cookies help us understand how visitors use our site by providing insights into which pages are visited most and how users navigate through the site. This information is collected in an aggregated form, helping us to enhance the site’s performance. If these cookies are declined, we won’t be able to track your visits or improve your browsing experience. These optional cookies can be managed through the cookie settings.
Next to these third-party services we measure our own site with a first-party system that runs on ProcessMind infrastructure. It is never shared with third parties, and it works in two modes:
- Always, without consent. Each page view, each click on a call to action and each form submission is recorded without anything that identifies you: the path of the page (query parameters removed), the equivalent English URL, the hour of the visit (minutes and seconds removed), how long the page was actively in view (rounded to 30 seconds, re-reported each time you switch away from or close the page), the site you arrived from (domain and path only, no search terms), the previous page when it is one of ours, which of the four main marketing pages (home, pricing, about us, partners) this browser tab had already opened earlier — page names only, kept in
sessionStoragefor the open tab and deleted by your browser when you close it, so it links nothing across tabs or visits — the campaign parameters we set ourselves, the page language and the language your browser asked for, the version of a page you were shown when we are testing one, whether you are viewing the light or dark theme, how far the page was scrolled, the country our CDN resolves, the label and destination of the element clicked, the placement of the clicked call to action, the browser family, the operating system family, the device class, the screen and viewport size, the device memory and CPU count in coarse buckets, the connection type and quality, and your timezone offset in whole hours. Each event also carries a random value generated for the open page, which groups the events of that one page load and is destroyed in your browser when you close the page — it is never saved in a cookie or browser storage, never reused and cannot link two page loads — together with the number of times you switched away from and back to that page during the load. These events carry no identifier of you and no cookie, and their time is rounded to the hour, so they cannot be linked to you. The stored copy carries one note added by our server — whether the browser was signed in to the ProcessMind application, a single yes or no, never an identifier — so returning users stay out of the signup-conversion figures. The same property means we cannot retrieve the rows that came from you: a request to access, correct or delete “your” website-measurement records cannot be actioned on individual rows. What does apply instead is set out in our Privacy Policy — “How we measure our own website” in section 5 and the rights section that follows it. - With analytics consent. The same events additionally carry the random identifier in the
website_useridcookie below and the exact time. That is what lets us count unique visitors, see which page a visit started and ended on, and follow a journey from a campaign landing to a signup. If you are signed in to the ProcessMind application and the telemetry setting of the organisation you belong to allows it, those events are also attached to your account, so we can see which pages preceded a signup. That is a separate choice from this banner and is described in our Privacy Policy.
If your browser sends a Global Privacy Control opt-out signal, none of the identifier-based part is recorded: the website_userid cookie is not set, the analytics and marketing categories stay disabled and your stored preferences are updated to match. The events that need no consent are unaffected — they carry no identifier of you, no cookie and an hour-rounded time, and reading them in aggregate is neither a sale nor cross-site tracking, so the page views, clicks and form submissions continue to be recorded anonymously.
| Cookie Name | Origin | Description | Content | Expiry |
|---|---|---|---|---|
| _ga | Google Analytics | Used to distinguish unique users by assigning a randomly generated number as a client identifier. Helps analyze how visitors interact with the site. | Client ID (e.g., GA1.1.xxxxxxxxxx.timestamp) | 2 years |
| _ga_TRT89GTFVH | Google Analytics | Used by Google Analytics 4 to persist session state and track user interactions across pages. | Session data including timestamps and engagement metrics | 2 years |
| _clck | Microsoft Clarity | Persists the Clarity User ID and preferences, unique to that site. Helps us understand user behavior through heatmaps and session recordings. | User ID and settings | 1 year |
| _clsk | Microsoft Clarity | Connects multiple page views by a user into a single Clarity session recording. Contains timestamps and page view counts. | Session ID and interaction data | 1 day |
| website_userid | ProcessMind | A randomly generated identifier that links the pages one visitor views into a single journey. Only set when analytics cookies are accepted, and the events sent without it carry no identifier of you (only the random value of the open page load, which is not kept in your browser and links nothing across page loads). Used to improve our understanding of how visitors use the site, and, for a signed-in visitor whose organisation allows telemetry, to attach the journey to their account. This data is stored exclusively on ProcessMind servers and is never shared with third parties. | UUID (e.g., a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d) | 1 year |
Marketing Cookies
These cookies are used to track visitors across websites and to display relevant advertisements. They help measure the effectiveness of advertising campaigns and limit the number of times you see an ad.
| Cookie Name | Origin | Description | Content | Expiry |
|---|---|---|---|---|
| _gcl_au | Google Ads | Used by Google Ads to measure advertising and conversion efficiency. Stores a unique identifier to track conversions. | Conversion tracking ID | 90 days |
| bcookie | Browser identifier cookie used to uniquely identify devices accessing LinkedIn. Used for tracking and advertising purposes. | Unique browser identifier | 1 year | |
| li_gc | Stores consent of guests regarding the use of cookies for non-essential purposes. | Consent timestamp and status | 6 months | |
| lidc | Used for routing and to optimize data center selection based on network performance. Also facilitates tracking. | Data center routing information | 1 day | |
| test_cookie | DoubleClick (Google) | Used to check if the user’s browser supports cookies. This is a temporary test cookie. | “CheckForPermission” | Session |
Functional Cookies
These cookies allow the website to offer improved functionality and personalized features. They might be set by us or by third-party providers that contribute services to our site. If you choose not to enable these cookies, some services may not operate as intended.
Currently, we do not use any functional cookies beyond those classified as strictly necessary.
Other Browser Storage
In addition to cookies, we use browser storage (localStorage and sessionStorage) for functional purposes — for example, remembering your cookie choices, theme and language preferences, and caching prices. If you accept analytics cookies, we also cache the country our CDN resolved and the random identifier described above. When error monitoring is active, Sentry may store session state in your browser so we can report and debug errors. Without analytics consent, the page measurement described under Analytics Cookies keeps no identifier of you in a cookie or in browser storage: only the in-memory value for the open page, discarded when the page closes, plus one small entry in sessionStorage that lists which of the four main marketing pages (home, pricing, about us, partners) the open tab has already visited. That entry holds page names only — never a path, a campaign value, a cookie or an identifier — is deleted by your browser when you close the tab, and is what lets a page view say that this tab had already seen the pricing page without linking anything across tabs or visits. This storage is not used for advertising, and tracking-related entries are removed when you reject the corresponding cookie categories.
Third-Party Cookies Notice
Some cookies listed above are set by third-party services (Google, Microsoft, LinkedIn) and are placed on their respective domains. These third-party cookies are governed by the privacy policies of those services:
- Google Analytics & Google Ads: Google Privacy Policy
- Microsoft Clarity: Microsoft Privacy Statement
- LinkedIn: LinkedIn Cookie Policy
- YouTube: when you choose to play an embedded video, YouTube may set cookies on youtube.com domains (Google Privacy Policy).
- Paddle: Paddle’s payment scripts load in the app when you open checkout. Paddle may set cookies on paddle.com domains to process and secure the payment (Paddle Privacy Policy).
- Paddle Retain (ProfitWell): the website does not load Paddle Retain on pricing pages. Paddle may load its retention service as part of in-app checkout, and it may set cookies on profitwell.com domains (Paddle Privacy Policy).
- Calendly: when you choose to open the scheduling calendar, the widget loads from calendly.com and Calendly may set cookies on its domains (Calendly Privacy Policy).
Additional third-party tags managed through Google Tag Manager load only after the matching consent category has been granted.
When you reject marketing or analytics cookies through our consent banner, we update Google Consent Mode to prevent these services from setting new cookies. However, existing third-party cookies on other domains can only be removed by clearing your browser cookies or through those services’ own opt-out mechanisms.
Log Files and Web Beacons
Web beacons (also called pixels or clear GIFs) are small image files placed on web pages or in messages to record that content was accessed — for example, that a page was viewed, a message was opened or a link was clicked. Where we use third-party web beacons, they load only after the matching consent category has been granted, as described above.
Our emails do contain a tracking pixel. The emails we send — service and notification mail (account, security, billing, usage, mention and digest), and our marketing mail — carry an invisible tracking pixel and rewritten links, so we can record whether a message was opened (the first open) and which link was first clicked. This measurement is not a cookie and the cookie consent categories do not govern it — the preferences banner cannot switch it off. Section 5 of our Privacy Policy describes what we record, why, and how to object. We also receive delivery, bounce and complaint events from our email provider; those are used to keep mail deliverable and to honour unsubscribes, and they are kept for the period described in section 7 of the Privacy Policy.
We also collect some information automatically and store it in log files. This is mostly anonymous usage data, such as browser type, internet service provider, clickstream data, operating system and timestamps. We use this information to operate and secure our websites and services, to understand how they are used and to improve them. How we handle personal data collected through these logs is described in our Privacy Policy.
Our own website measurement is part of those logs and runs as described under Analytics Cookies above: the page views, calls to action and form submissions we record without consent hold no identifier of you and are rounded to the hour, and only analytics consent adds the random identifier that turns them into a visitor journey. Server access logs kept for security and operations are separate, are kept for the retention period in section 7 of the Privacy Policy, and are not used for marketing.
Contact Us
If you have any questions about this policy or our use of cookies, contact us at privacy@processmind.com or by post at ProcessMind B.V., Willem Sandbergstraat 33, 7425RC Deventer, The Netherlands.