Your customers trust you. Here's how we keep it that way.
Plain answers to where data lives, who can see it and how we stop people gaming your rewards.
Our application server and Postgres database run in Mumbai. Nightly backups stay on the same Indian server for 14 days.
Every page, card update and API call uses HTTPS with automatically renewed certificates and HSTS.
Owner passwords and staff PINs are kept only as salted scrypt hashes. Sessions are signed and expire.
Owners see everything. Staff get a PIN that can only scan and stamp, for their own shop, nothing else.
A gap between stamps, a per-visit limit, one welcome offer per person and redemptions that can't fire twice.
Rate limits on logins, PINs and sign-ups, cross-site request checks, secret tokens on every card link and no framing.
Nearby reminders are decided by the customer's own phone. We never see or store where anyone is.
Ask for a copy of your customer list any time. Close your account and it is deleted, no exit fee.
Service providers
The only companies that touch personal data to run LoopinCard. Each gets only what it needs. We update this list before adding anyone new.
Application server, database and backups
Delivering and updating Apple Wallet cards
Delivering and updating Google Wallet cards
Web notifications for customers without a wallet
Turning a shop address into a map pin, only when the owner asks
No advertising networks. No analytics trackers. No data brokers.
Design it in two minutes. Free for your first 100 regulars.