Cookie Policy | Trakily

The short version

On trakily.com, essential cookies sign you in, keep things secure and remember your cookie choice. Our own analytics cookies and the affiliate referral cookie are set only if you accept them in the banner.
You can change your choice at any time with Cookie settings in the footer. We use no advertising or third-party tracking cookies.
The Trakily script sets two first-party cookies on our customers' websites: _trakily_vid (12 months) and _trakily_sid (30 minutes).
Those cookies hold random ids, belong to the website you are on, and are never shared across unrelated websites.
Website owners can switch to a cookieless script that sets no cookies at all and rotates its anonymous visitor id every day.
Each website owner decides whether to ask for consent before Trakily runs on their site.

This summary helps you find your way around. The full text below is what applies.

On this page

01What cookies and browser storage are
02Two places Trakily uses cookies
03Cookies on trakily.com
04Cookies set by the Trakily script
05The cookieless option
06Consent and who is responsible
07How to control cookies
08Third-party pages
09Changes and contact

01What cookies and browser storage are

A cookie is a small text file a website stores in your browser so it can recognise the browser on later requests. Websites can also keep data in the browser with localStorage (kept until cleared) and sessionStorage (cleared when the tab is closed). This policy covers all three, because the rules that apply to cookies usually apply to similar technologies too.

First-party cookies are set by the website you are visiting. Third-party cookies are set by another domain, often for advertising. Trakily uses only first-party cookies.

02Two places Trakily uses cookies

On trakily.com and the Trakily dashboard, where we are responsible. See Cookies on trakily.com.
On our customers' websites, where the Trakily script runs on behalf of the website owner, who is responsible for it. See Cookies set by the Trakily script.

03Cookies on trakily.com

The first time you visit trakily.com we ask whether you accept analytics cookies. Essential cookies are always on, because the site cannot work without them; analytics cookies wait for your choice. Rejecting is as easy as accepting, nothing is pre-selected, and your choice is remembered for 6 months before we ask again. On secure connections, the sign-in cookies carry the browser's __Secure- prefix.

Essential cookies (always on)

Name	Purpose	Duration	Type
`better-auth.session_token`	Keeps you signed in to the dashboard. Holds a random session token; the session record on our server notes the IP address and browser it was created from.	30 days, renewed while you use the dashboard; removed when you sign out	Strictly necessary, first-party, HTTP-only
`better-auth.state`	Protects the Google sign-in flow against request forgery while you are redirected to Google and back.	5 minutes	Strictly necessary, first-party, HTTP-only
`better-auth.two_factor`	Remembers that your password was accepted while you enter your two-factor code.	10 minutes	Strictly necessary, first-party, HTTP-only
`better-auth.trust_device`	Set only if you tick "Trust this device" when entering a two-factor code, so this browser is not asked for a code every time.	30 days	Strictly necessary, first-party, HTTP-only
`better-auth.better-auth-passkey`	Holds the one-time challenge while you add or sign in with a passkey.	5 minutes	Strictly necessary, first-party, HTTP-only
`trakily_consent`	Remembers whether you accepted or rejected analytics cookies, so we don't ask on every page.	6 months	Strictly necessary, first-party

Name: better-auth.session_token
Purpose: Keeps you signed in to the dashboard. Holds a random session token; the session record on our server notes the IP address and browser it was created from.
Duration: 30 days, renewed while you use the dashboard; removed when you sign out
Type: Strictly necessary, first-party, HTTP-only

Name: better-auth.state
Purpose: Protects the Google sign-in flow against request forgery while you are redirected to Google and back.
Duration: 5 minutes
Type: Strictly necessary, first-party, HTTP-only

Name: better-auth.two_factor
Purpose: Remembers that your password was accepted while you enter your two-factor code.
Duration: 10 minutes
Type: Strictly necessary, first-party, HTTP-only

Name: better-auth.trust_device
Purpose: Set only if you tick "Trust this device" when entering a two-factor code, so this browser is not asked for a code every time.
Duration: 30 days
Type: Strictly necessary, first-party, HTTP-only

Name: better-auth.better-auth-passkey
Purpose: Holds the one-time challenge while you add or sign in with a passkey.
Duration: 5 minutes
Type: Strictly necessary, first-party, HTTP-only

Name: trakily_consent
Purpose: Remembers whether you accepted or rejected analytics cookies, so we don't ask on every page.
Duration: 6 months
Type: Strictly necessary, first-party

