BoosterConsensus Pay Privacy Policy

Effective date: November 10, 2026
Applies to: the BoosterConsensus Pay Android mobile application (the "App")
Operated by: Consensus Systems LLC, a Texas limited liability company ("we," "us")

The App lets authorized adult staff accept in-person event-ticket payments for a club, school, or other organization ("Organization"). The initial public release uses Square Bluetooth readers. This policy explains mobile-app information handling, including permissions and third-party services. Related ticket purchases and event-management services are also described in the Ticketing by BoosterConsensus Privacy Policy; shared staff accounts are also covered by the BoosterConsensus Privacy Policy.

1. Information handled by the App

• Staff account information: your sign-in email, account identifier, authentication credentials and session tokens, club association, and permissions. You sign in with an existing BoosterConsensus account through Google Firebase Authentication. The App does not create a separate Pay account.
• Phone and reader registration: an App-generated installation identifier, the staff account associated with the phone, selected club, phone/reader label and identifiers, Android platform and App version, registration and activity timestamps, and reader connection state. The payment SDK also handles reader model, battery, and firmware information.
• Orders and transactions: order and payment references, confirmation codes, sale descriptions, amounts and fees, payment status, provider transaction identifiers, and decline or error codes. We use these to associate a reader payment with the correct box-office order and to recover interrupted transactions. A sale description may contain information entered in the web box office.
• Technical and security information: network information such as IP addresses, request timestamps, device and SDK information, app/device integrity signals and tokens, operational errors, and security/audit records. Our hosting, authentication, and payment providers also process technical information needed to supply and secure their services.
• Support requests: the contact details and information you choose to send us. Do not send passwords, full card numbers, security codes, or payment-provider access tokens.

2. Location, Bluetooth, and phone permissions

• Precise and approximate location: Square requires device location while using the payment service to verify where payments occur, enforce geographic eligibility, prevent fraud, and support disputes. Location information is processed by Square as part of payment processing; it is not used by us for advertising. The App does not request Android background-location permission.
• Nearby devices / Bluetooth: used to discover, pair with, and communicate with the Square card reader.
• Phone state: the Square SDK requires Android phone-state permission to identify the device communicating with Square servers. This permission request is not a request to read your contacts or text messages.

You can deny or revoke permissions in Android Settings. Required reader/payment features will not work without the permissions Square needs. The offline demonstration does not require a reader or live payment permissions.

3. Card information and payment processing

The Square reader and Square Mobile Payments SDK collect and process card information. Our App code and servers do not store full card numbers, card security codes, or raw card-reader data. We retain transaction references, amounts, statuses, and related financial records rather than raw card credentials. Square may process cardholder information, transaction location, device identifiers, and technical/security information under its own applicable privacy notices.

The Organization is the merchant for its ticket sales and can access its order and payment records. Questions about event fulfillment, ticket-holder information, or an Organization's own use of data should also be directed to that Organization.

4. Why we use information

We use information to authenticate staff, enforce Organization permissions, register and revoke phones, connect readers, deliver queued sales, process and reconcile payments, prevent duplicate charges and fraud, maintain accounting and audit records, troubleshoot errors, answer support requests, and comply with law. We do not sell or rent personal information, use App information for targeted advertising, or provide it to data brokers.

5. Who receives information

• Your Organization: authorized administrators and box-office staff can access the device and transaction records needed to administer readers and run sales, subject to their permissions.
• Google / Firebase: authentication, backend hosting and storage, and abuse prevention. Firebase App Check uses Google Play Integrity to verify genuine app/device requests. Google processes authentication, network, SDK, and integrity information for these services. See Google's Privacy Policy.
• Square: reader operation, card collection, payment processing, fraud prevention, and related payment services. See Square's seller privacy notice and consumer privacy notice. Payment providers have their own legal and regulatory responsibilities and are not acting solely on our instructions for every use.
• Other service providers: providers supporting hosting, communications, and requested support may handle information needed for those tasks. Opening a policy or support website also sends ordinary web-request information to that website and its hosting providers, including Cloudflare for this site.
• Legal obligations and business transfers: information may be disclosed when legally required, to protect rights and safety, or as part of a merger, acquisition, or asset transfer, subject to applicable law. Other disclosures require your consent.

Information may be processed in the United States and other countries where our providers operate. Those countries may have different privacy laws.

6. Device storage and security

The App uses Android-backed secure storage for small values such as the installation identifier, selected club, reader mode, and an in-flight payment recovery marker. Firebase and Square manage their own authentication/session storage. The App communicates with our API over HTTPS, and backend access is checked against staff permissions and app verification. No storage or transmission method is completely secure.

Signing out is not an account-deletion request. Removing a phone in the Organization's card-reader settings revokes its access; it does not erase transaction history. Uninstalling the App does not delete server records or your shared BoosterConsensus account.

7. Retention

Account, device-registration, operational, and security records are retained as needed to provide and secure the service, resolve support issues, and meet legal obligations. You may request their deletion as described below; revocation or sign-out alone does not delete them.

The related Ticketing service retains paid, refunded, and disputed order/ticket records for seven years for tax, accounting, and dispute purposes, and abandoned/unpaid orders for 90 days. Its policy provides for redaction of eligible personal details on request after those periods, rather than promising automatic erasure. Legal holds and other applicable legal obligations may require longer retention. Square and Google retain information they process under their own applicable policies.

8. Request account or data deletion

You can request deletion without installing or signing into the App. Email info@boosterconsensus.com with the subject BoosterConsensus Pay account or data deletion. Include the sign-in email, Organization name, and whether you want the shared account deleted, a phone registration removed, or particular personal information deleted. Do not include your password or card details.

We will verify your identity and, where needed, coordinate with the Organization. Because Pay uses a shared BoosterConsensus account, deleting that account can also affect your access to other BoosterConsensus services. We will clarify the requested scope before completing deletion.

We delete or de-identify eligible account, device, and personal information in response to verified requests. Transaction, accounting, dispute, fraud-prevention, and legal records may be retained when required for the purposes and periods described above. Deleting staff access does not delete an Organization's financial records or another person's data. We will explain applicable exceptions when handling your request. Requests for information held independently by Square or Google may also need to be directed to them.

9. Other choices and rights

You may ask to access or correct your personal information, receive a copy, or exercise other rights available under applicable privacy law. Contact us using the details below. We may need to verify your identity and will respond within applicable legal time limits. You can also sign out, ask an administrator to revoke a phone, or change Android permissions.

10. Offline demo and children

The clearly labeled offline demo uses fictional sample data and simulates approvals, declines, and cancellations. It does not collect card payments, issue live tickets, or write demo transactions to an Organization's ledger. That does not mean the installed app and its native service libraries are exempt from their normal technical/security processing.

The App is intended for authorized staff aged 18 or older, not children. Ticket-holder information supplied through related event services is covered by the Ticketing service's policy. Contact us if you believe a child has provided personal information through the App.

11. Policy changes

We may update this policy and will post the revised version with a new effective date. We will provide notice of material changes as required by law.

12. Contact

Consensus Systems LLC
c/o Northwest Registered Agent LLC
5900 Balcones Drive, Ste. 100, Austin, TX 78731
info@boosterconsensus.com