Privacy Policy
MTF Group Ltd. uses your information to answer requests, deliver and pick up bins, take payment, and see how the site is used. This page explains what we collect, who gets it, how long we keep it, and your privacy choices.
Last updated:
What we collect
Your name, mobile number, and email if you give it. Your delivery address and postal code. The bin and dates you book, and any notes about where to place it. The messages you send our booking assistant or dispatch. Using the site can also create page, event, browser, device, referral and campaign data, listed in the service table below.
Payment details
Stripe handles card payments through its secure payment form. MTF Group never sees or stores your full card number. Never type card details into chat - use the secure payment form only. We keep payment references and status for your booking, refunds and any extra charges. Where your visit came from may be attached to the payment as extra data.
How we use it
To book and complete your delivery and pickup. To contact you about your booking. To bill any extra charges. To keep the records the law requires. We never sell your information or use it for unrelated marketing.
The booking assistant
The chat on our site is an AI assistant. Anthropic processes your messages and chat history so it can reply. The booking details you give it go to our dispatch team.
To tell people from bots, the booking assistant uses Cloudflare Turnstile. It checks signals from your browser, such as your IP address, connection fingerprint and browser type, to block bots. See Cloudflare's Turnstile Privacy Addendum (cloudflare.com/turnstile-privacy-policy). The call-back form does not use Turnstile.
The call-back form
The call-back form asks for your name and phone number. If you add them, it also asks for your postal code and a message. If you land on one of our ad pages from an ad, the form also keeps that visit's ad-click details, such as the ad click identifier and utm_ values in the page address.
We e-mail your request to MTF through Postmark, our e-mail service. We also store it in our booking system so we can call you back.
Analytics and advertising
This site can load the analytics and ad services below. The table lists each one's purpose, data and consent category. The cookie policy covers storage.
Google Tag Manager (Google): loads the Google tracking and ad tags MTF sets up in it, and lets them use cookies for analytics and ads. Those tags send Google details of your visit: the pages you view, and your browser and device.
Usermaven: site analytics. It records the pages you visit and what you click, with your browser and device.
Who sees it
Our office, dispatch and drivers. Our payment processor. The services that help run our site and booking system, including Postmark and our booking system for call-back requests. Each only gets what it needs. We tell authorities only when the law makes us.
How long we keep it
Our site's scheduled cleanup removes your request details once they are older than ninety days. The exception: a request whose notification has not yet been delivered stays until delivery is done or an operator clears it. Copies already e-mailed or sent to our booking system have their own retention settings.
The assistant's cleanup removes sessions and drafts after twenty-four hours with no activity. It removes redacted transcripts after thirty days, and records of which tool or AI model handled each chat after ninety days. It clears the raw chat history when a session ends, or every hour once two hours pass with no activity. These are our app's own cleanup rules, not a promise that every copy or backup is gone by then.
We have not set a fixed deletion time for booking, payment, accounting, backup or server-log records. Contact us about any one record.
Your rights
You can ask to see the information we hold about you, fix it, or have it deleted when we don't have to keep it. Call or text dispatch at (647) 966-2300, e-mail hello@mtfgroup.ca, or write to MTF Group Ltd., 56 Hyde Ave, Toronto, Ontario M6M 1J4. You can ask for access, ask for a fix, or withdraw consent. Limits can apply under the law, our contract, or a notice period required by PIPEDA. We will explain any limit and what it means for the service you asked for.
Changes
If this policy changes, the updated version will be posted here with a new date.
Cookies
Our cookie policy and the table below explain tracking with no cookie.
Request attribution
We record campaign details (utm_ values) and ad click identifiers, plus where you came from and your device type, to link a request to its source. Our own mtf_attr cookie lasts thirty days. Landing forms also use tab-session storage with the same name.
Where a request came from is kept with your request or booking record, and can appear in request emails and our booking system. It can also reach Stripe as payment metadata. The analytics and ad services below get their own separate tracking data. Clearing a cookie does not delete a record you already sent.
Email communications
Sending us a request lets us reply about that request, and send related booking or service emails. It does not sign you up for promo email. Any promo message must meet CASL's rules: your consent or another valid reason, who sent it, and a way to unsubscribe. You can also contact us to withdraw marketing consent.
Tools, recipients and storage
This list covers services used for your request and payment, plus some optional tracking services. Not every service runs on every page.
| Tool and purpose | Data | Cookies, storage and lifetimes | Record retention | Consent state | Recipients |
|---|---|---|---|---|---|
| Google Tag Manager Loads the tracking tags set up for this site. | Page views and events, shared with the tools listed below. | This tool sets no cookie of its own. The tags it loads may set their own. | See the tool that gets the data. | - | Google and the tools set up inside it. |
| Google Analytics 4 Measures visits, pages and events on the site. | Page addresses, events, referral and campaign details, and your browser and device. | _ga* cookies. | Google lets us set how long it keeps event data. | Google can send a signal with no cookie. | Google. |
| Google Ads Measures ad clicks and the ads that led to a request or booking. | Ad click IDs, conversion events and campaign details. | _gcl_au and other Google ad cookies, depending on which tags are on. | - | Google can send a signal with no cookie. | Google. |
| Usermaven Measures the pages you visit and the things you click. | Pages visited, things clicked, and your browser and device. Full mode uses a visitor ID and your IP. Strict mode uses a code made from your IP and browser type, and hides your stored IP. | __eventn_id_* in full mode only. Strict mode writes no cookie, as its own docs say. | - | - | Usermaven. |
| Stripe Processes card payments, refunds and payment status. | Payment details you enter in the secure payment form, payment IDs, your booking reference, and where your visit came from. Do not type card details in chat. | Stripe manages its own storage for the payment form. | - | Needed to take the payment you start. | Stripe and anyone needed to process the payment. |
| Postmark Sends emails about your request or booking. | The email address, the request or booking details, and delivery records. | Sets no cookie in your browser. This runs server to server. | Postmark's default is to keep message content and records for forty-five days. | Needed to reach you about your request or booking. It does not sign you up for promo email. | Postmark and the people the email is sent to, including MTF dispatch. |
| Our booking system Keeps service records so MTF can respond and book the job. | Your contact details, address or postal code, the service and dates you asked for, booking and payment status, and where your request came from. | Sets no cookie in your browser. This runs server to server. | - | Needed to handle your request and provide the service. | MTF staff who use our booking system, and the systems behind it. |
| Google Maps / Places Suggests and checks the address entered for a booking. | The address you type, the place you pick, and its details. Sent through our server. | Sets no cookie in your browser. This runs on our server. | - | Essential for the address lookup you request. | Google. |
| Cloudflare Turnstile Tells people apart from bots in the booking assistant. | Browser signals: your IP address, a connection fingerprint, your browser type, our site key and page origin. | - | - | Needed for security when you use the assistant. | Cloudflare. |
| Anthropic Writes the assistant's replies and its booking actions. | Your chat messages and the details you give the AI assistant about your request. | Sets no cookie in your browser. This runs server to server. | - | Essential to reply when you use the AI assistant. You can contact dispatch instead. | Anthropic. |
| MTF first-party request and session storage Tracks where your request came from, keeps the assistant chat going, and stops duplicate events. | Your campaign details, click IDs, source and device type, a session ID, and guards against duplicate events. See the table below. | Four items in the storage table below: a cookie with where your visit came from, a signed code for your booking-assistant session, and two short notes that stop duplicate events while your tab is open. | See the lifetimes in the table below. A copy attached to a request is kept as long as that request record, per our Privacy Policy. | Needed to handle your request. | MTF. Where your request came from is kept in your request details, request emails and our booking system, and can also appear in Stripe's payment records. |
Application cookies and storage keys
| Key | Mechanism | Purpose | Browser lifetime |
|---|---|---|---|
mtf_attr | Cookie | Where your first visit came from: campaign and click details, source and device type, and landing details, so we can handle your request. | Thirty days from capture, unless cleared earlier in your browser. |
mtf_consent | Cookie | Records that you accepted analytics, so Usermaven runs in full mode from the next page load instead of strict mode. Not set unless you accept. | One year from acceptance, unless cleared earlier in your browser. |
mtf_asst | Cookie | A signed code that identifies your booking-assistant session. Page scripts cannot read it, it only travels over a secure connection, and it is only sent back to our booking-assistant service. | Twenty-four hours from the latest assistant response that renews the session, unless cleared earlier. |
mtf_attr | A note kept only while this tab is open | Campaign and click details carried by the landing-page form. Separate from the cookie of the same name. | Browser tab session. |
mtf_attr_pushed | A note kept only while this tab is open | Stops the same attribution event firing twice in one tab. | Browser tab session. |
mtf_lead_captured:* | A note kept only while this tab is open | Adds a request ID to this prefix to stop a duplicate request-success event. | Browser tab session. |
Each vendor's own storage is listed in the table above.