Data Sovereignty
for Gaming Apps

We benchmark performance and stability by analyzing telemetry, but we treat your data with the same precision we demand from our code. This is how Markeno.pro ensures transparency while delivering actionable insights.

Contact DPO

Scope

Applies to all telemetry, cookie data, and user interactions on markeno.pro and associated analytics dashboards.

Active since 2026

GDPR / KVKK

Full compliance with EU GDPR and Turkish KVKK regulations. Data residency located in Frankfurt, Germany.

Review Terms →
Data Flow Visualization

01. The Philosophy of "Clean Telemetry"

Most analytics platforms harvest everything and ask questions later. We invert that logic. Markeno.pro operates on a principle of Clean Telemetry—we only collect data that directly correlates to app stability, frame rates, and battery impact.

We do not sell your data. We do not store personally identifiable information (PII) longer than necessary to generate a snapshot. Once the analysis is complete, raw logs are purged. The insights, however, remain yours.

Method Note: We aggregate data in blocks of 1,000 unique users to ensure anonymity. No single user profile is ever reconstructable from our reports.

What We Collect

Transparency in three specific categories.

1

Technical Telemetry

  • Frame time & FPS stability
  • Memory footprint (anonymized)
  • Thermal throttling events
2

Session Metadata

  • Session duration (seconds)
  • Input latency metrics
  • OS version & Device Model
3

Contact Info

  • Email (for account recovery)
  • Company Name (for invoicing)
  • Never shared with 3rd parties

Evidence: Processing Constraints

Assumption Users expect real-time benchmarking results.
Constraint Processing heavy telemetry requires queueing. We aim for < 60s latency, but complex SDKs may delay this to 5 mins.
Trigger If latency exceeds 10 minutes, we shift to an email notification system rather than keeping the user waiting on-page.
What Changes Our View A switch to edge computing (WebAssembly) would allow instant processing, but currently impacts browser stability too heavily on mobile.

Pitfall: Misinterpreting "Anonymized"

Warning: Even with IP masking, a combination of Device Model + OS Version + Session Time can theoretically identify a user in very small sample sets (e.g., niche devices). We mitigate this by aggregating sessions into hourly blocks. If your app has fewer than 100 daily active users, we recommend opting out of the "Device Model" category in the dashboard settings.

Detailed Disclosures

Markeno.pro is committed to digital accessibility. This policy is written in plain English. If you need this document in a different format, contact us.

© 2026 Markeno. All rights reserved.