Reply Counter Privacy Policy

Effective October 21, 2026

Enroll Boost AI, LLC operates the EnrollBoostAI Reply Counter. This policy explains how we use information in the reply counter, its billing pages, and its connected services. Contact us at cade@enrollboostai.com with privacy questions or requests.

Information we use

• Business and account details: business name, billing email, CRM location and contact identifiers, and the QuickBooks customer identifier used for your account.
• Usage and service records: trial dates, reply balances, message identifiers and statuses, conversation text needed to operate an enabled AI conversation, appointment information, and service errors.
• Payment and authorization records: your payment-method reference, purchase amount, payment and receipt identifiers, refill preferences, spending limits, and the terms and time of your authorization.
• Connection and technical information: encrypted service credentials and OAuth tokens, security/session tokens, and technical request information processed by our hosting providers.

The counter connects to Enroll Boost AI, LLC's QuickBooks company to process payments and record receipts for our services. Clients do not have to connect their own QuickBooks companies.

Why we use it

We use this information to operate the assistant, count successful AI replies, maintain prepaid balances, process authorized purchases and refills, issue receipts, provide support, investigate billing errors, prevent duplicate sends and charges, and protect the service. We do not sell your personal information. QuickBooks financial records and payment credentials are not supplied to generative AI or used to train AI models.

When AI conversations are enabled, lead messages and approved business information may be sent through the configured CRM and Zapier AI workflow to generate a reply. This is separate from the QuickBooks payment and accounting data.

Payments and service providers

Payment services are provided by Intuit Payments Inc. Card details entered on the payment page are sent from your browser directly to Intuit for tokenization. The counter's server and database do not receive or store full card numbers or card security codes. We retain payment references and transaction records needed for billing and support. Intuit's own privacy terms govern its processing.

We use Vercel to host the application and Neon to store its database. GoHighLevel/LeadConnector handles CRM messaging and account notifications. Zapier and the configured AI service support enabled conversational workflows. Providers receive the information needed for their role. We may also disclose information when required by law or to protect legal rights and the security of the service.

Access and protection

The service uses HTTPS. Stored integration tokens and conversation payloads are encrypted at the application level. Private billing links and API credentials control access; billing-link secrets are not stored in the browser's persistent storage. Keep these links private and contact us if one is exposed. No system can guarantee complete security.

Retention, disconnection, and requests

We retain information for as long as needed to provide the service, resolve billing issues, satisfy accounting and legal obligations, and protect the service. There is currently no automatic deletion schedule for the ledger; deletion requests are reviewed and handled manually. Contact cade@enrollboostai.com to request access, correction, deletion, or information about the records we retain. We may verify your identity before acting and may need to retain some records for legal or accounting reasons.

Disconnecting QuickBooks stops future access through that connection. It does not itself erase accounting records already created in QuickBooks or cancel a client's refill authorization. Clients can turn off future refills through their private billing link or by contacting us. A payment already processing may complete.

Hosting and browser storage

The application and database are configured for hosting in the United States. This policy covers the counter, not separate provider websites. The counter does not use advertising trackers or analytics cookies. Hosting and connected providers may process technical request information under their own policies.

Updates

We will post revisions here and identify their effective date. For a material change in how we use client information, we will provide notice through an appropriate account channel.