We Use Cookies to Keep Your Macros Running Smoothly
Clickeno operates at the intersection of precision and performance. To deliver a reliable macro-automation tool that integrates seamlessly with your game client, we rely on a minimal set of cookie files. This isn't about tracking you across the web—it's about remembering your configuration, maintaining session integrity during intense gameplay, and ensuring our tools react faster than your opponents.
Unlike typical ad-tech networks, our cookie usage is strictly functional. We don't sell data, and we don't use third-party trackers to build profiles. If you're a competitive player, you know that latency is the enemy. These technical cookies are the backbone of low-latency communication between our desktop app and the Clickeno cloud sync.
> SYNC_TOKEN: VALID
> PING: 12ms
> SESSION: ACTIVE
What We Store and Why
Every cookie set by Clickeno serves a specific technical function. We categorize them by necessity to help you understand exactly what happens when you enable "Remember Me."
Our Philosophy
"If it doesn't improve macro execution or account security, we don't use it." We audit our cookie usage quarterly against game ToS updates to ensure compliance.
Authentication & Session
Keeps you logged in during gameplay. Prevents accidental disconnects mid-raid. These cookies contain encrypted session IDs only. Duration: 4 hours.
Config Sync
Loads your specific macro profiles (keybinds, delays, loops) instantly when the app launches. Essential for multi-game setups. Duration: 30 days.
Latency Telemetry
Anonymized data points on execution speed. We use this to optimize our API, not to profile you. Helps us maintain sub-20ms latency. Duration: Session.
Feature Adoption
Tracks which tools are actually used (e.g., "Mouse Jitter Correction" vs. "Simple Clicker"). No personal identifiers. Helps us build better tools, not sell ads. Duration: 7 days.
Method Note: Cookie Evaluation
- 1. Risk: Minimizing data residency exposure. All auth cookies are encrypted at rest and scoped to our primary domain only.
- 2. Robustness: Ensuring macro profiles load even if external ad-blockers aggressively purge storage. We use localStorage as a fallback.
- 3. Limits: We do not persist cookies for more than 30 days without re-authentication, regardless of user setting. This forces periodic security checks.
The Trade-offs We Accept
Mitigation: We detect unusual IP locations and force a logout + email verification.
Mitigation: Data is anonymized via hashing; we only see aggregate trends, never individual profiles.
Mitigation: We batch non-essential cookies behind a single "Opt-in to Performance" toggle at signup.
Key Terms
HTTPOnly
A security flag that prevents JavaScript from reading the cookie. We use this for auth tokens to stop credential theft via malicious scripts. Our Take: Mandatory for security.
SameSite
Restricts how cookies are sent with cross-site requests. Prevents CSRF attacks. Our Take: Always set to 'Lax' or 'Strict'.
LocalStorage
Not technically a cookie, but we use it to store heavy macro configs. It lives on your device and doesn't travel to our server. Our Take: Essential for offline mode.
Session ID
A random string generated when you log in. It identifies your current browser session. Our Take: Valid only until you close the browser (unless you check "Remember Me").
Fingerprint
A calculated hash of your device/browser specs to prevent duplicate logins. Our Take: We don't use this for ads; it's purely for security alerts.
Consent Token
A simple 'yes' or 'no' flag stored to remember your privacy choices. Our Take: Respects your decision so you don't have to click twice.
Need to Change Your Settings?
You can manage cookie preferences directly in the Clickeno app under Settings > Privacy. Or, use your browser's built-in controls to block/remove cookies anytime.