TADE
Français

Guest Privacy Policy

Last updated: October 5, 2026

TADE TECHNOLOGIES INC. operates Tade from Vancouver, British Columbia, Canada. This policy explains how guest information is handled when you browse a restaurant page, make or manage a reservation, join a waitlist, receive related messages, or contact us. Contact us at support@thetade.com.

This is the guest policy. Restaurant owners and staff using the admin website or manager app should read the Operator Privacy Policy and Operator Terms of Service. Guest use is covered by our Guest Terms of Service.

1. Tade and the restaurant

The restaurant decides how to manage its bookings, waitlists, guest relationships, and staff access. Tade processes guest information to provide those tools on the restaurant's behalf. Tade also uses limited information for service delivery, security, abuse prevention, support, consent and opt-out records, and legal obligations. A restaurant's independent use of information is also subject to its own privacy practices.

2. Information collected

Optional notes may contain sensitive information you provide, such as allergies, dietary requirements, or accessibility needs. Include only what the restaurant needs for your visit, and avoid unnecessary medical or other sensitive details. Confirm important requirements directly with the restaurant.

3. A profile for later visits to the same restaurant

A booking or waitlist entry can create or update a guest profile for that restaurant. Tade can match a later online or staff-entered request to an existing profile using a phone number or email address. This lets the restaurant recognize returning guests and reuse contact details, names, preferences, and notes while viewing past and upcoming activity.

The information is therefore not used only for the single reservation in which you first supplied it. Staff can review and correct the profile and add service notes. Existing contact details may be retained when a later submission differs; contact the restaurant if details are wrong or shared with another person. These profiles are scoped to the restaurant, rather than a shared guest directory available to every restaurant using Tade.

4. How information is used

We use information to process requests, manage availability and queues, provide booking links, show visit history, support staff service, deliver authorized operational messages, address support requests, and protect the service. Restaurants may use attendance history and restrictions when deciding whether to accept future requests. Tade does not sell guest personal information or share it for cross-context behavioral advertising.

5. Reservation emails and text messages

Where notifications are enabled and the required authorization applies, Tade uses the email address recorded for a booking to send confirmations, material changes to party size, date or time, cancellations, and reminders. Staff may record your request to receive emails for a reservation they enter. Not every edit creates a message, and delivery is not guaranteed. An email already sent cannot be recalled.

Email authorization is specific to the reservation, address, and disclosure version. Tade checks the current authorization again before dispatch. Changing the address requires the applicable authorization to be renewed; an address saved in a guest profile alone is not permission for messages about a later booking.

Tade sends transactional SMS text messages on the restaurant's behalf where texting is enabled and consent applies. Providing an optional phone number for an online reservation does not itself opt you into reservation SMS. Waitlist texts and eligible staff-created reservation texts have separate consent flows. The notice presented when you join or give consent describes the applicable messages. Message frequency varies, typically one to three messages per waitlist visit or staff-created booking. Message and data rates may apply. Consent to SMS is not a condition of purchase. Reply STOP to opt out at any time, or HELP for help. You may also contact the restaurant or us.

We do not send marketing or promotional text messages. No mobile information or text-message opt-in data is shared with third parties or affiliates for marketing or promotional purposes. Messaging providers receive information necessary to deliver transactional messages. We keep consent and suppression records to respect your choices; withdrawing SMS consent does not automatically delete your guest profile or cancel your reservation.

For the current Toll-Free texting flow, a number that opts out remains blocked until START or UNSTOP restores Toll-Free messaging. A reply of YES does not unblock Toll-Free delivery. Restoring delivery does not create permission for marketing or replace the consent needed for a particular reservation or waitlist visit.

Tade does not sell mobile information, text-message opt-in data, or consent evidence. Information needed for message delivery and compliance may be shared with messaging aggregators and providers (including Twilio and participating carriers). Twilio or a carrier may request relevant consent proof for a compliance review. These disclosures do not authorize third-party marketing or promotional use.

In staff-assisted SMS consent, the guest must personally read and check the current electronic disclosure. Restaurant staff must not check it for the guest. Permission is tied to the specific phone number and visit; changing a number requires the applicable consent again. The online waitlist flow does not offer a join-without-SMS option; ask the restaurant about another way to wait.

6. Who receives information

The relevant restaurant and its authorized staff can access information needed to manage your visits. Tade personnel and service providers may process information to operate and support the service. Providers include:

If you choose Add to Calendar in a reservation email, your browser opens Google Calendar with the booking name, party size, restaurant name and location, and reservation date and time. If you import the attached calendar file into another calendar service, that service receives the event details you choose to import. Calendar providers handle and retain this information under their own privacy and retention policies. Deleting information from Tade does not delete the calendar copy.

