Cookies & browser storage
A factual inventory of the storage used by this version of TN.TC.
These documents describe the proposed launch terms. Paid creator products are not yet available. The final terms and working support channel will be published before live sales begin.
On this page
1. Current choices
TN.TC does not use advertising pixels or session replay. Production may load the Cloudflare Web Analytics performance/visit measurement script; this is not a recording of screens, keystrokes or form content. Our server-side page and link click statistics are separate. Cloudflare infrastructure supports measurements such as Core Web Vitals and page loading. If optional advertising or behavioural tracking is introduced, it will not run before any required choice.
Essential sign-in/access storage and the preferences and drafts you request are described below. Fonts are served by TN.TC; no font request is sent to Google.
2. Sign-in and security cookies
Auth.js session cookies keep a web session for up to 24 hours. Temporary CSRF, callback and sign-in-flow cookies support secure authentication; their names may include secure prefixes on HTTPS. A Box PIN grant uses box-[slug] for up to 15 minutes. The separate box-sub-[slug] uploader cookie lasts up to 30 days and identifies that browser’s own submissions. A shared PIN is not proof of submission ownership.
3. Preferences and drafts
The selected workspace is remembered in tntc-workspace. Locale handling may use NEXT_LOCALE. Browser local storage remembers your theme and site-editor mode; it also holds QR drafts, conversation drafts and pending messages for the requested editing or messaging feature. Bell request drafts use session storage and normally end with that tab session.
In the mobile app, session tokens are kept in the device's secure key store (Keychain or Keystore). Unsent messages and unfinished large uploads stay in app storage, separated per account, so they can continue when the app is reopened; they are removed once finished, discarded, expired or when you sign out. Local storage has no automatic cookie-style expiry. Shared-device users should sign out and clear site data when appropriate. Clearing drafts or pending-message storage can remove work that has not yet been sent.
4. Other services and media
External sign-in, payment or app-store pages have their own storage notices. Our infrastructure may use security technologies when necessary to protect a request. The actual production inventory must be rechecked after deployment configuration is final. Opening a social link takes you to another service; showing its icon does not embed that service’s tracking code.
5. How to manage storage
You can remove or block TN.TC site data in your browser settings. Blocking essential cookies can prevent login, protected Box access or recognition of your own file submissions. Theme and language can also be changed through the application controls. There is no need to consent to marketing to use these controls.
Browser storage and the server’s own visit records are different. Clearing cookies does not delete a server-side account or transaction. See the Privacy Notice for data rights and the current retention limitations.