غلّة Ghallah
Loyalty policyGovernance and compliance

Advanced Package loyalty program

Loyalty Program Policy and Terms

A transparent customer document explaining enrollment, qualifying visits, reward use, data roles, and customer rights.

Policy version
LOY-POL-1.0
Effective date
29 July 2026
The car wash must show its campaign-specific terms before enrollment. The accepted published version prevails and cannot be changed retroactively.

At a glance

Enrollment is optional

Refusing loyalty does not prevent purchasing a wash at the ordinary price. Loyalty consent does not include marketing.

The car wash sets the offer

A campaign may require 5 or 10 visits or run for a limited period. The threshold, period, branches, services, and reward must be shown first.

Phone is not spending authority

A phone number only helps locate a membership. Reward use requires QR or fallback proof and the approved verification flow.

Customer promises survive

Stopping a campaign or downgrading the merchant plan does not erase a valid issued reward or financial obligation.

Who provides the program?

The car wash or business named in the campaign terms is the program owner, merchant, and controller of its customer data. It selects campaign rules within these controls and remains responsible for the offer, service, and reward.

Ghallah supplies the technical platform and processes the car wash's customer data under its instructions and data-processing agreement. Ghallah is an independent controller only for platform accounts, platform security, and its own legally required records.

Enrollment and consent

  • The car wash identity, campaign name/version, branches, eligible services, visit threshold, period, reward, validity, and exclusions are shown before consent.
  • Consent must be freely given, clear, and recorded with time, method, language, and wording version. Staff may not consent for a customer without signed paper evidence or a customer-device flow.
  • Ghallah does not collect a national ID, an ID image, or an electronic signature image for loyalty. A signed fallback paper form is retained by the merchant under the retention schedule.
  • Loyalty-service consent is separate from marketing consent. Enrollment does not authorize WhatsApp or SMS promotions; future marketing requires separate consent and easy opt-out.
  • The MVP is limited to a customer who confirms full legal capacity. A person lacking capacity is not enrolled in the current flow, and no guardian or identity documents are collected for that purpose.

Campaigns and visit thresholds

  • Each merchant selects an appropriate threshold per campaign, such as 5 or 10 visits, a seasonal campaign, or an ongoing campaign. There is no universal fixed visit count.
  • Publishing freezes an immutable version. Changing threshold, reward, scope, or period creates a new version and cannot reduce prior progress or rewards.
  • Only a fully settled eligible invoice family for an included service and branch earns progress. Drafts, failed or incomplete payment, duplicates, cancellations, excluded sources, and unsettled invoices do not.
  • The platform prevents prohibited campaign overlap and duplicate source use, and checks budget and liability limits before issuing value.
  • A quality-remediation rewash is neither a loyalty visit nor a reward. It creates no progress and consumes no loyalty value.

Rewards

  • A reward may be a fixed-amount discount or an eligible free service/wash subject to the published service list and monetary cap.
  • A reward is not cash, a bank balance, or transferable or resalable unless the campaign expressly allows this and applicable law permits it.
  • A free-service reward covers the eligible service up to the published cap. The customer pays any clearly disclosed upgrade or excess before confirmation.
  • Rewards do not stack on one invoice unless the campaign expressly says so and the platform permits it. Ghallah's default is no stacking.
  • The electronic invoice truthfully shows the service, discount, tax, and final amount. A reward never alters or conceals a historic invoice.

QR card and security

  • One QR card and an independent fallback code are issued per member at that merchant. Secrets are shown once through protected delivery and the customer confirms receipt.
  • The raw QR and fallback values are not stored; the platform retains cryptographic verification digests. Secrets are not printed automatically or placed in logs, URLs, or analytics.
  • A lost card must be reported promptly. The prior card is revoked and replacement follows verification. Revoked-card use and replayed redemption are refused and security-audited.
  • A phone number cannot link an existing member or authorize reward use. Lookup is masked, permission-scoped, and rate-limited.

Suspension, expiry, and honoring promises

  • Earning may pause when a campaign ends, budget is exhausted, misuse is suspected, a security incident occurs, or law requires it. The state must be clear and no false progress is created.
  • An issued reward remains usable until expiry unless law or proven fraud prevents it. Merchant subscription downgrade stops new earning but does not erase prior obligations.
  • If the merchant cannot provide a promised reward, it must handle the complaint fairly under the campaign terms and applicable law. A technical stop cannot be used to extinguish customer rights.

Your data and rights

  • Only necessary data is processed: member reference, protected phone matching, campaign version, eligible visits, rewards, consent evidence, and security/audit records.
  • Under the Saudi PDPL you may be informed, access and obtain a copy, request correction or destruction, and withdraw consent, subject to lawful exceptions.
  • Withdrawal is free and easy. Future consent-based processing stops without undue delay, while prior lawful processing and tax, dispute, fraud-prevention, or other mandatory records may remain.
  • No solely automated decision may impose a harmful legal or financial effect on the customer. Human review is available for complaints, corrections, and recovery.

Regulatory sources

This policy was prepared against the official sources below. Applicable law and competent-authority decisions prevail if they conflict with this document.

  • Saudi Personal Data Protection Law - SDAIA
  • PDPL Implementing Regulations - SDAIA
  • Privacy Policy Development Guideline - SDAIA
  • Personal Data Transfer Regulations - SDAIA
  • General VAT Guideline - ZATCA
  • Electronic Invoice Specifications - ZATCA
  • Essential Cybersecurity Controls ECC 2-2024 - NCA
  • E-Commerce Law and Implementing Regulations - Ministry of Commerce

Questions, complaints, and privacy requests

Contact the car wash first as program owner and controller of its customer data. Contact Ghallah for platform requests or privacy escalation. Withdrawing consent or making a privacy request is free.

Ghallah email: support@ghallah.net

© 2026 Ghallah
Privacy policyTerms of ServiceHome