Yulya Bot operates with a strict zero-advertising and zero-tracking philosophy. We do NOT use third-party marketing cookies, cross-site tracking pixels, fingerprinting scripts, Google Analytics, or retargeting beacons. Every cookie and web storage mechanism deployed across our web properties (discord.yulya.me) is strictly necessary to authenticate your dashboard sessions and preserve your personal UI preferences.
This Cookie Policy explains how Yulya Bot ("Yulya", "we", "us", or "our") utilizes HTTP cookies, browser local storage, and related web telemetry technologies when you visit our official web portal and services located at https://discord.yulya.me, including the Command Center (/dashboard), Personal Hub (/hub), Cosmetics Store (/store), and WebRTC Voice Portal (/mic).
This policy must be read alongside our Terms of Service and Privacy Policy. By accessing our web applications, authenticating via Discord OAuth2, or configuring your servers through our dashboard, you acknowledge and agree to our use of strictly necessary cookies and browser storage as detailed below.
Modern web applications rely on small, secure data fragments stored on your local device to enable interactive functionality:
discord.yulya.me origin. Unlike cookies, LocalStorage values are never automatically transmitted across the network in HTTP headers, reducing bandwidth consumption and enhancing security.Unlike commercial advertising networks, Yulya does not monetize user attention or personal browsing data. We do not partner with data brokers, ad networks, or commercial analytics trackers.
We practice extreme data minimization. Our web application issues only one first-party HTTP cookie, which is strictly necessary to operate the service:
| Cookie Identifier | Category & Function | Lifespan | Domain & Security Attributes |
|---|---|---|---|
yulya_session |
Strictly Necessary / Authentication Stores a secure, cryptographically random 32-byte hexadecimal session token issued after completing Discord OAuth2 authorization. Identifies your authenticated user profile across the Command Center ( /dashboard), Personal Hub (/hub), and Server Settings.
|
Session / 7 Days of Inactivity |
discord.yulya.meHttpOnly • Secure • SameSite=Lax |
The yulya_session cookie does not contain your Discord password, payment card data, or raw private tokens. It functions solely as an encrypted pointer to a volatile server-side session registry.
To optimize page responsiveness, minimize server latency, and provide a seamless user interface, our client-side scripts store non-sensitive preference keys within your browser's sandboxed localStorage:
| Storage Key | Category & Purpose | Lifespan | Data Content |
|---|---|---|---|
yulya_theme |
UI Preference — Remembers your chosen aesthetic display theme (Cyber Dark default). | Persistent until cleared | String identifier (e.g. "dark"). |
yulya_chart_range |
UI Preference — Remembers your preferred chart timeframe (e.g. 24h, 7d, 30d) in the server financial analytics view. | Persistent until cleared | String identifier (e.g. "7d"). |
dashboard_cache_servers |
Client Cache — Temporarily caches your accessible server list to eliminate UI stutter and prevent redundant Discord API fetches. | 15 Minutes / Session | JSON serialized server IDs, server names, and icon hashes. |
yulya_cart |
Functional — Maintains selected items in your cosmetics shopping cart on /store prior to checkout. |
Session | Array of virtual item package IDs. |
None of the data stored in client storage can be accessed by other websites, and none of it contains personally identifiable private credentials.
When interacting with our ecosystem, you may interface with third-party service providers that manage their own technical session cookies:
discord.com). Discord places its own essential session and authentication cookies to verify your Discord credentials. Those cookies are governed strictly by Discord's Privacy Policy.checkout.tebex.io). Tebex utilizes essential cookies strictly to maintain your cart state, prevent payment fraud, and ensure PCI-DSS Level 1 compliance. Those cookies are governed by Tebex's Privacy Policy.__cf_bm) to identify trusted web traffic and protect our infrastructure from malicious botnets. These cookies do not store personally identifiable data.Under the European Union ePrivacy Directive (Directive 2002/58/EC, amended by 2009/136/EC) and GDPR Article 5(3), website operators are legally required to obtain prior affirmative consent for cookies unless the cookie is strictly necessary in order to provide an information society service explicitly requested by the subscriber or user.
Because our sole HTTP cookie (yulya_session) is used exclusively to maintain your authenticated login session following your explicit request to log in via Discord OAuth2, it qualifies for the strictly necessary exemption. It cannot be disabled without completely preventing login functionality.
Under the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), California residents maintain the right to opt out of the "sale" or "sharing" of their personal information for cross-context behavioral advertising.
Affirmative Disclosure: Yulya Bot does NOT sell your personal data, nor do we "share" personal information with third parties for cross-context behavioral advertising via cookies, tracking pixels, or any other mechanism. Therefore, we do not provide a "Do Not Sell or Share My Personal Info" toggle, as no such practices take place.
You maintain complete, granular control over all cookies and storage items deposited on your device. You can view, manage, restrict, or purge them at any time through your web browser's privacy settings:
discord.yulya.me → Delete.discord.yulya.me → Remove Selected.yulya.me → Remove.Instant Session Destruction via Dashboard: You can immediately invalidate your session and instruct your browser to purge the yulya_session cookie by clicking the "Logout" button on any dashboard page or directly navigating to https://discord.yulya.me/logout.
Because we deploy only strictly necessary authentication cookies:
/dashboard), manage your personal profile on the Hub (/hub), or configure server BYOK keys, as the server will not be able to establish an authenticated session./daily, /crypto, /imagine) will continue to operate normally.We treat authentication tokens with enterprise-grade security engineering to safeguard against session hijacking, Cross-Site Scripting (XSS), and Cross-Site Request Forgery (CSRF):
yulya_session cookie is enforced with the HttpOnly attribute. This prevents malicious JavaScript or unauthorized scripts running in the browser from accessing or reading your session token.Secure attribute, ensuring that it is transmitted strictly over encrypted Transport Layer Security (TLS/HTTPS) tunnels. It will never be transmitted over plaintext HTTP.SameSite=Lax restrictions. Your authentication cookie is withheld during cross-site sub-requests (such as third-party image embeddings), protecting your account against cross-site forged requests.We may update this Cookie Policy from time to time to reflect modifications in our operational architecture, security implementations, or legal standards under Discord Developer Policies. Whenever changes occur, we will update the "Last Updated" date at the top of this document. We encourage users to periodically review this page to remain informed of our data storage practices.
If you have any questions, security inquiries, or data protection concerns regarding our use of cookies or browser storage, please reach out to our team:
/help command inside Discord.