Cookies

Kemble loads no advertising trackers, and nothing that counts your visits runs until you say yes. The first time you open this website or the app, it asks, with Decline and Accept side by side; until you choose, nothing is counted and no analytics cookie is set. A third party you load through a feature — YouTube’s player, Google sign-in — may set its own, under its policy.

If you accept, Kemble counts page views and a few actions with Google Analytics, through Cloudflare’s tag manager (Zaraz): your browser tells Cloudflare, at kemble.io itself, and Cloudflare’s servers pass it on to Google. No Google script runs in your browser, and your browser never contacts Google for it. What is counted: the kind of page you opened, by its template — /app/work/channel, never which channel, workspace, community or person, and never a search or anything after a ? in an address; the page’s general title (Kemble Work, Kemble Circle, or the website page’s own); the website you came from, by its name only; and six actions — signing up or signing in (only how: an emailed code, Google, a passkey and so on), downloading Kemble Desktop (for which system), sending the contact form (its topic) and pressing a plan’s button (which plan). Never your name, email address, account, or anything you write. Cloudflare passes on your browser’s make and version, your screen size and language, but not your IP address, and Google’s advertising features are off.

Your answer is kept in your browser’s local storage, on that device, for a year, and then you are asked again; the website and the app share it, and Kemble Desktop keeps its own. With a yes, Cloudflare’s tag manager also sets two cookies on kemble.io, each kept up to a year: one holding your answer, and one it uses to tell your browser’s visits apart. Google Analytics is given a random identifier for your browser, never your name or account, so visits can be counted without knowing who you are. To change your mind, use Cookie settings at the foot of any page of this website, or in the app: Settings › Account in Kemble Work, Settings › Privacy & safety in Kemble Circle. Declining stops the counting straight away and removes what the page can reach of it.

The app keeps what it needs in your browser’s local storage: the sign-in token for each account you use there, with that account’s name, email and picture; unsent drafts and messages waiting to send; your recent searches, emoji and switcher history; and interface settings such as theme, sidebar and panel sizes, with which of Kemble Work and Kemble Circle the device last showed, so the sign-in page opens as that one. It stays on that device. Signing out ends every session that sign-in holds in that browser — the one in front and those made by moving between your workspaces — and removes the token, and with it that account’s unsent drafts, messages waiting to send, recent searches, switcher history and its own background pictures from that browser. The same is removed when the account is signed out of that browser from somewhere else — your other sessions ended, a session that ran out — as soon as the app there learns of it. Drafts are also kept on our servers, so signing in again brings them back.

Kemble Desktop, the app for Windows, macOS and Linux, is this same app in a window of its own. It keeps its preferences, its window’s size and place, and the signed-in session in its own browser profile on that computer, as a browser would. Its notifications come from the open app over Kemble’s own connection, not through Google’s push service, and the desktop app keeps no copy of what they say. With more than one account signed in on it, the app asks that connection for each account’s notifications too, naming each by its own sign-in; Kemble checks each sign-in, sends each account’s notifications with the words its own settings allow, stops as soon as that account signs out, and keeps no record of which accounts share the app.

Kemble Desktop can show the game you are playing as “Playing …” in Kemble Circle. It is off until you turn it on in Kemble Desktop’s Preferences › Games. While it is on, the app reads the list of programs running on your computer every 20 seconds and compares it, on the computer, with a list of well-known games and any you added yourself; the list is thrown away straight after and never leaves your computer, and adding a game shows the running programs once, in a menu on the computer only. Only a recognised game’s name is sent to Kemble, and only while Kemble Circle is in front. Kemble keeps it as your activity for 10 minutes, renewed while the game runs, so it is gone at most 10 minutes after the game stops, the app quits or the computer sleeps. It is shown where Kemble Circle shows what you are doing — to your friends in Active Now and to the people in communities you are in — never in Kemble Work, and not while you are invisible. Turning off “Share my activity” in Settings › Privacy & safety stops it on every device and deletes the game shown straight away.

Without a yes, this website stores nothing about you but your answer. It caches its own pages in your browser so they open offline.

The first time you open this website or the app, a bar at the foot of the screen asks one question: may Kemble count which kinds of pages are opened and a few actions, with Google Analytics through Cloudflare? Decline and Accept look the same and sit side by side. Until you choose, nothing is counted, nothing is sent and no analytics cookie is set.

To change your mind at any time: Cookie settings, at the foot of every page of this website, or in the app — Settings › Account in Kemble Work, Settings › Privacy & safety in Kemble Circle. It opens the same question again, with what you chose. Declining stops the counting straight away.

Everything else Kemble does with your data is in the privacy policy