Cookie notice
Short version: this website sets no advertising or analytics cookies, and loads one thing from somebody else: a page counter that cannot identify you. Here is the detail.
Last updated 24 September 2026
This website
The pages you are reading are static files served from our own domain. There is no advertising, no tag manager and no embedded content from another company, and the typefaces are served from talkfront.app rather than a font CDN.
One request does leave for somebody else: a page counter, described below. It is the only one, it is hosted in the EU, and it is not told who you are, because it is never given anything that could say.
We do run our own chat widget here, because we use Talkfront ourselves. It is served fromwidget.talkfront.app, which is our infrastructure rather than someone else's, and it stores a visitor key described in the table below. The widget section explains what that key is for.
We count which pages people read, using Pirsch, a German company hosting in the EU. It sets no cookies and stores nothing in your browser. To tell one visitor from another for a day it hashes your IP address and browser together with a salt that it changes, on its servers, and keeps the hash rather than either ingredient. There is no identifier that follows you between sites and none that survives the salt changing.
What we get from it is totals: which pages, which countries, which sites linked to us. It is why there is no bar asking you to accept analytics, and why saying no to one would not change what this page does.
You will have seen a bar asking about this. It is still doing less than most: the page counter above needs no consent under PECR because it stores nothing in your browser and cannot identify you, so whichever button you pressed, the site behaves identically. What the bar does is record your answer, so that if we ever add something that does need consent, it starts switched off for everybody who already said no.
What is stored
| Name | Type | Purpose | Expires |
|---|---|---|---|
tf_consent | Local storage | Remembers whether you accepted or rejected non-essential storage, so you are not asked again. Holds one word. | Until you clear site data |
talkfront.visitor.… | Local storage | Recognises you as the same visitor across pages and return visits, so our own support team sees one person rather than a new stranger on every page. A random 32-character key holding nothing about you. | Until you clear site data |
tf_ref | Session storage | Remembers a referral tag from a ?ref= link so the referring customer can be credited if you sign up. Contains no personal data. | When you close the tab |
Our web server also keeps standard request logs for 30 days. Those are not cookies, but you should know they exist. The privacy notice covers them.
The Talkfront app
Signing in at app.talkfront.app is different. It needs cookies to work at all:
- A session cookie so you stay signed in as you move between pages.
- A CSRF token that protects your account from cross-site request forgery.
- A remember-me cookie, only if you ask to stay signed in.
These are strictly necessary. The app cannot function without them, so they do not require consent. None of them track you across other websites.
The chat widget on our customers' sites
If you met Talkfront as a chat window on someone else's website, this is the part that applies to you.
The widget stores a visitor token in its own frame's storage. It is what keeps your conversation attached to you as you move between pages and come back later. Without it, every page load would start a new chat with nobody knowing what you had already said.
- It is scoped to the site you are chatting on. It does not follow you to other websites.
- It is not used for advertising or profiling.
- The website owner can switch on a setting where nothing is stored at all until you actually start a chat.
- Clearing your browser storage removes it, and your next visit starts a fresh conversation.
The company whose site you were on decides how their chat is configured and is the controller of that conversation. Our privacy notice explains the split.
Controlling this
Every browser lets you view and delete cookies and site storage, and block them per site. The method differs by browser, and your browser's own help pages are the most reliable guide.
Blocking storage on our app will stop you signing in. Blocking it for a chat widget will make each page load start a new conversation. Nothing will break otherwise.
Changes
If we ever add analytics or anything that tracks you, this page changes on the same day, and it will honour the answer you already gave on the bar rather than assuming a yes. Email privacy@talkfront.app if anything here does not match what you observe. We would genuinely like to know.
Questions about this document? Email privacy@talkfront.app.