We may also disclose information when required by law or reasonably needed to protect rights, investigate misuse, respond to a security incident, or complete a business transfer with appropriate privacy protections. Restaurants and providers may retain their own records.

7. International processing and browser storage

Information may be processed in Canada, the United States, or other countries where providers operate, and may be accessible under those countries' laws. Opening tade.ca does not guarantee storage or processing exclusively in Canada.

Non-production test websites are for synthetic test information only and must not be used to submit information about a real guest or make an actual booking.

Essential browser storage can remember an active waitlist link and other service state. Management links contain tokens that provide access to the associated request; keep them private. Hosting and security systems process technical request data. Clearing browser storage may remove saved access on that device but does not delete restaurant records. This service storage is separate from advertising profiling.

The saved waitlist link has no fixed browser-side expiry; the application removes it in certain completed or invalid states, or you can clear it. Website and API hosting providers process management tokens as part of request paths. Booking submissions also use a random duplicate-submission key; anyone holding that key may retrieve the limited booking result while its server record remains available. Treat these identifiers like private links. We do not use advertising pixels or behavioural analytics on the guest pages, and do not request your device GPS location.

8. Retention and deletion

Retention depends on operational purpose, restaurant activity, legal obligations, disputes, and security needs. Where enabled, an automated routine is designed to anonymize restaurant guest profiles after more than three years of inactivity. Activity and active requests affect eligibility; this is not a guarantee that every record is erased on a fixed anniversary.

The guest deletion flow uses a one-hour confirmation link sent to your email for the selected restaurant. Once confirmed and processed, it cancels reservations still marked upcoming or seated and waitlist entries still marked waiting, notified, or confirmed, clears identifying profile details and notes, removes saved name aliases, and invalidates existing management links. Historical operational records may remain with identifying fields removed. Cancellation alone does not delete your profile.

Pending reservation-email delivery payloads have a maximum active lifetime of 24 hours, with earlier expiry or removal possible. That delivery limit is not the retention period for the reservation, consent evidence, or an email already delivered. Certain temporary request and duplicate-submission records become eligible for cleanup after 24 hours. With a normally running daily cleanup, physical retention can approach 48 hours for those 24-hour records. Disabled jobs, failures, processing limits, or records still in use can delay cleanup; this is not a guaranteed maximum for every record.

Exceptions include limited deletion, delivery, consent, and security records; protected contact fingerprints used to enforce restaurant restrictions; and the phone-based suppression record needed to honor STOP requests. Each stored restriction fingerprint has an expiry of up to five years from that record's creation, with physical removal subject to cleanup. A later replacement record or a restaurant's continuing restriction can last beyond the original record; this is not a promise that every restriction ends five years after it was first recorded. Suppression records can remain longer. Masked or protected records are not necessarily legally anonymous. Backups, previously delivered messages, and copies held independently by restaurants or providers may remain subject to their retention processes; deletion is not an instant purge of every copy.

Reservation-email authorization has an append-only ledger containing the authorization method and version, a masked address, a keyed matching digest and key version, contact version, internal references, and timestamps. It does not store a readable full email address, and it has no automated deletion schedule. Historical evidence is not proof that you accepted a later disclosure. SMS consent and suppression evidence may also remain after the visit or delivery record is removed.

Eligible completed email-delivery metadata is cleaned up after 90 days from creation; eligible SMS-delivery metadata uses 90 days from its last update. Unresolved failures are retained until acknowledged and otherwise eligible. Consumed SMS provider-status records use 90 days from consumption. Cleanup failures or limits can delay removal, and these rules do not erase consent evidence, emails already received, or provider and backup copies.

9. Your choices, rights, and safeguards

Contact the restaurant to correct booking details or discuss its guest records. Contact support@thetade.com for access, correction, deletion, consent withdrawal, privacy questions, or help directing a request. If you cannot use email verification, ask us for assistance. We may need to verify identity and restaurant context. Applicable law may provide additional rights or a right to complain to a privacy regulator. Some requests are subject to lawful retention or other exceptions.

You may contact the Office of the Information and Privacy Commissioner for British Columbia or the Office of the Privacy Commissioner of Canada, as applicable. We do not penalize people for exercising applicable privacy rights.

We use access controls and other technical and organizational measures intended to protect information. No service, transmission, or storage system is completely secure. We will assess suspected incidents and provide notices where required by applicable law.

We may update this policy as the service or its processing changes. The date above identifies this version; material changes will receive additional notice where appropriate or required.

Privacy Officer
TADE TECHNOLOGIES INC.
Vancouver, British Columbia, Canada
support@thetade.com