{ "schema_version": 1, "entity_slug": "tnaado-inc", "entity": "TNAADO Inc.", "jurisdiction": "Ontario, Canada", "product_slug": "service-tnaado-ca", "product": "service.tnaado.ca", "policy_slug": "privacy-policy", "policy": "Privacy Policy", "source_effective_date": "2026-01-30", "source_updated_date": "2026-08-22", "source_version": null, "canonical_url": "https://service.tnaado.ca/privacy", "captured_at": "2026-10-25T20:53:13+00:00", "source_html": "\n\n\n\n\n\nPrivacy policy | TNAADO\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n\n\n
\n\n \n Skip to content\n\n \n
\n \n \"TNAADO\"\n\n \n

A media and technology firm in Toronto.

\n \n
\n\n \n \n
\n\n
\n\n
\n
\n
\n

Legal

\n

Privacy policy.

\n

Effective January 30, 2026. Last updated August 22, 2026. This policy covers service.tnaado.ca, the site where clients reach TNAADO Inc. about technology, media and consulting work. The media site and the consumer apps, including The Dispatch, are governed by the universal policy at tnaado.ca/privacy.

\n
\n
\n
\n\n
\n
\n
\n\n \n\n

S.01 Scope

\n

This policy explains how TNAADO Inc. (“TNAADO”, “we”, “us”) collects and handles personal information through service.tnaado.ca. TNAADO Inc. is a Canadian company at 1050 King Street West, Toronto, and this site is governed by Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA), applicable provincial privacy statutes, and equivalent regimes where they apply to you.

\n

It covers this site only. Our media property, our newsroom and our consumer apps are separate systems with separate databases, and they are covered by the universal policy at tnaado.ca/privacy.

\n\n

S.02 What you tell us

\n

The only form on this site that collects anything about you is the booking form. When you use it we store what you type: your name, email address, and optionally your company, phone number and message, together with which service you selected, the half-hour slot you chose, and the time zone your browser reports so the confirmation shows you the right clock time.

\n

Nothing on this site asks for sensitive personal information, and nothing on it takes a payment. If you email or call us instead, we keep that correspondence in the ordinary way any business keeps its mail.

\n\n

S.03 What is collected automatically

\n

Every visit produces one pageview record: the path you looked at, the referring address if there was one, your browser’s user-agent string, whether the device is a phone, tablet or desktop, and how many seconds the page was actually visible. Your IP address and a coarse location derived from it are added by our server, not by your browser.

\n

If you arrive from an advertisement or a campaign link, the campaign parameters in that address are recorded with the visit: the utm_ values, and whichever click identifier the advertising platform attached: Google Ads (gclid, gbraid, wbraid), Microsoft Ads (msclkid) or Facebook (fbclid). If you then book, those values are attached to the booking, so we can tell which advertisement produced an enquiry.

\n\n

S.04 Cookies and local storage

\n

We set one cookie of our own. tn_vid holds a randomly generated identifier, lasts one year, and is first-party and SameSite=Lax: it lets us see that two pageviews came from the same browser without knowing who you are, and it is not readable by any other website. Where campaign values are held for later, they are held in a second first-party cookie, tn_attr. Neither is an advertising cookie and neither follows you off this site.

\n

Google Analytics sets its own cookies, described in S.05. The booking form also keeps the list of free slots in your browser’s sessionStorage for 45 seconds so that changing service does not re-request it; that cache holds no personal information and is gone when you close the tab.

\n

You can clear or block all of the above in your browser settings. If you block them the site still works; the booking form still books.

\n\n

S.05 Analytics

\n

These are separate systems.

\n
    \n
  • Google Analytics 4, property G-Y561C98Y8Q. Google receives the pageview and sets its own cookies. It is used for aggregate reporting: which pages get read, which campaigns bring people in. The same tag also reports to our Google Ads account, conversion ID AW-17175265494, so an advertisement can be credited with the enquiry it produced. Google’s own handling is described in their privacy policy, and you can opt out with their browser add-on.
    • \n
  • Our own pageview record. One request per visit to site.tnaado.ca/api/collect, a TNAADO endpoint, which writes the fields listed in S.03 into our own database. It runs on our infrastructure and the row is not shared with anyone.
    • \n
\n

