Shuppz Privacy Notice
What Shuppz collects in Early Beta, why it is used, how shopper intent is handled, and the controls available to users.
Shuppz is currently a pre-incorporation Early Beta project. These documents are tailored to the current Shuppz product and are intended to govern the Beta framework, but the formal operator identity, legal contact, formation jurisdiction and any jurisdiction-specific dispute provisions must be completed and reviewed by qualified counsel before production commercial launch.
1. Scope and current status
This Privacy Notice describes the personal information handled by the Shuppz Early Beta across public Beta signup, shopper accounts, merchant accounts, discovery, “I Want This,” follows and interests, Deals, Market Days, Campaign Studio, support and related product surfaces.
Shuppz is currently a pre-incorporation project. Formal controller/operator identity and legal contact details must be inserted before production commercial launch. References to Shuppz include any successor entity that lawfully assumes the project and this Notice.
2. Information Shuppz may collect
Account and identity data: name, email address, account type, verification state, authentication and security events, password hashes and one-time-code records.
Shopper intent and preference data: searches, categories, follows, interests, saved items, “I Want This” requests, price ranges, timing or distance preferences, and interactions with deals or Market Days.
Merchant and business data: business name, business type, locations, service area, products or services, typical pricing, hours, capacity or inventory information, store links, campaign choices and offer details supplied by the merchant.
Commerce and outcome data: deal claims, redemptions, completed purchase states, campaign or offer interactions and transaction-verified review activity where those features are enabled.
Communications and support data: Beta feedback, support submissions, messages and governance requests.
Technical data: IP address, browser/device information, session identifiers, security logs, timestamps and information needed to keep the service reliable and secure.
Cookie and local-storage data as described in the Cookie & Tracking Notice.
3. How Shuppz uses information
To create and secure accounts; verify email; provide authentication, password reset and account recovery; and prevent abuse.
To personalize discovery based on user-selected interests, follows and intent signals.
To surface relevant demand opportunities to participating merchants while preserving the product’s merchant-control model.
To operate Deals, Market Days, Campaign Studio, merchant profiles, Beta participation and support workflows.
To measure genuine product activity, troubleshoot defects, protect security, prevent fraud and improve the Early Beta.
To send Beta access and occasional Beta product communications requested by the user, subject to available opt-out controls.
To comply with law and enforce platform rules.
4. Shopper intent and merchant visibility
Shuppz is designed to turn shopper intent into useful marketplace signals. A shopper request may be categorized, summarized, matched, aggregated or shown in context to relevant merchants.
Shuppz should not expose a shopper’s direct contact details to a merchant merely because the shopper expressed intent. Direct identity or contact sharing should occur only when the user chooses a feature that requires it and the product clearly discloses that sharing.
Illustrative or Test Mode demand must be labeled and must not be mixed with genuine shopper activity.
5. How information may be shared
With participating merchants when needed to provide a shopper-selected marketplace interaction, subject to the limits described above.
With service providers that host, secure, deliver email, support, analyze or otherwise operate the service under appropriate contractual restrictions.
With authorities or other parties when reasonably necessary to comply with law, protect rights, investigate fraud or security incidents, or protect users.
In connection with a lawful financing, reorganization, incorporation, merger, acquisition or transfer of the Shuppz project, subject to continued protection of personal information.
Shuppz does not treat recognition of a third-party provider in the product as proof that the provider is connected or receiving data.
6. Sale, sharing and advertising
The Early Beta is not designed around selling personal information or paid cross-context behavioral advertising. Shuppz should not sell personal information or share it for cross-context behavioral advertising unless that practice is later introduced with legally required notice and choice.
Where a privacy law gives a right to opt out of sale or sharing, Shuppz will honor that right if the relevant activity and law apply.
7. Data retention
Shuppz should retain personal information only as long as reasonably necessary for the purpose collected, account security, fraud prevention, legal compliance, dispute handling and legitimate product records.
Authentication codes and other short-lived security data should have short retention periods. Marketplace and account records may be retained longer where needed to preserve transaction, audit or safety history.
A formal retention schedule should be approved before production launch and aligned with actual system behavior.
8. Security
Shuppz uses reasonable administrative, technical and organizational measures appropriate to the Early Beta, including access controls, authentication, security logging and data minimization. No system can guarantee absolute security.
Shuppz should collect only information reasonably needed for the feature being used and should avoid retaining sensitive information without a clear business need.
9. Your privacy choices and rights
You may update certain account information through available product controls and may unsubscribe from non-essential Beta product emails using the available opt-out method.
Depending on where you live and which law applies, you may have rights to know or access personal information, correct it, delete it, receive a portable copy, opt out of certain sales or sharing, limit certain sensitive-data uses, or appeal a privacy decision.
Where California privacy law applies, required notices should identify categories collected, purposes, retention practices and applicable rights. Shuppz must provide a compliant request method before it becomes subject to those obligations.
Shuppz will not discriminate against a user for exercising a legally protected privacy right.
10. Cookies and tracking
See the Cookie & Tracking Notice. Necessary cookies or storage may be used for sessions, CSRF protection, authentication, preferences and security. Non-essential analytics or advertising technologies should not be activated without the disclosures and consent required by applicable law.
11. Children
The Early Beta is not intended for children under 18 and Shuppz does not knowingly design the Beta to collect personal information from children. If Shuppz later offers a youth-facing experience, it must adopt age-appropriate safeguards before launch.
12. International use
If Shuppz offers services to people in jurisdictions with international transfer rules, it will implement the transfer mechanism and additional notices required by applicable law before relying on those transfers.
13. Changes and contact
This Notice may be updated as the Beta changes. The current version should display its effective date.
Privacy questions and rights requests should be submitted through the governance or support contact method displayed by Shuppz. A dedicated privacy contact and formal operator identity must be inserted before production launch.