Our Data Infrastructure: A Transparency Guide
Markeno.pro operates in a sector defined by precision. The tools we use to measure app performance, stability, and market position rely on technical data—some of which is collected through cookies. This document outlines our methodology.
“We treat every data point as an evidence packet. The origin of that data matters as much as the insight it unlocks.”
The Role of Cookies in Performance Analysis
Cookies are essential for contextualizing performance data. Without them, we cannot distinguish between a returning user testing a new feature and a new user experiencing initial load. This distinction is critical for accurate benchmarking.
1. Session Integrity & State Management
A small, temporary session cookie maintains your analysis state as you navigate between performance metrics, comparative panels, and our methodology notes. This ensures you don’t lose your work context when viewing a deep-dive audit.
- Persists for the duration of your visit only.
- Stores no personal information, only a unique session identifier.
- Deleted automatically upon browser close.
2. Diagnostic Data Aggregation
We employ a single, persistent cookie to anonymously collect aggregated diagnostic data—such as feature usage patterns and load-time variances across different device profiles. This data is crucial for identifying market-wide trends versus app-specific anomalies.
Questions a Due Diligence Team Asks
When evaluating a portfolio of gaming apps, understanding data provenance is key. These are the core inquiries from our partner investors.
How do you isolate organic growth from paid user acquisition impact?
We use a persistent, anonymous cookie to track cohort behavior over 30-day windows. This allows us to correlate specific ad spend dates with retention curves, separating lasting value from one-time spikes.
What data prevents us from comparing apples to oranges across different genres?
Our diagnostic cookies help normalize performance metrics against genre benchmarks. A puzzle game’s session time is weighted differently than an RPG’s; cookies maintain context for these critical comparisons.
How do we verify the stability score isn't inflated by selective crash reporting?
We cross-reference our session data with publicly available crash analytics (where accessible). Discrepancies >15% flag potential reporting gaps, prompting a deeper technical audit of the app’s telemetry setup.
What’s the trade-off between data granularity and user privacy?
Our model aggregates data into cohorts of 100+ users. We cannot and do not track individual behaviors. This is a trade-off: we lose fine-grained user paths but gain statistically robust, privacy-compliant trends.
How do cookies affect the reliability of cross-platform benchmarking?
We deploy device-type cookies to segment data by platform (iOS, Android). This prevents a high-performance flagship device from skewing the average load time metric for a mid-range portfolio target.
Is our monetization efficiency data tied to long-term user value or short-term spikes?
The 90-day persistence of our analysis cookies is critical here. It allows us to model Lifetime Value (LTV) and distinguish between a one-time high-value purchase and sustainable subscription revenue.
Methodology: From Raw Signals to Actionable Insight
Our approach is designed to produce verifiable, comparable performance scores. Cookies form one layer in a multi-source data acquisition strategy. The following flow outlines how anonymous session data integrates with our core analysis engine.
-
1
Anonymous Session Initiation
A temporary cookie is set upon first visit, creating a unique but non-identifiable session for the duration of your analysis work.
-
2
Aggregated Diagnostic Logging
We log feature clicks and page transitions in aggregate. This data is never linked to the session cookie after the initial request is processed.
-
3
Cohort-Based Analysis
Data is bucketed into cohorts of 100+ users. This is the smallest unit we analyze, ensuring individual privacy.
-
4
Benchmarking & Scoring
Aggregated cohorts are compared against our internal benchmarks to generate the performance scores you see on Markeno.pro.
-
Sample Size Variance
Cohorts smaller than 100 are marked “low confidence” in our internal dashboards and excluded from public scores.
-
Data Freshness
Public reports are generated weekly. The underlying cookie-based session data is processed and anonymized within 24 hours.
-
Third-Party Context
Our analysis does not ingest data from third-party trackers (e.g., social media pixels). All data originates from direct user interaction with the app.
Your Control & Technical Rights
Transparency is a principle, but control is an action. You have full authority over the data your browser shares with our infrastructure. Below are the technical methods to exercise those rights.
Browser-Level Controls
Most modern browsers (Chrome, Firefox, Safari, Edge) have built-in settings to block or delete cookies. Blocking our diagnostic cookie will limit your ability to save analysis state but will not prevent you from viewing performance reports.
Our Global Opt-Out
By engaging with our Cookie Consent banner (injected globally), you can opt out of the persistence of our analytics cookie. A session-only cookie will remain for operational stability.
For questions regarding data practices or to request deletion of your session data:
Data Protection Officer Markeno İstiklal Caddesi No: 123, Beyoğlu, İstanbul, Türkiye info@markeno.proResponse time: Within 30 days of receipt.
Need the full technical audit?
Our Cookie Policy is a section of our broader commitment to data integrity. The full transparency report is available upon request for enterprise partners.