Pud.ing operates a merchant loyalty platform and related services. This page describes the data practices that are actually supported by the current implementation. Where a control is not yet implemented or not documented, this page says so directly.
1. Data processing summary
We process the minimum personal data needed to provide the service: merchant owner name, email, and phone number; shop name, address, logo, username, page slug, and shop identifier; customer name, email, phone number, membership ID, points balance, and transaction history; Shopify customer identifiers, order details, refund details, product and variant identifiers, discount code records, login/session data, webhook event data, and operational logs.
We process that data to provide the service: onboarding, account access, loyalty management, Shopify order and refund reconciliation, product-specific earning and reward rules, Shopify discount creation and validation, storefront rewards surfaces, wallet passes, notifications, support, and service operation.
We limit use of the data to those service purposes. We did not find customer-data marketing use or unrelated profiling in the codebase.
We process merchant and customer personal data under the merchant relationship for the service. Merchants are responsible for telling their customers that Pud.ing is used as an underlying rewards-system provider and that customer identity and transaction information may be shared with Pud.ing automatically through the merchant's connected systems, including Shopify and point-of-sale workflows.
We do not use customer personal data for marketing. Where Shopify or a merchant provides consent or preference signals, the service is intended to respect those signals when processing customer data.
We never sell the personal data of merchants or their customers, so opt-out-of-sale is not applicable. Customers who do not want a merchant to share their information with Pud.ing for that merchant's rewards program may ask the merchant to opt them out.
We do not perform automated decision-making with legal or similarly significant effects, so opt-out is not applicable.
We use retention controls for short-lived tokens and sessions. OTPs, login tokens, auth sessions, and Shopify installation records expire or are cleared on uninstall. We keep customer data until the shop owner or the customer asks us to delete it, unless the service removes it earlier as part of uninstall, revocation, or operational cleanup.
We serve traffic over HTTPS. We use Supabase's managed platform for the database and backups, so backup handling and encryption are covered by the managed environment and the storage and hosting services we use.
We try to separate test and production behavior as much as possible, but not every workflow or dataset is fully separated yet.
As of now, we rely on Supabase and the other services we use for the security and control features they provide; we do not have a separate documented data loss prevention program.
We limit staff access to technical, support, and security purposes. We log many sensitive identifiers as hashes rather than plaintext where practical, but not all. Staff are not permitted to use, share, or disclose customer data for unrelated purposes, except where required by law or valid legal process.
We enforce strict access controls for staff sessions and try to keep access as secure as possible to reduce the risk of theft, leakage, or unauthorized access. No system can guarantee zero incidents, so merchants and customers should also use normal account-security practices and be prepared to respond if an incident occurs.
We log request and business events, including auth, onboarding, notification, and Shopify processing events, but we do not maintain a dedicated audit log for every personal-data read.
If an incident occurs, we try to identify it quickly, contain it, and fix it as soon as practical. During that period, some services may be delayed or temporarily paused.
2. What we process
Pud.ing services and related third-party services may process merchant owner name, email, and phone number; shop name, address, logo, username, page slug, and shop identifier; merchant-customer name, email, phone number, membership ID, points balance, and transaction history; Shopify customer identifiers, order details, refund details, product and variant identifiers, discount code records, login/session state, webhook events, and operational logs. In our systems, that includes fields such as shops.rep_name, shops.rep_contact, users.email, users.phone, shop_memberships.points_balance, shopify_installations.access_token, shopify_customer_links.shopify_customer_gid, shopify_checkout_reward_redemptions.discount_code, and auth_sessions.refresh_token_hash.
3. Pud.ing services
Pud.ing's core service lets merchants create and manage loyalty memberships, points balances, earning rules, redeemable rewards, perks, customer activity, wallet passes, and customer communications. We use merchant account data to create and support shops; shop profile data to display the merchant's rewards page and customer-facing loyalty experience; customer membership data to track balances and activity; transaction and reward data to award points and redeem benefits; and login/session data to keep merchant and customer access secure.
4. Shopify data and permissions
When a merchant installs the Shopify app, Pud.ing asks Shopify for the permissions needed to run the loyalty features the merchant enables. We use Shopify customer data to link or create Pud.ing rewards memberships for that merchant; order, refund, cancellation, and order edit data to award, adjust, or reverse points; product and variant data to support product-specific earning and reward rules; discount access to create and manage amount, percentage, product, and shipping rewards; and app proxy access to show the storefront rewards experience. This processing may happen automatically when a customer shops with the merchant through Shopify or point-of-sale workflows, even if the customer did not separately register on a Pud.ing-hosted page. Pud.ing also receives Shopify privacy webhooks for customer data requests, customer redaction, and shop redaction.
5. Why we process it
We use this data to operate the loyalty program, confirm merchant accounts, sync Shopify customers, orders, refunds, products, and discounts, issue and validate login sessions, create wallet passes, process webhook events, and provide support. We do not use customer personal data for unrelated advertising or cross-context behavioral marketing.
6. Sharing
We share data only with service providers that help us run the service, such as hosting, database, email, SMS, observability, and Shopify infrastructure. We also forward some shop registration details to the merchant notification workflow configured for that shop. We never sell personal data.
7. Opt-out and data deletion
Merchants can opt a customer out of a specific shop rewards membership from the customer section of the merchant dashboard. Opting out redacts the customer-facing identity for that shop membership, disables points and rewards activity for that membership, and prevents Shopify or point-of-sale reward processing for that membership. This shop-level opt-out is scoped to the selected merchant relationship and does not remove or change the customer's memberships with other shops.
When a merchant disconnects Shopify or we receive an uninstall event, the Shopify installation tokens are cleared. When an auth session is revoked, it is invalidated. If a merchant or customer asks us to delete data beyond a shop-level opt-out, we can remove account data where that is supported by the service, but we do not yet have a fully documented global deletion workflow for every data type in the repo.
8. Data retention
Short-lived tokens expire automatically, login and access sessions are time limited, and revoked sessions can no longer be used. We keep operational and security logs only as long as needed for support, fraud prevention, troubleshooting, and legal obligations. We do not have a single documented retention schedule for all data types yet.
9. Location of site and data
The service is operated from U.S.-based infrastructure. Our code and deploy configuration are set up for U.S. hosting and U.S.-based providers.
10. When transferring personal data
If we process or store data outside a customer’s local region, we do so through the hosting and service providers used to operate the service. Merchants are responsible for the notices, consents, and permissions required for their own customers and storefronts.
11. How we secure your data
Traffic is protected in transit with HTTPS. We log many request and business events with hashed identifiers where practical. We use Supabase's managed platform for the database and backups. Encryption at rest and backup encryption depend on the Supabase-managed environment and the configuration of the storage and hosting services we use.
12. Service reliability and limits
We use reasonable efforts to keep the service working, secure, and consistent, but no system is perfect and no third-party integration is guaranteed to be error-free or continuously available. Processing can depend on systems we do not control, including hosting, Shopify, email, SMS, and observability providers. If something fails, we try to diagnose it, fix it, and reduce the chance of it happening again.
13. Updates
We may update this page from time to time as the product, infrastructure, or legal requirements change. If you need help with a privacy request, contact us at [email protected].