Privacy Notice

Last updated: 11 April 2026

App: Tourney Ticker (the “App”)

This Privacy Notice describes how Volodymyr Kosynets (“we,” “us,” or “our”) handles information when you use the App. It is provided for information and transparency; it does not create contractual rights beyond what applicable law provides.



1. Summary

Tourney Ticker helps you run and manage live poker tournaments (structures, blind levels, breaks and other). It is not a real-money gambling service.

To provide sync, reliability, and improvement, we process:

  • Identifiers tied to your app installation and account on our servers (for example, an installation ID and a user ID assigned when the device registers).
  • Tournament data you create or sync (structures, levels, breaks, progress, and related metadata).
  • Product analytics and feature flags through PostHog (EU region) to understand usage and roll out features.
  • Crash and diagnostic data through Firebase Crashlytics.

We do not require your name, email, or phone number to use the core App features as described in this notice.

2. Who we are and how to contact us

Controller / operator:
Volodymyr Kosynets
street Mykhaila Komarova 2 apt 6
Kharkiv, 61047
Ukraine

Privacy / general contact:
Email: apps@vkosinets.com

3. Information we process

We aim to be explicit about categories of information and why they exist.

3.1 Account, device, and session identifiers (our servers)

When the App first registers with our API, we create or associate records that may include:

  • A user identifier on our servers (a pseudonymous account key without a traditional sign-in profile in the current release).
  • An installation identifier generated on your device to distinguish this install from others. We use it to support device-linked access, support, and future multi-device features (for example, syncing tournaments across devices for the same user).
  • Authentication material (for example, a bearer token stored on the device and a token hash on the server).

Purpose (high level): secure API access, associate data with your account, and operate sync and future multi-device scenarios.

3.2 Tournament and event data (our servers)

Depending on how you use the App, we may store tournament-related data such as:

  • Tournament metadata (for example, timing fields, player count, revision counters).
  • Blind level definitions and related configuration.
  • Break records and timestamps as you run an event.
  • Links between your user record and tournaments you create or follow.

3.3 Short-lived technical data (our servers)

To make network requests reliable, we may store short-lived idempotency and replay data (for example, keys and small response payloads) for a limited window (on the order of hours, not years), after which it is removed automatically as part of normal server maintenance.

3.4 Product analytics and feature management (PostHog)

We use PostHog, hosted in the EU for our project, to:

  • Measure how features are used (events and screen views we define in the App).
  • Support feature flags and gradual rollouts of new functionality.
  • Associate analytics with a distinct ID derived from our user ID after registration, and to distinguish installs using the installation ID as needed for analysis and multi-device planning.

PostHog processing is intentional and designed to help us improve the product; it is not used to sell your personal information.

3.5 Crash reporting and diagnostics (Firebase Crashlytics)

We use Google Firebase Crashlytics for crash reporting and related diagnostic logging (for example, crash traces, device/OS class information, and breadcrumbs we emit for debugging).

3.6 Notifications and alarms (on your device)

The App may use notifications and alarms so we can alert you about blind level changes and similar tournament timing events. These features rely on your device’s scheduling and notification systems.

4. Why we use information (purposes)

We use the information above to:

  • Provide core functionality: create, run, update, and sync tournaments and related state.
  • Operate accounts and devices: authenticate requests, prevent abuse, and prepare for multi-device use.
  • Maintain reliability: diagnose crashes and errors, and improve stability.
  • Improve the product: understand usage patterns and ship features responsibly (including feature flags).

We do not sell your personal information and do not use the App to display third-party advertising (see Section 10).

5. How long we keep information

5.2 User and installation identifiers

We retain user identifiers and installation identifiers for as long as they are in active use. If there is no app usage associated with a given identifier for one (1) consecutive year, we delete (or permanently anonymize) those identifiers and related account linkage as part of scheduled maintenance—unless a longer retention is required by law or a shorter period applies because you deleted data through the App (see Section 8).

5.3 Third-party tools (PostHog and Crashlytics)

Retention of data processed by PostHog and Google Firebase Crashlytics depends in part on provider settings and policies. We do not control every retention knob inside those services. For details, see their documentation:

6. Third parties and service providers

We use service providers to host and operate the service and to provide analytics and diagnostics. Depending on configuration, this may include:

Provider / category Role
GoDaddy (or a successor host we may use) Hosting infrastructure for our API and database
PostHog Product analytics, feature flags (EU region for our project)
Google Firebase (Crashlytics) Crash reporting and diagnostics

When we add or replace providers in a material way, we will update this notice or provide an additional summary where appropriate.

7. Security

We use reasonable technical and organizational measures appropriate to the nature of the service. No method of transmission or storage is completely secure; we work to reduce risk proportionate to the data involved.

8. Your choices and deletion

In-app deletion: You may request deletion of your data from within the App using the deletion function we provide. That flow sends the identifiers needed to process the request. We do not require additional identity verification beyond what the App submits for that request.

Depending on implementation, deletion may cover server-held identifiers and associated data tied to your account, subject to residual backups and legal retention requirements.

If you need help or cannot use the App, contact us at apps@vkosinets.com.

9. Children

The App is intended for a general audience of poker players and tournament organizers. It is not directed at children, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us at apps@vkosinets.com and we will take appropriate steps.

10. Advertising

The App does not show third-party advertising and does not use advertising networks for monetization within the App as described in this notice.

11. Changes to this notice

We may update this Privacy Notice from time to time. When we do, we will revise the “Last updated” date at the top and, where appropriate, provide additional notice (for example, in the App or on https://poker.vkosinets.com). Continued use of the App after an update may be subject to the updated notice where permitted by law.


End of Privacy Notice