Privacy Policy

This Privacy Policy explains how Brushler, LLC, an Arizona limited liability company (“Brushler,” “we,” “us”), collects, uses, stores, and shares information when you use the Brushler mobile/web application and related backend services (the “Service”). Brushler is a business-to-business pool-service operations tool used by pool companies and their staff.

Brushler, LLC is the data controller for account and staff information described below. For the customer and service data that an organization enters while running its own pool business, Brushler, LLC acts as a processor on that organization’s behalf.

Contact for privacy requests: support@brushler.com.

1. Who this policy covers

This policy covers (a) organization administrators and staff who create accounts in Brushler, and (b) customer / service data that those organizations enter into Brushler while running their pool businesses. Organizations are responsible for the customer information they upload or enter.

2. Information we collect

Depending on how the Service is used, we may process:

• Account information: name, email, username, phone (if provided), role, and organization membership.
• Customer / book-of-business records: customer names, phones, emails, service addresses, notes, route assignments, work orders, service logs, and related operational records.
• Photos: service-stop and work-order photos captured or selected for documentation.
• Location: device location while the route map is open (when-in-use), and customer address coordinates used for mapping/routing.
• Billing / QuickBooks data: if an organization connects QuickBooks Online (QBO), invoice/estimate/customer sync data needed to operate billing features.
• Device / app data needed to run the Service: authentication tokens, offline/sync queues stored on-device, and basic technical logs required for reliability and security.
• Push notification tokens: if a user enables push notifications, a device-level push token is stored with their account and used solely to deliver in-app notifications (for example, schedule changes or billing alerts). Tokens are relayed through Expo’s push notification service to Apple (APNs) and Google (FCM), and are deleted when a device unregisters.
• Support communications: if you contact us for help — by email, or by filing a support ticket from inside the app or the office web app — we store the subject and the messages you send, our replies, and the account and organization the ticket was filed from. Support tickets are readable by Brushler staff; that is what allows us to answer them.
• Support diagnostics: a ticket filed from inside the app also carries a small, fixed set of technical context about your device at that moment: app version and build number, platform, operating system version, device model, the screen you were on, your language setting, whether the device was offline, and counts of records and photos waiting to sync. This is a closed list enforced on our servers — anything a client sends that is not on it is discarded rather than stored. It deliberately excludes the contents of anything waiting to sync, your customers’ details, and any QuickBooks identifiers, tokens, or financial data.

Brushler does not include advertising SDKs, does not sell personal information, and does not use collected data for cross-app tracking.

3. How we use information

• Provide and operate the Service for the customer’s organization
• Authenticate users and enforce role-based access
• Support routing, service documentation, photos, work orders, and billing workflows
• Sync with QBO when an organization chooses to connect it
• Provide support, troubleshoot issues, and maintain security
• Improve reliability and product functionality

4. How we share information

We share information only as needed to operate the Service:

• Within the organization: data is available to authorized users of that organization according to roles/permissions.
• Service providers / subprocessors: hosting/database providers; map providers (Apple Maps on iOS; Google Maps / geocoding on Android and for address lookup); email transport for platform/admin communications when configured; Expo’s push notification service (relaying push tokens and notification payloads to Apple APNs and Google FCM) when a user enables push notifications; Intuit QuickBooks Online when an organization connects QBO; error-monitoring and log-aggregation providers that receive application error reports and server logs so we can diagnose faults (these may incidentally contain identifiers such as an email address present in the failing request).
• Legal / safety: if required by law or to protect rights, security, or integrity of the Service.

We do not sell personal information.

A current list of subprocessors is available on request from support@brushler.com.

4a. Brushler support access to your data

So that we can operate the Service and help when something goes wrong, Brushler, LLC personnel can access organization records through an internal support console. We hold ourselves to the following, and we would rather you know it up front than discover it later:

• Personal information is masked by default. Viewing unmasked customer contact details is a separate, permission-gated action.
• Unmasking requires a stated reason and is recorded. Every unmask writes an audit entry identifying who did it, when, and why.
• You can ask to see that trail. Email us and we will provide the record of support access to your organization’s data.
• We do not use your business data commercially. Brushler, LLC’s founder also operates a pool-service company. Your customer lists, pricing, and margins are yours; we do not use them to compete, and we do not share them with any other organization.

5. On-device storage

The mobile app may store authentication credentials in secure device storage, and may keep limited offline queues / caches (including photos pending upload) on the device so field work can continue without connectivity. Clearing app data or signing out may remove some local session data; queued offline work may be retained for the same user according to product behavior.

6. Retention

We retain organization data while the organization account remains active and as needed to provide the Service, comply with legal obligations, resolve disputes, and enforce agreements. Organizations may request export or deletion/offboarding support by contacting support@brushler.com.

7. Security

We use industry-standard safeguards appropriate to a multi-tenant SaaS product, including HTTPS for API traffic, authentication/authorization controls, and tenant isolation controls on the backend. No method of transmission or storage is 100% secure.

8. Children’s privacy

Brushler is a workforce / business tool and is not directed to children. We do not knowingly collect personal information from children under 13 (or the equivalent age in your jurisdiction).

9. International users

The Service may be hosted in the United States. If you access the Service from another country, you understand that information may be processed in the United States.

10. Your choices and requests

• Update profile information in the app where available
• Disconnect QBO from organization settings if connected
• Request access, correction, export, or deletion — see Account & Data Deletion
• Control device permissions (camera, photos, location) in system settings

11. Changes

We may update this policy from time to time. The “Last updated” date will change when we do. Continued use of the Service after an update means you accept the revised policy.

12. Contact

Privacy questions or requests:
Brushler, LLC (Arizona, USA)
Email: support@brushler.com