Clear rules for a civic chai network.

User accounts store a name, email address, optional age, and app role so the right dashboard can load.

Survey responses store the user ID, question ID, selected answer, submission timestamp, and stall ID when a response came from a specific partner stall.

Stall records store the stall name, stall ID, location, owning account, and creation timestamp so QR-based participation can be routed correctly.

The site does not present public profile pages, public response histories, or a public user directory.

Use one account per participant. Role changes are handled from the admin dashboard rather than through self-service registration.

Partner stalls should use unique stall IDs. That ID becomes part of the survey and reward flow, so collisions break attribution.

Responses are intended for real civic participation. Spam submissions, fake stalls, and impersonation are grounds for account removal from the app database.

Rewards shown on completion are app-generated participation tokens tied to the most recently completed prompt.

The app uses semantic forms, visible labels, high-contrast action states, and responsive layouts for mobile and desktop routes.

Interactive survey and dashboard actions are available through standard buttons, links, and form controls instead of canvas-only interfaces.

If a QR code cannot render, the reward and shop routes fall back to readable text content so the flow still remains usable.

Support requests can be sent to support@chaithepeople.app.