Tracking Technologies Documentation
Document Revision: February 2025
This page explains how our website at manthex.com relies on small data files and technical mechanisms to function properly. We're documenting what happens behind the scenes when you visit our platform and why these technologies exist in the first place.
The scope of this disclosure covers every tracking mechanism active across our domain. Some pieces are necessary for basic operations. Others support optional features you might find helpful.
What Occurs When You Access Our Platform
Your browser exchanges information with our servers the moment you navigate to any page under our domain. During this exchange, small text strings get stored locally in your browser's storage area. These strings contain identifiers, preferences, and session markers.
Think of it as leaving breadcrumbs that help the system recognize you on return visits. Without these breadcrumbs, each page load would treat you as a completely new visitor, which breaks functionality you'd normally expect to work.
Primary Functions These Technologies Serve
Session Continuity
Maintaining your connection as you navigate between pages prevents constant re-authentication and preserves your current workflow state.
Interface Memory
Recording your display preferences, language choices, and layout configurations means you don't reset these every single visit.
Security Verification
Detecting suspicious patterns and validating legitimate access requires tracking request sequences and timing patterns across your session.
Performance Monitoring
Understanding which sections load slowly or fail frequently lets us fix problems affecting actual user experience rather than guessing.
Technical Categories We Employ
Foundation Layer Technologies
These mechanisms keep the platform operational at the most basic level. Disabling them means core functionality simply stops working.
- Authentication Tokens: Verify your logged-in status without forcing repeated password entries. Expires when you close your browser or after 12 hours of inactivity.
- Session Identifiers: Track your current browsing session to maintain state across page transitions. Deleted automatically when you terminate your browser session.
- Security Markers: Prevent cross-site request forgery attacks by validating that form submissions originate from legitimate sources. Lives only during active form interactions.
- Load Balancing Cookies: Direct your requests to the same server cluster to maintain data consistency. Necessary for distributed infrastructure to work properly.
Preference Storage Systems
These remember choices you've made about how you want the interface to behave. You can refuse these, but you'll reconfigure settings repeatedly.
- Display Configuration: Stores whether you prefer grid or list views, sidebar positions, and panel visibility states. Persists for six months unless you clear browser data.
- Language Selection: Remembers your chosen interface language to avoid auto-detection errors. Remains active for one year.
- Notification Settings: Tracks which alert types you've dismissed or want to see. Kept for three months to respect your feedback preferences.
Analytical Observation Tools
We monitor aggregate usage patterns to identify what works and what creates friction. Individual sessions get anonymized before analysis.
- Page Navigation Tracking: Records which pages get visited in which sequence to understand common workflows. Data gets aggregated weekly and individual identifiers removed after 90 days.
- Feature Interaction Logging: Captures which buttons, tools, and options actually get used versus ignored. Helps prioritize development effort on things people actually need.
- Performance Metrics Collection: Measures page load times, render delays, and interaction responsiveness from real user perspectives across different connection types.
- Error Event Recording: Captures technical failures, broken features, and system anomalies so engineering can reproduce and fix issues affecting users.
Third-Party Integration Points
Some features require external services that set their own tracking mechanisms. We've selected providers carefully but their policies govern their data practices.
- Content Delivery Networks: Serve static assets like images and stylesheets from geographically distributed servers. Sets minimal routing cookies to optimize delivery paths.
- Support Chat Service: Powers the help widget visible on certain pages. Creates session identifiers to maintain conversation context if you navigate away and return.
- Video Embedding Platform: When tutorial videos appear on pages, the hosting service may set cookies for playback optimization and view counting. Only active on pages containing embedded content.
Detailed Technical Inventory
Below you'll find specific identifiers, their retention periods, and what they accomplish. This represents our complete deployment as of February 2025.
| Identifier Name | Purpose | Duration | Category |
|---|---|---|---|
| _mx_session | Primary session tracking across page navigation | Browser session | Essential |
| _mx_auth | Authentication state verification | 12 hours | Essential |
| _mx_csrf | Cross-site request forgery protection | Session duration | Essential |
| mx_ui_prefs | Interface display preferences and layout choices | 6 months | Functional |
| mx_lang | Selected interface language | 1 year | Functional |
| mx_analytics_id | Anonymous usage pattern tracking | 90 days | Analytics |
| mx_performance | Page load speed measurement | 30 days | Analytics |
| _cdn_route | Content delivery optimization routing | 24 hours | Third-party |
| support_chat_sess | Help chat conversation continuity | Session duration | Third-party |
Storage Duration Principles
Session cookies disappear when you close your browser completely. Persistent cookies remain until their expiration date or until you manually delete them through browser settings.
We periodically review retention periods to minimize data persistence. Technical requirements and legitimate operational needs determine minimum storage times.
Your Control Mechanisms
Every modern browser provides tools to manage these tracking files. You decide what gets accepted, what gets blocked, and when stored data gets cleared.
Browser-Level Management
Access your browser's settings panel to configure cookie handling policies. Common options include accepting all cookies, blocking third-party cookies specifically, or rejecting everything except essential ones.
Most browsers also let you delete existing cookies through their privacy or history management sections. This clears previously stored data but doesn't prevent future storage unless you change acceptance policies.
Functionality Impact Warning: Blocking essential cookies will break authentication systems, session management, and security protections. You won't be able to log in or maintain state across pages.
Refusing functional cookies means repeatedly configuring preferences. Analytics cookies don't affect your immediate experience but help us identify and fix problems that might otherwise persist unnoticed.
Data Handling Practices
Information collected through these mechanisms gets treated according to our broader data protection protocols. We don't sell this data or share it with advertisers.
Analytics data undergoes anonymization processes that remove personally identifiable details before aggregation. Session information gets encrypted during transmission and storage.
Third-party services operate under their own privacy policies. We've vetted these providers but recommend reviewing their documentation if you want specifics about their data practices.
Technical Security Measures
Sensitive cookies use the Secure flag requiring HTTPS transmission. HttpOnly flags prevent JavaScript access to authentication tokens. SameSite attributes restrict cross-origin request attachment.
Our servers validate cookie integrity on every request and reject tampered values immediately. Session tokens rotate periodically to limit exposure windows if somehow compromised.
Changes and Updates
We modify our tracking implementations when adding features, removing deprecated services, or responding to technical requirements. Significant changes get reflected in updated versions of this documentation.
Check the revision date at the top of this page to see when we last updated the content. Material changes appear here within 30 days of implementation.
Continuing to use the platform after changes go live constitutes acceptance of modified tracking practices. If you disagree with updates, discontinue use and contact us to discuss data deletion.
Questions About These Technologies
Specific concerns about tracking mechanisms, data retention, or technical implementation details warrant direct discussion. Reach our team through any of these channels: