Privacy Policy

Route Fuse connects homeowners who need work done with one contractor who can do it. To make that work, we collect your contact details and a description of your job, and we pass them to a single matched contractor in your area. We are not a lead broker: your details are not sold, and they are not blasted to a list of competing companies.

We ask separately before sending you marketing email, every marketing email carries a working unsubscribe link, and you can ask us at any time what we hold about you.

Route Fuse Systems Inc. ("Route Fuse", "we", "us") operates this website and the lead-routing service described in it. We are an Alberta corporation. Our mailing address is 12236 104 Street NW, Edmonton, Alberta T5G 2L6, Canada.

Our Privacy Officer is accountable for our compliance with the federal Personal Information Protection and Electronic Documents Act (PIPEDA), Alberta's Personal Information Protection Act (PIPA), and Canada's Anti-Spam Legislation (CASL). You can reach the Privacy Officer at support@routefuse.ca.

If you request quotes as a homeowner: your name, phone number, email address, city, the service you need, how urgent it is, and anything you write in the project details field. You may optionally provide the property type, project street address and Canadian postal code. We use those fields to derive municipality, area or neighbourhood evidence where the source supports it; you are not required to know or select your neighbourhood. We also record the time you submitted, your IP address, and, if you arrived through a referral link, the referral code.

If you apply as a contractor: your name, business contact details, city, the services you offer, and anything you tell us about licensing, insurance, or experience. If you subscribe to a paid plan, our payment processor collects your payment details; we receive only a customer reference and the status of your subscription.

If you seek the public Verified status: we collect the limited evidence listed in your verification checklist, which may include an identity document, business or sole-proprietor registration, municipal or provincial authorization, trade credentials, WCB clearance where applicable, and current commercial-liability insurance evidence. Files are stored privately; the public sees only the verification status, policy version, scope and validity date—not the documents, document numbers, address, birth date, or insurance policy details.

For business bookkeeping and accountant access: we retain recorded payment, refund, credit, dispute, provider-fee, payout, bank-deposit, expense, receipt, tax, advertising-spend-link and classification evidence. If a shareholder pays a business cost personally or advances money to Route Fuse, we may record the shareholder name, purpose, amount, reimbursement or repayment state, supporting reference, optional account label and only the last four account or card digits. Accountant and owner classifications, corrections, approvals and reasons are retained in the financial audit trail. Route Fuse does not decide deductibility, taxable-benefit, dividend, capital-contribution or filing treatment; those remain for the accountant.

Automatically, for everyone: standard server and analytics information such as pages viewed, approximate location derived from IP address, browser type, and the time of the visit. We also record how you reached us — the website or search that referred you, and any campaign tags on the link you followed — and keep it against a first-party cookie so a return visit is recognised. Section 9 explains this in full.

For geographic intelligence: if you supply a project address or postal code, a mapping provider may return coordinates, accuracy, locality and neighbourhood labels. Route Fuse stores a keyed query fingerprint instead of a reusable plain-text geocoding query in the evidence record. We also use official municipal, regional and provincial geography datasets across Route Fuse markets. Where a municipality does not publish comparable local units, we may use clearly labelled 2021 Statistics Canada census tracts, dissemination areas or aggregate dissemination areas as statistical analysis units—not as neighbourhoods or routing zones. We retain the publisher, dataset, licence, source identifier, source confidence, refresh evidence, name and a centroid or bounding box where useful; source polygon payloads are not retained. Aggregate public permit records, where available, are stored as neighbourhood/day/category totals. These public geography records do not contain household addresses or names.

As a request moves through Route Fuse: we record operational milestones such as qualification, routing attempts, offers, responses, contact confirmation, optional estimate and scheduling updates, completion evidence, reroutes, activation steps, and email or SMS delivery status. Where you choose to tell us why something did not proceed, we keep the selected reason and any optional detail you provide. Each record also states whether it came from the system, a homeowner, a contractor, or an administrative correction, and how certain that evidence is.

For paid subscriptions, we separately record an accepted-opportunity event after a valid acceptance and contact release, together with the provider-period evidence, plan and price snapshot, service/city dimensions, and any objective restoration review. We also classify declines and offer timeouts for observation. Proposed allowance scenarios and decline review states are analytical evidence only unless Route Fuse later documents and activates a separate owner-approved policy; current observation does not change routing, billing, existing completed-job caps, accepted work, warning delivery, or contractor pause status.

For lead timing and readiness: contractors may save a separate schedule for each canonical job-city timezone they serve, including weekly opening and closing intervals, date exceptions, completeness and validation history, plus a separate emergency coverage schedule and explicit opt-in. Route Fuse may keep the canonical job-city timezone, local request date, schedule snapshot, eligibility or no-coverage reason, exact offer and first-contact deadline calculations, the notification channel and whether a notification was queued, accepted by the provider, delivered or failed, and contractor-logged call-attempt or substantive-message metadata. Emergency qualification may record explicit job-local coverage, Emergency-Ready status, `available_now` status and evidence that the availability confirmation was no more than 60 minutes old. A first-contact record includes its type, time, recorded time, a deduplication key and a short privacy-minimized evidence reference. We do not request call recordings or message bodies for this record.

