Current operational statement

What is stored.
What is not.

LeakHunter processes voluntarily exported histories from completed GG and PokerOK sessions. This page describes the current production behavior—not a future enterprise promise or a substitute for a pilot-specific agreement.

VERIFIED AGAINST PRODUCTION CODE · 22 AUG 2026

A hand history has one short path.

  1. Player selects `.txt` files

    Only voluntarily exported, completed-session histories are supported.

  2. Upload travels over HTTPS

    Each file is limited to 10 MB in the application layer.

  3. Temporary analysis

    The server parses the file and creates the report response.

  4. Temporary file is deleted

    The raw upload is removed in a cleanup block even when analysis fails.

Raw histories

Raw hand-history uploads are written to a temporary server file for parsing and are not inserted into the application database. The temporary path is deleted after the request. The report is returned to the browser.

  • DatabaseNo raw hand-history table and no stored report table.
  • Derived jobsIn-memory analysis-job results expire after 24 hours by default.
  • Player profileReport history and weekly progress are kept in that browser's local storage and can be cleared from the Profile view.

Product telemetry

The application records five player funnel stages—page view, upload selected, successful analysis, paywall opened and checkout started—and three partner-page stages: page view, PDF opened and form submitted. Each row contains the event, campaign source, an opaque browser session identifier and a timestamp.

  • Not in event rowsNo email, hand history, report, poker identity or payment credential.
  • RetentionApplication event rows expire after 90 days by default.
  • Infrastructure logsReverse-proxy logs can contain IP address and request metadata for security and operations; current Nginx files rotate daily and retain 14 rotations.

Orders and enquiries

An order record contains provider, status, amount, attribution source, timestamps and an optional email used for delivery or renewal. Card and SBP details are handled by the configured payment provider, not by LeakHunter. A partner enquiry stores the contact details and message that the sender submits.

  • Never sendPoker-room passwords, payment credentials, seed phrases, private keys or player datasets through the partner form.
  • DeletionDeletion and retention of order or partner records are handled through the written business contact; there is no self-service enterprise console today.

Product boundary

LeakHunter is post-session study software. It does not connect to a live table, request a poker-room login or provide real-time assistance. A partner must have lawful permission to invite its cohort, and every player supplies their own export voluntarily.

  • No outcome claimNo guaranteed winnings, ROI, retention lift or solver-perfect coverage.
  • No silent collectionNo scraping of player accounts or ingestion of datasets obtained without authorization.

A paid pilot gets a written data boundary.

Before payment, the partner and LeakHunter name the cohort, invitation authority, permitted inputs, primary metric, access owner, deletion route, incident contact and any retention requirement that differs from the current defaults. Data residency, DPA, SLA or integration commitments exist only when they are written into the approved scope.