Cookie Policy
Every cookie and browser storage key Projments uses, what each one is for, how long it lasts, and how to control them.
- Effective
- 16 August 2026
- Last updated
- 16 August 2026
- Version
- 1.0
In short
- Projments sets no advertising cookies and runs no third-party behavioural analytics.
- The only cookies we set are the ones that keep you signed in and protect the sign-in form.
- Your preferences — theme, column layouts, last workspace — are kept in your browser’s local storage and never sent to us.
This summary is for orientation only. The sections below are the document that applies.
1. What cookies are#
A cookie is a small file a site stores in your browser and reads back on later requests. Local storage is a similar mechanism, except the data stays in the browser and is only read by the page itself. Projments uses both, for the narrow purposes below.
2. Cookies we set#
All of these are strictly necessary: without them you cannot sign in or stay signed in. None of them track you across other sites.
| Name | Purpose | Lifetime | Type |
|---|---|---|---|
| __Secure-next-auth.session-token (next-auth.session-token over plain HTTP in development) | Holds your signed session so the app knows who you are on each request. HttpOnly, so no script can read it. | Up to 30 days, and invalidated immediately when you change your password | Strictly necessary |
| __Host-next-auth.csrf-token | Protects the sign-in and sign-out forms against cross-site request forgery. | Until the browser session ends | Strictly necessary |
| __Secure-next-auth.callback-url | Remembers which page to return you to after signing in. | Until the browser session ends | Strictly necessary |
The same session cookie is used by the Projments mobile app when it opens web views, so there is one session across the products rather than several.
3. Preferences kept in your browser#
These are stored locally by the app and are never transmitted to our servers. Clearing your browser data removes them and resets the interface to its defaults.
| Key | What it remembers |
|---|---|
| tt_theme_config | Light or dark mode, accent colour, corner radius and font scale |
| tt_last_workspace | The workspace to return you to, so “Back to app” lands in the right place |
| tt_nav_order_*, tt_col_order, tt_col_widths, tt_col_visibility | Your navigation order and table column layout, per list |
| tt_*_panel_width, tt_collaboration_sidebar_* | Widths of side panels you have dragged |
| tt_*_status_options, tt_priority_options, tt_currency | Status, priority and currency choices you have customised |
| tt_read_notifications, tt_deleted_notifications, tt_calls_last_read_at | Which notifications and calls you have already seen |
4. Third-party cookies#
We embed no advertising, no social widgets and no third-party analytics, so no third party sets a cookie on our pages. Two adjacent surfaces are worth knowing about:
- Stripe. Paying takes you to Stripe’s own checkout, hosted by Stripe. Stripe sets its own cookies there, for payment processing and fraud prevention, under Stripe’s privacy policy.
- Calls. Audio and video calls run over LiveKit using tokens issued by us, not cookies. Nothing is stored in your browser for them beyond the page session.
5. Consent#
Under the ePrivacy rules that apply in the EU and UK, cookies that are strictly necessary to deliver a service the user asked for do not require consent. Every cookie in §2 is in that category, which is why Projments shows no cookie banner. If we ever add an optional cookie — analytics, for instance — we will ask for your consent before setting it, and this page will say so.
6. Controlling cookies#
Every browser lets you view, block and delete cookies, usually under Settings → Privacy. You can also use private browsing, which discards them when the window closes.
7. Contact#
Questions about this policy go to our Support Center. See also the Privacy Policy. This version is 1.0, effective 16 August 2026.