Lead Timing V3 is active-capable but may be prepared rather than active. When the exact guarded V3 policy is active, only newly committed V3 generations use the recorded matrix: emergency uses 15 continuous minutes for the offer and, after contractor acceptance and committed contact access, 15 continuous minutes for first contact; urgent same-day uses 45 continuous offer minutes and 30 continuous first-contact minutes without an overnight hold; normal uses 180 and 120 business minutes in the canonical job-city timezone and the accepting contractor's complete valid receiving schedule; planning/future requests remain on legacy timing. The V3 offer clock starts only when the first configured notification provider accepts the API request. Provider acceptance is not delivery or read; those are separate events when evidence exists.

V2 rows remain observation-only, and all existing or already in-flight legacy generations remain isolated on their recorded 12-hour offer, 24-hour contact nudge and 48-hour accepted-contact workflow without backfill or shortening. A V3 first-contact record may satisfy the pinned rule, but it is not homeowner confirmation. If an accepted V3 contact deadline is missed, Route Fuse may record one breach, send the configured reminder and ask the owner to follow up. That miss does not automatically reroute the accepted request, revoke contact access, increment ghost or decline counters, change billing, consume or alter a trial, change a cap, or pause the contractor.

Privacy Policy v12 changes the timing disclosure, not the retention schedule or contact-access periods: the periods in Section 6 and the existing purpose-bound access rules remain unchanged. Route Fuse does not claim that this policy or the timing evidence has certified legal sufficiency; professional Canadian privacy and consumer-protection review remains appropriate.

For a normal homeowner request, we store a short-lived one-way hash of the email-confirmation link, the normalized email address, send attempts, confirmation status and timestamps. We do not store the usable link. Emergency requests may enter matching before confirmation and are recorded as an unverified emergency bypass for owner monitoring rather than being mislabelled as verified.

If you call Route Fuse: we record minimal call status, duration, keypad selection and provider references. Live calls are not recorded. If you choose voicemail after hearing the notice, Twilio records and transcribes that message so Route Fuse can respond; email remains the non-recorded alternative.

We do not knowingly collect personal information from children, and we do not collect health information. Full payment-card and bank-account credentials are not stored by Route Fuse; the Finance portal may retain an optional account label and last four digits solely to identify a business payment or reimbursement record.

We use your information to match a request to one contractor, to notify that contractor, to confirm the outcome with you, to operate accounts and billing, to maintain and reconcile business financial records, to support accountant review and lawful filings, to detect spam and fraudulent submissions, to investigate complaints, and to improve how well the matching works.

We also use the operational history to measure where requests repeatedly stop, distinguish known facts from estimates, and show an administrator evidence-backed opportunities to improve the marketplace. These reports do not automatically change routing, pricing, contractor access, advertising campaigns, or budgets, and an uncertain inference is not used as a contractor penalty.

Geographic evidence helps us describe service coverage and compare city, area or neighbourhood patterns after enough Route Fuse activity exists. It does not automatically change which contractor receives a request, target a household, prove homeowner demand, forecast work, or change advertising spending.

Contractor verification evidence is used only to decide, maintain, explain, expire or revoke the public Verified status; prevent unsupported trust claims; and investigate credential complaints. Public verification is separate from the operational approval that determines whether a contractor may receive a request. It is not used to guarantee workmanship, pricing, job completion, future insurance coverage, or conduct after the review date.

We use it for marketing — newsletters, seasonal reminders, feature announcements — only where you have given us express consent by ticking the optional marketing box, or where the law otherwise permits it.

When you submit a request, you must tick a box confirming that you understand your details will be shared with one matched contractor. That consent is required, because sharing your details with a contractor is the service. We store the exact wording you agreed to and the moment you agreed to it, so there is a record of what was actually said rather than a bare "accepted" flag. The record separately identifies the Privacy Policy and Terms versions presented with the request. Marketing consent remains separate.

Normal requests are held until you use the one-time link sent to the email address you supplied. The link expires after 24 hours and a replacement revokes the older link. Emergency requests are not delayed by this email step, but their contact information is clearly recorded as unverified and monitored accordingly.

Marketing consent is a separate, optional box that is never pre-checked, and declining it does not affect your request. You may withdraw marketing consent at any time using the unsubscribe link in any marketing email or by emailing us. We act on withdrawals immediately; CASL permits up to 10 business days and we do not rely on that allowance.

Withdrawing marketing consent does not stop service messages you asked for, such as the receipt for your own quote request, a contractor's contact details, or billing notices on an active subscription. If you want to stop those, ask us to close the account.

Text-message consent is controlled separately from marketing email. Replying STOP immediately suppresses future texts to that number; START restores them, and HELP returns assistance information. Route Fuse retains the suppression record so deleting it cannot accidentally permit renewed contact.

