Cookies

Four cookies, all set by InkTick itself, all needed for the app to work. No analytics, no advertising, no tracking of any kind — which is why you were not asked to click anything on the way in.

Why there is no banner

The rules ask for your agreement before a site stores anything it does not need in order to do what you came for. Signing you in, keeping that sign-in secure, and remembering the language you chose are all things InkTick needs. Counting you, profiling you or advertising to you are not, and InkTick does none of them.

A banner that asks permission to do nothing is theatre. If InkTick ever adds analytics or advertising, a real choice will appear here and on every page, and it will default to off.

Every cookie, in full

All four are first-party, meaning they are set by InkTick and sent to nobody else. The three that matter for security cannot be read by JavaScript at all.

Name	What it does	How long
inktick_session	Keeps you signed in. Without it every page would ask for your password again.	30 days, or until you sign out
inktick_org	Remembers which company file you are looking at, so a bookkeeper with several does not land in the wrong one.	30 days, or until you sign out
inktick_2fa	Carries you from the password step to the six-digit code step. Signed, so it cannot be edited or reused.	Five minutes
inktick_lang	Remembers the language you picked, so the site opens in it next time.	Until you clear it

Things kept in your browser that are not cookies

Three small notes about how you arranged the screen. They live in this browser, are never sent to InkTick, and are gone the moment you clear site data.

inktick.nav.rail — Whether you collapsed the sidebar to icons.
inktick.nav.closed — Which sidebar sections you folded away.
inktick.nav.order — The order you dragged your menu into.

The one thing that is not ours

Creating an account asks you to prove a mobile number, and the text message is sent through Google’s Firebase. To stop that being abused to send strangers thousands of messages, Google runs a robot check, and that check sets cookies of its own on Google’s domains.

It loads on the sign-up page and nowhere else. Browsing InkTick, signing in, and using the app never touch it. Google explains what it collects in its own privacy policy.

What InkTick does not do

No analytics. Nobody is counting your visits or watching where you click.
No advertising cookies, no pixels, no remarketing, no audience lists.
No tracking you across other websites, and nothing sold or shared for that.
Nothing in a cookie identifies you by name. The sign-in cookie is a random token that means nothing away from our server.

Getting rid of them

Signing out deletes the sign-in and company-file cookies immediately. Every browser can clear the rest under its privacy or site-data settings, and you can block cookies for this site entirely — though if you do, InkTick will not be able to keep you signed in, so the app will not work.

This describes how InkTick behaves today, checked against the code rather than copied from a template. Formal terms and a full privacy policy are published before public sign-up opens — the short version of what we store and why is on the trust page. Questions, or want something deleted: support@inktick.com.