Who we are
Metabus Automation Solutions Inc. ("Metabus", "we", "us") operates the website at metabus.ca AND a multi-tenant marketing-technology platform used by client brands to capture, route, and follow up on leads from their own marketing campaigns. We are based in Alberta, Canada.
Scope of this policy
This document serves three roles, all governed by the same rules below:
- App Privacy Policy for the MAS Inc. Marketing App on Meta (Facebook, Instagram, Threads). This is the privacy policy referenced in our Meta App configuration and reviewed by Meta during App Review.
- Privacy Policy for the metabus.ca website and the forms, booking flow, and informational surfaces it hosts.
- Platform Privacy Notice describing the role Metabus plays when client brands operate marketing campaigns on the Metabus platform.
Two ways your data may flow through us
This policy reflects that we play two different roles depending on how you encountered us:
- Direct interaction with metabus.ca (we are the data controller).
You submitted a form on metabus.ca, booked a call with Metabus, or interacted with a Metabus-branded ad selling Metabus's own services. Metabus is the data controller for that information. This policy governs it.
- Interaction with a client brand running on the Metabus platform (we are the data processor).
You filled out a lead form for a client brand whose campaigns and lead capture are operated on the Metabus platform (examples include Cebucan, BuildGravity, Confluence AI, and other tenant brands). In that case the client brand is the data controller and their own privacy policy governs the use of your information. Metabus processes the data on the client's behalf only. Refer to the client brand's website for their privacy policy and contact details.
The rest of this policy describes what we do as the data controller for metabus.ca interactions and as the platform processor for client interactions.
What we collect
Depending on your interaction we may collect:
- Form submissions and bookings. Name, business email, phone number, company, role, free-text answers describing your business or inquiry, scheduled call time.
- Attribution and traffic data. Referring URL, UTM parameters, landing page, click identifiers (e.g.
fbclid, gclid), browser user-agent, IP-derived country. - Analytics events. Page views and conversion events via Google Analytics 4 and Meta Pixel (where you have not opted out via your browser settings or a regional consent gate).
- Ad-platform interaction data. When you interact with a Metabus-powered Lead Form on Meta (Facebook, Instagram, Threads), Meta provides us with the data you submitted plus standard interaction metadata. The client brand whose campaign you interacted with is the controller of that data; we route it to their tenant on our platform.
- Booking data. When you schedule a call via Cal.com, we receive your name, email, scheduled time, and any answers you provide on the booking form.
Meta platform data access (App-specific disclosures)
The MAS Inc. Marketing App connects to Meta's developer platform to operate ad campaigns on behalf of Metabus and our client tenants. The App accesses the following Meta data:
- Lead Ads submissions. When a user submits a Meta Lead Form connected to a Page that authorizes the App, Meta sends the submitted fields (those the form requests, such as name, email, phone, company, and any custom questions) plus the lead identifier and the originating Page and form IDs to the App via the Lead Ads webhook. The App routes the submission to the relevant tenant's storage in our dialer / CRM and triggers the tenant's configured automation.
- Conversions API events. The App sends server-side conversion events (page views, form submissions, qualified leads, booked calls) back to Meta via the Conversions API to improve ad attribution and optimization. The events include hashed identifiers (email, phone) where the user has provided them, in accordance with Meta's documented hashing requirements.
- Meta Pixel. Where a brand has provisioned a Pixel ID on the platform, the App injects the Meta Pixel on the relevant marketing surfaces (metabus.ca, client tenant sites) to record events used for attribution.
- Page-level access (where granted). Where a Page admin grants the App access to their Page for Lead Ads delivery, the App receives the Page ID, name, and the access scopes the admin has approved. The App uses this access only to receive Lead Ads submissions for that Page and to honor admin actions (revocation, deletion).
- What the App does NOT access. The App does not read Pages' organic posts, comment streams, message inboxes, follower lists, or any user-level data beyond the Lead Ads submissions and the explicit permissions a Page admin has granted.
Meta platform data is held under the same retention, sharing, and deletion rules described below. When Meta sends a Data Deletion Callback for a user, the App locates and deletes the corresponding records and confirms deletion to Meta within Meta's published SLA.
How we use it (for metabus.ca interactions)
- To respond to inquiries you submit to Metabus directly and book follow-up conversations about Metabus's services.
- To send marketing communications you have consented to receive about Metabus. You may unsubscribe at any time.
- To measure our marketing performance, attribute conversions, and improve our content and campaigns.
- To meet legal, accounting, and security obligations.
How we use it (for client-brand interactions)
When you fill out a lead form for a client brand running on the Metabus platform, we use the data only to operate the platform on the client's behalf: routing the lead to the client's tenant, triggering the client's configured automation (auto-replies, booking offers, sequence enrollments), and producing analytics for the client. We do not use client-tenant data for our own marketing. The client's own privacy policy governs further use.
Who we share it with
We share information only with the service providers that operate the platform on our behalf:
- Hosting and analytics: Google (Firebase Hosting, Google Analytics 4), Meta (Meta Pixel and Conversions API for ad attribution).
- Lead routing and automation: Our dialer / CRM running on Google Cloud (Cloud Run + Firestore), operated by BuildGravity Inc. as a sub-processor to Metabus under a written Data Processing Agreement.
- Email and SMS: Mailgun (email), Telnyx (SMS), where applicable.
- Booking: Cal.com.
For client-brand interactions, the data is also routed to the client brand whose campaign you engaged with. The client brand's own privacy policy lists their further sub-processors.
We do not sell personal information. We do not share data with third parties for their independent marketing.
How long we keep it
We retain personal information for as long as is necessary to fulfill the purposes described above. For metabus.ca leads and bookings, records are typically retained for the duration of our commercial relationship plus seven years for accounting and audit purposes, after which they are deleted or fully anonymized. For client-tenant data we follow each client's documented retention schedule.
How we protect it
We protect personal information using industry-standard administrative, technical, and physical safeguards including: TLS encryption for data in transit; encryption at rest on Google Cloud Firestore and Cloud Storage; role-based access controls with the principle of least privilege for staff and sub-processor access; audit logging on production systems; multi-factor authentication on administrative consoles; and breach notification procedures aligned with PIPEDA, GDPR Articles 33 and 34, and CCPA where applicable. No system is perfectly secure and we cannot guarantee absolute security.
Your rights
Depending on your jurisdiction (including Canada's PIPEDA, the EU GDPR, the UK GDPR, and the California CCPA) you may have the right to:
- Access the personal information we hold about you;
- Request that we correct inaccurate information;
- Request that we delete your personal information (see data deletion);
- Object to or restrict certain processing;
- Withdraw consent for marketing communications at any time;
- Lodge a complaint with your local data protection authority.
For data Metabus controls (metabus.ca interactions), contact us at jason@metabus.ca. For data a client brand controls (their lead forms, their campaigns), contact the client brand directly. We forward platform-side deletion requests upon confirmation.
Cookies and tracking
We use first-party cookies on metabus.ca to remember your preferences and third-party pixels (Meta, Google) to measure ad performance. You can block cookies in your browser settings. Where required by law (EU/UK/EEA) we surface a consent prompt before non-essential tracking fires. Client-brand websites operate their own cookie programs under their own consent regimes.
International transfers
Our servers and the service providers listed above operate primarily in the United States and Canada. Where personal information from the European Economic Area, the UK, or Switzerland is transferred to a country without an adequacy decision, we rely on Standard Contractual Clauses with our processors.
Children
Our services are intended for businesses and adults. We do not knowingly collect personal information from anyone under 16.
Changes to this policy
We will post any material changes here with a new "last updated" date.
Contact
Questions about this policy or our handling of personal information that Metabus controls: jason@metabus.ca. For client-tenant data, contact the client brand whose campaign you interacted with.