Last updated: 13 November 2026
This Privacy Policy explains how Fortis Communications Inc (“Fortis”, “we”, “us”, “our”) collects, uses, discloses, and protects personal information when you visit veloconnect.me or use VeloConnect — the messaging platform, its APIs and the VeloConnect mobile app (the “Services”). Fortis is a Canadian company and complies with the federal Personal Information Protection and Electronic Documents Act (PIPEDA). If you are a resident of the European Economic Area, the United Kingdom, or California, we honour the data-subject rights granted to you under your local law on request, even where this policy is framed around PIPEDA.
Who we are
Fortis Communications Inc is a Canadian corporation headquartered in the Province of Ontario, Canada. VeloConnect is its customer-messaging platform. For any privacy matter, contact [email protected]. We do not maintain a public office address; all correspondence should be by email.
What personal information we collect
We collect personal information in three contexts, each described below.
(a) Website visitors. When you visit veloconnect.me our server automatically records your IP address, browser user-agent, the page you requested, the page that referred you, and the date and time of the request. If you submit a contact, demo or pricing form we store the fields you fill in (typically name, work email, company, phone, country and your message), together with the page you submitted from, the page that referred you, any campaign parameters in the link you arrived by (such as utm_source, or a Google Ads click identifier), your browser user-agent, and a one-way cryptographic hash of your IP address. We store the hash rather than the address itself: it lets us recognise repeated and abusive submissions without keeping a record of where our visitors are.
The site’s firewall (Wordfence, running on our own server) also records the IP address, browser user-agent and requested address of requests it blocks and of sign-in attempts, to protect the site from attacks. These records stay on our server and are not shared with Wordfence or anyone else.
On the pricing page your browser asks our server which country your connection comes from — Cloudflare derives it from your IP address — so that the page can offer the prices that apply there. The country is not stored.
Cloudflare Web Analytics. Cloudflare, which fronts this website, adds its Web Analytics script to our pages as they pass through its network; nothing in the site itself loads it. Your browser fetches the script from static.cloudflareinsights.com, and the script reports page-load timing measurements, read from the browser’s Performance API, to Cloudflare at /cdn-cgi/rum on this site. Cloudflare gives us aggregate figures — visits, page views, load times and Core Web Vitals — which can be broken down by country, page, referring site, browser, operating system and device type. Cloudflare states that Web Analytics uses no cookies, localStorage or other client-side state, does not fingerprint visitors by IP address or user agent, does not track individual visitors across the websites it serves, and does not collect or use visitors’ personal data.
Google Analytics and the Meta Pixel, only if you accept. On your first visit a banner asks whether we may use them; until you accept, neither sets a cookie. If you accept, Google Analytics (through Google’s tag) and the Meta Pixel set cookies in your browser and report the pages you view, the page that referred you, your browser and device, and your IP address, from which they derive an approximate location, to Google and to Meta. They use it to give us statistics about visits and to measure and improve our advertising on their platforms. With the Meta Pixel, our server also reports the same page views to Meta directly (Meta’s Conversions API), with your IP address and browser user-agent.
If you decline, or have not chosen yet, no Meta code runs and nothing is sent to Meta. Google’s tag still runs, in Google’s consent mode: it sets and reads no cookies and sends Google only cookieless measurements of the visit, which carry no identifier that links one visit to another. You can change your choice at any time with Cookie settings at the foot of every page. Google and Meta handle what they receive under their own privacy policies; each cookie is listed, with how long it lasts, in our Cookie Policy.
(b) Customers. When you create an account or purchase a Service, we collect the information needed to operate the account: your name, business email, billing address, billing currency, payment method details (handled by our payment processor — we never store full card numbers), and the contents of any support or sales tickets you open with us.
(c) End-user traffic data. Some of our Services process personal information about your end-users — the people you send messages to, place calls to, or verify numbers for. For this category Fortis acts as a service provider (PIPEDA), data processor (GDPR), or service provider (CCPA), and the customer is the controller. We process this data only on the customer’s documented instructions under the applicable order form or master services agreement, and we do not use it to build profiles, train models or market to your customers.
VeloConnect mobile app
VeloConnect is the mobile app for users of VeloPBX, our cloud phone system. Your employer (our customer) gives you access and decides how its phone system is set up, for example whether calls are recorded. For call data your employer is the controller and we process it on its behalf, as described under “end-user traffic data” above.
Sign-in details. Your company domain, user name and extension. Your passwords are stored only on your device, in the operating system’s secure storage, and are sent only to your company’s phone system over an encrypted connection.
Signed-in phones. When you sign in, the app asks Apple (App Attest) or Google (Play Integrity) to confirm that it is the genuine VeloConnect app on a real device. With your session we keep the result of that check, the platform (iOS or Android) and a one-way hashed identifier of the device, so that your administrator can see which phones are signed in and sign a lost or stolen phone out remotely.
Calls. Call signalling is encrypted with TLS. Voice is encrypted with SRTP whenever the other phone supports it, and you can choose to allow encrypted calls only. The app does not record calls. If your employer turns on call recording, the phone system stores the recordings; administrators can play them in the app, which downloads a recording for playback only and deletes it when the player is closed.
Call history, colleagues and status. The app shows call records and the company directory (names, extensions and whether colleagues are online or on a call) from your company’s phone system; your own recent calls are also kept on your device. The status you choose in the app (for example available, away or do not disturb) is saved on your company’s phone system, where your colleagues and administrators can see it. Administrators see their company’s call statistics and call log.
Your phone’s contacts. Only if you allow it, the app reads the names and phone numbers in your device’s contacts to show them in the Contacts tab so you can call them. They are read on your device only: the app does not store them and never sends them to us, to your company’s phone system or to anyone else. When you call one of them, the number you dial goes to your company’s phone system like any other call. You can turn contacts access off at any time in your device settings.
Push notifications. To ring your device when the app is closed, the app gives your company’s phone system the push tokens that Apple or Google issue for your device. They are used only to deliver incoming calls and are switched off when you sign out.
Crash reports. When the app crashes or stops responding, it sends a report to Firebase Crashlytics (Google): the error, the app and operating-system versions, the device model and the names of the last screens used. Phone numbers, extensions, names, email addresses, passwords and tokens are removed on the device before a report is sent. Reports are kept for 90 days and used only to fix problems.
What the app does not do. No advertising, no analytics or advertising SDKs, no tracking across other companies’ apps or websites, no sale of data.
Permissions. Microphone (calls); notifications (incoming calls); contacts, only if you allow it (see above); the camera only when you scan a setup QR code from your administrator, and the camera image is neither stored nor sent. On iPhone, local network access is used only to reach your company’s phone system when it is on the same network. On Android, the phone-call and Bluetooth permissions are used to show incoming calls and to use headsets.
Retention and deletion. Data on your device stays until you sign out, an administrator signs the phone out, or you remove the app; signing out deletes your passwords, session and local call history from the device. Your account, call records and recordings are kept and deleted according to your employer’s phone system settings; ask your administrator, or write to [email protected].
How we collect it
Most personal information is collected directly from you when you fill in a form, create an account, send us an email, or place an order. Some information is generated automatically — server logs, and traffic records produced as your messages or calls transit our infrastructure. We do not buy contact lists, scrape third-party sites, or enrich your profile from data brokers.
Why we collect it
PIPEDA requires us to identify the purpose of each collection at or before the time it occurs. We use personal information to: provide and operate the Services you have requested; respond to your enquiries; bill you and reconcile payments; protect the Services against fraud, abuse, and unauthorized access (including bot-protection challenges on our forms); detect and prevent telecommunications fraud such as IRSF, wangiri, and AIT; comply with our obligations under telecommunications, anti-spam, sanctions, and tax law; and send transactional notifications (such as account, security, and billing alerts), and — only with your explicit opt-in — marketing communications, each of which carries an unsubscribe link. We do not use your personal information for any purpose materially different from these without first asking for your consent.
Legal basis and consent
Under PIPEDA, our basis for processing is your knowledge and consent, except where another basis is permitted by law (for example, where we are required to disclose information to law enforcement under a valid order). Consent is implied for activity that is reasonably necessary to operate a Service you have already requested (such as routing your message through our carrier partners). Consent is express — collected through a checkbox or equivalent affirmative action — for marketing communications and any other use that is not strictly necessary. You may withdraw consent at any time by writing to [email protected]; we will explain the practical consequences if withdrawal would end your access to a Service.
If you are in the EEA or UK, the legal bases under Article 6 GDPR are the same set translated into GDPR terms: performance of a contract, legitimate interests (fraud prevention and security), legal obligation, and consent — which is the basis for Google Analytics and the Meta Pixel on veloconnect.me, given or refused in the cookie banner. If you are in California: we do not sell personal information. If you accept the cookie banner, Google and Meta receive information about your visit that they may use for advertising, which California law can treat as “sharing” for cross-context behavioural advertising; it happens only after you accept, and declining, or withdrawing later in Cookie settings, opts you out.
How we share personal information
We share personal information only with parties that need it to deliver the Services or to meet a legal obligation. Categories of recipients are:
- Sub-processors and service providers: our hosting provider; Cloudflare, which fronts this website, runs the bot-protection challenge on our forms and provides the Web Analytics described above; Google (Analytics) and Meta (the Meta Pixel and its Conversions API), only if you accept cookies, as described above; our email and customer-support tooling; payment processors; the telecommunications carriers, aggregators and messaging providers that route your messages and calls — including Meta (WhatsApp, Facebook Messenger, Instagram), Viber, Telegram and mobile network operators, because a message cannot be delivered without handing it to the network that delivers it; and, for the VeloConnect mobile app, Apple and Google (device checks and push notifications) and Firebase Crashlytics (crash reports), as described above.
- Professional advisers: our lawyers, accountants, auditors, and insurers, bound by their own confidentiality obligations.
- Authorities: where we are required by Canadian law or a valid order from a competent authority to produce information.
- Acquirers: if Fortis is involved in a merger, acquisition, financing, or insolvency, personal information may be transferred to the acquiring or succeeding entity, subject to equivalent confidentiality obligations.
We do not sell personal information.
International transfers
Fortis is based in Canada, but our sub-processors and carrier partners operate globally. Personal information may be processed outside the country where it was collected, including in the United States and the European Union. By using the Services or veloconnect.me you acknowledge this. Where the transfer involves personal information of EEA or UK residents, we rely on the European Commission’s Standard Contractual Clauses (or equivalent UK transfer mechanism) with the sub-processor. Canada holds a partial adequacy decision from the European Commission, covering commercial organisations subject to PIPEDA.
How long we keep it
We keep personal information only as long as we have a legitimate purpose for doing so. As a guide: contact-form messages and demo enquiries are retained for up to 24 months from last contact; customer account data for the duration of the account plus seven (7) years after closure for tax and audit purposes; billing records for seven (7) years to meet Canada Revenue Agency requirements; server logs for up to 90 days unless retained longer for an active security investigation, and the firewall’s records for up to 30 days. The counters our forms and price lookups keep against a hash of your IP address, to limit abuse, expire after one hour. End-user traffic data processed on behalf of customers is retained per the customer’s order form. Data handled by the VeloConnect mobile app is kept as described in that section above.
How we protect it
We apply administrative, technical, and physical safeguards proportionate to the sensitivity of the personal information we hold. These include role-based access controls, separation of customer data per tenant, encryption in transit, and two-factor authentication for administrator accounts on the VeloConnect platform. No system is ever perfectly secure; in the event of a breach involving real risk of significant harm we will notify affected individuals and the Office of the Privacy Commissioner of Canada as required by PIPEDA’s mandatory breach-reporting rules.
Your rights
Under PIPEDA you have the right to: (a) be informed about the existence, use, and disclosure of your personal information; (b) access the personal information we hold about you; (c) request correction of inaccurate or incomplete information; and (d) withdraw consent (subject to legal or contractual restrictions). To exercise any of these rights, write to [email protected] from the email address associated with your account or enquiry. We respond within 30 days; if we cannot meet that timeline we will tell you why and provide a revised date. There is no charge for a standard request. We may decline to act on a request that is manifestly unfounded, excessive, or that would require us to disclose information about another individual.
If you are in the EEA or UK you additionally have rights of erasure, restriction of processing, data portability, and objection to processing under Articles 15–22 GDPR. If you are in California you additionally have rights to know, delete, correct, and limit the use of sensitive personal information under CCPA/CPRA. To exercise any of these regime-specific rights, write to the same email and tell us which jurisdiction you are exercising rights under.
If your request concerns data we process on behalf of one of our customers — for example, a message you received from a business using VeloConnect — we will refer you to that business, because they decide what happens to it and we may not act on it without their instruction.
See also our data deletion instructions.
Cookies and similar technologies
veloconnect.me sets analytics and advertising cookies — Google Analytics and the Meta Pixel — only if you accept them in the cookie banner, and you can withdraw at any time with Cookie settings at the foot of every page. Everything else it stores is strictly necessary, or remembers a choice you made. Each cookie and storage entry is listed, with its purpose and duration, in our Cookie Policy. Cloudflare Web Analytics, which sets no cookie and stores nothing in your browser, runs for every visitor; it is described under (a) above.
Automated decision-making
We do not use personal information collected from veloconnect.me to make decisions about you that produce legal or similarly significant effects without human review. Some Services use automated systems internally — for example, fraud-detection rules that flag suspicious traffic patterns for review — but a human Fortis operator is in the loop before any account-level action is taken.
Children
Our Services are not directed at children under 16 and we do not knowingly collect personal information from them. If you believe a child has provided personal information to us, please write to [email protected] and we will delete it.
Changes to this policy
We may revise this Privacy Policy from time to time. When we make material changes we update the “Last updated” date at the top of this page and, where appropriate, notify account holders by email. Continued use of veloconnect.me or the Services after a change takes effect constitutes acceptance of the revised policy.
How to complain
If you have a concern about how Fortis handles your personal information, contact us first at [email protected]. We take complaints seriously and will work to resolve the matter directly. If you are not satisfied with our response, you may file a complaint with the Office of the Privacy Commissioner of Canada. EEA / UK residents may also complain to their local supervisory authority; California residents may contact the California Privacy Protection Agency at cppa.ca.gov.
Contact
Fortis Communications Inc, Ontario, Canada. For any privacy question, please write to [email protected].