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, banking, rakeback, objectives, habits, tilt, focus and imports.
- Communications: contact or feedback messages, response emails and requested subscriptions.
- Safety and operation: identifiers, transformed IP for frequency limits, errors and technical logs.
- Optional public data: username, bio, avatar, name or nickname and fields of the challenge that the user decides to publish. The surname and exact discharge date are not published. They are only displayed when activating the corresponding profile or public challenge.
- Aggregated cover statistics: when the required sample is available, exact global historical figures for accounts, sessions, and playing and study hours are published, including accounts without a public profile only within those aggregates. A count of distinct users with a playing or study session in the “running” or “paused” state started during the previous 24 hours is also published, together with an aggregate breakdown by format: Cash, Spins, MTT, Live, and Study. A person with several formats open counts once in the total and once in each corresponding format. Starts up to five minutes in the future are tolerated to absorb small clock differences. No identities, personal rows, or per-account figures are published. Deleted accounts, deleted sessions, and profiles with a pending deletion request are excluded. The endpoint is public, requires no credentials, and the homepage may query it again at most every five minutes, so the count reflects people with an open session within a protective window rather than instantaneous web presence.
- 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 email into a marketing list; This registration is only done from the specific newsletter form.
4. Providers observed in the code
| Supplier | Technical flow |
|---|---|
| Supabase | Account, authentication, database, storage and associated functions. |
| Coolify | Hosting, application delivery and technical infrastructure records. |
| Sentry | Server errors in production and, with permission, errors, performance and Replay in the browser. |
| Resend | Transactional emails and, only by explicit subscription, mailing lists. |
| Upstash | Rate limits when Redis is configured; if not, database fallback is used. |
| Gravatar | Optional avatar: only choosing “Use Gravatar” saves and requests a URL derived from a hash of the email. |
The list describes integrations of the repository, it does not alone determine its legal fit, effective location or the contractual conditions of each deployment.
5. Diagnosis 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. Conservation and controls
The account retains data as long as it exists, except for specific deletions. The app offers export and durable account deletion: delete avatars using the Storage API, delete the account and its associated rows, remove the active contact from Resend, and automatically retry any interrupted steps. The application provides a private receipt before enabling 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 your cryptographic fingerprint. The fingerprint is deleted 30 days after the deletion is completed. Upon completion, the job also deletes the email and user ID that it required 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. By hiding it, the alias is still reserved for its owner and may still be listed as unavailable, although the profile data is no longer displayed. External caches may take time to update or retire 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; The terms and conditions of each supplier follow.
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 securely.
Last technical review of the content: July 18, 2026. Legal bases, contracts and external deadlines require validation by the person responsible before production.