Analytics and affiliate cookies (only if you accept)

We measure trakily.com with our own product. If you choose “Accept analytics”, the Trakily script loads and sets the same two first-party cookies it sets on our customers' websites, on trakily.com only. If you arrived through a Trakily affiliate's link, accepting also sets the affiliate referral cookie. If you reject, or have not chosen yet, the script is not loaded at all and none of these cookies are set.

Name	Purpose	Duration	Type
`_trakily_vid`	Recognises a returning browser so we can count unique visitors and see which pages and channels bring sign-ups. Stores a random visitor id, the date of the first visit and a visit counter.	12 months, renewed on each visit	Analytics, first-party
`_trakily_sid`	Groups page views into a single visit. Stores a random session id.	30 minutes, extended while you stay active	Analytics, first-party
`trakily_ref`	Set only if you accept and arrived through a Trakily affiliate's link, so the affiliate who referred you is credited if you sign up. Holds the affiliate's code, the time of the click and a signature, nothing about who you are.	60 days	Affiliate, first-party, HTTP-only

Name: _trakily_vid
Purpose: Recognises a returning browser so we can count unique visitors and see which pages and channels bring sign-ups. Stores a random visitor id, the date of the first visit and a visit counter.
Duration: 12 months, renewed on each visit
Type: Analytics, first-party

Name: _trakily_sid
Purpose: Groups page views into a single visit. Stores a random session id.
Duration: 30 minutes, extended while you stay active
Type: Analytics, first-party

Name: trakily_ref
Purpose: Set only if you accept and arrived through a Trakily affiliate's link, so the affiliate who referred you is credited if you sign up. Holds the affiliate's code, the time of the click and a signature, nothing about who you are.
Duration: 60 days
Type: Affiliate, first-party, HTTP-only

When you open an affiliate's link we count the visit for that affiliate whatever you choose, without a cookie and without storing your IP address or anything else that identifies you: only the affiliate, the page you landed on, the website you came from and the time. If you reject, the affiliate is not credited for a later sign-up.

Changing your choice

Use Cookie settings in the footer of any page, or the button below, to reopen the banner. If you withdraw consent, we delete the analytics cookies and the affiliate referral cookie and reload the page without the script.

Browser storage on trakily.com

These keys never leave your browser. They remember interface preferences and, briefly, an email change you started.

Key	Purpose	Kept	Storage
`trakily-theme`	Your light, dark or system theme choice	Until you clear it	localStorage
`trakily:sites-sort`	How you sort the list of websites	Until you clear it	localStorage
`trakily-pinned-ranges`	Date ranges you pinned in the date picker	Until you clear it	localStorage
`trakily_funnel:…`	Which funnel you last opened for a website	Until you clear it	localStorage
`trakily_exclude:…`	Remembers that you excluded your own visits to one of your websites, so settings can show it	Until you clear it	localStorage
`trakily:pending-email:…`	Remembers an email change you started (the new address), so the dashboard can show that it is waiting for confirmation	Until the change is confirmed, at most 1 hour	localStorage

Key: trakily-theme
Purpose: Your light, dark or system theme choice
Kept: Until you clear it
Storage: localStorage

Key: trakily:sites-sort
Purpose: How you sort the list of websites
Kept: Until you clear it
Storage: localStorage

Key: trakily-pinned-ranges
Purpose: Date ranges you pinned in the date picker
Kept: Until you clear it
Storage: localStorage

Key: trakily_funnel:…
Purpose: Which funnel you last opened for a website
Kept: Until you clear it
Storage: localStorage

Key: trakily_exclude:…
Purpose: Remembers that you excluded your own visits to one of your websites, so settings can show it
Kept: Until you clear it
Storage: localStorage

Key: trakily:pending-email:…
Purpose: Remembers an email change you started (the new address), so the dashboard can show that it is waiting for confirmation
Kept: Until the change is confirmed, at most 1 hour
Storage: localStorage

04Cookies set by the Trakily script

When a website uses the standard Trakily script, it sets two first-party cookies on that website's own domain (including its subdomains). They are set by JavaScript, use SameSite=Lax, and contain random identifiers created in your browser, not your name, email or IP address.

