Cookie Policy
Last updated: 4 August 2026.
This page lists the cookies and similar technologies in use on getreditus.com, and the cookies the Reditus tracking script can set on our customers' websites. It accompanies our Privacy Notice, which explains the processing behind these cookies and the legal basis for each.
An honest note first: getreditus.com does not show a cookie consent banner today. We say the same thing in our privacy notice, and a consent mechanism for the analytics and marketing cookies below is being rolled out. Until it ships, you can control cookies through your browser settings, and you can object to analytics and company-lookup processing by emailing privacy@getreditus.com.
Cookies on getreditus.com
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
_gr_id |
Reditus (our own affiliate program) | Records that a visit came through an affiliate link, so the referring partner can be credited. Set only when you arrive via an affiliate link. Does not build a visitor profile | 60 days | Affiliate attribution |
_gr_cookietest |
Reditus | Checks whether the browser accepts cookies, then is discarded | Transient | Functional |
ph_*_posthog |
PostHog, Inc. (EU cloud, data in Frankfurt) | Product and website analytics: which pages are visited and how the site is used. Session recording is disabled on this website | Up to 12 months | Analytics |
_lfa |
Dealfront (Leadfeeder) | Identifies the company (not the person) a visit likely comes from, based on IP address, for our B2B sales follow-up | 24 months | Marketing |
featurebase-anon-id |
CORDNET OU (Featurebase, Estonia) | Keeps the support chat and feedback widget working across pages | Persistent, set by the widget | Functional |
__session |
SaaSflow OU (Guideflow, Estonia) | Powers the interactive product demos on demo booking pages | Approximately 2 years | Functional |
We also store a small number of values in your browser's local storage that are not cookies, such as your display currency preference.
Cookies the Reditus tracking script sets on our customers' websites
When a business installs Reditus on its own website, our script can set the following first-party cookies there. The business, as the operator of its own website, decides whether these require consent in its jurisdiction and describes them in its own cookie notice. Details are published in Annex A1 of our Data Processing Agreement.
| Name | Purpose | Duration |
|---|---|---|
_gr_id |
Affiliate referral attribution: a random identifier recording that the visit came via an affiliate link | 60 days by default, configurable from 1 to 120 days |
_gr_cookietest |
Cookie support check | Transient |
_gr_referral_widget |
Powers the in-app referral widget, where the business has enabled it | 30 days |
The _gr_id cookie records one thing: that a signup came via an affiliate, so the referral can be attributed. It does not build a visitor profile and our script does not fingerprint devices. Under Dutch law (Telecommunicatiewet article 11.7a), an affiliate cookie used this way is generally exempt from the consent requirement; rules differ by country, and our customers should confirm the position for their own jurisdiction.
Managing cookies
You can delete or block cookies in your browser settings at any time; the site keeps working, though some conveniences (like the support chat remembering your conversation) will not. For anything else, write to privacy@getreditus.com. We acknowledge within 5 working days.