Clover Privacy Policy

This Privacy Policy describes how BEB Technologies LLC, doing business as Birds Eye Brew("BEB," "we," "us," or "our"), collects, uses, stores, and shares information when merchants connect and use the Clover integration offered through the Birds Eye Brew merchant platform. This policy supplements the general Merchant Privacy Policy and applies specifically to information accessed through or associated with the Clover connection.

BEB does not process payments on behalf of merchants through the Clover integration. All payment processing continues to happen through Clover directly. BEB accesses transaction context solely to support loyalty accrual, reward redemption, and related merchant-configured workflows.

1. Information We Collect Through Clover

When a merchant connects their Clover account to BEB, we may receive and process information made available through that authorization. This may include:

• Merchant and location identifiers — Clover merchant ID, location or store identifiers, and account-level details needed to associate transactions with the correct merchant.
• Order and transaction context — Order identifiers, transaction identifiers, timestamps, and order-level metadata used to determine whether a transaction is eligible for point accrual or redemption. BEB does not receive or store raw payment card data, full card numbers, or card verification values through this integration.
• Item and catalog context — Item identifiers, names, and category information from the Clover catalog as needed to support reward eligibility rules or redemption workflows configured by the merchant.
• Webhook and event data — Event payloads delivered by Clover webhooks, which may contain order, payment, refund, or other transaction-related context used to keep loyalty records synchronized.
• Customer association context — Limited customer-linking context (such as a phone number or customer lookup result) used to associate an eligible transaction with a BEB loyalty account. BEB does not use Clover-sourced customer data for purposes unrelated to the loyalty workflow.

We also collect standard account and usage information as described in the general Merchant Privacy Policy, including merchant contact details, login credentials, and technical access logs.

2. How We Use Clover-Connected Information

We use information received through the Clover connection only for the following purposes:

• • Operating and delivering the BEB loyalty and rewards service
• • Authenticating merchants and linking Clover accounts to BEB accounts
• • Determining eligibility for point accrual on transactions
• • Processing loyalty point awards and reward redemptions
• • Maintaining loyalty history, records, and reconciliation logs
• • Preventing duplicate event processing and detecting fraud or abuse
• • Troubleshooting integration issues and providing merchant support
• • Improving the accuracy and reliability of the service
• • Communicating with merchants about integration status or account matters

We do not use Clover-connected data for advertising, marketing to third parties, building consumer profiles unrelated to the loyalty program, or any purposes outside of operating the BEB service.

3. Payments and Financial Data

BEB does not process, store, or transmit payment card data through the Clover integration. BEB does not initiate charges or modify payment amounts in Clover on behalf of merchants or their customers. Transaction context received from Clover is used solely to support loyalty workflows and is not used for payment processing purposes.

4. Webhook and Event Processing

BEB receives event data from Clover webhooks to keep loyalty records synchronized in real time. These events may contain order, payment, refund, or other transaction-linked context. We may store event records, event identifiers, and related metadata to support duplicate-event prevention, reconciliation, auditing, fraud prevention, service reliability, and troubleshooting.

Webhook payloads containing sensitive customer or payment information are handled using reasonable security controls and are not retained longer than necessary to serve their operational purpose.

5. Customer Information Processed Through the Integration

In operating the Clover integration, BEB may process limited end-customer information on behalf of participating merchants, such as phone number or other loyalty account lookup identifiers, loyalty account status, points activity, redemption history, and transaction-linked reward activity. This information is processed to operate the loyalty service on behalf of the merchant and is not used for purposes unrelated to loyalty.

Merchants remain responsible for their own customer relationships and for complying with laws applicable to their businesses and customer data practices.

6. Sharing of Information

We may share Clover-connected information with service providers that help us operate the platform, such as hosting, infrastructure, authentication, logging, analytics, and support vendors. We may also share limited information with Clover where reasonably necessary to support integrations, account linking, security, or troubleshooting.

We do not sell merchant personal information or Clover-connected data. We do not share Clover-connected data with third parties for advertising, marketing, or purposes unrelated to operating the BEB service.

7. Data Retention

We retain Clover integration records, webhook/event records, transaction-linked loyalty records, and merchant account information for as long as reasonably necessary to operate the service, maintain business records, resolve disputes, enforce agreements, prevent fraud, and comply with legal obligations.

Even after a merchant disconnects their Clover account, uninstalls the BEB app from Clover, or closes their BEB account, we may retain certain information where reasonably necessary for legal, security, auditing, or legitimate business purposes.

8. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect merchant and Clover-connected information. These measures may include access controls, encrypted transmission, logging, and secure credential handling. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

9. Merchant Choices and Rights

Merchants may disconnect the Clover integration at any time through their BEB account settings or through Clover. Merchants may also request access to or correction of certain account information, or request account closure, by contacting us. We may limit or deny certain requests where retention is required for legal, security, operational, or contractual reasons.

10. Clover's Own Privacy Practices

Clover and its parent company have their own privacy policies and terms that govern Clover's collection and use of information. BEB is not responsible for the privacy practices of Clover or any other third-party platform. We encourage merchants to review Clover's privacy documentation directly.

11. Changes to This Policy

We may update this Clover Privacy Policy from time to time. Continued use of the Clover integration after an updated version becomes effective constitutes acceptance of the revised policy.

12. Contact

BEB Technologies LLC operates Birds Eye Brew at birdseyebrew.com. For privacy-related questions about the Clover integration, contact us at support@birdseyebrew.com.