Free Bonus 100 Privacy Policy: Personal Data, Choices and Rights
Free Bonus 100 Privacy Policy: Personal Data, Choices and Rights
Before sharing personal information through Free Bonus 100 or a linked service, identify the organisation receiving it, the purpose, relevant recipients and retention information. This page explains privacy checks for Philippine users. Specific processing arrangements require the actual service’s notice; this guide does not certify compliance or promise unverified security controls.
Understand the notice for the service you use
Browsing Free Bonus 100, following an offer and opening an operator account may involve different organisations. Read the privacy notice of the organisation actually requesting your information, not just an article on the page where you started. Read the Philippine Data Privacy Act.
Republic Act No. 10173, the Philippine Data Privacy Act of 2012, provides the national framework for processing personal information. Its principles include transparency, legitimate purpose and proportionality. Referring to the law does not independently prove compliance.
This is a privacy-information guide. A complete service-specific notice needs confirmed controller identity, contact details, data flows, retention criteria and implemented safeguards. Those facts have not been supplied here; no DPO email, no-selling pledge or particular storage arrangement is invented.
On this page
- 1 Information categories to check
- 2 Where information requests can arise
- 3 Purposes and processing explanations
- 4 Sharing, recipients and linked services
- 5 Safeguards, account access and incident concerns
- 6 Cookies, analytics and preferences
- 7 Data-subject rights and requests
- 8 Retention and deletion questions
- 9 Age restrictions and accidental disclosure
- 10 Notice versions and privacy questions
1. Information categories to check
The categories below are a checklist for reading a service’s notice. They are not a confirmed inventory of information collected or stored by Free Bonus 100. Check the particular request and destination before providing details.
Details you may submit
A registration, payment or support process may request information directly. Establish which fields are required, why they are needed and which organisation receives them.
- Name or account identifier requested by a form.
- Contact details such as a phone number or email.
- Age or identity information where required.
- Documents requested through a verified process.
- Payment references relevant to a transaction.
- Support messages and attachments you choose to send.
- Account preferences supplied to the service.
Technical information to ask about
Browsing can involve technical information. Read the actual notice and available controls; do not assume that an IP address is anonymous, that browsing creates an account or that all linked sites share a database.
- IP address and device information described in the notice.
- Browser and operating-system details described in the notice.
- Page visits or interactions, where measured.
- Session information, where used.
- Cookie identifiers, where used.
- Referral or offer-link information, where recorded.
- Any profiling or automated processing disclosed by the service.
| Category | What to establish | Do not assume |
|---|---|---|
| Contact details | Purpose, required fields and recipient. | A shared account database. |
| ID documents | Verified request and submission channel. | Offline storage or instant deletion. |
| Payment references | Relevant process and recipient. | Zero storage or wallet endorsement. |
| Device or IP data | Actual purpose and notice explanation. | Automatic anonymity. |
| Cookies or referrals | Providers, uses and controls. | No tracking at all. |
2. Where information requests can arise
Forms at a verified destination
Use the destination’s live form and notice. A Free Bonus 100 offer link does not establish that the destination shares this site’s controller, account system or privacy contact.
Browsing and link activity
Check the notice for explanations of cookies, analytics and referral handling. This guide does not confirm which trackers operate on Free Bonus 100 or a linked service.
Support and privacy requests
A support exchange may contain identifiers or transaction details. Use a verified channel and keep unnecessary documents, passwords, OTPs and wallet credentials out of messages.
Check purpose before disclosure
Read the data requested, intended purpose, stated basis, recipient information and retention explanation. A privacy notice and a consent choice serve different functions; read any actual choice before selecting it. Read the NPC’s privacy-notice guidance.
If a request seems excessive or the recipient cannot be identified, pause and ask through an independently verified contact route. Do not send extra documents merely because an unverified chat contact asks.
3. Purposes and processing explanations
Match each data category with the actual purpose and stated basis in the relevant notice. The lists below are questions to check, not assertions that Free Bonus 100 carries out these activities.
Account and service processes
- Which details are needed to create an account?
- Which information is used for contact verification?
- What is required for age or identity checks?
- Which preferences are stored and why?
- Which notices are necessary for the service?
Security-related processing
- What information is used to investigate suspicious activity?
- Who can access relevant security records?
- Are account restrictions or decisions automated?
- What profiling, if any, is described?
- Which legal obligations are identified as relevant?
Analytics and service improvement
- What usage measurements are collected?
- Are identifiable details used in analytics?
- Which providers receive analytics information?
- How can available tracking preferences be changed?
Messages and marketing
- Which messages concern an account or transaction?
- Which communications are promotional?
- How can available marketing choices be changed?
- Where can an unwanted-message concern be raised?
4. Sharing, recipients and linked services
Read the recipient explanation
Look for the recipients or recipient categories relevant to the processing. Ask about the purpose and handling arrangements if sharing is unclear. No general zero-disclosure guarantee is established by this guide.
Separate third-party services
When a link opens another destination, check that service’s identity and notice. An operator, a payment provider and an article publisher may have separate roles and contact routes.
- Identify the organisation responsible for the request.
- Read any described service-provider involvement.
- Check the purpose of payment-related disclosures.
Assess a data-selling claim
A no-selling statement requires verified information about the actual service. A familiar logo, a padlock or a confidentiality claim does not establish what is disclosed, transferred or used for marketing.
- Read any identified legal disclosure circumstances.
- Ask about recipients outside the Philippines where relevant.
- Use the actual destination’s privacy-request route.
- Do not assume shared branding means shared privacy controls.
5. Safeguards, account access and incident concerns
HTTPS helps protect a connection to its destination. It does not establish the operator’s identity or guarantee that information cannot be exposed. Verify the address as well as the request.
Connection security has limits
Read what the actual service says about access controls and document handling. This guide does not confirm encryption at rest, tokenisation, offline ID servers or zero credential storage.
Handling sensitive information
A safeguard claim should describe the relevant arrangement and scope. A security-product logo or an unexplained certification is not evidence that every record is protected in the same way.
Verification codes and access controls
Use the security options actually available in the verified account process. Do not assume Free Bonus 100 provides 2FA, biometric access or a particular recovery feature. Keep passwords, OTPs and wallet MPINs private.
If you suspect an incident
Record the suspicious request, affected service and relevant time without publishing sensitive details. Use the verified organisation’s support or privacy route and your payment provider’s official channel where appropriate.
Ask the relevant organisation about its incident process and any applicable notification obligations. This guide does not promise a response deadline, automatic compensation or an independently verified security audit.
6. Cookies, analytics and preferences
What a cookie does
Cookies are small pieces of information stored by a browser for a website. Their purpose and duration depend on the particular cookie and service. Read the notice rather than assuming all cookies are required or harmless.
Session and preference uses
A service may use cookies for sessions or preferences. Check which uses apply and what happens if you restrict them. This guide does not confirm a Free Bonus 100 cookie inventory.
- Check the session-related purpose where stated.
- Check any preference-related purpose.
- Read cookie duration or expiry information.
Analytics and referral uses
Analytics or referral tools may measure visits or offer-link activity. Read the actual provider and purpose information; this guide does not state that such tracking is absent or anonymous.
- Identify analytics or referral providers where stated.
- Check the scope of any available opt-out choice.
- Read what changing a preference actually affects.
Read the controls actually available
Use available site controls and browser settings where appropriate. Restricting or clearing cookies may affect sessions or preferences and does not necessarily remove information already retained by a service.
7. Data-subject rights and requests
The National Privacy Commission describes data-subject rights under Philippine law. Their application depends on the circumstances and relevant legal conditions. Read the NPC’s data-subject rights guide.
Access
You may seek confirmation and information about relevant processing through the responsible organisation’s request process.
Rectification
Ask to correct inaccurate personal information and identify the specific correction sought.
Erasure or blocking
Erasure or blocking may apply in relevant circumstances. Account closure does not automatically erase every record.
Information and complaints
Ask for information about processing, and consult current NPC complaint instructions for an unresolved concern.
Data portability
Portability applies subject to the relevant conditions; it is not an unconditional right to every internal record.
Objection
An objection can concern certain processing, including marketing where applicable. Check the relevant process and basis.
Use a verified request route
Identify the organisation handling the information and state the account or processing activity concerned. Keep a request reference and follow an appropriate identity-check process.
Ask for an explanation if the request is limited or refused. No fixed Free Bonus 100 response time, deletion guarantee or compensation promise is established here.
8. Retention and deletion questions
Check the period or criteria by record type
The relevant notice should explain retention information. Ask about the period or criteria, purpose and any continuing reason for keeping records after closure. This guide does not establish fixed one-, two-, three- or five-year Free Bonus 100 retention schedules.
| Record category | Ask about | After closure |
|---|---|---|
| Account details | Period or retention criteria. | Check what remains and why. |
| Identity documents | Handling and retention explanation. | Do not assume immediate deletion. |
| Transaction records | Purpose and applicable obligations. | Ask about continued retention. |
| Support correspondence | Purpose and retention criteria. | Keep your own request reference. |
| Technical logs | Relevant purpose and duration. | Do not assume anonymity. |
| Cookies | Expiry and preference controls. | Clearing cookies does not erase all server records. |
9. Age restrictions and accidental disclosure
Gaming eligibility and account access
PAGCOR guidance prohibits under-21 players and identifies additional restricted or excluded categories. Being 21 or older does not override every access restriction. Do not use another person’s identity to bypass a rule. Read current PAGCOR eligibility guidance.
- Read the current age and access rules.
- Do not use borrowed account or identity details.
- Keep account credentials away from children.
- Use the relevant verified route for an accidental submission.
Keep devices and sensitive information protected
If a child’s information was accidentally submitted to a service, contact the relevant verified organisation with a clear description of the issue. This guide does not promise that no such data exists or that every record is deleted immediately.
- Keep sensitive details out of public posts.
- Record the request reference and response.
- Ask what information is held and how it is handled.
- Check available account or exclusion controls where relevant.
10. Notice versions and privacy questions
Keep the notice relevant to your activity
A service’s notice may change. Keep the version relevant to a submission or offer, including the destination and any stated effective information. This article does not invent automatic email notification or treat continued browsing as consent to every processing activity. Find the NPC’s complaint guidance.
- Save the relevant notice and destination.
- Check which version applies to the processing concerned.
- Read the scope of any actual consent or preference choice.
- Ask for clarification when a purpose or recipient is unclear.
Identify the right contact before sending information
Use the independently verified privacy contact of the organisation responsible for the information. A copied chat profile or affiliate contact is not sufficient proof.
State the issue, relevant account or activity and requested outcome. Do not send passwords, OTPs, wallet MPINs or unnecessary ID images with the initial question.
For an unresolved privacy concern, consult current National Privacy Commission complaint guidance and retain the relevant correspondence. No refund, compensation or specific outcome is guaranteed.