Privacy Policy — Cadance AI Clover Integration
Effective Date: August 25, 2026
This Privacy Policy explains how Cadence AI Inc. ("Company," "we," or "App Provider") collects, uses, discloses, and otherwise processes personal data on behalf of the dance studio businesses that use our application (each, a "Merchant") in connection with the Cadance AI integration with the Clover Point of Sale system ("Clover POS").
This Privacy Policy applies only to the Cadance AI Clover integration. It does not apply to Company's privacy practices in any other context. Company's processing of personal data in connection with the integration is governed by this Privacy Policy and our written agreement with each Merchant. In the event of any conflict, the Merchant agreement controls to the extent permitted by applicable law.
This Privacy Policy is not a substitute for any privacy policy that a Merchant may be required to provide to its own customers or personnel.
Scope of this integration. Cadance AI is a private application. It is not listed on the Clover App Market and is not available for general installation. It is installed only by dance studio locations that Cadence AI Inc. onboards directly, each of which authorizes the application against its own Clover merchant account using Clover's OAuth flow.
How payments are processed. The integration supports both online (card-not-present) payments and in-person (card-present) payments through the Merchant's own Clover merchant account. For in-person payments we use Clover's REST Pay / Cloud Pay Display APIs: payment requests are sent from our backend over the cloud to Clover's own payment application running on the Merchant's Clover device. We do not install custom software on Clover hardware. For online payments, card details are entered into Clover's hosted payment components and tokenized by Clover before reaching our systems.
Cardholder data. We do not collect, store, process, or transmit full payment card numbers, card verification values, magnetic stripe or chip data, or PINs. Cardholder data is captured and processed entirely by Clover and its payment processors. We receive only the limited transaction results described below.
1. Information we collect
Merchants determine the scope of personal data we receive. In connection with the Clover integration, the information we collect is limited to the following.
Information we collect when a customer of a Merchant makes a payment
When a payment is completed through the integration — whether online (card-not-present) or in person on a Clover device (card-present) — Clover returns transaction results to us. These may include:
- The transaction amount, date, time, and currency
- The Merchant's store location and, for in-person payments, the Clover device used
- The card brand and the last four digits of the payment card
- The name associated with the payment card, where Clover provides it
- For online payments, the billing postal code and, where the customer provides it, the billing address and email address used for verification and receipt purposes
- A tokenized payment reference and the Clover transaction and order identifiers
- The approval, decline, refund, or void status of the transaction
- The lesson, lesson package, group class, membership, or gift card purchased
We use these results to record the payment against the correct student, package, membership, or gift card balance in the Merchant's Cadance AI account. We do not collect additional information from the customer through the Clover device or through Clover's hosted payment components.
Additional information customers provide ancillary to a payment
Where the Merchant enables it, Clover may pass us a customer email address or phone number captured at the point of sale for the purpose of issuing a receipt, or the identifier of a Merchant loyalty or lesson-package record. We do not collect marketing preferences, physical addresses, dates of birth, or reviews through the Clover integration.
Information we collect about personnel of a Merchant
We may receive the Clover employee identifier and display name of the staff member who processed a transaction, so that the Merchant can attribute sales to the correct instructor or front-desk employee. We do not receive Social Security numbers, government identification numbers, dates of birth, or payroll records through the Clover integration.
Additional information Merchants provide to us
Separately from the Clover integration, a Merchant provides us with the student and lesson records held in its own Cadance AI account. The Clover integration reads and writes only the payment-related fields needed to reconcile a transaction to a student record. We do not transmit a Merchant's broader student records to Clover.
2. How we use the information we collect
We use the information described above solely to provide the integration to the Merchant on whose behalf it was collected, specifically to:
- Initiate an online or in-person payment request through the Merchant's Clover account and return the result to the Merchant's staff
- Record a completed payment against the correct student, lesson package, membership, or gift card balance
- Apply refunds, voids, and adjustments requested by the Merchant
- Produce payment and revenue reporting for the Merchant's own use
- Provide support to the Merchant and investigate transaction discrepancies
- Maintain the security, integrity, and reliability of the integration
- Comply with legal obligations and prevent fraud or unauthorized use
We do not use Merchant data or personal data obtained through the Clover integration for our own purposes. We do not sell it, we do not use it for advertising or marketing of any kind, we do not use it to build products or datasets for other customers, and we do not use it to train artificial intelligence or machine learning models.
3. How we share information
We share personal data obtained through the Clover integration only with:
- The Merchant from whom or on whose behalf we collected it
- Clover, as the platform on which the integration operates. Clover's Privacy Notice is available at https://www.clover.com/privacy-policy.
- A small number of infrastructure providers that host and secure the application on our behalf, under written contracts that prohibit them from using the data for their own purposes. These are currently Amazon Web Services, Inc. (cloud hosting and storage) and Cloudflare, Inc. (network security and content delivery).
- Third parties that a Merchant specifically directs us to share with
We do not sell personal data as that term is defined under applicable privacy laws, and we have not done so in the preceding twelve months. We do not share personal data with third parties or affiliates for marketing or promotional purposes.
We may disclose personal data where required by law, court order, or lawful government request, or where we reasonably believe disclosure is necessary to protect our legal rights or the safety of any person, or to investigate fraud or unauthorized activity.
If Company is involved in a merger, acquisition, or sale of assets, personal data may be transferred as part of that transaction, and we will require the recipient to honor this Privacy Policy.
4. How long we keep information
We retain transaction records for as long as the Merchant's account is active, plus the period required to comply with tax, accounting, audit, and legal obligations — typically seven years. On termination of a Merchant's agreement, we delete or return the personal data we hold on that Merchant's behalf in accordance with our agreement with that Merchant, subject to any retention required by law. System logs are retained for no longer than ninety days.
5. Security
We maintain reasonable administrative, technical, physical, and organizational safeguards designed to protect personal data, including encryption in transit using TLS, encryption at rest, role-based access controls limiting access to authorized personnel, audit logging, and periodic security review.
Because the integration relies on Clover's payment APIs and hosted payment components for both online and in-person transactions, cardholder data remains within Clover's PCI DSS-validated environment at all times. We receive only tokenized references and transaction metadata.
No method of transmission or storage is completely secure. If we become aware of a security incident affecting personal data processed on a Merchant's behalf, we will notify that Merchant without undue delay in accordance with our agreement and applicable law.
6. Your rights and choices
Data subject rights
Individuals with questions or requests regarding personal data processed through the integration should contact the Merchant they interacted with. The Merchant determines the purposes and means of processing and is responsible for responding. To the extent Clover is responsible for responding to a request under applicable law, individuals may contact Clover as described in Clover's Privacy Notice at https://www.clover.com/privacy-policy. Company will assist a Merchant or Clover in responding to such requests as required by our agreement with them.
Complaints
If you have a complaint about our handling of personal data, contact us using the details below.
Updates
We may modify this Privacy Policy. We will indicate changes by updating the Effective Date above.
7. Contact us
You may contact us with any question, comment, or complaint about this Privacy Policy or our privacy practices:
8. Merchants located in Europe
The Cadance AI Clover integration is currently offered only to Merchants located in the United States, and we do not knowingly process personal data of individuals located in the European Economic Area, the United Kingdom, or Switzerland through the integration.
Where the integration is used by a Merchant subject to European data protection law, Company acts as a data processor for and on behalf of that Merchant, who is the controller. Clover is also a controller in certain circumstances; Clover's Privacy Notice is available at https://www.clover.com/privacy-policy. The Merchant is responsible for establishing a legal basis for our processing. Where a transfer of personal data outside Europe or the United Kingdom is required, we make that transfer under Standard Contractual Clauses approved by the European Commission or another lawful transfer mechanism. Data subjects should direct rights requests to the relevant controller.
9. Your California privacy rights
California residents have the rights described below with respect to personal information we process. These rights are not absolute, and we may decline a request as permitted by the California Consumer Privacy Act ("CCPA").
- Information. You may request the categories of personal information we collected, the sources, the business purpose for collecting it, the categories of third parties with whom we shared it, and whether we disclosed it for a business purpose or sold it, in the past 12 months.
- Access. You may request a copy of the personal information we maintain about you.
- Deletion. You may request that we delete the personal information we maintain about you.
- Nondiscrimination. We will not discriminate against you for exercising these rights.
Because we process personal information solely on behalf of Merchants as a service provider, individuals should generally direct requests to the Merchant they interacted with. You may also contact us at privacy@cadance.ai with the subject line "California Privacy Request," or write to Cadence AI Inc., 222 Chamundi Ln, McMinnville, TN 37110. We will verify your identity before responding substantively, and a request must include enough detail for us to evaluate it. A request may be made on behalf of a child under 13. An authorized agent may submit a request on your behalf with written authorization.
Sale of personal information. We do not sell personal information as defined under the CCPA. In the preceding twelve months, we have not sold any personal information.
Personal information we collect, use, and share through the Clover integration
The chart below summarizes the categories of personal information processed through the Clover integration in the twelve months before the Effective Date of this Privacy Policy. "Shared for business purposes" means disclosed to the Merchant on whose behalf it was collected, to Clover as the payment platform, or to our infrastructure providers.
| Category (see glossary below) | Do we collect this information? | Do we share it for business purposes? |
|---|---|---|
| Identifiers | Yes | Yes |
| Online Identifiers | No | No |
| Protected Classification Characteristics | No | No |
| Commercial Information | Yes | Yes |
| Biometric Information | No | No |
| Internet or Network Information | No | No |
| Geolocation Data | No | No |
| Sensory Information | No | No |
| Professional or Employment Information | Yes | Yes |
| Education Information | No | No |
| Inferences | No | No |
| Financial Information | Yes | Yes |
| Medical Information | No | No |
Notes. "Identifiers" is limited to the name associated with a payment card and the Merchant's own student or customer record reference. "Commercial Information" is limited to the lesson, package, class, membership, or gift card purchased. "Professional or Employment Information" is limited to the Clover employee identifier and display name of the staff member who processed a transaction. "Financial Information" is limited to transaction amount, card brand, last four digits, and tokenized payment references — we do not collect full payment card numbers, card verification values, magnetic stripe or chip data, or PINs.
10. Glossary
| Category | Data elements within the category |
|---|---|
| Identifiers | Real name, alias, postal address, unique personal identifier, customer number, email address, account name, and other similar identifiers. |
| Online Identifiers | IP address, device identifier, cookie identifier, account login, and similar identifiers used to recognize a device or user across services. |
| Protected Classification Characteristics | Age, race, color, ancestry, national origin, citizenship, religion or creed, marital status, medical condition, physical or mental disability, sex, sexual orientation, veteran or military status, and genetic information. |
| Commercial Information | Records of products or services purchased, obtained, or considered, and other purchasing or consuming histories or tendencies. |
| Biometric Information | Physiological, biological, or behavioral characteristics used to establish individual identity, such as fingerprints, faceprints, and voiceprints. |
| Internet or Network Information | Browsing history, search history, and information regarding an individual's interaction with a website, application, or advertisement. |
| Geolocation Data | Precise geographic location information about a particular individual or device. |
| Sensory Information | Audio, electronic, visual, thermal, olfactory, or similar information. |
| Professional or Employment Information | Job title, employer, work history, shifts worked, and sales attribution information. |
| Education Information | Information relating to a student maintained by an educational institution, as defined under the Family Educational Rights and Privacy Act. |
| Inferences | Profiles reflecting preferences, characteristics, psychological trends, predispositions, behavior, attitudes, intelligence, abilities, or aptitudes. |
| Financial Information | Bank account number, credit card number, debit card number, or other financial information, including tokenized payment references and transaction amounts. |
| Medical Information | Information about an individual's medical history, mental or physical condition, or medical treatment or diagnosis by a health care professional. |