Most cookie policies are long because the site has a lot to declare. This one is short for the opposite reason: Tessira sets a single cookie, it only keeps you signed in, and there is nothing else to tell you about.
Last updated: 23 August 2026
tessira_sess. It is what
keeps you signed in, it is strictly necessary for the app to work at all, and it holds a
random token rather than anything about you. There is no analytics cookie, no advertising
cookie, no third-party cookie, no pixel and no tracker anywhere on this site — which is why
you were not shown a consent banner. Tessira does not use local storage or any similar
browser storage either.
A cookie is a small piece of text that a website asks your browser to store and send back on every subsequent request to that site. Cookies are how a website recognises that two separate requests came from the same person — which is the only reason a site can keep you signed in as you move from page to page.
Cookies are also, notoriously, how sites follow people around the internet for advertising and measurement. Those are two very different uses of the same mechanism, and the law treats them differently: a cookie that is strictly necessary to deliver a service the user asked for does not require consent, while a cookie used for analytics or advertising does.
There is one, so rather than a wide grid with a single row in it, here it is in full:
| Property | Value |
|---|---|
| Name | tessira_sess |
| Category | Strictly necessary — authentication |
| Purpose | Keeps you signed in. It holds a random session token; the token is meaningless on its own and is matched to your account on the server. It contains no name, no email address and nothing about your CV. |
| Lifetime | 30 days, or until you sign out, or until a password reset revokes every session |
| Party | First-party, set by cubicpixel.co — the site you are on |
| Flags | HttpOnly, Secure, SameSite=Lax, Path=/ |
| Set when | You sign in. Cleared when you sign out. |
Those flags matter, so here is what each one buys you. HttpOnly means page
scripts cannot read the cookie, so a script injection cannot walk off with your session.
Secure means it is only ever sent over an encrypted connection.
SameSite=Lax means another website cannot cause your browser to send it along
with a request that changes your data.
The cookie is set when you sign in, and it is cleared when you sign out. Nothing sets it before you have an account, so simply reading this page does not put a cookie on your device.
A consent banner exists to ask permission for cookies that are not strictly necessary. Tessira does not set any, so there is nothing to ask you about. Showing a banner anyway — to look diligent, or to harvest an "accept" — would be theatre, and it would train you to click through the ones that actually matter elsewhere.
If Tessira ever adds a cookie or similar technology that is not strictly necessary, it will ask first, properly, with a real refusal option, and this page will be updated in the same release.
Tessira does not use localStorage, sessionStorage, IndexedDB,
browser fingerprinting or any other client-side storage or identification technique. Your
work is not held in the browser between visits — it is saved to your account as you type,
which is why you can open the same CV on another device and find it exactly as you left
it.
Your browser will, as it does with any website, cache ordinary files such as the stylesheet, the fonts and the images. That is standard browser behaviour, is not a cookie, identifies nobody, and clearing your browser cache removes it.
You are always in charge of cookies in your own browser. Every major browser lets you view and delete stored cookies, block cookies from specific sites, block third-party cookies, or refuse all cookies; the controls sit under Settings, usually within a Privacy or Security section. Private or incognito windows discard cookies when the window closes.
What happens if you block Tessira's one cookie: you will not be able to sign in. Sign-in will appear to succeed and then bounce you straight back to the login page, because the server has no way to recognise the next request as yours. The editor, your CVs, previews and PDF downloads are all behind that check and none will load.
Deleting the cookie is the same as signing out — your CVs are entirely unaffected, they live in your account, and signing in again brings everything back.
The public pages of this site — the home page, features, templates, the guides and these legal pages — work perfectly with all cookies blocked. There is nothing to sign into here.
This page covers cookies only. For what Tessira stores, how CVs are encrypted at rest, who else processes your data, and exactly what is sent to an external AI provider when you ask for a review, see the privacy policy. The terms of service cover the rest of the arrangement.
If the cookies Tessira uses ever change, this page changes in the same release. The date at the top is the date of the last change.
Questions about cookies or anything else on this page:
privacy@cubicpixel.co
General enquiries: hello@cubicpixel.co
Enquiries are handled by email only.