Legal · medievalttimesise.cc
Privacy Policy
At a glance. Toronto Castle Dinner Guide is an independent visitor guide. Toronto Castle Dinner Guide is an independent visitor guide, not affiliated with any dinner theatre or its operator. We do not sell tickets and never process payments. We do not run Google Analytics, Google Ads tags, Meta Pixel, or TikTok Pixel on these pages. The only cookie we may set is a strictly necessary session cookie from the web server. Questions: [email protected].
1. Who is responsible
Publisher / data controller: Toronto Castle Dinner Guide, an independent editorial project at medievalttimesise.cc.
Email: [email protected]
Place of publication: Toronto, Ontario
There is no company behind this site. If you are in Canada, the EEA, the United Kingdom, or Switzerland, use the same address for PIPEDA / GDPR / UK GDPR requests. This is not the privacy notice of any dinner theatre or its operator.
2. Scope
This Policy covers https://medievalttimesise.cc only — the editorial pages you are reading now. It does not cover any operator, ticket vendor, payment processor, or any site we merely link to.
3. What we collect
3.1 You send us
If you write to [email protected], we receive your email address, message, and the time it arrived. We do not operate a public web form. Do not send card numbers, passport scans, or booking references. If they arrive by mistake we delete them.
3.2 The server records
Each page load typically leaves an ordinary hosting / security log: IP address (including an address forwarded by Cloudflare when the domain is proxied); date and time; URL; referrer; status code; browser / user-agent; approximate country from IP; and the cookies described in the Cookie Policy.
3.3 What we do not ask for here
Payment cards, government identification, precise GPS, account passwords, or a customer login. We do not sell tickets and we do not collect checkout data on these pages. There is no checkout on this site.
4. Cookies
We may set a strictly necessary first-party session cookie so the server can keep request state. We do not place Google advertising cookies, Google Analytics (_ga, _gid, _gcl_aw), Floodlight, Meta Pixel, TikTok Pixel, Hotjar, Clarity, or similar measurement cookies on these editorial pages.
You may still arrive after clicking an advertisement. That click lives on the network’s services, under that network’s policy. We may see a standard HTTP referrer or a campaign parameter such as gclid, gbraid, wbraid, or utm_source. We do not use those parameters to retarget you. Full table: Cookie Policy.
5. How we use it
- to deliver and secure the Site;
- to answer editorial mail and correct published errors;
- to see, in aggregate, which pages are requested;
- to comply with law;
- to show advertising platforms and regulators who we are and how to reach us.
We do not sell personal information. We do not share it for cross-context behavioural advertising. We do not use automated decisions that produce legal or similarly significant effects about you. We do not operate a ticket desk.
6. Legal bases
Canada (PIPEDA): we collect and use the information above for the reasonable purposes of running an editorial website, answering mail, and protecting the service.
GDPR / UK GDPR (if those laws apply): legitimate interests (Art. 6(1)(f)) for operating and securing a publication; your request (Art. 6(1)(b)) when you write to us; legal obligation (Art. 6(1)(c)) if a competent authority issues a lawful order. We do not rely on consent for advertising cookies because we do not set them.
California and other US state privacy laws: we do not sell or share personal information as those statutes define those terms. We do not use sensitive personal information for inferring characteristics.
7. Sharing
We share information only with hosting, DNS, TLS, and security providers (a VPS host and, when the domain is proxied, Cloudflare); email infrastructure if we reply; professional advisers or authorities when the law requires it; and a successor if the publication is transferred, under this Policy or a notice posted first. We do not forward your email to any dinner-theatre operator.
8. International transfers
Hosting, DNS, or security providers may process technical data in the United States, the European Union, Canada, or other countries where they operate. Where GDPR applies, those transfers rely on the provider’s appropriate safeguards (for example Standard Contractual Clauses) or an adequacy decision.
9. How long we keep it
- Server and security logs: typically up to 30 days, unless a security investigation needs a longer copy;
- Editorial email: up to 12 months after the last reply, unless you ask us to delete sooner and no legal hold applies;
- Session cookie: until the browser session ends, or shortly after.
10. Children
The Site is written for adults planning a visit. It is not directed at children under 13 (or 16 where that is the relevant digital-consent age). If you believe a child sent us information, write to [email protected] and we will delete it.
11. Your rights
Subject to the law that applies to you, you may ask us to access, correct, delete, or export the personal information we hold, or to restrict or object to certain processing. Send requests to [email protected]. We may need to verify that the request comes from you.
You may complain to the Office of the Privacy Commissioner of Canada, your EEA supervisory authority, or the UK ICO. We would rather fix the issue first if you write to us.
12. If you came from an advertisement
Occasionally people arrive after seeing an online advertisement that mentioned a Toronto castle dinner show or tickets. That advertisement is not mine. I do not advertise this guide and I do not sell tickets. If an ad led you here expecting to buy, leave this page and use the operator’s own official website. Nothing here will take a card payment.
- the advertising network (for example Google) is a separate controller for the ad click and any cookies it sets on its own domains;
- we do not operate a Google Ads tag, Floodlight tag, conversion linker, or remarketing tag on these editorial pages;
- we do not upload customer lists to advertising platforms;
- this Policy, the Cookie Policy, the Terms of Use, and the Contact page exist so a reviewer can see who publishes the Site, what we collect, and how to reach us;
- the landing pages do not sell tickets, show live fares, or process payments.
Google’s own notices: policies.google.com/privacy and policies.google.com/technologies/ads.
If you clicked something suspicious and landed here, a short note to [email protected] with what you clicked helps me flag it.
13. Security
The public site is served over HTTPS. The origin is access-controlled. No method of transmission is perfectly secure. Do not send secrets to an editorial inbox.
14. Photographs and third-party links
Photographs are from Wikimedia Commons and are credited under each figure with licence and author. Editorial links are context, not endorsements. Those sites have their own policies. This Site does not load Google Fonts or other third-party font CDNs.
15. Changes
If we change this Policy we update the date at the top. If a change is material — for example if we ever introduced analytics cookies — we will post a short notice on the Site as well. There is no mailing list.
16. How to reach us
Toronto Castle Dinner Guide
Toronto, Ontario
[email protected]
https://medievalttimesise.cc/privacy ·
https://medievalttimesise.cc/cookies ·
https://medievalttimesise.cc/terms ·
https://medievalttimesise.cc/contact