Privacy Policy

Effective 10 October 2026

PaySquatch Counter is operated by PaySquatch in the United States. This Privacy Policy explains how we handle information for our point-of-sale web application and its operator console. Our public website is paysquatch.com. Participating retail stores use the service to accept cash payments for prepaid wireless top-ups and send them to the carrier through our payment processor, Paymaster.

Customers pay at the store. Google sign-in is only for staff, including operators and store owners. It is not a customer sign-in service. The information we handle depends on whether you are using a staff account or making a top-up payment at a participating store.

1. Google account data for staff sign-in

When a staff member signs in with Google, we receive their email address, display name, Google account identifier and whether their email is verified. When enabled, we also receive sign-in time signals: the time the Google account last authenticated.

We use this Google account data only to confirm that the person is on our staff allowlist, bind their Google account to their staff record and write audit records of staff actions. Having a Google account does not by itself give someone access to PaySquatch Counter or the operator console.

We do not request or receive access to Gmail, Drive, Contacts, Calendar or any other Google service. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Staff can withdraw access through their Google account permissions. Removing a staff member from our allowlist ends their ability to sign in. Withdrawing access does not automatically erase records of earlier staff actions. Those records remain subject to the retention practices below.

2. Store and staff account information

We handle store names, store codes, owner and clerk names, phone numbers and password hashes. We also keep sign-in logs and audit logs of staff actions. This information supports store and staff accounts, access controls and accountability for activity in the service.

Staff activity is recorded so that actions can be linked to the relevant staff record and store. Account information and audit records help us understand who performed an action when reviewing a payment, resolving a dispute or investigating possible misuse.

3. Customer transaction information

For a top-up, we handle the mobile phone number being topped up, carrier, product, amount, time, store and clerk. We also record the payment outcome and the payment processor's reference. These details identify the requested top-up and its result.

We collect this information to deliver the top-up, print the receipt, reconcile cash at the end of the day, handle disputes and detect fraud. We do not use customer transaction information for marketing. Please confirm the mobile phone number with the store before it submits the payment.

4. Technical information

We handle IP addresses, browser types, timestamps and security logs. These records support operation and security of the service. They help us review sign-in activity and investigate access problems, suspicious activity or interference with the application.

We share transaction information with Paymaster and the relevant carrier to complete the top-up. We also share information with service providers that host the service. We may disclose information when required by law.

We never sell personal information. We do not use it for advertising. The reasons for collecting and using customer transaction details are delivering and managing payments, reconciliation, disputes and fraud prevention, as described above.

6. How long we keep information

We keep transaction and audit records for as long as needed for reconciliation, disputes, fraud prevention and legal obligations. Retention depends on those needs, so a completed payment or an inactive staff account does not necessarily mean its related records can be deleted immediately.

We keep Google account data while the staff member is active, plus the audit retention period. This allows records of staff actions to remain useful when earlier activity needs to be reviewed.

7. Security

We use HTTPS, limit access to allowlisted staff, log staff actions and encrypt backups. These measures help protect information and support investigation of misuse. No online service can promise complete security. Staff should keep their credentials private and report suspected account misuse promptly.

8. Children

PaySquatch Counter is not directed to anyone under 18. If you believe a child has provided personal information through the service, contact us so we can review the situation.

9. Changes and contact

We will post changes to this Privacy Policy on this page with a new effective date. You can return to this page to review how we describe our handling of information.

For privacy questions or questions about information associated with a store, staff account or transaction, contact PaySquatch. Please do not send passwords or other sign-in credentials in your message.

10. Public website and customer app

Your language choice is stored on your device. The customer app caches this site's public pages, translations and published public data files for offline use. It does not cache other websites. You can clear these preferences and cached files in your browser settings.