COOKIE
ARCHITECTURE
"At Runorya, we treat performance as a science and transparency as a standard. Our cookie infrastructure is designed to maintain your session integrity without compromising your machine's velocity."
01. What are Cookies?
In the context of high-performance gaming applications, cookies are small packets of data stored on your device that help us "remember" your technical preferences. Whether it is your preferred server region in Istanbul or your specific HUD layout configurations, these files ensure that your return to Runorya is seamless and optimized for your specific hardware.
These files allow us to differentiate between a first-time visitor and a returning professional, enabling us to skip redundant loading sequences and deliver a personalized dashboard experience immediately upon authentication.
Method Note: Evaluation Criteria
We evaluate our cookie usage based on a "Performance-to-Privacy" ratio. Every cookie injected into the user's browser must justify its existence through measurable UX improvements—such as a reduction in login latency or the persistence of mission-critical settings. We avoid "tracking for the sake of tracking," prioritizing system robustness over marketing data density.
02. How We Deploy Data
Our architecture categorizes cookies into three distinct tiers: Essential System State, Performance Analytics, and Functional Experience. Each serves a specific purpose in the Runorya ecosystem, ensuring compliance with Turkish digital regulations (KVKK) while maintaining a global competitive standard.
-
Essential Cookies
Mandatory for secure login, anti-fraud measures, and maintaining your session across different app modules. Without these, the core platform functionality is disabled.
-
Performance & Optimization
These help us identify bottleneck points in our Istanbul and Ankara server routes by tracking how users navigate our interface under different network conditions.
ENGINEERING TRADE-OFFS
Downside: Third-party analytics cookies can inject up to 200ms of additional scripts onto the initial DOM load.
Mitigation: We use asynchronous loading and prioritize critical server-side session management over client-side scripts.
Downside: Tracking IP ranges to assign Turkish servers requires storing geographical metadata.
Mitigation: IP addresses are anonymized and hashed before being stored in the session cookie.
Downside: Extended cookie expiration (1 year) can lead to outdated security tokens.
Mitigation: We implement a 30-day "forced refresh" on sensitive auth tokens regardless of cookie age.
COOKIE INVENTORY
A transparent breakdown of the identifiers currently utilized by the Runorya domain architecture.
Regional Control
We respect your right to manage your data footprints. Most modern browsers allow you to block or delete cookies through their settings menu. For more information on managing cookies in Turkey, visit the Official KVKK Information Portal.
MANAGE YOUR PROTOCOL
Adjust your preference via standard browser control panels. Be advised that disabling essential cookies will lead to immediate service degradation.
CHROME
Settings > Privacy and Security > Cookies and other site data
FIREFOX
Options > Privacy & Security > Cookies and Site Data
SAFARI
Preferences > Privacy > Manage Website Data
EDGE
Settings > Cookies and site permissions > Manage and delete cookies
Questions regarding our cookie architecture?