Requests our own system identifies as coming from a bot or crawler are discarded rather than recorded.

\n\n

S.06 Booking a call or a visit

\n

The booking form is served by Supabase, which hosts our database and the two functions behind it: one that lists free slots, one that books one. Booking writes a row holding the fields in S.02, the slot, its status, and the page you booked from.

\n

Booking also creates a real event in a Google Calendar belonging to the person you are meeting, with you added as an attendee. That is how the invitation reaches you: Google emails it to the address you gave. A call receives a Google Meet link in that invitation; a booked visit to the office receives the street address and no video link. Cancelling or removing yourself from the event is done from the invitation in your own calendar, and you can ask us to delete the booking outright.

\n

Your enquiry is also forwarded once to TNAADO’s own client-enquiry system at site.tnaado.ca, so that a real person sees it rather than only a calendar entry. That system is ours, it is not a third-party CRM, and the enquiry is not sent to our billing systems.

\n\n

S.07 Spam and abuse controls

\n

The booking form is protected by Cloudflare Turnstile. Turnstile runs a challenge in your browser and issues a token; we send that token and the IP address the request came from to Cloudflare to be verified. Cloudflare’s handling is covered by its own privacy policy.

\n

We also rate-limit bookings. Doing so means recording the IP address a booking request came from, for the length of the limiting window, in a table used for nothing else. Without it a single script could take every appointment in the calendar.

\n\n

S.08 The on-site assistant

\n

The home page offers an assistant that answers questions about the firm. What you type into it is sent to one of our own Supabase functions to generate a reply. Do not put confidential or sensitive information into it: if something needs to be handled carefully, email or call us so it can be.

\n\n

S.09 Third parties, named

\n

These are all of them, and what each one is for:

\n
    \n
  • Vercel: hosts and serves the site.
    • \n
  • Cloudflare. DNS and content delivery in front of it, and Turnstile on the form.
    • \n
  • Supabase: the database and the functions behind the booking form and the assistant.
    • \n
  • Google. Analytics and Google Ads conversion measurement; Calendar and Meet for bookings, including delivery of the invitation email; and Google Fonts, which your browser requests directly, so Google sees the request.
    • \n
  • jsDelivr: a public code CDN that serves one JavaScript library to the home page; it sees the request for that file.
    • \n
\n

Each is bound by its own terms and by confidentiality where a contract applies. Beyond these, we disclose personal information only where the law requires it: a court order or a regulatory request: or in connection with a merger or transfer of the business, with notice where that is reasonably practicable.

\n\n

S.10 What this site does not do

\n

This site does not sell or rent your data. It carries no advertising: no ad network, no ad units, no remarketing pixel from a social platform. Visits are reported to Google Ads for conversion measurement, described in S.05. It takes no payment, so it never sees a card number. It has no login, so there is no account and no password. It does not add you to a mailing list: booking a call subscribes you to nothing.

\n\n

S.11 Retention

\n

Enquiries and bookings are kept while the conversation or engagement is live, and afterwards only as long as needed for our legal, tax and accounting obligations, then destroyed. Rate-limit records are short-lived by design. Analytics records are kept in aggregate. You can ask us to delete your enquiry at any time and we will, subject to anything we are required to retain.

\n\n

S.12 Your rights

\n

Subject to applicable law you may ask us for a copy of the personal information we hold about you, ask us to correct it, ask us to delete it, withdraw consent where consent is what we relied on, and complain to a privacy regulator: in Canada, the Office of the Privacy Commissioner. Write to [email protected] and say which of those you want; we do not require a particular form of words.

\n\n

S.13 Where the data sits

\n

Our database is hosted in Canada. Some of the providers named in S.09 operate globally and may process data outside Canada, principally in the United States. Where that happens we rely on those providers’ contractual and organisational safeguards, which are intended to give comparable protection. Transmission to and from this site is over HTTPS with current TLS. No transmission over the internet is perfectly secure; do not send documents you would not want intercepted over a network you do not trust.

\n\n

S.14 Changes and contact

\n

When this policy changes, the current version is posted here and the “last updated” date above changes with it. A material change will be noted on this page.

\n

TNAADO Inc.. Privacy Officer
1050 King Street West
Toronto, Ontario, Canada M6K 0C7
[email protected]

\n\n

