PESOWIN Privacy Policy: information, sharing and your choices
Read how the published PESOWIN privacy material describes account, identity, payment and technical information. Review the current policy on the active platform before submitting real details. It also identifies retention, contact and security details that need confirmation under the current policy.
Contents: privacy topics
- 1. Information described in the policy
- 2. How information is collected
- 3. Purposes of processing
- 4. Recipients and overseas processing
- 5. Cookies and browser choices
- 6. Security and account precautions
- 7. Requests and privacy choices
- 8. Retention and deletion questions
- 9. Age restrictions and younger users
- 10. Changes to the policy
Before you provide personal data
The published policy links data processing to registration and platform use and should be read with the account terms. Understand why information is requested, who may process it and what choices are available. No blanket no-sharing or no-sale promise is added to the supplied policy. If a material purpose remains unclear, ask before submitting documents.
1 Information described in the policy
The published material describes personal, payment and technical information collected during registration, verification, transactions and service use. The exact information requested can depend on the account process. Review the purpose of each request on the verified platform, and do not submit additional sensitive information through an unsolicited message or an information-page practice form.
Identity and contact information
- Full name and other identifying details provided for the account.
- Date of birth for identity and eligibility checks; this site requires participation aged 21+.
- Telephone or mobile details used in the account and contact process.
- Email details where requested for account communications.
- Residential or mailing address where required by the current process.
Payment and transaction information
- Details needed to identify a personal e-wallet or bank account and process a payment.
- Deposit, withdrawal and other transaction records described in the policy.
- Payment-related account information; ask about the exact data fields if unclear.
Technical and usage information
- IP address and relevant technical connection information.
- Browser type and software diagnostics described in the policy.
- Access date, time and pages visited.
- Language preferences, site preferences and feedback where provided.
Protect sensitive credentials
The supplied evidence does not establish that full card details are never stored or that all financial data has a particular encryption format. Do not disclose a password, withdrawal PIN or one-time code to another person. Use only the secure, verified payment or account process for required information.
2 How information is collected
Published material describes information supplied directly by users, information collected automatically during service use and information received from authorised service providers or payment processors. Ask which process applies to a particular request rather than assuming all collection depends on a single consent checkbox.
| Collection context | Information to expect | Published purpose or question |
|---|---|---|
| Actual registration form | Identity and contact details requested by the platform | Create and administer the account |
| Identity verification | Valid ID, selfie and related verification details | Check identity and account eligibility |
| Payment processing | Payment-account and transaction details | Process deposits and withdrawals |
| Cookies and technical collection | Access, browser and preference information | Support functionality and usage analysis |
| Support contact | The question, relevant account details and references | Respond to an account or service issue |
| Platform use | Relevant activity and service information | Operate and maintain the service |
Understand the requested information
Some account, identity and transaction information is necessary to use a service or complete a withdrawal. Ask about the purpose and consequences before declining a request. The supplied material does not establish that all processing stops immediately when a general consent is withdrawn, or that every field is optional.
3 Purposes described in the policy
The published policy describes processing for account services, identity and security checks, payments, support, communications and compliance obligations. It also discusses optional promotional activities. The current policy and account process should explain which purpose applies; this page does not add an undisclosed profiling system or claim that every use has been independently audited.
- Account operation: Provide and administer access to the platform’s services.
- Payments and support: Process transactions and help resolve account, technical or payment questions.
- Identity and security checks: Verify information and review suspected fraud or other security concerns.
- Compliance purposes: Meet applicable obligations described in the current policy and terms.
- Communications: Send service information and, where applicable, promotional messages.
- Service functionality: Use technical and preference information for operation and maintenance.
- Responsible-gaming research: The published policy mentions anonymised research disclosures; it does not establish a specific behavioural-monitoring feature.
Read optional-use conditions separately
The published policy discusses surveys, promotions and the use of a participant’s name or likeness in connection with accepting rewards. Review any current campaign conditions before participating. Do not infer a blanket marketing-consent rule or a guarantee that information is never shared from a general privacy statement.
4 Recipients and overseas processing
The published policy describes service-provider processing and disclosures for transactions, verification, security and relevant legal requirements. It also states that data may be stored on servers in Germany or other jurisdictions. Understand the recipients and safeguards before sharing information; this page does not certify that every overseas transfer provides equivalent protection.
Recipient and disclosure contexts
- Payment providers: Information needed by electronic payment processors to complete account transactions.
- Verification and service providers: Relevant information for authorised identity checks or service operation described in the policy.
- Competent authorities: Disclosures where required by applicable law, regulation or legal process.
- Fraud and security review: Relevant information shared with financial institutions, processors or other permitted recipients in suspicious-activity cases.
- Other external services: Read the privacy terms of linked services and ask which recipients process data for the particular function.
Questions about safeguards and transfers
The published policy refers to confidentiality and contractual obligations for recipients and discusses cross-border processing. Ask which entities, countries and safeguards apply to the current service if those details affect your decision. A general statement about contractual protection is not an independent certification of each provider’s practices.
5 Cookies and browser choices
The published policy discusses cookies that support functionality, remember preferences and analyse usage. It names session, persistent and analytical cookies. The labels below explain these topics and the need to verify any marketing-specific use; they are not a live cookie inventory or a claim that this page provides a consent-management system.
- Session cookies: The policy describes cookies active during a browsing session and removed when the browser closes.
- Analytical cookies: The policy describes statistical information about usage patterns and performance.
- Persistent cookies: The policy describes cookies retained for a period to remember preferences.
- Marketing-related choices: Check the current policy and settings for any marketing cookies or technologies. No particular vendor list or opt-out control is established here.
Managing browser cookies
You can review browser controls for refusing or deleting cookies. The published policy warns that refusing cookies may limit some functions. Removing cookies can also end a session or clear preferences; check the effect before doing so during an unresolved account task.
6 Security and account precautions
The supplied material includes security claims, but it does not establish a current independent certification or an absolute guarantee against loss, misuse or unauthorised access. Older technical descriptions and conflicting mirror slogans are not presented as verified specifications. Use practical account precautions and ask for current security information if a claim affects your decision.
- Connection protection: Verify the destination and use the actual secure account process before entering sensitive information.
- Additional login checks: Check the active account settings; a specific two-factor feature is not independently established here.
- Access controls: Keep your device locked, use a unique password and sign out on shared devices.
- Audit information: No schedule or named independent security auditor is established in the supplied evidence.
- Fraud review: The published policy allows security checks; it does not establish a real-time detection guarantee.
- Information displayed on screen: Redact unrelated personal details before sharing a screenshot with verified support.
- Storage location: Published material allows Germany or other jurisdictions; do not assume all data stays in the Philippines.
If you suspect a privacy or security incident
Pause account activity, secure your login through the verified process and report the concern through the platform’s current support route. Save relevant references without spreading sensitive information. The supplied material does not establish a 72-hour user-notification promise or a guaranteed incident-resolution time.
7 Privacy requests and choices
The published policy describes requests concerning accuracy, correction or deletion, consent withdrawal, complaints and promotional communications. The current process may require identity checks and assessment of applicable obligations. The request topics below explain what to ask; they do not create additional unconditional rights, formats or response deadlines.
- Ask about information held: Request an explanation of the personal information associated with your account and how to verify its accuracy.
- Request correction: Identify inaccurate information and ask how to provide the required correction evidence securely.
- Request deletion: Ask what can be deleted and whether any records must be retained for relevant obligations.
- Ask about limiting a use: Explain the processing purpose you are concerned about and ask what restriction options are available.
- Ask about receiving a copy: Confirm whether a copy is available and in what format; no JSON or CSV export is promised.
- Raise a concern or complaint: Identify the specific data use, disclosure or request that needs an explanation.
- Consent and marketing choices: Ask how to withdraw relevant consent or stop promotional messages, and what processing may continue for other obligations.
How to make a request
Use the support entry within the verified platform and ask for the current privacy-request procedure. Provide only the information needed to identify the request through verified platform support. Do not send passwords or one-time codes. No 30-working-day response promise or dedicated privacy mailbox is established here.
8 Retention and deletion questions
The supplied material does not establish fixed retention periods for account details, transactions, verification documents, game history or support records. Ask for the current retention criteria and how closure, exclusion or a deletion request affects each category. Do not assume that closing an account removes every record immediately or that an old table supplies a binding storage deadline.
| Information category | Retention period | Question to ask |
|---|---|---|
| Account information | Not established in the supplied material | What is retained after closure, and why? |
| Transaction records | Confirm the current policy | Which payment and compliance obligations apply? |
| Identity documents | Confirm the current policy | Who retains verification copies and for how long? |
| Game-related records | Confirm the current policy | What records exist and what retention criteria apply? |
| Support correspondence | Confirm the current policy | How are case records retained and accessed? |
| Cookie information | Check cookie-specific duration | Which session or persistent periods apply? |
Deletion and remaining obligations
Ask which information can be deleted, what must be kept and how the outcome will be confirmed. No particular deletion technology, irreversible-erasure guarantee or fixed completion time is established by the supplied material. Keep your own permitted receipts where needed before requesting closure or deletion.
9 Age restrictions and younger users
Participation on this site is for eligible adults aged 21+ only. Use accurate age and identity details and follow the current participation restrictions. Do not allow a younger person to register, use an existing session or provide identity information through your account.
- Use accurate date-of-birth and identity details in the actual account process.
- Published guidance calls for valid ID and selfie verification before withdrawals.
- Report suspected underage account use through the verified platform support route.
- Ask how information linked to an ineligible account will be handled under the current policy.
For parents, guardians and account holders
If you believe a younger person has accessed an account or submitted information, secure the device session and contact verified platform support to request an account and data review. Do not share further documents through an unsolicited contact or assume immediate deletion without confirmation.
10 Changes to the privacy policy
The published policy reserves the right to update its terms and describes changes taking effect on publication. Review the current platform version before a new disclosure, payment or optional promotion. This page does not promise a particular notification method for every change or identify its content-review date as the operator’s policy effective date.
- Check any notice actually displayed by the platform; email notification is not guaranteed here.
- Read the effective or revised date on the current policy itself.
- The published policy treats continued use after amendments as acceptance of the revised version.
- If a change is unacceptable, stop the affected use and ask about closure and data-request options.
Content-review record
This page was reviewed against the supplied materials on 28 October 2026 . This is a content-review date. No future policy revision or scheduled review is announced.
Privacy questions you can raise
Use the current policy and verified request process to understand the information associated with your account.
Information and purposes
Ask what personal information is held, how it was obtained and which processing purposes apply. The published policy discusses account, payment, support and technical data.
Correction
Identify the detail that is inaccurate and ask for the secure correction process. Do not create a duplicate account to fix identity information.
Deletion
Ask which information can be deleted and which records may need to remain. No unconditional immediate deletion promise is made here.
Receiving a copy
Ask what information can be supplied and in which format. A downloadable JSON or CSV privacy export is not established in the supplied material.
Processing concerns
Explain the particular use or disclosure you object to and ask what choices and complaint process apply under the current policy.
Consent and communications
Ask how to withdraw relevant consent or stop promotional messages. Confirm which account or transaction processing may continue for other purposes.
Six practical privacy checks
These questions help you assess current information handling without treating promotional security claims as independent certification.
Secure connection and destination
Verify where you are entering information. HTTPS helps protect a connection but does not alone confirm operator identity, licensing or every storage practice.
Account verification options
Check the security settings actually available and protect any codes you receive. No two-factor feature guarantees that an account cannot be accessed improperly.
Security-review information
The policy allows verification and fraud review. Ask what data is required and why; no specific automated detection system is independently verified here.
Overseas storage
The published policy permits storage in Germany or other jurisdictions. Ask which countries and safeguards apply rather than assuming domestic storage.
Independent assurance
Request verifiable audit or certification details if a technical claim matters to you. No auditor, audit frequency or universal compliance certificate is established here.
Recipients and choices
Understand payment providers, verification recipients, relevant disclosures and the privacy-request route. A general protection statement does not answer every recipient or retention question.
Review privacy before choosing to continue
Read the current policy, clarify any material data-use question and submit real information only through the verified account process. Participation is for adults aged 21+ and involves financial risk; no absolute privacy or security guarantee is made by this page.
