Privacy

1. Responsible and contact

The service is PokerView. The sole channel for privacy and support enquiries is info@pokerview.pro.

2. Data managed by the product

• Account and profile: email, optional name, avatar, preferences and optional public profile.
• Poker activity: sessions, results, stakes, bankroll, rakeback, goals, habits, tilt, focus and imports.
• Communications: contact or feedback messages, response emails and requested subscriptions.
• Security and operations: identifiers, transformed IP for rate limits, errors and technical logs.
• Optional public data: username, bio, avatar, name or nickname and the challenge fields the user decides to publish. The surname and the exact signup date are not published. They are only shown when the corresponding public profile or challenge is enabled.
• Aggregated cover statistics: …together with an aggregate breakdown by mode: Cash, Spins, MTT, Live, and Study. A person with several modes open counts once in the total and once in each corresponding mode.
• Support messages: you can hide your name publicly. If you're signed in, we keep the link to your account private to include the message in your export and delete it with your account; that identifier is not displayed to the public.

3. What are they used for?

The data is used to operate the account, calculate the requested views and statistics, recover in-progress flows, import compatible files, respond to support requests, send requested communications, limit abuse, diagnose incidents, and show exact global historical figures and an aggregated count of recent activity on the homepage as defined above. The product contains no data-sale path or advertising integrations.

Creating an account can generate necessary transactional emails, such as welcome or recovery. It does not automatically enroll your email in a marketing list; that signup only happens from the specific newsletter form.

4. Providers observed in the code

The list describes the repository's integrations; it does not by itself determine their legal fit, effective location or the contractual conditions of each deployment.

5. Diagnostics and consent

Sentry receives errors from the server when the integration is enabled in production. No errors, traces, Web Vitals, or Replay are initialized in the browser until the user chooses “Allow diagnostics”. Replay masks text and blocks media. The choice can be changed on the cookies and storage page.

6. Retention and controls

The account retains data as long as it exists, except for specific deletions. The application offers export and durable account deletion: it deletes avatars through the Storage API, deletes the account and its associated rows, removes the active contact from Resend, and automatically retries any interrupted step. The request delivers a private receipt before enabling the irreversible deletion, so you can save it. If the final response is lost, that receipt allows you to confirm the status without logging in; the application saves only its cryptographic fingerprint. The fingerprint is deleted 30 days after the deletion is completed. Upon completion, the job also deletes the email and user ID it needed during the process. Editorial articles remain as site assets, but are no longer linked to the deleted account.

Uploaded photos are saved in a private space and are delivered without a shared cache: only their owner can see them, unless they publish the profile. When you replace them or choose Gravatar, a durable task deletes previous private copies and tries again if Storage is unavailable.

When you publish a profile, its URL is included in the sitemap and its metadata may appear in search engines or external previews. If you hide it, the username is still reserved for its owner and may still show as unavailable, although the profile data is no longer displayed. External caches may take time to update or remove previous results.

Drafts saved in the browser remain until the flow clears them or the user clears the site data. Emails already sent, technical logs, backup copies and data subject to the provider's obligations are not necessarily deleted instantly from the application; they follow each provider's retention periods and conditions.

To request access, correction, export or deletion, write to info@pokerview.pro. Do not send identity documents by email unless support explains why they are necessary and how to send them properly.