Report what happened today, not what you assume.
A small, firsthand signal is more useful than a confident guess. Reports stay separate from the dated source record.
Useful reports are firsthand
- Choose “Worked” only after a Paze checkout worked for you at that restaurant.
- Choose “Unavailable” only when Paze was not offered during a current checkout attempt.
- Use “Ordering issue” for a broken or unusable ordering path.
- Choose “Looked closed” only when the restaurant appears closed at the time of your attempt.
Do not submit
- Names, phone numbers, card details, order numbers, or other personal information. The report has no free-text field for a reason.
- Rumors, secondhand claims, promotions, reviews, advertising, or disputes with a restaurant.
- Automated, repeated, coordinated, deceptive, abusive, or unlawful submissions.
How reports are handled
A pseudonymous random identifier in an HttpOnly cookie limits duplicate reports. The site displays aggregated counts from the last 30 days, not individual identities. Reports are deleted after 90 days and may be removed earlier when they appear abusive or conflict with the dated source record.
The dated record stays separate
A community report does not change the Paze configuration record date shown for a restaurant. The two signals answer different questions: what Clover payment-configuration reported on the recorded date, and what a visitor recently experienced.
Common questions
What happens to a report after I send it?
It is stored as a restaurant, the outcome you chose, the report time, and a hashed pseudonymous identifier. It is shown as a 30-day count and deleted after 90 days.
Can a report change a restaurant’s observation date?
No. Community counts sit beside the dated source record and never overwrite it. The two answer different questions.