Name	Purpose	Duration	Type
`_trakily_vid`	Recognises a returning browser so the site owner can count unique visitors, returning visits and the journey that led to a purchase. Stores a random visitor id, the date of the first visit and a visit counter.	12 months, renewed on each visit	Analytics, first-party
`_trakily_sid`	Groups page views into a single visit. Stores a random session id.	30 minutes, extended while you stay active	Analytics, first-party

Name: _trakily_vid
Purpose: Recognises a returning browser so the site owner can count unique visitors, returning visits and the journey that led to a purchase. Stores a random visitor id, the date of the first visit and a visit counter.
Duration: 12 months, renewed on each visit
Type: Analytics, first-party

Name: _trakily_sid
Purpose: Groups page views into a single visit. Stores a random session id.
Duration: 30 minutes, extended while you stay active
Type: Analytics, first-party

Browser storage used by the script

Key	Purpose	Kept	Storage
`trakily_sid`	Cookieless script only: a random id for the current tab's visit and the time of the last activity.	Until the tab is closed, or after 30 minutes of inactivity	sessionStorage
`trakily_payment_…`	Remembers that a payment confirmation page was already reported, so a purchase is not counted twice on reload.	Until the tab is closed	sessionStorage
`trakily_ignore`	Set only when a website owner opens their own site with the ?trakily_ignore=1 link from the dashboard (removed again with =0), so their own visits are excluded. Read by the script on every page.	Until cleared	localStorage

Key: trakily_sid
Purpose: Cookieless script only: a random id for the current tab's visit and the time of the last activity.
Kept: Until the tab is closed, or after 30 minutes of inactivity
Storage: sessionStorage

Key: trakily_payment_…
Purpose: Remembers that a payment confirmation page was already reported, so a purchase is not counted twice on reload.
Kept: Until the tab is closed
Storage: sessionStorage

Key: trakily_ignore
Purpose: Set only when a website owner opens their own site with the ?trakily_ignore=1 link from the dashboard (removed again with =0), so their own visits are excluded. Read by the script on every page.
Kept: Until cleared
Storage: localStorage

Linking a visit across a company's own domains

When a website owner lists several of their own domains, the script adds the visit identifiers to links between them as URL parameters (_pl_vid, _pl_sid, _pl_vfs and _pl_vsn), so a visit continues on the second domain. These parameters are removed before the page address is stored. This never happens for links to unrelated websites, and never in cookieless mode.

What the script does not do

It does not set third-party cookies or follow you across unrelated websites.
It does not use browser fingerprinting to recognise you when cookies are blocked.
It does not load other trackers or advertising scripts.
It stops running when it detects automated browsers, and does not run inside iframes by default.

05The cookieless option

Website owners can choose a cookieless version of the script. It sets no cookies. In sessionStorage it keeps a per-tab session id and a marker for payments already reported, both gone when the tab closes. It writes nothing to localStorage, unless the website owner uses the exclude-my-visits link in their own browser.

To count unique visitors, our server creates an anonymous daily id from the IP address, the browser's user agent, the website and a random value (a “salt”) that changes every day. The result is a one-way hash: it cannot be turned back into the IP address. Salts are deleted two days after their day ends, so ids from earlier days can never be recomputed or connected. The IP address is not stored.

The trade-off is that the same person counts as a new visitor each day, and journeys or revenue attribution spanning several days are less complete.

Whether cookieless measurement needs consent depends on the law that applies to the website and how regulators interpret it. Website owners should make that assessment for their own site.

07How to control cookies

Your browser. All major browsers let you block or delete cookies and site data, for all websites or for specific ones. Blocking the Trakily cookies does not stop the website from working.
The website's consent tool. If the website you are visiting has a cookie banner, use it to change your choice at any time.
Content blockers. Many privacy extensions block analytics scripts entirely.
On trakily.com. Use Cookie settings in the footer to accept or reject analytics at any time. If you block the essential cookies, you will not be able to sign in.

Questions about a specific website's use of Trakily are best sent to that website's owner. You can also write to us at [email protected].

08Third-party pages

Some steps take you to pages run by others, which set their own cookies under their own policies: Google when you sign in with Google or connect Search Console or Analytics, Meta when you connect Meta Ads, and Dodo Payments when you check out or open the billing portal. Our dashboard also loads small website icons from DuckDuckGo's icon service and profile images from the platforms they belong to; these requests do not set cookies for us.

09Changes and contact

We will update this policy whenever we add, remove or change a cookie, and update the date at the top. For anything else, see our Privacy Policy or contact [email protected].