Cookie & Tracking Technologies Policy
A clear, comprehensive breakdown of operational cookies, authentication tickets, local storage tokens, and our uncompromising zero-third-party-ad-tracker pledge.
1. Understanding Cookies, Local Storage & Cryptographic Tokens
Cookies and modern browser storage technologies are small data files placed on your device when you interact with digital web applications. Ozikol utilizes cookies, HTML5 LocalStorage, and encrypted session tokens strictly to authenticate administrators and members, enforce cryptographic security against cross-site attacks, and remember functional UI preferences such as interface language and dark/light display modes.
2. The Ozikol Zero-Ad-Tracker Guarantee
Uncompromising Ad-Free Environment: Ozikol does not deploy third-party advertising cookies, cross-site tracking pixels, social media remarketing beacons, or data broker scripts (such as Google AdSense, Facebook Pixel, or TikTok Trackers). We do not monetize your browsing behavior, and we never share visitor telemetry with advertising networks.
3. Comprehensive Platform Cookie & Storage Inventory
The following table provides an exhaustive, transparent inventory of all first-party cookies and local storage keys utilized across the Ozikol platform:
| Cookie / Key Identifier | Category | Specific Operational Purpose | Standard Duration |
|---|---|---|---|
.AspNetCore.Antiforgery.* |
Strictly Necessary | Cryptographic token designed to prevent Cross-Site Request Forgery (CSRF) attacks, ensuring form submissions originate from your authorized session. | Session (Purged on browser close) |
.AspNetCore.Identity.Application |
Strictly Necessary | Encrypted authentication ticket verifying the identity of logged-in administrators, staff members, and residents across secure portal pages. | 7 Days (Sliding expiration) |
.AspNetCore.Culture / ozikol_culture |
Functional Preference | Remembers your selected language and localization formatting (e.g. English, French, Spanish, German, Arabic). | 1 Year |
ozikol_cookie_consent |
Functional Preference | Stores your cookie acknowledgement preferences so you are not repeatedly prompted on subsequent visits. | 1 Year |
ozikol_tenant_context |
Strictly Necessary | Caches active organization workspace routing context to ensure requests are routed to the correct dedicated tenant instance. | Session |
ozikol_theme_preference |
Functional Preference | Records user preference for visual display theme (Default Light, Dark Mode, or System Synchronized). | 1 Year |
ozikol_sidebar_state |
Functional Preference | Remembers whether the executive MIS navigation sidebar was collapsed or expanded by the user. | 180 Days |
4. Native Desktop & Mobile Client Storage Architecture
When you interact with Ozikol via our native mobile applications (iOS/Android) or our Windows Desktop Enterprise application, traditional browser HTTP cookies are not utilized. Instead, native applications employ operating-system-level secure cryptographic vaults:
- Windows Desktop Enterprise Client: Stores authentication tokens and workspace credentials using the Windows Data Protection API (DPAPI) and local encrypted SQLite files (SQLCipher AES-256).
- iOS Mobile Application: Employs Apple Keychain Services for secure storage of JSON Web Tokens (JWT) and biometric authentication flags.
- Android Mobile Application: Employs Android Keystore and EncryptedSharedPreferences for hardware-backed token encryption.
5. Server-Side Operational Telemetry & Diagnostics
To maintain 99.99% availability and defend against cyberattacks, our cloud web servers log technical diagnostic telemetry. These logs record API response latency, HTTP status codes, browser user-agent tokens, and IP addresses. IP addresses in general diagnostics are truncated and anonymized. Diagnostic logs are used strictly for system performance tuning, DDoS mitigation, and intrusion prevention, and are automatically purged after 30 calendar days.
6. How to Manage, Inspect, and Block Cookies
You maintain full control over cookie storage through your web browser configuration:
- Google Chrome: Settings > Privacy and Security > Cookies and other site data.
- Microsoft Edge: Settings > Cookies and site permissions > Manage and delete cookies.
- Mozilla Firefox: Options > Privacy & Security > Cookies and Site Data.
- Apple Safari: Preferences > Privacy > Manage Website Data.
Impact of Disabling Cookies: If you configure your browser to block all cookies, strictly necessary security and authentication cookies will be blocked. Consequently, you will not be able to log into your administrator account or submit authenticated forms. To configure your settings without breaking core functionality, visit our Privacy Choices Portal.