Your account. Your choices.
Dineover Privacy Policy
Updated October 4, 2026 · Dineover & Dineover Partner
TML Agency operates Dineover and Dineover Partner. This policy explains how we handle information when you browse restaurant deals, manage a restaurant, reserve a table, or contact us.
The public diner and restaurant previews use sample data and do not create real bookings or take payments. These policies also describe our connected account services.
Account information
We process your email address, account identifier, name, and authentication information to create and secure your account. If you choose Google or Apple sign-in, we receive the account information you authorize that provider to share. Apple can provide a private relay email address. We do not receive your Google or Apple password. A mobile number is collected during registration and verified by SMS when the phone-verification service is available. Returning accounts with a verified number do not repeat this step. Guest browsing does not require a number. Firebase provides the one-time mobile verification after email or Google registration. Before requesting a code, we disclose that Google receives and stores the number for authentication and spam/abuse prevention across Google services. We attempt to remove the temporary Firebase sign-in account after verification; this does not remove information Google retains for its security and legal purposes.
Location and maps
Location permission is optional. If you allow it, Dineover reads your device location in the foreground to find nearby restaurants. The search coordinates are sent to our Supabase backend to calculate nearby deals. Google Maps processes map requests and may receive location, network and device information through its SDK. Opening directions sends the destination to the map service you choose. You can deny location access and choose an Edmonton area manually. We do not request background location or sell your location.
Reservations and payments
We process the restaurant, sitting time, party size, guest name, booking code, locked offer terms, check-in, cancellation and bill information to provide reservations, apply discounts and resolve issues. Restaurant staff can see the guest name, party size, booking code and reservation details for their venue. Stripe processes card information when card payment is enabled; our app backend stores payment references, fee amounts and payment/refund status rather than full card numbers. Stripe and your bank may retain payment records under their own obligations. The reservation QR contains only the booking code. Dineover Partner requests camera access when staff open the scanner; our app does not record or upload camera photos or audio. Staff review the matched reservation before confirming check-in. Manual code entry works without camera access.
Restaurant information and uploads
Dineover Partner processes business and manager contact information, addresses, menu information, listing photos and business-verification documents. Restaurant listing information and approved listing photos are public. Verification documents, which may include government identification and licences, are stored privately and used by authorized platform staff for verification. Only the files you select are uploaded; we do not need access to your entire photo library. Do not include unrelated personal information in public listing content.
Support and operational information
If you contact support, we process the information you send to investigate and answer your request. Our hosting, authentication, map, email and payment providers may process IP addresses, device information, request logs and security signals to deliver and protect their services. Account sessions and saved restaurants are stored on your device. Dining preferences currently stay within the app session. The current release does not offer advertising, cross-app advertising tracking, referral rewards, public review publishing or push-notification delivery.
In-app updates and content reports
Booking confirmations, cancellations, check-ins and confirmed payment/refund updates are stored in an account-specific in-app inbox. We record whether you have read an update. Booking updates are not sent by email. If you report a restaurant, we process the category and details you provide and the report outcome for review by authorized staff. A hidden-restaurant preference is linked to your account and filters that restaurant’s offers; you can restore it in Profile. Avoid including sensitive information that is not necessary for a report.
Who receives information
We use Supabase for authentication, database and file storage, Google for maps, optional Google sign-in and Firebase mobile verification, Apple for optional Apple sign-in, Stripe for payments, and our hosting and email providers for websites and support/authentication emails. Restaurants receive the reservation details needed to serve their own guests. Authorized TML Agency staff access information needed for support, verification and security. Information may also be disclosed when legally required or necessary to investigate fraud or protect rights. We do not sell personal information or use it for targeted advertising.
Retention and account deletion
Account information is retained while your account is active. You can initiate diner account deletion from Profile → Delete account. Upcoming reservations must be cancelled and ongoing restaurant visits completed first. Deletion removes the login and profile and clears the account’s locally saved restaurants. Historical booking and fee records are retained with the guest name removed and the account link cleared for transaction records, reconciliation and disputes. Limited moderation/security records and information we are legally required to keep may be retained. Deletion does not itself issue a fee refund; the booking’s cancellation terms still apply. Restaurant account closure also requires handling its listing, uploaded files and outstanding reservations. You can request deletion without reinstalling either app through the Account deletion page or our support address. We verify requests to protect the account holder and explain any records we must retain. Service logs and backup copies may remain until the applicable retention or backup rotation completes.
Your choices and rights
You can browse without creating an account, choose an area manually, withdraw location permission in device settings, and choose email sign-in rather than a social provider. Contact us to request access, correction or deletion of your personal information, or to ask about data retained after closure. We may need to verify your identity. The rights available to you depend on your location. Withdrawing information required for a reservation or restaurant verification may prevent us from providing that service.
Security and international processing
We use encrypted connections, authenticated access and role-based restrictions to protect information. No system can promise absolute security. Our selected Supabase project is hosted in the United States; our other providers may process information in additional countries. Information processed outside your country may be subject to that country’s laws.
Children and policy changes
Dineover is a general-audience dining service and is not directed to children under 13. We do not knowingly seek their personal information. Contact us if you believe a child has supplied information. Restaurants remain responsible for age restrictions on alcohol and other regulated items. We may update this policy and will show the updated date; material changes will be communicated as required.
Questions about this page?
Contact TML Agency at support@dineover.com. Never send passwords, verification codes or full payment-card details.