Cookie policy
Last updated: 6 November 2026.
This statement covers the website www.repmanager.ai. The app (app.repmanager.ai) has its own cookie notice. The controller is Dibbes Group B.V. (Repmanager), Dynamostraat 44, 1014 BK Amsterdam, Chamber of Commerce 80407374.
1. What are cookies?
Cookies are small text files a website places on your device. Some tools use your browser's storage instead (localStorage or sessionStorage). For the rules that makes no difference, so in this statement we call all of it cookies.
2. What we ask you
On your first visit we ask whether you accept or decline cookies. Declining is just as easy as accepting. Until you make a choice, we only place the strictly necessary cookies from the next section. We store your choice for 12 months, after which we ask again.
You can change your choice at any time via Cookie settings. You can find this cookie policy at the bottom of every page.
3. Strictly necessary cookies (always on)
These cookies keep the site secure and remember your cookie choice. They do not require consent.
- rm_consent (Repmanager): remembers whether you accepted or declined cookies. Retention: 12 months.
- __cf_bm (Cloudflare): security and bot protection. Retention: 30 minutes.
- No cookie (Cloudflare Web Analytics): anonymously counting visitors and how fast pages load. It stores nothing on your device and does not follow you across other sites. Retention: not applicable.
4. Analytics cookies (only with consent)
These show us how visitors use the site, so we can improve it.
- _ga, _ga_* (Google Analytics): measuring how the site is used. Retention: 2 years.
- _clck, _clsk, CLID (Microsoft Clarity): heatmaps and session recordings to improve the site. Retention: _clck and CLID 1 year, _clsk 1 day.
- No cookie (Promptwatch): measuring whether visitors arrive via AI assistants such as ChatGPT. It sends the page visited, the page you came from and your browser language. Retention: not applicable.
5. Marketing cookies (only with consent)
These measure which ads and campaigns work, show relevant ads and tell us which companies visit our site.
- _gcl_au, _gcl_aw (Google Ads): measuring which ads lead to sign-ups and showing relevant ads. Retention: 90 days.
- _fbp (Meta (Facebook, Instagram)): measuring and advertising on Facebook and Instagram. Retention: 90 days.
- li_fat_id, bcookie, lidc (LinkedIn): measuring and advertising on LinkedIn. Retention: li_fat_id 30 days, bcookie 1 year, lidc 1 day.
- _li_id, _li_ses (Leadinfo): recognising which companies visit the site, and screen recordings of those visits. Retention: _li_id 2 years, _li_ses until the end of your visit.
- sib_cuid (Brevo): email marketing and measuring what you do on the site after opening one of our emails. Retention: about 6 months.
A few of these tools need extra explanation:
- Leadinfo recognises companies by the IP address of their network. It is meant to recognise companies, not people. Leadinfo also makes screen recordings of visits: how you scroll and click through the pages. We watch them to see what a company is interested in.
- Meta can use details you enter in a form on this site, such as your email address, name or phone number, in encrypted (hashed) form to link your visit to a Facebook or Instagram account. This is called automatic advanced matching and only happens if you accept cookies.
- Brevo can link your visit to your contact details, for example when you arrive on the site from one of our emails.
Legal basis: strictly necessary cookies do not require consent. For analytics and marketing cookies we ask for it. Google, Microsoft, Meta and LinkedIn may process data in the United States. How we handle that is explained in our privacy statement.
6. If you decline
- We place no analytics or marketing cookies, and the tools in sections 4 and 5 do not load.
- Google tags then only send a cookieless signal without identifiers (Google Consent Mode). Google uses it to estimate the number of conversions statistically. Google does process your IP address, as with any request on the internet.
- If you click a Google ad, we pass the ad ID (gclid) to our app via the link. That way we can see that a sign-up came from that ad. We place no cookie for this.
7. Changing or withdrawing your choice
Click Cookie settings to change your choice. Withdrawing is as easy as giving consent and applies from that moment. Cookies already on your device can also be deleted in your browser.
8. Changes
If we add a tool or something changes in an existing one, we update this statement. The date of the last change is shown at the top.
9. Contact
Questions about cookies or privacy? Email [email protected]. How we handle personal data otherwise is described in our privacy statement.