Keep the value. Minimize the exposure.
RewardHound is being built to organize sensitive wallet items without casually spreading their credentials. This page describes the current product design and security commitments while the app is still in development.
Gift cards
- Gift-card credentials are designed to stay in secure wallet storage, not ordinary analytics or logs.
- Provider credentials for authorized balance APIs remain server-side and are never returned to the mobile app.
- RewardHound does not scrape merchant balance pages or automate CAPTCHA bypasses.
- For supported Buy New integrations, checkout and payment can remain with the retailer or authorized provider while the newly issued card is returned securely to RewardHound and added to the user's wallet.
RewardHound Send
The planned Send flow is app-to-app. An email or text may carry an invite, but it must not contain the spendable gift-card number, PIN, barcode or reusable claim secret.
Recipient rule: the recipient must install or open RewardHound and complete an authenticated claim before a usable gift can be released.
Live cross-device claims remain disabled until authenticated accounts, encrypted credential custody, expiring one-time claims and revocation are implemented.
Family Sharing
Family Sharing is designed as permissioned, per-item household access — not a public sharing link. Eligible gift cards may eventually support balance-only or use permissions. Rewards sharing follows the loyalty program's own rules.
Dynamic tickets are not copied into household sharing. Where an issuer such as Ticketmaster or AXS requires official transfer or a live rotating credential, RewardHound keeps that boundary intact.
Rewards and loyalty programs
RewardHound does not collect loyalty-program passwords for manual wallet use. Automatic balances or account linking are enabled only through authorized provider/program integrations.
Program sharing rules are treated as verified shareable, verified personal-only, or review-needed. RewardHound does not infer permission to share from another program's behaviour.
Tickets
Static passes may be stored when appropriate. Dynamic or rotating tickets remain with their original issuer. RewardHound recognizes supported issuer links and opens the live source instead of recreating a barcode that may no longer be valid.
What RewardHound tries not to collect
- Retailer checkout/payment credentials
- Loyalty-program passwords
- Gift-card credentials in logs or support emails
- Dynamic ticket barcodes copied from issuer apps
- Provider API secrets in mobile wallet records
Early access emails
If you join the RewardHound early-access list, we collect the email address you submit and store it with our email service provider, Resend.
We use that address for the welcome message and RewardHound launch or product updates. You can unsubscribe from those emails at any time. Joining the list does not require you to provide gift-card, rewards or ticket credentials.
Questions or security concerns
Email team@rewardhound.ca. Please describe the issue without including sensitive wallet credentials.
Status: RewardHound is in active development. This page will be updated before public launch as account, sync and production-provider systems are finalized.