Shuppz Early Beta Terms
Rules for early access, product changes, feedback, sample data and Beta expectations.
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. Beta purpose
The Shuppz Early Beta gives shoppers and businesses access to a real but evolving product so Shuppz can learn what creates value before broader release.
Beta access is not a promise that every feature will be available to every participant or that a feature will remain unchanged.
2. No purchase or payment required to join the current Beta
The current Early Beta signup is free to join and does not require payment. This does not promise that all future Shuppz services will be free.
If Shuppz introduces paid features, pricing and payment terms must be presented separately before a user incurs a charge.
3. Experimental features and availability
Beta features may contain bugs, incomplete workflows or test-mode data and may be modified, paused or removed.
Shuppz does not promise a service-level commitment, uptime percentage, backup guarantee or uninterrupted availability during the Early Beta.
4. Sample, simulated and genuine activity
Sample or simulated activity may be used to explain the product, but it must be visibly identified. It must not be presented as genuine shopper demand, genuine merchant performance, real reviews or real transactions.
Live Mode should rely on genuine activity and fail closed rather than fabricate marketplace evidence.
5. Early recognition and access
Shuppz may record that an account joined during the Early Beta period. That recognition is descriptive only and does not create equity, ownership, cash value, lifetime pricing, ranking priority, exclusive territory or guaranteed future benefits.
Access may be limited for security, capacity, legal, abuse-prevention or product reasons.
6. Feedback
Participants are encouraged to report defects and suggest improvements. Shuppz may use voluntary feedback to improve the product without payment or attribution.
Feedback does not transfer ownership of a participant’s unrelated confidential information, business methods or pre-existing intellectual property.
7. Confidential features
The public Early Beta is not subject to a blanket confidentiality obligation. If Shuppz provides a specific unreleased feature under a confidentiality notice or separate NDA, that notice or agreement controls for that material.
8. Beta conduct
Participants must not probe, exploit or publish security vulnerabilities in a way that harms users or the service. Good-faith security reports should be made through the support or governance contact method displayed by Shuppz.
Participants must follow the Terms of Use and Acceptable Use Policy.
9. Data and account continuity
Shuppz may migrate, reset or modify Beta data when reasonably necessary to maintain the service. Where feasible, Shuppz should avoid deleting genuine user data without notice.
A Beta account may later be migrated to a successor production service under updated terms.
10. Pre-incorporation status
Shuppz is currently a pre-incorporation project. These Beta Terms are intended to travel with the project to a successor entity when lawfully formed and assigned.
The formal operator name, governing law and legal contact must be finalized before production commercial launch.