Shuppz Feedback & Ideas Policy
How Shuppz may receive and use voluntary product feedback, feature ideas and Beta observations without confusing feedback with shopper intent, merchant offers, support cases or confidential business information.
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. Purpose and scope
Shuppz is an Early Beta, dual-sided marketplace built around shopper intent, discovery and merchant-controlled responses. Feedback from shoppers, merchants and other participants can help Shuppz improve the product, but product feedback must remain legally and operationally distinct from shopper demand signals, merchant offers, transactions, support requests and confidential business information.
This Feedback & Ideas Policy applies when you voluntarily send Shuppz suggestions, comments, feature requests, product ideas, interface observations, workflow ideas, Beta survey responses or similar product-development feedback through a Shuppz feedback form, Beta research interaction or other channel that clearly identifies the submission as feedback.
This policy does not replace the Terms of Use, Privacy Notice, Early Beta Terms, Merchant Terms or other applicable Shuppz policies. If another policy applies to a particular activity, that policy continues to govern.
2. What Shuppz treats as feedback
Feedback includes voluntary suggestions about Shuppz discovery, search, following, interests, “I Want This,” demand-signal presentation, shopper feeds, merchant opportunity review, Commerce Profile, Campaign Studio, Deals, Drops, Flash Events, Clearance, Launches, service or dining windows, Market Days, transaction-verified reviews, account security, passkeys, email verification, login OTP, governance pages, accessibility, navigation, onboarding and similar Shuppz product or marketplace features.
Feedback can also include ideas about how an existing Shuppz workflow could be clearer, safer, faster, more useful or better suited to a shopper, merchant, artisan, creator, restaurant, local business or other participating business category.
Feedback may be positive or negative. A bug report can include feedback, but security vulnerabilities, suspected account compromise and privacy-rights requests should use the appropriate security, support or privacy channel instead of an ordinary product-feedback form.
3. What is not feedback
A shopper’s search, follow, saved interest, “I Want This” request, price range, location preference or other expression of shopping intent is marketplace activity, not a product-idea submission under this policy.
A merchant’s product, price, inventory, service capacity, Deal, Drop, Flash Event, Clearance, Launch, Market Day participation, Campaign Studio configuration or other commercial response remains merchant-controlled commerce activity and is not transferred to Shuppz merely because it appears in the platform.
A completed purchase, redemption, fulfillment event, transaction-verified review, support case, security incident, privacy request, legal notice, partnership proposal, investment proposal, employment application or confidential business communication is not ordinary product feedback under this policy.
Shuppz will not use this policy to convert a shopper’s marketplace intent, a merchant’s inventory or commercial offer, or a user’s pre-existing copyrighted content into Shuppz-owned intellectual property.
4. Voluntary submissions; no confidential relationship
Unless Shuppz has signed a separate written confidentiality agreement that expressly covers the submission, product feedback and ideas submitted through ordinary Shuppz feedback channels are voluntary and should be treated as non-confidential.
Do not submit trade secrets, source code you do not want disclosed, unpublished patent material, confidential customer lists, merchant pricing formulas, private contracts, credentials, one-time codes, payment credentials or information that you are not authorized to disclose.
Submitting feedback does not create a fiduciary, advisory, employment, partnership, agency or confidential relationship between you and Shuppz.
5. Your existing rights and the license you give Shuppz
You retain ownership of intellectual property that you owned before submitting feedback. Shuppz does not claim ownership of your pre-existing business, brand, product, copyrighted work, confidential know-how or other rights merely because you provide feedback.
By voluntarily submitting feedback, you grant Shuppz and any lawful successor operator a perpetual, irrevocable, worldwide, non-exclusive, transferable, sublicensable, royalty-free license to use, reproduce, analyze, modify, adapt, combine, create derivative works from, develop, test, commercialize, distribute and otherwise exploit the feedback for Shuppz products, services, marketplace operations, research, documentation and business purposes.
This license allows Shuppz to implement an idea without having to seek additional permission from or make additional payment to the person who submitted it. It also allows Shuppz to combine feedback from many participants into a broader product design.
Where applicable law does not permit a particular waiver or license term to operate as written, the term applies to the maximum extent permitted by law.
6. No promise of payment, equity, royalties or credit
Unless Shuppz expressly agrees otherwise in a separate signed written agreement, submitting feedback does not entitle you to payment, a reward, equity, revenue share, royalty, licensing fee, founder status, advisory status or ownership of a feature that Shuppz later builds.
Shuppz is not required to publicly credit or identify a feedback contributor. Shuppz may choose to thank or recognize Beta participants, but recognition does not create additional ownership or compensation rights.
If Shuppz intentionally runs a separate paid research, bounty, advisory or design-partner program, the written terms of that program control over this general policy for submissions made under that program.
7. Independent development and similar ideas
Shuppz may already be researching, designing or building features that are the same as or similar to a submitted idea. Other shoppers, merchants, team members, contractors or third parties may independently submit similar concepts.
A later Shuppz feature that resembles submitted feedback does not by itself establish that Shuppz copied a protected idea, accepted a confidential obligation or owes compensation.
Shuppz may decide not to use feedback, may use only part of it, may implement a different solution, or may discontinue an experiment at any time.
8. Shopper-specific feedback
Shoppers may provide product feedback about discovery, following, interests, Market Days, Deals, Drops, “I Want This,” relevance, accessibility, account security and other shopper experiences.
A shopper’s feedback about how Shuppz should work is different from the shopper’s actual marketplace intent. For example, “I wish I could filter Market Days by distance” is feedback; “I want a patio set under $700 within 20 miles” is a shopper intent signal.
Shuppz may use shopper feedback to improve product design while handling personal information and marketplace-intent data under the Privacy Notice.
9. Merchant-specific feedback
Merchants may provide feedback about Commerce Profile, demand-signal presentation, Campaign Studio, Deals, Drops, Flash Events, Clearance, Launches, service or dining windows, Market Days, merchant controls, reporting, verified reviews and other business workflows.
A merchant’s suggestion that Shuppz add a new campaign format or dashboard feature is product feedback. The merchant’s actual products, inventory, capacity, prices, margins, campaign terms and customer relationships remain governed by the Merchant Terms, Privacy Notice and other applicable agreements.
Merchants should not place confidential pricing formulas, trade secrets, customer lists or other competitively sensitive material in an ordinary feedback submission.
10. Feedback about marketplace mechanisms and new features
Because Shuppz is developing demand-led marketplace mechanics, feedback may relate to how shopper signals are aggregated, how businesses discover opportunities, how Market Days group participating businesses, how Campaign Studio presents response formats, or how transaction-verified reviews are displayed.
Submitting such feedback does not give a contributor control over the Shuppz roadmap or a proprietary right in the marketplace mechanism. Shuppz retains responsibility for deciding whether a proposed mechanic is technically, commercially, legally and ethically appropriate.
Shuppz will not represent feedback-driven experiments as guaranteed demand, guaranteed revenue, guaranteed conversion or guaranteed inventory reduction.
11. Beta feedback and product telemetry are different
Voluntary feedback is information you intentionally submit as feedback. Operational telemetry, login-security events, device information, marketplace activity and product analytics are separate categories of information and are handled under the Privacy Notice and applicable product terms.
Shuppz will not label routine security logging or marketplace events as voluntary feedback merely to expand rights over that information.
Sample or Test Mode activity must remain clearly identified and is not treated as genuine participant feedback or real marketplace activity unless a real participant actually submits feedback about it.
12. Privacy, personal information and attribution
Feedback may include your name, email, account type, business identity or other personal information. Shuppz processes that information under the Privacy Notice and for legitimate Beta support, research, product-improvement, security and governance purposes as applicable.
The license in this policy does not automatically authorize Shuppz to publish your private contact information, use your name or business as a testimonial, or imply your endorsement. Public attribution or testimonial use requires an appropriate separate permission or other lawful basis.
Do not include personal information about another person unless you are authorized to provide it.
13. Third-party rights and lawful submissions
You should submit only feedback that you are legally permitted to provide. Do not copy another company’s confidential roadmap, proprietary source code, protected design or other third-party material into Shuppz feedback.
You represent that, to your knowledge, your voluntary feedback submission does not knowingly violate another person’s intellectual-property, privacy, confidentiality or contractual rights.
Shuppz may remove, disregard, quarantine or restrict feedback that appears unlawful, abusive, malicious, deceptive, infringing or unsafe.
14. Security reports, account incidents and urgent matters
Do not use the ordinary feedback channel to send passwords, passkeys, private keys, authentication codes or payment credentials.
A suspected account takeover, unexpected login OTP, security vulnerability, privacy incident or other urgent account-security matter should be submitted through the Contact Shuppz account-and-security channel or another security channel Shuppz designates.
Shuppz may reclassify a feedback submission as a support, security, privacy or legal matter when that is necessary to route the issue appropriately.
15. No obligation to review, respond or implement
Shuppz may review and prioritize feedback in its discretion. Beta participation does not guarantee that every submission will receive an individual response or that any feature will be built.
Shuppz may retain feedback for a reasonable period to evaluate product patterns, investigate issues, maintain governance records or defend legal rights, subject to the Privacy Notice and applicable law.
Where Shuppz provides a response, that response does not create a promise to implement the suggestion or a commitment to a release date.
16. Changes to this policy and questions
Shuppz may update this Feedback & Ideas Policy as the Beta evolves, particularly when new feedback channels, paid research programs, merchant programs or product-development processes are introduced.
Material changes should be reflected through an updated date and, where appropriate, additional notice.
Questions about this policy can be submitted through Contact Shuppz. Legal, privacy and security matters should be identified as such so they can be routed appropriately.