Privacy Policy
Last updated: October 30, 2026
1. Introduction
This Privacy Policy explains how Trudy's Table Inc. ("we," "us," "our") collects, uses, discloses, and protects personal information when you use our reservation management platform. We follow the Personal Information Protection and Electronic Documents Act (PIPEDA) and Quebec's Act Respecting the Protection of Personal Information in the Private Sector (Law 25).
Two different roles apply, depending on whose information it is. For guest information, the restaurant is the person responsible and we act as its service provider: we handle that information on the restaurant's instructions and for no purpose of our own. For information about restaurant owners, managers, staff, and visitors to our website, we are the person responsible ourselves. Our obligations toward restaurants are set out in our Terms of Service.
2. Information We Collect
We collect the following personal information.
Guest information: phone number, name, email address, preferred language, and payment card details. Card details are tokenized by Stripe; we store only the last four digits, the card brand, and Stripe identifiers.
Reservation details: date, time, party size, seating preference, and anything written into the free-text special requests field. There is no separate dietary or allergy field on the platform, so if a guest mentions an allergy or a dietary restriction, it is stored in that free-text field.
Notes and tags recorded by restaurant staff: staff can attach internal notes and tags to a guest profile at their restaurant, such as a seating preference or a repeat-guest marker. These records are kept separately for each restaurant. A note or tag written at one restaurant is visible only to that restaurant, and never to another restaurant where the same guest has also booked. That content is written by the restaurant, and the restaurant is responsible for it.
Restaurant operator information: phone number, name, email address, restaurant details (name, address, hours, capacity), and billing information.
Staff information: phone number, name, and role within the restaurant.
Prospect information: when someone uses our no-show calculator or begins our sign-up flow, we store the phone number along with any details entered, which may include name, email address, restaurant name and address, and the figures entered into the calculator. We keep these records even when someone does not finish signing up, so that a partly completed sign-up can be resumed and so we can follow up about our product.
Contact form submissions: the name, email address, restaurant name, and message sent to us through the contact form on our website.
Usage data: how visitors interact with our marketing site and how staff use the dashboard, including pages viewed, features used, and device and browser information. Section 9 sets out where this does and does not apply.
Advertising data: if you turn on Advertising on our marketing site, the pages you view, your IP address, browser details and advertising identifiers go to Meta and Google. Section 9 explains how.
Technical records: IP addresses and account identifiers held briefly to rate limit our public endpoints and to lock out repeated incorrect PIN attempts, plus error diagnostics generated when something fails.
Communication records: reservation confirmations, reminders, offer emails, unsubscribe requests, and support correspondence.
3. How We Use Your Information
We use personal information to:
Provide and maintain the reservation management service.
Process reservations and send booking confirmations, changes, cancellations, card requests, and reminders by email and text message.
Save cards on file through Stripe and process a no-show fee when a restaurant applies one.
Maintain guest profiles and reservation history for the restaurant's guest management features.
Send offer emails on a restaurant's behalf where the restaurant uses that feature, each carrying a working unsubscribe link.
Keep the platform secure and available, through rate limiting, PIN lockout, abuse prevention, and error monitoring.
Understand how our marketing site and our staff dashboard are used, so we can improve them.
Measure our advertising and show it to people who have visited our marketing site, if they have turned on Advertising.
Respond to enquiries, follow up on sign-ups, and communicate about your account.
Meet our legal and financial reporting obligations.
4. Third-Party Services
We share personal information with the service providers below, only as needed to run the platform. Each is bound by contract to protect the information it handles.
Stripe: payment processing, card tokenization, no-show fee charges, and restaurant payouts. Stripe is PCI DSS compliant.
Supabase: database hosting and authentication. Reservation, guest, and account records live here.
Vercel: application hosting and delivery.
Telnyx: text message delivery for one-time login codes and reservation messages.
Resend: email delivery for reservation confirmations, reminders, and offer emails, and receipt of email sent to our platform addresses.
Sentry: error monitoring. Sentry is configured to send no personal information: the personal-data option is turned off, and session replay, which would record what is on screen, is deliberately not enabled because this platform handles payment flows. Diagnostics carry record identifiers, counts, and statuses only, never card data, phone numbers, email addresses, or guest names.
Upstash: a short-lived key-value store used for rate limiting and PIN lockout. It holds IP addresses and account identifiers as counters, which expire within minutes.
PostHog: product analytics, on our marketing site and on the staff dashboard only. It is never loaded on the booking widget, so a guest booking a table is not tracked by analytics. Session recording is disabled, and we do not use it for advertising.
Google: address autocomplete when a restaurant enters its address during sign-up. No guest information is sent to Google.
OpenAI: image generation for articles on our blog. No guest, staff, or operator information is sent.
Meta and Google (advertising): they receive information from our marketing site only if you turn on Advertising (see section 9). Unlike the other providers, they also use it for their own purposes, under their own privacy policies. No guest information is sent to them for advertising.
We do not sell personal information. We share it for advertising only as described in section 9, and only with your consent.
5. Where Your Information Is Processed
Our primary database is hosted in Canada, in the Canada Central region (ca-central-1), so reservation, guest, and account records are stored in Canada.
Some of the providers listed above process information outside Canada. Email received at our platform addresses is handled by Resend's inbound service in the United States (us-east-1), and PostHog runs on its United States cloud. If you turn on Advertising, Meta and Google receive information in the United States and possibly other countries. Others may process limited data outside Canada in the course of delivering their service.
Before relying on a provider that processes personal information outside Quebec, we assess the transfer as Law 25 requires, weighing the sensitivity of the information, the purpose it is used for, the protections in place, and the legal framework of the destination country. If you would like details about a specific provider, write to us at privacy@trudystable.com.
6. Data Retention
We keep personal information for as long as the account it belongs to is active, and for as long as we need it to provide the service. Guest reservation history is kept so that a restaurant can see a guest's history with that restaurant.
Deletion requests are handled manually. Write to privacy@trudystable.com and we will complete the request within 30 days, or tell you within that time why we cannot and what we are keeping. We retain information where the law requires it. Payment records may be kept for up to seven years to meet financial reporting obligations.
Technical records expire on their own: rate-limit and PIN-lockout counters within minutes, and error diagnostics within our monitoring provider's retention window.
7. Security
We use technical and organizational measures appropriate to the sensitivity of the information: encryption in transit and at rest, role-based access controls, row-level security in the database so each restaurant reaches only its own records, and phone-based authentication for staff accounts. Card numbers never reach our servers; they are collected directly by Stripe.
One point is worth knowing as a guest. The link in your confirmation email that lets you view, change, or cancel your reservation contains a random token, and that token is what proves the reservation is yours. Anyone holding the link can see and change that booking. Treat the link as private, and do not forward it to people you would not want to have that access.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
8. Your Rights
Under PIPEDA and Quebec's Law 25, you have the right to:
Access the personal information we hold about you.
Have inaccurate or incomplete information corrected.
Ask us to delete your personal information, subject to legal retention requirements.
Receive the computerized personal information you provided to us in a structured, commonly used technological format, or ask us to transfer it to another organization where that is technically feasible. This is the right to data portability.
Withdraw your consent to processing that is not necessary to provide the service.
Be informed of a decision based exclusively on automated processing, and to have it explained. We do not make such decisions today.
File a complaint with the Commission d'accès à l'information du Québec or the Office of the Privacy Commissioner of Canada.
To exercise any of these rights, write to us at privacy@trudystable.com. Where your request concerns a restaurant's guest records, we will pass it to the restaurant responsible for those records and help that restaurant answer you.
9. Cookies and Tracking
Cookies are small files stored on your device. We also use similar technologies, such as your browser's local storage. The list at the end of this section names the main ones.
On our marketing site and blog, a banner asks for your choice on your first visit. Until you choose, and if you reject non-essential cookies, only essential cookies are stored on your device and no advertising tag loads. You can accept all, reject non-essential, or choose by category.
Essential: these keep the site working, keep staff signed in, and remember your language and your cookie choices. They are always on.
Analytics (PostHog): with your consent, PostHog recognizes your browser between visits so we can see what is useful on the site. Without your consent, including after you reject, we still count visits and clicks anonymously: nothing is stored on your device, and PostHog, on its United States cloud, receives your IP address to produce that count.
Advertising (Meta and Google): with your consent, we load the Meta Pixel and the Google Ads tag. They tell Meta and Google which pages you view on our site, along with your IP address, browser details and the identifiers in their cookies, and those companies may connect this to an account you have with them. We use this to measure our ads and to show them to people who have visited our site. Without your consent, neither tag loads.
You can change your choices at any time with the "Cookie settings" link in the footer of our site. Your choices are kept for one year, and then we ask again. Turning a category off deletes the cookies it set on our site and stops new information from being sent once the page reloads. It does not remove you from an advertising audience you have already joined: that membership ends on its own. To manage the ads you see, use your Google ad settings (myadcenter.google.com), your Meta ad preferences (facebook.com/adpreferences) or the Digital Advertising Alliance of Canada's tools (youradchoices.ca).
On the staff dashboard, analytics runs without a separate banner, on the basis of the Terms of Service accepted when the account was created. This applies to restaurant staff, not to guests. No advertising tags run there.
On the booking widget there is no analytics and there are no advertising tags: no banner and no tracking by us. A guest booking a table is not analytics-tracked. When a guest reaches the card step, Stripe sets essential cookies to prevent fraud.
Session recording is disabled everywhere.
Cookies and similar technologies
| Name | Provider | Purpose | Lifetime |
|---|---|---|---|
| Essential | |||
tt_cookie_consent | Trudy's Table | Remembers your cookie choices | 1 year |
locale | Trudy's Table | Remembers your language | 1 year |
sb-…-auth-token | Supabase | Keeps staff signed in | Up to 400 days |
trudys-nav-collapsedLocal storage | Trudy's Table | Remembers the dashboard menu state | Until deleted |
freshLoginSession storage | Trudy's Table | Handles the PIN step after login | Until the tab closes |
themeLocal storage | Trudy's Table | Remembers the dashboard display mode | Until deleted |
__stripe_mid | Stripe | Prevents fraud when a card is entered | 1 year |
__stripe_sid | Stripe | Prevents fraud when a card is entered | 30 minutes |
| Analytics | |||
ph_…_posthogCookie, local and session storage | PostHog | Recognizes your browser between visits | 1 year |
| Advertising | |||
_fbp | Meta | Identifies your browser for advertising | 90 days |
_fbc | Meta | Records the ad click that brought you here | 90 days |
multiFbcLocal storage | Meta | Records the ad click that brought you here | Until deleted |
lastExternalReferrerLocal storage | Meta | Records the site that sent you here | Until deleted |
lastExternalReferrerTimeLocal storage | Meta | Records when that site sent you here | Until deleted |
_gcl_au | Measures ad conversions | 90 days | |
_gcl_aw | Records the ad click that brought you here | 90 days | |
_gcl_lsLocal storage | Measures ad conversions | Until deleted | |
This list reflects the tools we use as of the date at the top of this policy. Meta and Google can also set cookies on their own domains, as described in their privacy policies.
10. Children's Privacy
Trudy's Table is not directed at children under 13. We do not knowingly collect personal information from children. If we learn that we have collected information from a child under 13, we will delete it promptly.
11. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email, through the platform or on our website. The "Last updated" date at the top of this page shows when the policy was last revised.
12. Contact
If you have questions about this policy or about our data practices, write to us at privacy@trudystable.com.
The person responsible for the protection of personal information at Trudy's Table is our Privacy Officer, who can be reached at the same address.
If you are not satisfied with our response, you may contact the Commission d'accès à l'information du Québec or the Office of the Privacy Commissioner of Canada.