Privacy Policy

This policy describes how RAFIE B LLC, doing business as Cardenza (“we,” “us”), handles information for our website, merchant dashboard, scan page, and the loyalty passes we issue. The short version is unusual for a loyalty product and we’re proud of it: your customers never give us their name, email, or phone number — there is nothing like that for us to lose, sell, or leak.

1. Two kinds of people use Cardenza

• Merchants — business owners with a Cardenza account. We collect real account information from you.
• Your customers — people who add a loyalty pass to their phone’s wallet. We collect no identifying information about them, by design.

Your relationship with your customers (what you promise them, what you know about them from your own till) is yours; this policy covers only what passes through Cardenza.

Who is responsible for what. For merchants’ account information we decide how it is handled, as this policy describes. For the loyalty records behind your customers’ passes we act as the merchant’s service provider (a “processor,” in the words of some privacy laws): we hold them to run the merchant’s program, on the merchant’s instructions, and the merchant decides what the program promises and how long it runs.

2. What we collect from merchants

• Account: email address and password (passwords are handled by AWS Cognito; we never see them in plain text), and your business name as you want customers to see it.
• Program configuration: your card design — logo, artwork, colors, reward text, labels — and program settings.
• Billing: handled by Stripe. We receive subscription status and billing metadata; your card number never touches our servers.
• Operational records: paired scanner devices (a device name you choose and a credential we issue) and logs of stamping activity for your program.
• Support: whatever you send us when you contact us.

3. What we collect about your customers — and what we deliberately don’t

When someone adds your pass, we create a record consisting of: a randomly generated pass ID, a stamp count, a lifetime redemption count, timestamps of stamps and redemptions, and the technical registration that lets their phone receive pass updates (for Apple Wallet, an Apple-issued device token).

We do not collect their name, email address, phone number, precise location, contacts, or anything else about them. The pass ID is random — it identifies a pass, not a person. We cannot connect a pass to a human, and neither can anyone who obtains our data.

We never see your customers’ payment details either — a loyalty pass is not a payment method, and nothing about how they pay you passes through Cardenza.

Deleting the pass deletes the record. When a customer removes the pass from their wallet, the associated record and its stamp history are deleted from our systems shortly after (within about a day). There is no dormant profile — no pass, no data.

If you are a customer holding a pass: the record behind your pass is the anonymous one described above. The business whose name is on the pass runs the loyalty program, so questions about stamps and rewards go to them; questions about this record can come to us (Section 12).

4. How we use information

To operate the service: issuing and updating passes, counting stamps and redemptions, showing merchants their program’s activity, billing, preventing abuse (for example, throttling repeated failed pairing attempts by network address), and support. We do not sell personal information, use loyalty data for advertising, or market to your customers.

5. Data retention

• Stamp/redemption event logs are automatically deleted after one year — a deliberate data-minimization policy.
• Customer pass records live only as long as the pass does (Section 3).
• Merchant accounts: after cancellation, your data is retained for 90 days (so you can reactivate) and then deleted.

6. Who we share data with (subprocessors)

Service providers that host and operate parts of Cardenza, under their own security and privacy obligations:

• Amazon Web Services — hosting and storage (United States).
• Stripe — payment processing.
• Apple — Wallet pass delivery and update notifications.
• Google — Wallet pass delivery, when Google Wallet support is available.

We keep this list current. Adding a provider that would handle loyalty records is a material change under Section 11.

We may also disclose information if required by law, or as part of a merger or sale of the business (in which case this policy continues to apply to it).

7. Cookies and local storage

The dashboard and scan page use browser storage for sign-in sessions and device credentials — strictly functional. Signing in to the dashboard also sets one functional cookie on cardenza.app — a signed-in flag with no identifier — which expires within a day or when you sign out. Our marketing site sets no advertising or analytics cookies and loads nothing from third parties.

8. Security

Traffic is encrypted in transit (TLS). Scanner credentials are stored hashed. Passwords are managed by AWS Cognito. Access to production systems is limited. No system is perfectly secure, but our best protection is structural: the most sensitive category — your customers’ identities — is data we simply don’t have.

9. Your choices and rights

• Merchants: you can update your information in the dashboard, cancel your plan there, or ask us to close your account (Section 5 retention applies). You can ask us for a copy of your account data at any time. Contact us for anything you can’t do yourself.
• Your customers: removing the pass from their wallet deletes their data (Section 3). Pass update notifications can be turned off per pass using the wallet’s own controls.

10. Children

Cardenza is a business tool and is not directed at children under 13. We do not knowingly collect personal information from children.

11. Changes

We may update this policy; material changes will be noticed to merchants by email or in the dashboard before they take effect. The current version always lives at this page.

12. Contact

RAFIE B LLC d/b/a Cardenza
hello@cardenza.app