TapTap Privacy Policy

TapTap "the Extension" is developed and operated & maintained by Batman Tech.

TapTap is a token-based browser extension that monitors a specific supported website, communicates with Batman Tech's backend service, and uses account and token information to determine whether its notification functionality is authorized.

1. Information We Collect and Process

TapTap processes information that is necessary to provide its account, device registration, token, payment, website-monitoring, notification, security, and support functionality.

1.1 Email Address and Account Identifier

When you connect TapTap to an account, you provide an email address.

TapTap may process:

• Email address.
• Account/device identifier.
• Account registration status.
• Account activity status.
• License or service status.

How it is collected: The email address is entered by the user into the TapTap extension and sent to the TapTap backend when the user registers or synchronizes the extension.

How it is used: The email address is used to identify the user's TapTap account, associate token balances with the account, authorize service functionality, and provide support.

Where it is stored: Account information may be stored on Batman Tech's backend infrastructure and database services.

2. Device and Installation Information

TapTap generates and processes an identifier associated with an extension installation and account.

This information may include:

• Device or installation identifier.
• Account identifier.
• Registration timestamp.
• Last-seen or heartbeat information.
• Activation status.
• Service status.

This information is used to identify an installation, maintain service availability, associate token usage with the correct account, prevent unauthorized or duplicate token use, and maintain the reliability and security of the service.

TapTap does not intentionally collect a user's precise physical location.

3. Token and Service Information

TapTap processes token-related information required to provide its token-based service.

This may include:

• Current token balance.
• Token consumption.
• Token consumption records.
• Transaction identifiers used for token authorization.
• License or activation status.
• Service activity status.

When TapTap detects a supported transaction on the monitored website, it sends the relevant transaction identifier and account identifier to the TapTap backend.

The backend determines whether the transaction is authorized and whether a token may be consumed.

TapTap's notification/alarm functionality is activated only after the server authorizes the relevant transaction.

Token information is used to:

• Determine whether the user has available tokens.
• Authorize service usage.
• Record token consumption.
• Prevent duplicate token consumption.
• Maintain account balances.
• Provide TapTap monitoring and notification services.

4. Website Monitoring

TapTap is designed to operate on the supported website:

https://www.gamemania.co.ke/

The Extension's website-monitoring functionality operates only on the supported website for which TapTap is designed.

TapTap may inspect relevant webpage elements necessary to identify supported transaction information, including information such as:

• Transaction or order identifier.
• Transaction time.
• Other webpage information required by TapTap's monitoring rules.

TapTap uses this information to determine whether a supported transaction has occurred and to request authorization from the TapTap backend.

TapTap does not intentionally collect general browsing history or monitor unrelated websites.

TapTap does not intentionally collect unrelated webpage content.

The transaction identifier generated by the Extension is used for token authorization and duplicate-transaction prevention.

5. Information Stored Locally by the Extension

TapTap uses Chrome's extension storage facilities to store information necessary for the Extension to operate.

This may include:

• Account/email identifier.
• Installation identifier.
• Activation or service status.
• Last-used payment phone number.
• Auto-refresh settings.
• Monitoring settings.
• Extension preferences.
• Previously processed transaction identifiers used to prevent duplicate processing.

Local information is stored using Chrome's extension storage environment on the user's device.

Local storage allows TapTap to maintain user preferences and prevent the same transaction from being processed repeatedly.

Users can remove locally stored TapTap information by uninstalling the Extension or clearing the Extension's stored data through Chrome.

6. Payment Information

TapTap provides token purchases through Safaricom M-Pesa payment functionality.

When a user initiates a token purchase, TapTap may process:

• Mobile phone number provided for the M-Pesa payment.
• Requested token quantity.
• Payment amount.
• Payment transaction reference.
• M-Pesa checkout request identifier.
• Payment status.
• Payment timestamp or transaction information.
• TapTap account/device identifier associated with the payment.

The mobile phone number is used to initiate the requested M-Pesa payment.

Payment information is used to:

• Initiate payment requests.
• Confirm successful payments.
• Associate successful payments with the correct TapTap account.
• Credit the appropriate token balance.
• Maintain transaction records.
• Detect failed or cancelled payments.
• Resolve payment-related problems.

M-Pesa PIN

TapTap does not collect, receive, or store the user's M-Pesa PIN.

The M-Pesa PIN is entered directly by the user through Safaricom's payment interface and is not provided to TapTap.

TapTap also does not intentionally collect bank passwords, card PINs, or other banking authentication credentials.

7. Server Communication

TapTap communicates with Batman Tech's backend using HTTPS.

The backend provides the central service for:

• Account/device registration.
• Account identification.
• Token balance management.
• Token authorization.
• Token consumption.
• Transaction tracking.
• Payment initiation.
• Payment confirmation.
• Monitoring-rule delivery.
• Service status.
• Security and abuse prevention.

Information transmitted between the Extension and backend may include:

• Account/email identifier.
• Device or installation identifier.
• Transaction identifiers.
• Token-related information.
• Payment information required for payment processing.
• Service and status information.

TapTap uses HTTPS to protect information while it is transmitted between the Extension and the backend.

The Extension does not download or execute remote JavaScript or other executable code as part of its normal operation.

8. How We Use Information

Batman Tech uses information processed by TapTap for:

1. Registering and identifying TapTap accounts.
2. Associating extension installations with accounts.
3. Maintaining token balances.
4. Authorizing token usage.
5. Recording token consumption.
6. Detecting supported transactions.
7. Providing monitoring and notification functionality.
8. Initiating and confirming M-Pesa payments.
9. Crediting successful token purchases.
10. Preventing duplicate transactions and token consumption.
11. Preventing unauthorized use and abuse.
12. Maintaining service security.
13. Monitoring service availability and reliability.
14. Troubleshooting technical problems.
15. Providing customer support.
16. Maintaining and improving the TapTap service.

