Cookies Aren't Invisible Code. They're Your Digital Fingerprint.

In the digital arena, every click, every pause, every weapon swap leaves a trace. At Digavo, we use these traces to understand how you play, so we can optimize the game for you—not just the hardware. This policy details how we collect, use, and protect that data to build a faster, smoother, and more responsive gaming experience.

Abstract representation of data flow and session tracking

Session Analysis

Session ID: #A7F3C2 | Input Latency: 2.1ms

Section 1

The Essential & The Optional: A Necessary Division

Strictly Necessary Cookies

These are the non-negotiables. Without them, the Digavo app cannot function. They are tied to your session, enabling the secure login process, remembering your calibration preferences (like your preferred refresh rate or macro setup), and ensuring the game's anti-cheat systems recognize your authorized session. They are temporary, deleted when you close your browser, and contain no personal data beyond your unique session ID.

Technical Note

These cookies are first-party only, meaning they originate strictly from digavo.pro and are not shared with third-party domains.

Performance & Analytics Cookies

This is where we learn. These cookies (which are strictly optional and require your explicit consent) collect anonymized data on app performance. We track metrics like frame rate stability, input latency spikes, and network jitter patterns *without* linking them to your personal identity. This data helps us answer real player scenarios: "Why does my FPS drop in dense environments?" or "Is my 240Hz monitor being utilized correctly?" The goal is to build better optimization profiles for everyone.

Dashboard view of performance metrics tracking
Fig. 1: Anonymized Performance Dashboard

Your Control & Consent

  • You can accept or decline performance analytics cookies via the global consent banner.
  • You can clear your session data at any time in the Digavo app settings.
  • You can contact our team to request a full report on the data linked to your account.
Read the Full Privacy Policy →

Section 2

The Analyst's Lens: Five Critical Questions

For anyone scrutinizing our data handling—be it a tournament organizer, a hardware reviewer, or a privacy-conscious player—this is where we address the scrutiny head-on.

1. What data is linked to my personal identity?

None, for analytics. Session IDs are anonymized. Only your email (for account) and billing details (if you subscribe) are personally identifiable, and these are held in a separate, encrypted database compliant with standard security practices.

2. Does cookie data affect my game's anti-cheat?

No. Digavo operates in a separate layer. Our cookies do not interact with or modify game files. Anti-cheat systems see our app as a trusted overlay, and our performance data collection is passive and read-only.

3. Can you sell my playstyle data?

No. Our business model is based on software subscription, not data brokerage. Aggregated, anonymous data may be used in public benchmarks (e.g., "average input latency for Valorant players"), but your individual data is never sold.

4. How does this work across different games?

We use distinct cookie profiles per game title (e.g., a 'Valorant' profile, a 'CS2' profile). This allows for precise, game-specific optimizations without cross-contamination of settings or data across your gaming library.

5. What's the retention period?

Session cookies expire on browser close. Analytics cookies expire after 12 months, but you can opt-out at any time, which will delete active analytics data associated with your session.

Section 3

Methodology: How We Validate Our Claims

🧠

Core Assumptions

  • • Hardware variability exists (CPU/GPU/RAM).
  • • Game engine latency is consistent per frame.
  • • User input is the most variable, measurable factor.
🔒

Operational Constraints

  • • No modification of protected game files.
  • • <5% CPU overhead target for the app itself.
  • • Compatibility with major overlay systems (Discord, Steam).
⚖️

What Changes Our View

Our methodology is iterative. We would reconsider our approach if:

  • • Independent benchmarks show no latency reduction.
  • • User reports consistently link crashes to our session tracking.
  • • A major game patch breaks our compatibility model.

The Cookie Collection Process

When you consent, a lightweight script activates. It measures input-to-frame delta (how long a click takes to register on screen) and frame rendering consistency (variation between frames). This data is compressed, encrypted with a session key, and sent to our analytics endpoint once per gameplay session—not in real-time, to minimize performance impact.

Note: You can disable this process entirely in the app's 'Performance & Privacy' settings without losing core functionality.

Simplified data flow schematic

Have More Questions About Your Data?

Our commitment to transparency is as important as our commitment to performance. If you need clarification beyond this policy, our privacy team is available during business hours.

Working Hours

Mon-Fri: 9:00-18:00 (TR)

Address

Istiklal Caddesi 123, Istanbul
Contact The Privacy Team