1. Sign-in and account information
You can browse the public plaza without signing in. Participation uses Google sign-in or an email address and password. Email accounts need verification.
Firebase Authentication provides identity verification. Walletwait uses an account identifier to associate your profile and activity records, and handles the nickname and avatar you choose. Passwords are handled by the authentication service; purchase-discussion API endpoints do not receive your email password.
The website does not require your legal name, identity document number or bank card details.
2. Content you submit
The service handles the item names, amounts, currencies, buying reasons, alternatives, images and opinions you submit. It also handles group membership, votes, flowers, spectator activity, blocked words, reports and feedback as needed for those features.
The contact field in feedback is optional. Avoid sending passwords, verification codes, identity document numbers or sensitive information unrelated to your discussion.
3. What other people can see
The plaza is public. People who are not signed in may read content posted there. Group content is shown according to membership and participation permissions. Sharing, viewing and interaction records follow the rules shown for the relevant feature.
The plaza limits some identity details in the interface, but account identifiers are still used to manage access, reservations and votes. This does not mean all content or activity is untraceable. Check your text, images and sharing scope before publishing.
4. Browser storage
Browser storage helps retain sign-in state, editing drafts, currency preferences and interface hints. Clearing browser data may sign you out or remove unsubmitted work. Use the account page to sign out after using a shared device.
5. Technical services and analytics
The current website stores purchase-discussion records and uploaded images on a VPS server. Firebase Authentication handles sign-in. Necessary request information is also processed for permission checks, rate limits and troubleshooting.
When Firebase Analytics is enabled, the website records page visits, sign-in steps and actions such as posting a decision, voting, withdrawing or sending a flower. A signed-in account identifier may be used to distinguish activity. Analytics events do not include the text of buying reasons, review opinions or feedback. Firebase services process the information needed under their configuration.
6. Updating, deleting and signing out
The relevant pages let you edit your profile, withdraw pending decisions, remove your content or leave groups, subject to the record state and the feature's instructions.
The account page offers account deletion. Confirmation revokes business access and starts cleanup of the associated profile, uploads and personal records. Group history may retain processed interaction results. Cleanup can happen in stages, and content another person has already saved cannot be recalled on their behalf.
7. Questions and updates
For questions about data, feedback or deletion, use our contact page or email hi@Walletwait.app. The Walletwait official development team will update this notice when the service's data handling changes.