Batman Tech does not use collected information for unrelated advertising or behavioral advertising.

9. Third-Party Services and Data Sharing

Batman Tech does not sell, rent, or trade users' personal information.

However, TapTap relies on specific third-party services to operate. Information may therefore be processed by the following service providers.

9.1 Render

TapTap's backend application is hosted using Render.

Render provides cloud hosting and infrastructure for the TapTap backend.

Information transmitted by the Extension to the TapTap backend is processed by the hosted backend infrastructure in order to provide TapTap's functionality.

This may include:

• Account/device identifiers.
• Token information.
• Transaction information.
• Payment-related information.
• Technical request information necessary to operate the backend.

Render processes information as an infrastructure and hosting provider for Batman Tech.

9.2 Supabase

TapTap uses Supabase as part of its backend database infrastructure.

TapTap's backend uses a PostgreSQL database hosted through Supabase to store service information.

Information stored in the database may include:

• Account/device identifiers.
• Token balances.
• Token consumption records.
• Payment transaction records.
• Payment status.
• Checkout request identifiers.
• Service activity information.
• Other records necessary to operate and secure TapTap.

Supabase processes and stores this information as a database and infrastructure provider for Batman Tech.

9.3 Safaricom / M-Pesa

TapTap uses Safaricom's M-Pesa payment services, including the M-Pesa Daraja API, to initiate and confirm token purchases.

When a user initiates an M-Pesa purchase, relevant payment information may be transmitted to Safaricom as necessary to process the transaction.

This may include:

• Mobile phone number.
• Payment amount.
• Payment request information.
• Transaction or checkout identifiers.

Safaricom processes payment information under its own terms and privacy practices.

TapTap does not receive or store the user's M-Pesa PIN.

9.4 WhatsApp Support

TapTap provides a customer-support option that can open WhatsApp to contact Batman Tech.

When the user chooses this option, TapTap may prepare a support message containing the user's TapTap account/device identifier.

The user controls whether the WhatsApp message is sent.

If the user sends the message, the information is transmitted through WhatsApp/Meta's services and is subject to their applicable privacy policies and terms.

TapTap does not automatically send a WhatsApp message without the user's action.

9.5 Legal and Security Disclosures

Batman Tech may disclose information when reasonably necessary to:

• Comply with applicable law.
• Respond to valid legal requests.
• Protect the security of TapTap.
• Investigate fraud or abuse.
• Prevent unauthorized access.
• Protect the rights, property, or safety of Batman Tech, users, or others.

Batman Tech does not share TapTap user information with advertisers for targeted advertising.

10. Data Storage

TapTap uses both local browser storage and server-side storage.

Local Storage

Certain settings and identifiers are stored locally within Chrome's extension storage on the user's device.

Server-Side Storage

Account, token, transaction, and service information required to operate TapTap is processed by Batman Tech's backend and stored in its database infrastructure.

The backend application is hosted on Render and the database infrastructure is provided through Supabase.

11. Data Retention

Batman Tech retains information for only as long as reasonably necessary for the purposes described in this Privacy Policy.

Account, device, token, and service records may be retained while an account is active or while they are necessary to provide TapTap.

Payment and transaction records may be retained for as long as reasonably necessary for:

• Payment verification.
• Accounting and transaction records.
• Dispute resolution.
• Fraud prevention.
• Security.
• Legal or operational requirements.

Technical and security information may be retained for as long as reasonably necessary to maintain the security and reliability of TapTap.

Local Extension information remains on the user's device until the user removes it, uninstalls TapTap, or clears the Extension's stored data.

12. Data Security

Batman Tech uses reasonable technical and organizational measures designed to protect information against unauthorized access, alteration, disclosure, or destruction.

TapTap uses HTTPS for communication between the Extension and its backend.

Backend access and administrative functions are protected using authentication and access-control mechanisms.

However, no electronic transmission or storage system can be guaranteed to be completely secure.

Users are responsible for maintaining the security of their own devices, accounts, and authentication information.

13. Information We Do Not Intentionally Collect

TapTap does not intentionally collect or store:

• M-Pesa PINs.
• Bank passwords.
• Banking authentication credentials.
• Card PINs.
• Personal files stored on the user's computer.
• Precise physical location information.
• General browsing history unrelated to TapTap.
• Private messages unrelated to TapTap.
• Unrelated website content.
• Information from unrelated websites.

TapTap's website-monitoring functionality is limited to the supported website for which the Extension is designed.

14. Your Choices and Data Requests

Users may:

• Stop using TapTap at any time.
• Uninstall the TapTap Extension.
• Clear locally stored Extension data.
• Stop using TapTap payment functionality.
• Contact Batman Tech regarding their account or personal information.
• Request information about personal data associated with their TapTap account.
• Ask questions about how their information is collected, used, stored, or shared.
• Request deletion of personal information where applicable.

Some information may need to be retained where reasonably necessary for legitimate security, fraud-prevention, payment, accounting, legal, dispute-resolution, or operational purposes.

Requests involving personal information may require reasonable verification of account ownership or identity.

15. Children's Privacy

TapTap is not specifically directed toward children.

Batman Tech does not knowingly collect personal information from children for purposes unrelated to providing the service.

If you believe that information belonging to a child has been improperly provided to Batman Tech, please contact us so that we can review the matter.

16. Changes to This Privacy Policy

Batman Tech may update this Privacy Policy when TapTap's functionality, data practices, services, or applicable requirements change.

The latest version will be published on this page together with its effective date.

Users are encouraged to review this Privacy Policy periodically.

17. Contact Us