This Addendum covers Customer Data that Merchant collects through the Service and the marketing tools the Service provides. Capitalized terms not defined here have the meanings in the Merchant Agreement.
1. Roles
1.1 Merchant decides what Customer Data to collect and how to use it. Merchant is the controller (or "business") of Customer Data; Ridge is a service provider (or "processor") acting on Merchant's instructions, which are this Agreement and Merchant's use of the Service's features.
1.2 Merchant is responsible for giving Customers any privacy notice the law requires for the data Merchant collects, and for having a lawful basis to collect it.
2. How Ridge handles Customer Data
2.1 Use. Ridge uses Customer Data only to provide and support the Service to Merchant, to prevent fraud and abuse, to comply with law, and as described in Section 8.2 of the Merchant Agreement (aggregated and de-identified data). Ridge does not sell Customer Data or use it to market to Customers on Ridge's own behalf.
2.2 Subprocessors. Ridge uses these subprocessors: Stripe (payments and identity); Microsoft Azure (hosting, in the United States); Azure Communication Services or a comparable provider (email and text delivery); and analytics and error-monitoring providers that receive no Customer contact details. The current list is at ridgeapp.app/subprocessors. Ridge will post changes at least 15 days before they take effect, and Merchant may object in writing on reasonable data-protection grounds.
2.3 Security. Ridge maintains administrative, technical and physical safeguards appropriate to the data, including encryption in transit and at rest, access controls, logging, and regular testing. Card data never reaches Ridge's systems.
2.4 Incidents. If Ridge confirms unauthorized access to Customer Data in its systems, Ridge will notify Merchant within 72 hours of confirmation with what is known, and will cooperate with Merchant's notifications to Customers and regulators. Merchant is responsible for incidents on its own devices and accounts.
2.5 Requests. If a Customer asks Ridge to access, correct or delete their data, Ridge will refer the request to Merchant and assist Merchant in responding through the Service.
2.6 Retention and deletion. Ridge keeps Customer Data while the Agreement is in effect. After termination Ridge keeps it available for export for 90 days, then deletes it within 90 further days, except transaction records Ridge or Stripe must keep for disputes, tax or legal obligations.
3. Text message marketing
3.1 Merchant is the sender of every text sent through the Service. Ridge provides the tools; Merchant is responsible for compliance with the Telephone Consumer Protection Act, the CAN-SPAM Act as it applies to texts, CTIA messaging principles, carrier rules and state law.
3.2 Consent. Before adding a phone number to a marketing list, Merchant must hold the Customer's prior express written consent to receive marketing texts from Merchant, obtained with a clear disclosure that consent is not a condition of purchase, that message and data rates may apply, and how to opt out. Ridge's checkout and sign-up screens provide a consent prompt; consent gathered anywhere else must meet the same standard and be recorded with date, time and source.
3.3 Opt-out. Every marketing text must identify Merchant and include opt-out instructions. The Service honors STOP, UNSUBSCRIBE and similar replies automatically; Merchant will not re-add a number that has opted out without new consent.
3.4 Hours and content. Merchant will not send marketing texts before 8 a.m. or after 9 p.m. in the Customer's local time, and will not send content prohibited by carrier rules (including cannabis, firearms, gambling, adult content, and loan or debt-relief offers).
3.5 Transactional texts (receipts, order-ready notices, appointment reminders) require only the Customer's phone number given for that purpose and are not marketing.
3.6 Limits. Each Plan includes the number of marketing texts shown at ridgeapp.app/pricing; additional texts are billed at the add-on rate. Ridge may limit sending volume or velocity to protect deliverability.
4. Email marketing
4.1 Merchant is the sender of every marketing email sent through the Service and is responsible for compliance with the CAN-SPAM Act and state law.
4.2 Every marketing email will identify Merchant, include Merchant's physical address, carry an accurate subject line, and include a working unsubscribe link, which the Service inserts. Merchant will honor opt-outs within 10 business days; the Service does so automatically.
4.3 Merchant will send only to Customers who gave their email address to Merchant and will not upload purchased, rented or scraped lists.
5. Loyalty programs
Merchant is responsible for the terms of any loyalty or rewards program it runs through the Service, including disclosure of how points are earned and expire, and for any state law on stored value or promotional credits.
6. Ridge's rights
6.1 Ridge may suspend text or email sending, without liability, if Ridge receives carrier complaints, spam reports above industry thresholds, or evidence of sending without consent, and will tell Merchant why.
6.2 Merchant will indemnify Ridge under Section 15 of the Merchant Agreement for claims arising from Merchant's marketing, including TCPA claims.
7. Merchant's Staff and Customer Data
Merchant will give Staff access to Customer Data only as needed for their roles, will remove access when Staff leave, and will not export Customer Data for any purpose other than Merchant's own business.