Loyalty that earns real retention.

Yes. Managed-cloud deployments are operated by our team on AWS, GCP, or other cloud providers per customer preference. Self-hosted deployments on your VPC or on-premises infrastructure ship with the same source code, a deployment runbook, and an update cadence agreed during contracting.

Singapore is our default controller seat for regional deployments. Per-jurisdiction hosting is supported where regulations require - Indonesia public-scope on Indonesian territory under PP 71/2019, Vietnam impact-assessed transfers under PDPD 13/2023, and so on. Transfer logs and named DPO contacts are provided per jurisdiction.

Schema-preserving data export including member identity, transaction history, points ledger, and tier movement audit, delivered within an agreed window at no additional charge. For custom-engineered deployments, source code is transferred to you.

Three layers. On earn: per-identity rate limits, transaction-level deduplication, and configurable suspicious-pattern flagging. On identity: deduplication across phone, email, and device fingerprint, with manual merge tools for genuine duplicates. On redeem: redemption velocity caps, tier-eligibility checks at point of sale, and an audit log on every redemption. Fraud safeguards are tunable per programme.

Yes. Segments, eligibility rules, point multipliers, A/B test arms, exclusions, and reward catalogue items are all admin-UI configurable. Engineering is required only for new earn-event source types (such as integrating a new POS) or new compliance reporting fields.

Two distinct entity types. Benefits are one-time: a member earns them by hitting a points threshold; they are issued once, consumed once, and written off the books. Privileges are recurring: they apply while the member sits in a given tier (priority access, free upgrades, partner perks, fee waivers) and suspend automatically on tier downgrade. Reporting separates the two so finance can quote benefit cost and privilege cost distinctly.