Cookie Policy

Comprehensive Institutional Cookie Policy and Web Telemetry Framework

Absolute technical transparency and strict user telemetry governance constitute the foundational pillars of digital security, exceptional user experience, and institutional respect for client privacy. The digital web platform of Ariana Tejarat utilizes lightweight text-based data objects commonly designated as "Cookies," alongside modern client-side storage technologies including Local Storage and Session Storage. This institutional policy is formulated to provide an exhaustive technical explanation of what cookies are, the precise operational purposes for which they are deployed, our taxonomy of active cookies, and your sovereign legal prerogatives to audit, configure, or restrict their execution.

Ariana Tejarat operates upon a disciplined data minimization standard: we utilize client-side storage strictly to deliver core technical functions, maintain transport security, and remember functional regional preferences. We categorically do not store unencrypted personally identifiable information, financial telemetry, or corporate secrets within cookies, nor do we deploy intrusive third-party commercial advertising tracking networks.

What Are Cookies and How Do They Support Modern Web Applications?

Cookies are compact text files transmitted by a web server and stored by your internet browser upon your local device (workstation, portable laptop, tablet, or smartphone). Upon subsequent requests, your browser transmits these identifiers back to our infrastructure, enabling our server to recognize your device, maintain your authenticated administrative session, preserve your selected localization language across page transitions, and prevent repetitive cryptographic challenges. Cookies contain no executable binary instructions, cannot introduce malware, and cannot independently read data from your hard drive.

Taxonomy of Cookies Deployed on the Ariana Tejarat Digital Platform

All client-side storage mechanisms utilized across our platform are strictly classified under four functional technical tiers:

• 1. Strictly Necessary & Transport Security Cookies: These cookies are indispensable for core platform execution, cryptographic validation, and security integrity. Key examples include Django’s Cross-Site Request Forgery security tokens (csrftoken) designed to neutralize malicious request spoofing, and secure session identifiers (sessionid) maintaining authenticated state. These security cookies activate automatically upon establishing connection with our servers and cannot be disabled without compromising platform stability.
• 2. Functional & Localization Preference Cookies: These identifiers store your chosen user preferences to eliminate redundant configuration during subsequent visits. This includes preserving your active language choice (Persian, English, or Arabic via the django_language cookie), remembering dismissed notification banners, and retaining layout density selections.
• 3. Performance Telemetry & Anonymized Analytics Cookies: These cookies compile aggregated, strictly anonymized statistical data concerning page interaction patterns, server response times, Core Web Vitals telemetry, and HTTP error frequencies. This intelligence is utilized exclusively by our engineering team to diagnose architectural bottlenecks, accelerate page render speeds, and enhance navigation ergonomics.
• 4. Perimeter Defense & Infrastructure Shielding Cookies: Specialized operational cookies deployed at the Web Application Firewall (WAF) and Content Delivery Network (CDN) tiers to distinguish authentic enterprise traffic from automated malicious bots (Bot Detection) and mitigate Distributed Denial of Service (DDoS) threats.

Lifecycles and Retention Horizons of Deployed Cookies

Cookies deployed across our platform adhere to two distinct operational retention lifecycles:

1. Transient Session Cookies: These identifiers remain active strictly during your active browsing session and are erased automatically from local memory the moment your browser application is terminated. Cryptographic CSRF tokens and session identifiers operate on this transient model.
2. Persistent Operational Cookies: These files carry a predefined expiration horizon (ranging from thirty days up to a maximum of twelve months) and persist across browser restarts, ensuring your chosen linguistic interface and regional settings remain consistent upon your return. These cookies purge automatically upon reaching their expiration timestamp.

Browser-Level Governance, Privacy Controls and Cookie Erasure

You retain sovereign authority over client-side storage across all visits. Modern web browsers provide granular controls empowering you to inspect stored cookies, reject non-essential categories, or purge local storage archives entirely. Guidance for popular browsers includes:

• Google Chrome: Navigate to Settings > Privacy and Security > Cookies and other site data.
• Mozilla Firefox: Navigate to Settings > Privacy & Security > Enhanced Tracking Protection > Cookies.
• Apple Safari: Navigate to Preferences > Privacy > Manage Website Data > Remove All.
• Microsoft Edge: Navigate to Settings > Cookies and site permissions > Manage and delete cookies.

Operational Caution: Restricting or disabling strictly necessary cookies will induce technical degradations, including inquiry form submission failures, loss of multilingual language persistence, and potential CSRF security blocks.

Prohibition of Third-Party Advertising Trackers and Cross-Site Profiling

In contrast to consumer advertising platforms, Ariana Tejarat maintains an institutional policy strictly prohibiting third-party commercial tracking networks, behavioral retargeting scripts, and data broker telemetry. Your interaction with our website is never monetized, packaged into algorithmic advertising profiles, or shared with commercial marketing syndicates.

Technical Specification Matrix of Active Cookies

To maintain absolute technical transparency, the detailed technical characteristics and security properties of all cookies deployed by Ariana Tejarat are documented below:

• csrftoken: Strictly Necessary - Provider: Django Framework - Function: Neutralizing Cross-Site Request Forgery vulnerabilities across form inputs - Duration: 12 months - Flags: SameSite=Lax.
• sessionid: Strictly Necessary - Provider: Django Framework - Function: Preserving authenticated administrative session integrity - Duration: 14 days or browser termination - Flags: HttpOnly, Secure.
• django_language: Functional Preference - Provider: Ariana Tejarat - Function: Persisting chosen localization language (fa, en, ar) across views - Duration: 12 months.
• cookie_consent: Functional Preference - Provider: Ariana Tejarat - Function: Recording user acknowledgment of the cookie transparency banner - Duration: 6 months.

Alignment with the ePrivacy Directive and International Web Standards

Our web telemetry architecture adheres strictly to the European Union ePrivacy Directive (Directive 2002/58/EC as amended), the Privacy and Electronic Communications Regulations (PECR), and W3C web privacy guidelines. We empower users with proactive choice: non-essential functional and analytical telemetry can be toggled without disrupting public website access. If you revoke consent, our infrastructure immediately terminates tracking tokens and updates your client-side storage state accordingly.

Server-Side Telemetry, Anonymized Logging & Hash Masking

Beyond browser cookies, our production infrastructure records standard network request logs for performance monitoring and intrusion defense. Crucially, these server logs do not store identifiable IP addresses; all incoming client IPs undergo cryptographic truncation and irreversible one-way hashing before writing to persistent storage disks. This architecture prevents any correlation between network telemetry and individual corporate entities, guaranteeing absolute anonymity across all digital touchpoints.

Periodic Policy Reviews and Regulatory Compliance

As web architectural standards evolve, software frameworks are upgraded, and international data protection regulations are updated, this Cookie Policy undergoes periodic technical and legal reviews. Any adjustments to our cookie taxonomy will be reflected on this page alongside a revised effective date.