Trayza by AQERIONX
Privacy Policy
This policy explains what information Trayza by AQERIONX handles, why it is used, and how to contact us with a privacy request. It covers the Trayza website, restaurant portals, QR ordering and reservation features.
Last updated: 1 November 2026
1. Who we are and who this policy covers
Trayza is a restaurant technology service operated by AQERIONX in Jaipur, Rajasthan, India. This policy applies when restaurant owners and staff use Trayza, when guests use a restaurant’s Trayza QR ordering or reservation page, and when anyone submits a website contact or restaurant enquiry.
2. Information the service handles
Depending on the features a restaurant uses, this can include account names and email addresses; restaurant, menu, table, staff and configuration details; order items, totals and payment status; and guest names, contact details, booking times, party size and requests supplied with a reservation.
Website contact and onboarding forms can include a person’s name, email, phone number, restaurant details and message. Security and audit records may include an IP address, browser user-agent, account identifier and the action taken.
3. Location and restaurant geofencing
If a restaurant enables location-based order checks, a guest’s browser may ask for permission to share the device’s current location. When the guest allows it, Trayza processes the coordinates to check the restaurant’s configured geofence and may associate them with the order record. Restaurant owners can also enter their restaurant’s location in settings. Location is not used for background tracking by Trayza.
4. How information is used
We use information to provide and secure the service; route restaurant orders and reservations; maintain restaurant records and reports; respond to enquiries and support requests; send transaction-related email when the relevant email service is configured; investigate abuse or service problems; and meet applicable legal obligations.
5. Service providers and sharing
Information is available to the restaurant and its authorised users where needed to operate that restaurant’s service. AQERIONX also uses service providers for hosting and application delivery (Vercel), database storage (Neon), Google sign-in verification (Firebase), public menu and restaurant images (Cloudinary), private profile image storage (Vercel Blob), and email notifications (Resend, when configured).
These providers process information to provide their services to Trayza. Depending on provider configuration, information may be handled in locations outside the guest’s or restaurant’s state or country. We do not sell personal information or share it for third-party advertising.
6. Payments
Trayza can store restaurant order totals and payment status for operations and reconciliation. The current Trayza order flow records payment status; it does not ask guests to enter card or bank credentials into Trayza. A restaurant may collect payment separately and is responsible for explaining its own payment and refund practices to guests.
7. Cookies and device storage
Trayza uses authentication cookies needed to keep signed-in sessions working. The app may use browser storage for interface preferences and a TV display session. Browser settings can clear cookies or local storage, but doing so may sign users out or reset saved preferences.
8. Retention and your requests
Information is kept for as long as needed to provide the service, maintain restaurant records, resolve issues, protect the service and meet applicable obligations. Restaurant owners can view and manage operational records available to them through their account. To ask about access, correction or deletion of information, email aqerionx@gmail.com and describe the request and the restaurant or account involved. We may need to verify the request and may retain records where required or permitted by law.
9. Security and changes
We use account authentication, role-based access controls and security logging to help protect information. No internet service can guarantee absolute security. We may update this policy as Trayza changes; the date at the top shows when this version was last updated.