Menu
Features Product About Brand Story Get a Demo Sign In

Clover + Legal

Clover End User Agreement

Effective date: February 23, 2026

1. Scope and acceptance

This Clover End User Agreement applies when a merchant connects Clover to Bestorant. By connecting Clover, you authorize Bestorant to access and process Clover account data required to provide menu sync, webhook processing, and related restaurant operations features.

2. Clover authorization

When you complete Clover OAuth, Bestorant receives an access token and merchant identifier so the integration can be linked to your restaurant account. You represent that you are authorized to grant this access for the merchant.

3. Data accessed from Clover

Depending on enabled features, Bestorant may access and process:

  • Merchant account identifiers and business profile data returned by Clover.
  • Catalog/menu data, including item names, prices, categories, descriptions, and visibility status.
  • Order metadata submitted by your workflows, including customer contact fields you provide.
  • Webhook event payloads and related technical metadata required for synchronization and reliability.

4. How Clover data is used

  • To link and maintain your Clover connection.
  • To synchronize menu data and keep local menu snapshots current.
  • To process integration events and forward menu-related updates to internal Bestorant services.
  • To troubleshoot integration issues, monitor reliability, and improve service quality.

5. Webhooks and security

Bestorant supports Clover webhook signature validation and event deduplication to reduce unauthorized or duplicate processing. You are responsible for configuring your Clover app and webhook settings correctly, including shared secrets where required.

6. Merchant obligations

  • Maintain lawful rights to use Clover data within your business operations.
  • Provide legally required notices and obtain required end-customer consents.
  • Ensure your Clover account settings and permissions are accurate and up to date.

7. Service limitations

Integration availability depends on Clover systems, network connectivity, and third-party uptime. Bestorant is not responsible for downtime, API changes, or service interruptions caused by Clover or other third parties.

8. Termination and revocation

You may disconnect Clover at any time through your Bestorant or Clover administration controls. After disconnection, Bestorant will stop new Clover API calls except as needed for security, legal compliance, or limited operational cleanup.

9. Provider terms

Your use of Clover remains subject to Clover's own developer and merchant terms, privacy requirements, and platform policies. This agreement supplements, and does not replace, those Clover terms.

10. Contact

For Clover integration legal questions, contact legal@bestorant.ai.