TitiLisa Back to Home

Cookie, Session & Storage Policy

Last updated: June 1, 2026 — Decentralized System Edition

1. Application Login Cookies (Central SaaS Core)

The central licensing portal uses standard functional cookies strictly to maintain user authentication states, track license validations, and handle secure billing processing. These cookies do not track your browsing habits or intercept your marketing activities.

Cookie Purpose Duration Type
tl_session User authentication session token 24 hours Functional
tl_license License validation state 30 days Functional
tl_csrf Cross-site request forgery protection Session Functional
tl_pref UI preferences (language, theme) 1 year Functional

We do not use any third-party analytics cookies, advertising trackers, or social media pixels on the central licensing portal.

2. Customer Edge Cookies (The Runtime Isolation Layer)

To execute 4-way syndication and manage mass-satellite interaction rings, the TitiLisa worker container must actively process, store, and refresh session cookies belonging to your personal, brand, and satellite social media accounts.

Storage Sovereignty: These session cookies (session_cookies JSONB database structures) are stored exclusively within the private PostgreSQL instance deployed on your personal Virtual Private Server (VPS).

Zero Cloud Leakage: The central TitiLisa platform developers have zero access to these authentication tokens. The data is completely containerized at your network edge.

Data Type Storage Location Access Layer
Social media session tokens Customer VPS PostgreSQL Customer only Edge
Proxy authentication credentials Customer VPS encrypted volume Customer only Edge
Satellite account cookie jars Customer VPS PostgreSQL (JSONB) Customer only Edge
Browser automation profiles Customer VPS Docker volume Customer only Edge

3. Third-Party Browser Fingerprinting Bypass

The TitiLisa automation engine utilizes localized browser automation paths that dynamically mimic human session data:

  • User-Agent strings (rotated per session)
  • Screen configurations and viewport metrics
  • WebGL and Canvas fingerprint noise injection
  • Timezone and locale spoofing based on proxy geolocation

These temporary local files are stored inside a localized Docker volume cache on your VPS host and are automatically deleted ("garbage-collected") immediately after an automated posting or interaction task is marked complete.

Cache Type Lifecycle Cleanup Category
Browser profile cache Task duration only Auto-deleted on task completion Temporary
Fingerprint rotation data Per-session Garbage collected after session end Temporary
Media processing cache Pipeline duration Purged after successful upload Temporary

4. Your Rights and Controls

Because TitiLisa operates on a hybrid decentralized model, your data control varies by layer:

  • Central SaaS cookies: Can be cleared through your browser settings at any time. Clearing session cookies will require re-authentication.
  • Edge cookies (your VPS): You have complete and exclusive control. Delete, modify, or export at any time through your PostgreSQL admin interface or by destroying the Docker containers.
  • Temporary automation caches: Automatically purged. No manual intervention required.

5. Policy Updates

This Cookie and Session Policy may be updated to reflect changes in the platform's cookie usage or regulatory requirements. Significant changes will be communicated through the licensing dashboard. For questions regarding this policy, contact mediaxtremeusa@gmail.com.

© 2026 mediaXtreme LLC. | TitiLisa All rights reserved.

Terms Privacy Refund Cookies