Skip to content
Cashback Builder

Privacy

Privacy policy summary

This summary describes our public-facing privacy approach for website visitors, prospects, customers, and authorized platform users. Final policy language should be reviewed with counsel before production rollout. Last updated May 28, 2026.

1. Information we collect

We may collect business contact information, enquiry details, account credentials, support communications, billing records, technical logs, and platform usage data needed to operate and improve the service.

2. How we use information

We use information to respond to enquiries, onboard customers, authenticate users, provide support, maintain security, deliver the SaaS platform, process billing, and communicate relevant service updates.

3. How we share information

We may share information with infrastructure providers, payment processors, implementation partners, and professional advisers that help us deliver the service. We do not sell prospect or customer information for consumer advertising purposes.

4. Security, retention, and data handling

We use administrative, technical, and organizational safeguards appropriate for a B2B SaaS service. Retention depends on account status, legal obligations, security requirements, and support needs.

5. Customer responsibilities

Customers operating rewards programs are responsible for their own consumer-facing privacy notices, consent flows, partner disclosures, and compliance obligations for the markets they serve.

6. Contact and requests

Business contacts can use the request demo form to ask privacy or data handling questions. We may need to verify the requester before acting on account or data requests.

7. Policy updates

We may update this public summary as our service, vendors, legal obligations, or commercial process changes. Material customer-facing policy commitments should be confirmed in the applicable agreement and production privacy notice.

Next step

Map Cashback Builder to your launch plan.

Share your target market, expected site count, integration needs, budget range, and timeline. We will recommend the right implementation path.