Reader account information
Registration records a username, email address, password hash and consent information in WordPress. A password hash is not the original plain-text password. Account information supports sign-in and administration. Do not use your casino password for a reader account, and do not publish private account details in correspondence about an article.
Cookies and browser preferences
WordPress uses cookies for authenticated sessions. The site stores theme preferences and comparison selections in browser storage. Clearing this site's browser data can remove those preferences and require you to sign in again. Browser-only comparison selections are not a promise of cross-device account synchronisation.
Optional phone numbers and Telegram preferences
If you add a phone number, the account stores it with verification and offer-preference information. The configured verification design uses Telegram: when you choose to share your own contact with the site's bot, the number and Telegram identifier can be matched to the pending request. This confirms the association with that Telegram account, not current SIM ownership, legal identity or age.
Offer eligibility requires a verified number and a separate opt-in; adding a number alone does not subscribe you. You can change the preference in your account or use the bot's stop instruction when available. Clearing and saving the number removes its account link and verification data. The preference and its timestamp may remain as a record of your choice. Phone details are not included in public article schema.
Article audio and AI overviews
Listen uses the browser's speech service, whose processing depends on the browser and operating system. AI overviews use article content and recorded research context. If the configured API is used, that context is sent to OpenAI; the overview request does not intentionally include reader passwords or account records. A saved overview is tied to the content version. If none is available for the current version, the interface reports that rather than substituting a human-written summary labelled as AI.
External sites and infrastructure
Following a source, support or partner link opens a separately operated service with its own privacy practices. The web host and email service may process technical or correspondence data needed to deliver the site. Their retention and settings must be assessed for the deployed environment; this page does not promise a fixed log-retention period that has not been configured.
Access, correction and deletion requests
Contact wdev@baazidaily.com from your reader-account address and describe the request. WordPress provides personal-data export and erasure tools, including the site's phone-preference integration. We may need to establish that a request relates to your account before acting. Do not attach identity documents or credentials to an initial message.
Backups can retain an earlier state separately from the active account database. Deletion from the live site is not a claim of instant removal from every backup. Contact information and terms of use provide the related service context.
Encrypted reader accounts and personalized messages
When you create a reader account, we collect your chosen username, email and country of residence. Your phone number is optional. We suggest a country in the signup form using your IP address through Country.is, a third-party IP-to-country service. Your browser connects to that service over HTTPS without sending signup form values, account identifiers, cookies or the site referrer. We use the returned country code, do not store the returned IP, and keep the selector editable. You can correct the suggestion, including when traveling or using a VPN. We store the country you submit as your declared residence. It helps us choose relevant guidance and in-app messages; it does not verify your identity, age or legal access to gambling.
Reader contact details, country, message choices, consent records, verification information and private account notes are encrypted in our database. We keep passwords as secure password hashes. WordPress uses an opaque internal account identifier in place of your supplied email and username. You can view your own contact details in your signed-in Profile; staff contact tables remain masked, and private reader profiles are not published in the public user API.
Authorized server processes decrypt information when needed to provide your account, deliver a password-recovery email or select an appropriate in-app update. Encryption does not make a compromised server or an improperly shared backup safe. We keep the encryption key separate from the database and restrict access to reader management.
Personalized updates and offers in the site inbox require your optional message permission. Popups require a separate permission, include a close control and are limited in frequency. Essential account or safety information may remain in the inbox without marketing consent. You can change your country, preferred topics and permissions in your reader account at any time. Telegram offer preferences remain separate.
We store your latest preferences and consent time, inbox read/dismissal state and limited popup history to respect those choices. We retain account records while your account is active, subject to deletion requests and any applicable retention obligations. You can contact us to request access, correction or account erasure. Personal-data exports are private documents and may contain your readable account information.
Email newsletter
The newsletter form collects only your email address. Selecting Subscribe requests Gaming4U guides and updates by email. We send a confirmation link and activate the subscription only after you confirm it. Creating a reader account or accepting our terms does not subscribe you to the newsletter.
Newsletter emails, subscription status, consent records and confirmation information are encrypted in the database. Staff see masked email addresses. We use a keyed lookup value to find an existing subscription without keeping a readable email index. We decrypt the address only when needed for authorized email delivery. Our hosting mail service processes the address to deliver confirmation emails and newsletters.
Confirmation links expire after 48 hours and require an explicit confirmation button, rather than automatically subscribing someone when a link is previewed. Every newsletter must include an unsubscribe link. Unsubscribing removes your newsletter subscription record. You can also request a personal-data export or erasure. We remove unconfirmed requests after 30 days.
Reader profiles and contributions
Your original login, email and optional phone remain private. Public comments and articles use your approved display name and chosen visibility setting. You can show it, mask its middle with three stars or appear as Anonymous. Anonymous mode also hides your public profile photo. These choices apply to your existing public contributions and comments.
Display names, photos, private author follows and unpublished article submissions are encrypted in the reader data store. Uploaded photos are re-encoded as small JPEG images to remove file metadata, remain private during review and become public only after approval when your identity setting permits it. Photos can be removed in your account. Never upload another person’s image without permission.
Comments are held in WordPress’s moderation queue and screened for common spam, promotional wording, excessive links and contact details. Accepted comments and published reader articles are public content, so do not include private or sensitive information. Moderators can approve, decline or request changes. Unpublished article text and moderator feedback stay encrypted until the relevant article is approved for publication.
Following an author records a private reading preference. It does not send them your email address or automatically subscribe you to marketing. Reader community records are included in personal-data export. Full reader-account erasure removes the account’s photo and follows, along with its comments and reader articles. See the contribution guidelines for publication rules.
Reader article activity
Reader contributions show aggregate reading visits, approved comments and useful feedback. A reading visit counts after the article is visible for at least ten seconds; repeat activity from the same browsing session is deduplicated. This measures visits, not verified completion of the article. Authors and administrators are excluded from the reading counter.
A temporary random browser-session identifier helps prevent repeat counts and is not joined to contact details. Useful feedback requires a reader account and can be removed; your selections and contributor follows are encrypted in your private account. Aggregate article totals are public. Activity begins when this feature is enabled; we do not invent historical counts.
Contributor profiles
Your approved display name, biography and profile photo can appear with your published reader contributions. Anonymous mode hides your public profile, photo and biography. You can edit your profile and visibility in your account.
Gender and birthday are optional, stored in your encrypted private account record and never displayed on public profiles or in public structured data. Profile names, biographies and photos are reviewed before publication.
Email and phone verification codes
Your signed-in Profile shows your private email and optional phone number. Email and phone have separate verification codes. Email codes are delivered through our transactional mail service. Phone codes use our connected Telegram bot: first share your own matching Telegram contact, then enter the code delivered to that account. This confirms access to the Telegram account associated with the number; it does not establish current SIM possession, identity or age. Sharing a contact alone does not complete phone verification.
Codes expire after ten minutes, can be used only once and are limited to five incorrect attempts. Resends are restricted. We store an encrypted challenge containing a keyed digest rather than a readable code. Changing a contact invalidates its verification. Adding a phone number or confirming a code does not subscribe you to marketing; offer permissions remain separate.