Back to Legal DirectoryLEGAL DIRECTIVE // 04

COOKIE
POLICY.

Functional tracking matrices and anonymous analytics declarations.

TRANSPARENCY

We use absolute minimum tracking. No third-party ad networks. No cross-site profiling. We use localized tokens exclusively to maintain decentralized session states and essential interface settings.

01

What are Cookies?

Cookies are local files stored on your machine.

They contain data retrieved by your browser to serve specific purposes. TALA heavily relies on client-side storage to execute cryptography without touching servers.

  • Session Data Temporal state tokens deleted upon browser exit.
  • Persistent Storage Local hardware storage preserving UI themes (Dark/Light).
  • First-Party Only Set uniquely and explicitly by the TALA protocol domain.
02

Why We Use Cookies

Our decentralized service completely requires local authentication matrices to function:

  • Identity & ConnectionWallet connection persistence (Web3Modal/Wagmi flags) preventing immediate disconnection upon refresh.
  • Authentication OverlaysSecuring JWTs holding the server signature proving you own the connected Web3 wallet.
  • Performance & DiagnosticsBasic Vercel/NextJS routing cache variables essential to SPA architecture.
03

Detailed Inventory

We believe in verifiable transparency. Here is the strict index of all potential local variables utilized by TALA:

Token/CookieTypeTTLLogic Vector
auth_sessionHTTP Cookie7 DaysRetains cryptographic wallet signature proof
wagmi.storeLocal StorageBrowserCached RPC provider and Web3 connection state
tala-themeLocal StorageInfiniteUI contrast mode preference
csrf_tokenHTTP CookieSessionAnti-forgery injection block
04

Third-Party Vectors

While TALA fundamentally limits external vectors, interacting with decentralized networks triggers external network tracking.

  • Web3 Wallets (MetaMask etc.) Inject completely siloed variables entirely out of our domain scope.
  • RPC Provider Analytics Alchemy and independent RPC nodes passively log query IPs globally via the transaction broadcast route.
WE HAVE ZERO ADMINISTRATIVE CONTROL OVER PROTOCOL-LAYER METADATA AGGREGATION.
05

Consent Mechanics

Navigating the protocol and successfully deploying vaults constitutes active consent to fundamental storage mechanics outlined here, as it is mathematically impossible to sustain a session otherwise.

06

Control Access

Browsers grant absolute client-side sovereignty. You can nuke LocalStorage and clear Cookies manually via developer tools. Disabling these immediately bricks the DApp connection.

T.A.R.A. - Trustworthy AI Response Assistant