One matched contractor. When your request is accepted, the receiving contractor can reveal your name, contact details, city and job description for the purpose of following up on that accepted request. Route Fuse records the matched contractor, purpose, data categories, policy versions, disclosure channel and access time. If that contractor declines or does not respond in time, the request may be offered to the next contractor in line — but Route Fuse offers the request to only one contractor at a time. This does not prevent you from independently contacting or hiring anyone else. Normal requests reach this step only after email confirmation; an emergency request may be released sooner so Route Fuse does not delay urgent help, and that bypass remains visibly unverified.

Service providers. We rely on third parties for hosting and databases, private file storage, mapping/geocoding, transactional email delivery, SMS delivery, payment processing, and analytics. They may process your information only on our instructions and only to provide those services. Some of them store or process data in the United States, which means it can be subject to lawful access requests by foreign courts and authorities. Alberta's PIPA requires us to tell you this plainly, and this paragraph is that notice.

Legal and safety. We may disclose information where required by law, to enforce our Terms, or to address fraud, security incidents, or a threat to someone's safety.

Business transfers. If Route Fuse is sold or merged, your information may transfer as part of that transaction, and the recipient will remain bound by this policy or a materially equivalent one.

We do not sell personal information, and we do not share it with data brokers.

We keep personal information only as long as we need it for the purpose it was collected for, or as long as the law requires. Our current schedule is below.

Consent and unsubscribe records are the deliberate exception to deletion: if we erased them we could not prove we had permission to contact you, and we could not reliably keep you off a list you asked to leave.

When we honour an erasure request, we remove person-level links and optional free-text evidence from the marketplace history. We may retain anonymous facts such as the service, city, lifecycle stage, timing, and outcome for the remainder of the schedule above, because those facts support billing history and operational reliability without identifying the person.

For project-location evidence, erasure clears the optional street address and postal code, precise coordinates, provider result identifiers and derived area/neighbourhood labels. We may retain the non-identifying city and service skeleton for the same operational and accounting purposes described above.

You have the right to ask what personal information we hold about you, how we have used it, and who we have disclosed it to. You also have the right to have inaccurate information corrected.

Email support@routefuse.ca from the address you used, or include enough detail for us to locate your record. We respond within 30 days, as PIPEDA and PIPA require. If we need more time or must refuse part of a request, we will tell you why and explain how to challenge that decision. There is no charge for a routine request; if a request is unusually costly to fulfil we will give you an estimate before proceeding.

You may also ask us to delete information we are not legally required to keep. Where a deletion request conflicts with a retention obligation above, we will tell you which part we cannot delete and why.

A contractor may replace inaccurate or expired verification evidence through the contractor portal and may ask us to correct a review decision. Removing evidence that is required for the public Verified status will remove that status; it does not require Route Fuse to publish the underlying document or keep an unsupported badge active.

Traffic to this site is encrypted in transit. Access to the administrative tools that contain personal information is restricted to authenticated staff accounts, and significant actions are recorded in an audit log. Payment card details never touch our servers; they are handled by our payment processor.

Contractor verification files are stored outside the application database in private object storage. The database keeps only bounded metadata, a cryptographic file hash, review state and an internal storage key. Contractors may access only their own evidence; owner review access uses short-lived signed links and every approval, rejection, replacement request, expiry and revocation is retained in an append-only decision history.

Detailed marketplace timelines and failure classifications are restricted to the owner-administrator. They are not shown to other contractors, and corrections append a replacement record instead of silently rewriting the original evidence.

Homeowner contact details are omitted from bulk contractor and administrative lead lists. An authenticated user must request a purpose-specific reveal through the application, and Route Fuse records whether access was allowed or denied. The owner may revoke or restore a contractor's future portal access with a reason. Automatic time-based expiry is not active unless Route Fuse later adopts an owner-approved, legally reviewed lifecycle policy; historic consent, disclosure and access evidence remains preserved even when future visibility ends.

No safeguard is absolute. If a breach creates a real risk of significant harm to you, we will notify you and the Office of the Privacy Commissioner of Canada as the law requires.

We use a session cookie to keep you signed in, and a first-party cookie that lasts up to 180 days so we can recognise a returning visit. Alongside it we record the pages you visit on this site, the website or search that referred you, any campaign tags on the link you followed, your device type, and a one-way hashed version of your IP address used to tell real visitors from automated traffic. We keep this so we can tell which of our own advertising and referrals actually bring homeowners and contractors to Route Fuse.

If you go on to submit a request or an application, that visit history becomes linked to your record. We do not run third-party advertising trackers, we do not record your screen or mouse movements, we do not buy additional data about you, and we do not build advertising audiences from your behaviour. If you ask us to erase your information under section 7, the linked visit history is deleted along with it. Most browsers let you block or delete cookies, though blocking the session cookie will prevent signing in to the contractor portal.

If you are not satisfied with how we have handled your information or your request, tell us first at support@routefuse.ca so we have a chance to fix it. You may also complain to the Office of the Privacy Commissioner of Canada, or, for matters under Alberta's PIPA, to the Office of the Information and Privacy Commissioner of Alberta.

If we change how we handle personal information, we will update this page and its version stamp. Where a change materially affects how we use information you already gave us, we will seek fresh consent rather than rely on a silent update.