See also: universal privacy policy · contact

\n\n
\n
\n
\n\n
\n\n
\n \n\n
\n \n\n \n
\n
\n\n\n\n\n\n\n", "source_sha256": "0cd712e9dbf50a62433ba05855ce51263e1db6b7313fb97c3a6fd30cf80233d9", "text": "Legal\n\nPrivacy policy.\n\nEffective January 30, 2026. Last updated August 22, 2026. This policy covers service.tnaado.ca, the site where clients reach TNAADO Inc. about technology, media and consulting work. The media site and the consumer apps, including The Dispatch, are governed by the universal policy at tnaado.ca/privacy.\n\nOn this page\n\nS.01Scope\n\nS.02What you tell us\n\nS.03What is collected automatically\n\nS.04Cookies and local storage\n\nS.05Analytics\n\nS.06Booking a call or a visit\n\nS.07Spam and abuse controls\n\nS.08The on-site assistant\n\nS.09Third parties, named\n\nS.10What this site does not do\n\nS.11Retention\n\nS.12Your rights\n\nS.13Where the data sits\n\nS.14Changes and contact\n\nS.01 Scope\n\nThis policy explains how TNAADO Inc. (“TNAADO”, “we”, “us”) collects and handles personal information through service.tnaado.ca. TNAADO Inc. is a Canadian company at 1050 King Street West, Toronto, and this site is governed by Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA), applicable provincial privacy statutes, and equivalent regimes where they apply to you.\n\nIt covers this site only. Our media property, our newsroom and our consumer apps are separate systems with separate databases, and they are covered by the universal policy at tnaado.ca/privacy.\n\nS.02 What you tell us\n\nThe only form on this site that collects anything about you is the booking form. When you use it we store what you type: your name, email address, and optionally your company, phone number and message, together with which service you selected, the half-hour slot you chose, and the time zone your browser reports so the confirmation shows you the right clock time.\n\nNothing on this site asks for sensitive personal information, and nothing on it takes a payment. If you email or call us instead, we keep that correspondence in the ordinary way any business keeps its mail.\n\nS.03 What is collected automatically\n\nEvery visit produces one pageview record: the path you looked at, the referring address if there was one, your browser’s user-agent string, whether the device is a phone, tablet or desktop, and how many seconds the page was actually visible. Your IP address and a coarse location derived from it are added by our server, not by your browser.\n\nIf you arrive from an advertisement or a campaign link, the campaign parameters in that address are recorded with the visit: the utm_ values, and whichever click identifier the advertising platform attached: Google Ads (gclid, gbraid, wbraid), Microsoft Ads (msclkid) or Facebook (fbclid). If you then book, those values are attached to the booking, so we can tell which advertisement produced an enquiry.\n\nS.04 Cookies and local storage\n\nWe set one cookie of our own. tn_vid holds a randomly generated identifier, lasts one year, and is first-party and SameSite=Lax: it lets us see that two pageviews came from the same browser without knowing who you are, and it is not readable by any other website. Where campaign values are held for later, they are held in a second first-party cookie, tn_attr. Neither is an advertising cookie and neither follows you off this site.\n\nGoogle Analytics sets its own cookies, described in S.05. The booking form also keeps the list of free slots in your browser’s sessionStorage for 45 seconds so that changing service does not re-request it; that cache holds no personal information and is gone when you close the tab.\n\nYou can clear or block all of the above in your browser settings. If you block them the site still works; the booking form still books.\n\nS.05 Analytics\n\nThese are separate systems.\n\nGoogle Analytics 4, property G-Y561C98Y8Q. Google receives the pageview and sets its own cookies. It is used for aggregate reporting: which pages get read, which campaigns bring people in. The same tag also reports to our Google Ads account, conversion ID AW-17175265494, so an advertisement can be credited with the enquiry it produced. Google’s own handling is described in their privacy policy, and you can opt out with their browser add-on.\n\nOur own pageview record. One request per visit to site.tnaado.ca/api/collect, a TNAADO endpoint, which writes the fields listed in S.03 into our own database. It runs on our infrastructure and the row is not shared with anyone.\n\nRequests our own system identifies as coming from a bot or crawler are discarded rather than recorded.\n\nS.06 Booking a call or a visit\n\nThe booking form is served by Supabase, which hosts our database and the two functions behind it: one that lists free slots, one that books one. Booking writes a row holding the fields in S.02, the slot, its status, and the page you booked from.\n\nBooking also creates a real event in a Google Calendar belonging to the person you are meeting, with you added as an attendee. That is how the invitation reaches you: Google emails it to the address you gave. A call receives a Google Meet link in that invitation; a booked visit to the office receives the street address and no video link. Cancelling or removing yourself from the event is done from the invitation in your own calendar, and you can ask us to delete the booking outright.\n\nYour enquiry is also forwarded once to TNAADO’s own client-enquiry system at site.tnaado.ca, so that a real person sees it rather than only a calendar entry. That system is ours, it is not a third-party CRM, and the enquiry is not sent to our billing systems.\n\nS.07 Spam and abuse controls\n\nThe booking form is protected by Cloudflare Turnstile. Turnstile runs a challenge in your browser and issues a token; we send that token and the IP address the request came from to Cloudflare to be verified. Cloudflare’s handling is covered by its own privacy policy.\n\nWe also rate-limit bookings. Doing so means recording the IP address a booking request came from, for the length of the limiting window, in a table used for nothing else. Without it a single script could take every appointment in the calendar.\n\nS.08 The on-site assistant\n\nThe home page offers an assistant that answers questions about the firm. What you type into it is sent to one of our own Supabase functions to generate a reply. Do not put confidential or sensitive information into it: if something needs to be handled carefully, email or call us so it can be.\n\nS.09 Third parties, named\n\nThese are all of them, and what each one is for:\n\nVercel: hosts and serves the site.\n\nCloudflare. DNS and content delivery in front of it, and Turnstile on the form.\n\nSupabase: the database and the functions behind the booking form and the assistant.\n\nGoogle. Analytics and Google Ads conversion measurement; Calendar and Meet for bookings, including delivery of the invitation email; and Google Fonts, which your browser requests directly, so Google sees the request.\n\njsDelivr: a public code CDN that serves one JavaScript library to the home page; it sees the request for that file.\n\nEach is bound by its own terms and by confidentiality where a contract applies. Beyond these, we disclose personal information only where the law requires it: a court order or a regulatory request: or in connection with a merger or transfer of the business, with notice where that is reasonably practicable.\n\nS.10 What this site does not do\n\nThis site does not sell or rent your data. It carries no advertising: no ad network, no ad units, no remarketing pixel from a social platform. Visits are reported to Google Ads for conversion measurement, described in S.05. It takes no payment, so it never sees a card number. It has no login, so there is no account and no password. It does not add you to a mailing list: booking a call subscribes you to nothing.\n\nS.11 Retention\n\nEnquiries and bookings are kept while the conversation or engagement is live, and afterwards only as long as needed for our legal, tax and accounting obligations, then destroyed. Rate-limit records are short-lived by design. Analytics records are kept in aggregate. You can ask us to delete your enquiry at any time and we will, subject to anything we are required to retain.\n\nS.12 Your rights\n\nSubject to applicable law you may ask us for a copy of the personal information we hold about you, ask us to correct it, ask us to delete it, withdraw consent where consent is what we relied on, and complain to a privacy regulator: in Canada, the Office of the Privacy Commissioner. Write to [email protected] and say which of those you want; we do not require a particular form of words.\n\nS.13 Where the data sits\n\nOur database is hosted in Canada. Some of the providers named in S.09 operate globally and may process data outside Canada, principally in the United States. Where that happens we rely on those providers’ contractual and organisational safeguards, which are intended to give comparable protection. Transmission to and from this site is over HTTPS with current TLS. No transmission over the internet is perfectly secure; do not send documents you would not want intercepted over a network you do not trust.\n\nS.14 Changes and contact\n\nWhen this policy changes, the current version is posted here and the “last updated” date above changes with it. A material change will be noted on this page.\n\nTNAADO Inc.. Privacy Officer\n\n1050 King Street West\n\nToronto, Ontario, Canada M6K 0C7\n\n[email protected]\n\nSee also: universal privacy policy · contact", "text_sha256": "2dae0c3cc10937e312d65bdb3a955b44028f6b8598425eaaa5bf690fa0553da4", "extraction": "main text, whitespace normalized" }