Privacy Policy
Last updated 18 November 2026
This policy covers restaurantguests.com, operated by Restaurant Guests Co., Ontario, Canada. Questions or requests: [email protected] or +1 437-525-0595.
1.What we collect
- What you give us — name, email, phone, restaurant name and location, and anything else you enter when you submit the form, book a call, or message us.
- What we collect automatically — IP address, browser, pages viewed and referring site, and advertising cookies and identifiers.
We do not ask for payment card details, government ID, or sensitive personal information through this website.
2.Why we use it
To reply to you, assess whether your restaurant is a fit, contact you about our services, deliver our services if you become a client, measure how our advertising works, and meet legal obligations. We do not sell your personal information.
3.Email and SMS
If you give us your number or submit the form, we may contact you by phone, email and text message. Message frequency varies. Message and data rates may apply. Reply STOP to opt out, or HELP for help. You can also use the unsubscribe link in any email, or contact us. Carriers are not liable for delayed or undelivered messages.
No mobile information is shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with anyone, other than the providers who deliver the messages for us.
We handle marketing messages in line with Canada's Anti-Spam Legislation (CASL) and the U.S. CAN-SPAM Act and TCPA.
4.Who we share it with
Only with the service providers who help us operate, and only for that purpose: LeadConnector / HighLevel (forms, calendar, CRM, email and SMS), Meta and Google (advertising and measurement, excluding the mobile data described in section 3), our website host, and Anthropic (Claude, our AI assistant, which processes the client ad data described in section 6). We may also disclose information where required by law, or in connection with a sale of our business. Some providers are based in the United States, so your information may be processed outside Canada, under contractual protections comparable to our own.
Where we send messages to your guests on your behalf as your service provider, we use that guest data only to deliver your campaigns, never for our own marketing, and we return or delete it when our engagement ends.
5.Cookies and advertising
We use cookies necessary for the site and its embedded form and calendar to work, and the Meta Pixel to measure which ads lead to enquiries and to show ads to people who have visited this site. You can block or delete cookies in your browser, and control ad targeting in your Facebook and Instagram ad preferences and your device's advertising settings — though parts of the site may then not work.
6.Ad account data from Meta (Marketing API)
We run an internal tool, "Claude Reporting", that connects to Meta's Marketing API. It is not a public app, and no one logs in to it but us.
What it reads. Only the Facebook and Instagram ad accounts that a client has shared with our Meta business portfolio. From those accounts it reads: campaign, ad set and ad settings; budgets and spend; results such as reach, impressions, clicks, leads, messages and purchases; ad text, images and videos; and audience totals by age group, gender, placement and region. These totals never identify a single person. The tool does not read anyone's profile, friends, messages or contact details.
What it does. With the client's approval, it creates and changes campaigns, ad sets and ads in that client's ad account. New campaigns start paused, and nothing runs until the client or we approve it.
Why. Only to plan, run, and report on that client's own advertising. We never use one client's data for another client, never sell it, never use it to build profiles of people, and never use it to train AI models. We share a client's results in our own marketing, as a case study, only with that client's written approval.
Who processes it. Our team, and Anthropic (Claude), which reads the data to write reports and draft campaigns for us. We share a client's data with no one else except that client, unless the law requires it.
How long we keep it. The tool fetches data when we need it and keeps no separate database. We keep the reports we make for a client only while we work together. We delete them, and remove the tool's access to that ad account, within 30 days after the engagement ends, after the client removes our access in Meta Business Settings, or after the client asks.
How to ask for deletion. Email [email protected] with the subject "Delete Meta data" and the name of the ad account. We confirm deletion within 30 days. A client can also cut our access at any time in Meta Business Settings, under Accounts > Ad accounts.
7.How long we keep it
Enquiry records: up to two years, or less if you ask us to delete them. Client records, such as contracts and invoices: for the length of our engagement and seven years afterwards, to meet tax and legal requirements. Ad account data from Meta is not a client record for this purpose; we keep it only as section 6 says.
8.Your rights
You can ask what we hold about you, ask us to correct or delete it (including data from Meta, as section 6 explains), withdraw consent to marketing at any time, and complain to a regulator. Email [email protected] and we will respond within 30 days. We may need to verify who you are first.
In Canada, PIPEDA applies and you may complain to the Office of the Privacy Commissioner of Canada. If a breach creates a real risk of significant harm, we will notify you and the regulator as the law requires. In California, the CCPA/CPRA gives you rights to know, delete, correct, and to opt out of the sale or sharing of your information — we do not sell it, we honour Global Privacy Control signals for advertising cookies, and we will not treat you differently for exercising these rights.
9.Security and changes
We use reasonable measures to protect personal information and limit who can access it, though no system is completely secure. We may update this policy; the date at the top shows when it last changed.