Privacy policy
Last updated: October 14, 2026
What we collect
Account details (name, email), menu content you upload (photos, dish details, restaurant information), and usage analytics for menus you publish. To limit repeated view and scan counts, we derive a hashed identifier from the visitor's IP address and browser information. Restaurant dashboards show aggregate counts, not individual visitor identities.
How we use it
To provide the service: digitizing menus you upload, hosting your public menu pages, generating QR codes, and showing you analytics. Menu photos are processed by an AI service (Google Gemini) solely to extract menu content.
Location search
Restaurant maps, place suggestions and address lookup use Google Maps Platform. Your browser sends search text, map-view requests and, when you choose to share them, location coordinates directly to Google. Selecting a restaurant fills an editable address and map location for you to review. The restaurant details you save, including the address, map pin and selected Google place ID, are stored with your restaurant or menu and shown publicly when you publish. A diner's selected area is used for the current browsing session, not saved to their account. Browsing location is requested when you choose “Use my current location.”
Optional table service
At participating restaurants, joining a table or calling staff can request your device's location to check proximity. These verification commands do not save raw guest coordinates. The restaurant's staff can access sent requests, accepted items and bills; your unsent cart remains private to your visit access. Accepted items and the shared table bill are visible to guests in the same party. Ask staff for help if location verification is unavailable. Invoice-sharing links grant access to anyone holding the link until they expire or are revoked.
Staff who enable background alerts register a browser push subscription for up to 30 days. The browser's notification provider, such as Google, Apple or Mozilla, delivers a generic prompt to open the service screen, not the customer's cart or invoice details.
Optional analytics
Optional website analytics are off by default and can be enabled or disabled using the setting below. They send only an action name and a broad acquisition category, not uploaded menu content or full referrer URLs. Signup, menu creation and first-publication operational counters are aggregated separately. These counters do not identify a customer's browsing history or establish a user-linked organic conversion rate.
Help us improve Qrezy by sharing which actions are used and whether visits come from search, social links or other broad sources. No uploaded menu content or full referrer URLs are sent. Off by default.
Cookies and browser storage
The marketing site does not set advertising cookies. The app uses browser storage to keep you signed in and to remember choices you make. Optional analytics preferences are saved separately on each website; choosing not to enable analytics does not prevent you from using Qrezy. Google Sign-In and Zoho Payments may use their own storage when you use those services. Google Maps receives your browser's network requests when you open a map or search for a place. See Google's Privacy Policy.
Payments
Qrezy subscription payments are processed by Zoho Payments. We never see or store your card or UPI credentials. We retain transaction identifiers, amounts, selected plans, discounts, and payment status to activate plans and support billing enquiries.
Table-service bills and cash or external-payment entries are records entered by restaurant staff. Qrezy does not process or verify those dining payments.
Uploads, backups and retention
Source scans are private; menu logos, covers and dish images intended for public display use public media links. We keep recovery backups to protect against accidental loss. Previous media versions are scheduled for removal after 30 days, so deleting an image does not immediately erase every backup copy. Database recovery backups and retained financial or audit records also require separate retention and deletion review.
Sharing
We don't sell your data. Data is shared only with the infrastructure providers needed to run Qrezy (Amazon Web Services for hosting and storage, Google for maps, place search, AI processing and optional sign-in, Zoho for payments).
Your rights
You can update your details or request account deletion in Settings. For questions about data access, deletion, or retained billing records, email support@viaom360.site with the email address associated with your account.
Business owners need a closure or ownership-transfer review before account deletion, to protect staff access, published menus and retained financial records. Contact support to arrange that review rather than relying on immediate self-service business deletion.
