Homeowner Marketplace Agreement

Effective: on publication, if eznest publishes this version before 1 December 2026 and before the first business or household that is not eznest's own test account opens an account on eznest; otherwise thirty days after eznest gives you the notice described in §13. Until 1 December 2026, or until that first outside account is opened, whichever comes first, eznest publishes changes to this Agreement with effect on publication; from then on, the notice rule in §13 applies.

What changed in 2.3.6. Versions 2.3.5 and earlier said in §2 that if you set up an account for a young person in your household, you consent on their behalf, but they did not say that a child may use eznest inside your household without being a party to this Agreement, that you are responsible for that use, or what a child's profile can and cannot do. Version 2.3.6 says so, from what the Platform does today. This is a minor change under §13 because it adds no charge and no duty: you were already responsible for what household members do on the Platform and for the young person's account (§2), and this states how that works and changes nothing you get, owe or can do. It takes effect on publication. No one is asked to accept this Agreement again for this version.

• §1.1. The age of majority rule applies to the person who holds an account and accepts this Agreement; a child in a household is not a party.
• §2. New paragraphs on a child in your household: what the profile is, that the child is not a party and you are responsible, what the child can reach, that eznest AI is off for a child unless you switch it on, and what happens to the child's data.
• §13. Records this version.

What changed in 2.3.3. Versions 2.3.2 and earlier said in §7.1 that eznest starts a cooling-off period only if you tell us a project is a direct agreement, and that if you do not flag the project the app shows no cooling-off window. That was not accurate. eznest records a cooling-off window for the project when a marketplace agreement is signed in eznest, with nothing from you, and while it runs it blocks milestone approval and approval of a change order that adds to the price. Version 2.3.3 says so. This is a minor change under §13 because it adds no charge and no duty: it states what the Platform already does and changes nothing you get, owe or can do. It takes effect on publication. No one is asked to accept this Agreement again for this version.

• §7.1. Says the window is recorded automatically when a marketplace agreement is signed, is counted from the signing date, and blocks milestone approval and approval of a change order that adds to the price while it runs. Removes the statement that you must flag a project. Says that on an older project page you can record that the agreement was signed at your home, and that for any other agreement that is not a marketplace agreement eznest records no window.
• §5.6. Says that a change that adds to the price cannot be approved while a cooling-off period runs, instead of every change.
• §13 and the appendix. Record this version and add the cooling-off window to the capability list.

What changed in 2.3.2. Versions 2.3.1 and earlier said in §4.1 that you do not confirm or decline a visit in the app. That was not accurate. You can confirm, reschedule or cancel an appointment a provider proposes. You can approve or decline a visit beyond a seasonal plan's season snowfall cap. For a booking, you can confirm or decline a window the provider's business proposes, accept or decline a different time it offers in answer to your request, ask for another time and withdraw that ask, accept or decline another time the business asks for, and end a booking whose visit the crew could not get into. Version 2.3.2 says so. This is a minor change under §13 because it adds no charge and no duty: it states what the Platform already lets you do and changes nothing you get, owe or can do. It takes effect on publication. No one is asked to accept this Agreement again for this version.

• §4.1. Replaces the sentence that you do not confirm or decline a visit in the app. It now states what you can do about a proposed appointment, a visit beyond a season snowfall cap and a booking's visit time, still says that a job visit's status is the provider's report, and still says to arrange access to your home directly with your provider.
• §13. Records this version.

What changed in 2.3.1. Versions 2.3 and earlier said eznest verifies one thing, that a provider controls an email address, and does not verify business registration. They left out that, once payments through eznest are on, eznest records Stripe's outcome on a provider's connected account as business-registration evidence. This is a minor change under §13: it states what the Platform already does and changes nothing you get, owe or can do. No one is asked to accept this Agreement again.

• The short version, item 2. Qualifies the statement about business registration.
• §3.1. Describes the Stripe outcome, that it is Stripe's determination on records eznest cannot see, and that it says nothing about licences, insurance or identity.
• §3.2. Business registration is listed with that exception, and badges and trust levels are said to reflect the Stripe outcome too.
• §13. Records this version.

What changed in 2.3. Version 2.2 described paying through eznest milestone by milestone and invoice by invoice, and said that nothing is charged without your approval. It did not describe a seasonal plan, whose payments fall due on dates rather than on an approval. Version 2.3 describes how a seasonal plan is paid through eznest: what your household's billing owner accepts, that each dated payment is then charged on its date to the card saved for that plan, how a visit beyond a plan's season snowfall cap is approved before it is charged, and what leaving a plan does. This is a material change under §13 because it describes a way you can be charged. It takes effect as the Effective line above states. No one is asked to accept this Agreement again for this version: nothing for a seasonal plan is charged through eznest until your household's billing owner accepts that plan's billing terms, which is a separate acceptance.

• The short version, item 4. Adds that a seasonal plan's payments are charged on their dates under billing terms your household's billing owner accepted, and that a visit beyond the plan's season snowfall cap needs separate approval from the person entitled to approve its invoice (§5.7).
• §5.1. Our fee to the business is also charged on a seasonal-plan payment, and nothing of ours is added to what you pay for one.
• §5.2. "Approving is the charge" now speaks of a milestone, and points to §5.7 for a seasonal plan. The card you save can be authorised for a seasonal plan. An invoice for a seasonal plan's stage is charged on its date as §5.7 describes; if that charge could not be made, its recorded payer can also pay it after signing in. An invoice for a visit beyond a plan's cap is paid only by approving it, as §5.7 describes.
• §5.4. Says that a seasonal plan's dated payments are not approvals: each is charged on its date because your household's billing owner accepted that.
• §5.5. A payment for a seasonal plan is one of the payments eznest takes.
• §5.7. New. Seasonal plans: joining, the billing terms and who accepts them, the charge on each date, a payment that cannot be charged, a change of billing owner, visits beyond a season snowfall cap and how each is approved, leaving a plan, and whom to contact.
• §13. Records this version.
• Appendix. The rows for deposits and for automatic approval of milestones are updated, and a row for seasonal-plan billing is added.

What changed in 2.2. Version 2.1.1 described the credential levels shown for a provider and said they are not a performance rating, but it did not describe the work record: a second, separate measure of the work a provider has completed on eznest, which eznest shows beside the provider's credentials once it is in operation. Version 2.2 describes it. This is a material change under §13 because it describes something new you will be shown about providers on eznest. It changes nothing you owe and nothing you can do, and until the work record is in operation it changes nothing you see. It takes effect as the Effective line above states. No one is asked to accept this Agreement again for this version.

• §3.2. Adds that the work record is a separate measure and does not change what badges and trust levels are.
• §3.5. New. Describes the work record: what it counts, what you see and what you never see, that it informs you and does not rank, endorse or vouch for a provider, where its criteria are published, and when it begins.
• §8.1. Adds that a dispute outcome in your favour, or a split, is one of the events that can count against a provider's work record, and that opening or withdrawing a dispute does not count against the provider.
• §13. Records this version.
• Appendix. Adds a row for the work record.

What changed in 2.1.1. Version 2.1 said a change to quote-built marketplace work is handled as a change order and a new agreement version. Version 2.1.1 states the rule more completely: an agreement that eznest prepared from an accepted quote can be changed only by a change order; it cannot be replaced by an uploaded PDF. This is a minor change under §13 because it states the rule the Platform already enforces and changes nothing you get, owe or can do. No one is asked to accept this Agreement again for this version.

• §6. States that a quote-built agreement cannot be replaced by an uploaded PDF.

What changed in 2.1. Version 2.0 said in-system contract creation and signing were not available. Version 2.1 corrects that. For work that came through eznest, the Platform prepares the written agreement from the approved template and the accepted quote, and both sides sign it inside eznest. For a provider's own client, the provider may upload the PDF that both sides sign. The signed copy and audit certificate are kept for both parties. This is a material change under §13 because it changes what you can do in the Platform. It took effect on publication, on 2026-10-14, under the rule stated at the top of this Agreement; no one is asked to accept this Agreement again for this version.

• §6. Replaced the statements that in-system contract creation and signing are not available, and that signing will be described later. The section now describes the agreement sources, native signing, change-order versions, signed copy and audit certificate.
• Appendix. The capability row for creating or signing a contract now records that marketplace work is prepared and signed in the Platform, while uploaded PDFs remain available for provider-owned relationships.

What changed in 2.0. Version 1.2.1 described a beta in which you pay your provider directly and eznest charges you nothing and moves no money. Version 2.0 describes how payments work once they run through eznest. It changes what you owe and what you can do about it, so it is a material change under §13. It took effect on publication, on 2026-10-12: until 1 December 2026, or until the first business or household that is not eznest's own test account opens an account on eznest, whichever comes first, eznest publishes changes to this Agreement with effect on publication, and from then on the notice rule in §13 applies. Section by section against 1.2.1:

• The short version, items 4 and 5. Say how a payment through eznest works, that a milestone of a provider who takes payment through eznest cannot be approved without a saved card, and that the only money a dispute outcome can move is a refund of a payment we processed.
• §1. The list of things we are not no longer says we are not a payment processor, and now says we are not a holder of other people's funds. Payments through eznest are processed by Stripe, and we hold no funds.
• §5.2. Replaced. It sets out the two ways you can pay: through eznest, where your provider's business is set up for it, or directly to your provider, and it says that while your provider's business takes payment through eznest a milestone cannot be approved until a card is saved for it. It says whose card is charged, when, to whose account, and what happens when a charge fails.
• §5.3. Approving a milestone is, where payment is taken through eznest, the moment your card is charged.
• §5.4. Automatic approval is removed. Version 1.2.1 described a setting that approved small milestones for you after 72 hours. eznest does not approve milestones on your behalf, so that section said something the product does not do. Nothing is approved or charged without you.
• §5.5 and §5.6. A deposit is still not something eznest collects. A change that adds to the price is charged like a milestone, and a reduction refunds nothing on its own.
• §7.1. The reference to automatic milestone approval is removed, and the refund after a cooling-off cancellation is described.
• §8.1 and §8.2. Replaced the statements that our outcome "moves no money" and that we do not "issue refunds". A dispute outcome in your favour or a split exists only as a refund of a payment we processed. §8.2 says exactly when, how much, from whose account, and what a refund does not decide.
• §12. Adds that we are not responsible for a refund the processor refuses or for a provider's account being unable to fund one.
• §13. Records this change. It applies to work already under way: from 2026-10-12, the date it took effect, approving a milestone of a provider whose business takes payment through eznest charges it, or needs a saved card, as §5.2 describes, whenever the work began. Before that date nothing is charged.
• Appendix. The capability status table is updated to match.

This Agreement is between you and Eznest Technologies Inc. ("eznest", "we", "us") — a corporation incorporated under the Canada Business Corporations Act on 13 June 2026, corporation number 1801532-5, with its registered office at 226 Kinloch Crt, Nepean, Ontario K2J 5S9, Canada. It governs your use of the eznest platform as a homeowner or household member. If you are a service provider, the Provider Terms of Service apply to you instead.

By using eznest, you agree to this Agreement, the Acceptable Use Policy, and the Privacy Policy.

The short version

Six things worth knowing before you read the rest. Each is expanded below, and where the short version and the detail differ, the detail governs.

1. eznest introduces you to a contractor. We are not part of the deal you strike with them. The agreement to do the work is between you and them, and we do not sign it, guarantee it, or stand behind it.
2. We do not check contractors. We do not verify licences, insurance or identity, and we run no background checks of any kind. We do not verify business registration either, with one qualification: once payments through eznest are on, a provider's business-registration evidence can be Stripe's outcome on the provider's payment account. That is Stripe's decision on records we cannot see, and it says nothing about licences, insurance or identity (§3.1). Check them yourself before you let anyone into your home.
3. eznest is free for homeowners. We charge you nothing. Our revenue comes from a fee charged to providers.
4. We never hold your money. Where your provider's business takes payment through eznest, approving a milestone charges your saved card, directly on your provider's own payment account, and we keep nothing of it but the fee we charge your provider. Where it does not, you pay your provider directly, outside eznest. Where it does, you cannot approve a milestone until a card is saved for it. A seasonal plan is paid differently: once your household's billing owner accepts the plan's billing terms, each of its payments is charged on its date to the card saved for that plan, and a visit beyond the plan's season snowfall cap needs separate approval from the person entitled to approve its invoice (§5.7).
5. We will help if something goes wrong, but we are not a court. Our dispute process is an internal case record that pauses approvals and binds no one. The only money it can move is a refund of a payment we processed.
6. Reviews here are from people who actually hired. We never filter, gate or delay a review because of what it says.

1. What eznest is

eznest is a venue. We help homeowners describe what they need and connect with local service providers, and we give both sides tools to keep track of the work — a project record, messages, quotes, milestones, change orders and documents.

We are not a contractor, a broker, an agent, an employer, or a party to your work agreement. When you engage a provider through eznest, the contract for that work is between the two of you. Every contract document our system produces names exactly two parties — you and the provider — and eznest is not one of them. We have no signature line on it, and we could not add one.

We are also not a bank, a lender, an insurer, a holder of other people's funds, a lawyer, or an arbitrator. Payments made through eznest are processed by Stripe, and we hold no funds (§5.2).

1.1 Who can use eznest

You must be the age of majority in your province and able to enter a binding contract. eznest currently serves Ontario.

That rule applies to the person who holds an account and accepts this Agreement. A child may use eznest inside an adult account holder's household without being a party to this Agreement or to the Privacy Policy. A child accepts neither document and has no account of their own to sign in with; §2 says how that works and who is responsible.

Access is by invitation only. During this beta, creating an account requires an invitation code from us. We may end, extend or change the beta at any time.

1.2 The Platform is early

eznest is in an early, invited release. Features described here may change, and some capabilities that exist in the product are switched off. Where that is the case, this Agreement says so rather than describing them as though they were running. We will not tell you something works when it does not.

2. Your account

You are responsible for your account and for what happens under it. Keep your sign-in secure and tell us promptly at support@eznest.ca if you think someone else has access.

We do not offer two-factor authentication today. We are telling you so you can judge for yourself how to secure the account you use to sign in.

You may add household members. If you do, you are responsible for what they do on the Platform, and for having the authority to share your household's information with them. A child in your household. If you are the owner, an administrator or a manager of your household, you can set up a profile for a child or teen of your household. A child may use eznest that way without being a party to this Agreement or to the Privacy Policy, and you, the adult account holder, are responsible for that use as you are for any household member's (above). By setting the profile up, you consent on the child's behalf, and eznest records that you did. What that means in practice:

• What the profile is. It holds a name, an optional date of birth, an avatar and a PIN you choose. It has no real email address, no password and no sign-in of its own. A child uses it on a shared device, after you enter the PIN from your own signed-in account. On the website, that child session locks again after 15 minutes.
• What a child can reach. The household chore board, the child's coin balance and the reward store. The child can claim chores and ask for a reward; unless you have turned that requirement off, a reward request waits for your approval. The child can also reach the home document vault, but only at the level you set for that child, which starts at none, and never to delete, share or export. A child's profile cannot be given access to your household's projects, quotes or visit photos, which are for adult members only. The eznest apps give a child's profile no screen for messages with a business, and the eznest server refuses a child's profile any request to open a conversation with a business, to write in one or to hold its live connection.
• eznest AI is off for a child until you switch it on for that child. Even then, a child keeps only a short list of read-only help about their own screens.
• What you control. You can change a child's controls, set or clear their PIN, and see, download and delete the child's data. A real cash allowance is off until you switch it on, and eznest records that you did.
• A child's data. §11 of the Privacy Policy says what eznest keeps for a child's profile, what your download holds and what deleting the profile erases and keeps.

You can close your account at any time from Settings → Account. What that erases, and what it does not, is set out in §7.4 of the Privacy Policy.

3. Providers, and the fact that we do not check them

Read this section twice. It is the most important thing in this document.

3.1 What we actually verify

We verify one thing ourselves: that a provider controls the email address on their account.

We also record one outcome that someone else determined. Once payments through eznest are on, and a provider has connected a Stripe account, we record Stripe's outcome on that account as the provider's business-registration evidence when Stripe has enabled the account for charges and has nothing outstanding on it. This is Stripe's determination, made on records eznest cannot see. It is not a review by eznest, and it is not confirmation with any registry or regulator. It says nothing about licences, insurance or the identity of the individual behind the business (§3.2). If Stripe later restricts or disables the account, or asks for more and the deadline passes, we stop recording it. Until payments through eznest are on, there is no such outcome to record.

That is the entire list.

3.2 What we do not verify

We do not verify, and you must not assume we have verified:

• trade licences or certifications, with any regulator or issuer;
• Home Construction Regulatory Authority registration;
• Electrical Safety Authority licensing;
• WSIB coverage or clearance;
• liability insurance — whether it exists, what it covers, or its limits;
• business registration or corporate standing, other than by recording Stripe's outcome as §3.1 describes, which is Stripe's determination and not ours;
• the identity of the individual behind the business;
• criminal record, police clearance, or vulnerable-sector screening.

We run no background check of any kind, at any level, on any provider. No tier of our system includes one. If you have read otherwise anywhere, that was wrong.

Providers may upload business documents — a registration, an insurance certificate, a trade certification — and an eznest administrator may look at them. That is a person's eyes on a PDF, not verification with the issuer. A document we have looked at may be expired, altered, or belong to someone else, and we would not know.

Badges, trust levels, and words like Bronze, Silver or Gold that appear in the product reflect how much a provider has told us and shown us, and, once payments through eznest are on, the Stripe outcome described in §3.1. They are not a performance rating, an endorsement, or a safety assurance. The work record in §3.5 is a separate measure. It does not change a provider's badges or trust level, and they do not change it.

3.3 What that means for you

Before you let anyone into your home or pay them anything:

• ask for their licence number and check it yourself with the relevant Ontario regulator;
• ask for a certificate of insurance and confirm it with the insurer, not the contractor;
• ask for a WSIB clearance certificate if the work warrants one;
• get references and call them;
• get the agreement in writing before work starts.

You choose your provider. You accept the risk of that choice. We provide the introduction and the tools; we do not provide assurance about the person.

3.4 We do not guarantee the work

We do not warrant, guarantee, insure or stand behind any provider's work — its quality, its timeliness, its completion, its compliance with the building code, or anything else. Any warranty on the work runs from your provider to you, under whatever you agreed with them. eznest gives no warranty on the work at all.

3.5 The work record

Beside a provider's credentials, eznest can show a second and separate thing: the provider's work record. The badges and trust level in §3.2 reflect what a provider has told us and shown us. The work record reflects what has happened on eznest: the jobs the provider completed through eznest, and whether anything on those jobs went wrong in a way that eznest decided was the provider's doing. The two are never combined into one number.

When it begins. eznest shows the work record only from the date it puts the work record in operation under the Provider Terms of Service, after giving providers notice. Until that date, eznest shows you no work record for any provider.

What it counts. A job counts once a project on eznest has reached delivery and been closed. Requests, quotes, bids that were not accepted, and cancelled work never count. A completed job counts against the record only because of an outcome eznest decided: a dispute eznest resolved in the client's favour, a dispute eznest resolved with fault on both sides, or a refund eznest records as issued for a service failure. A dispute being opened is not evidence of anything, so a dispute that was withdrawn, decided by a card network, or resolved in the provider's favour never counts against the provider. Faults stop counting after a set period, and every provider starts from the same published starting point, so a small number of jobs cannot produce a misleading figure.

What you see. Once a provider has completed enough jobs on eznest for the record to mean something, the provider's page shows a number out of 100 and a band in words, with the facts beneath it: the number of jobs completed on eznest, the provider's dispute history, the average client rating and the number of verified reviews where there are any, and every event that moved the number, with what it was and the month it happened. A bid or quote from the provider shows a shorter line: the number, the band and the number of jobs completed, with a link to the criteria. Before a provider has completed enough jobs, you see a statement that the provider is new to eznest and does not yet have enough completed work to show a record, with no number and no band. Until eznest has verified that its dispute records are complete, the record is calculated without disputes and says that dispute history is not yet part of it. It never shows a count of disputes, including zero, that eznest has not been able to observe.

What you never see. Individual dispute records, dispute reason codes, evidence, payment-processor identifiers, internal notes, the reasons for eznest's decisions, or any appeal the provider has made. The provider sees the same record you see and can ask eznest to correct an event on it. When eznest overturns a decision on appeal, the record is calculated from the corrected outcome.

What it is not. The work record is information for you to weigh. It is not a ranking: it does not decide which providers you are shown or in what order. It is not an endorsement or a recommendation of any provider, eznest does not vouch for a provider through it, and it does not predict how a provider will do your job. It is not verification of anything listed in §3.2: a provider with a high work record has been checked no more than any other, and everything in §3.3 still applies. A provider cannot buy a better work record or improve it by paying eznest anything. When no work record is shown for a provider, that is not a mark against them; they may simply not have completed enough jobs on eznest yet.

The criteria. What counts, how each event is weighted, the starting point, the period after which faults stop counting, the number of completed jobs needed before a record is shown, and the bands are published in full at eznest.ca/work-record (How the work record is calculated), together with the version of the criteria in force. A change to any of them is published there with a new effective date before it applies.

4. How hiring works

There are two routes to the same place, and either is a valid way to engage a provider.

Post a project and take bids. You describe the work. Eligible providers submit bids. You review them and award one. The winning bid is accepted, the others are declined, and a conversation opens between you and the provider you chose.

Accept a quote. A provider sends you a quote — a price, a scope, and any terms they attach. You accept it. That accepted quote becomes the basis for the work, and any competing quotes on the same project close.

Either way:

• You are never obliged to award anything. A posted project creates no commitment. You may take no bids at all.
• A bid or quote is the provider's offer, not ours. We do not set, review, approve or vouch for any price.
• What you agree with your provider is your contract with them. eznest records it. eznest is not bound by it.

4.1 Site visits

A provider schedules visits and updates a job visit's status — confirmed, on the way, on site, working — from their side of the product. A status showing in eznest for a job visit is the provider's report of what they are doing, not our verification of it, and you do not set it.

You can do these things about a visit in eznest:

• An appointment a provider proposes. When a provider proposes an appointment to you, you can confirm it, reschedule it or cancel it in eznest. A proposed appointment is confirmed only by the other person, so the provider cannot confirm it for you.
• A seasonal-plan visit beyond the season snowfall cap. You can approve or decline each such visit, as §5.7 describes. Only the person §5.7 names can answer it.
• A booking's visit time. When a provider's business proposes a window for a booking, you can confirm it or decline it; declining leaves the booking in place for the business to propose another window. When the business answers your booking request with a different time, you can accept that time or decline it; declining withdraws your request. Once a booking is scheduled, you can ask for another time, which changes the booking only if the business accepts it, and you can withdraw your ask until the business answers it. When the business asks for another time, you can accept it or decline it; declining keeps the booking's time. If the crew could not get into your home for a visit, you can end that booking until the business books a new time for it.

Arrange access to your home directly with your provider.

4.2 Work agreed at your door

If a provider signs an agreement with you at your home and then records it in eznest, that agreement is between you and them, made outside the Platform. This Agreement governs your use of eznest; it does not govern that contract, and it does not displace any statutory right you have in relation to it — see §7.

5. Money

5.1 eznest is free for homeowners

We charge you no fee: no booking fee, no service fee, no commission, no subscription, no percentage of your project. Our revenue comes from a fee we charge providers on work you have approved, and on seasonal-plan payments charged through eznest under billing terms your household accepted (§5.7). That fee is between us and them. Where a payment goes through eznest, our fee and Stripe's card-processing cost come out of your provider's side of the payment. The amount charged to your card is the amount of the milestone or invoice you approved or paid, or of the seasonal-plan payment as your household accepted it, with nothing of ours added to it.

5.2 Two ways to pay

For each piece of work, one of two things is true.

Your provider's business takes payment through eznest. In that case:

• You save a payment method with Stripe. Stripe's hosted page collects the card, and eznest never receives your card number. Only the household's billing owner can save the card that will be charged, except that an already-issued seasonal-plan invoice is paid with its recorded payer's card (§5.7), and the card you save is authorised for that provider and that milestone or invoice, or for that provider's seasonal plan (§5.7). You can see each authorisation, and whether it is charged through eznest, on your saved payment methods page.
• Approving is the charge. When you approve a submitted milestone, we charge that saved card for the milestone's amount in the same step (§5.3). We take no money for a milestone before you approve it. A seasonal plan's dated payments are charged differently, under the billing terms your household accepted for that plan (§5.7).
• The charge goes to your provider's own Stripe account. It is a direct charge on that account. Your provider is the merchant, Stripe pays them out, and eznest takes only the fee we charge your provider out of that payment. We do not collect your payment into an account of ours.
• We never hold your money. We have no trust account, no pooled account and no custodial hold, and there is no eznest account that your project money passes through.
• The billing owner pays. The card charged is the household billing owner's, who may be a different person from the household member who approved the milestone. For an issued seasonal-plan invoice, the recorded payer stays responsible as §5.7 describes, even after a billing handover.
• Invoices. If your provider sends you an invoice that is not part of a marketplace project or a seasonal plan, you pay it yourself after signing in. A link to an invoice cannot charge your card. An invoice for a seasonal plan's stage is charged on its date as §5.7 describes; if that charge could not be made, its recorded payer can also pay it after signing in. An invoice for a visit beyond a plan's cap is paid only by approving it, as §5.7 describes.
• A saved card is needed before you can approve. While your provider's business takes payment through eznest, you can approve a milestone only once your household has a billing owner and the billing owner has saved a card for that milestone. Until then the approval is refused, and eznest says what is missing.
• If a charge does not go through. If your card is declined, nothing is paid, the milestone is not marked paid, and we tell you why. A further attempt needs a new authorisation from the billing owner. If we cannot tell whether a charge went through, we check with Stripe using the same reference and do not charge you twice.
• Refunds. A refund of a payment through eznest goes back to the payment method you paid with, and comes out of your provider's Stripe account. §8.2 and §7.1 say when we make one. Your provider can also refund you from within eznest.

You pay your provider directly. If your provider's business is not set up for payments through eznest, approving a milestone still records your acceptance, but nothing is charged. You and your provider agree how and when you pay, whether by cheque, e-transfer or card, and the money moves directly between you, outside eznest. We do not process, collect, hold, transmit, remit or refund that payment, and we cannot release, reverse or protect it.

eznest offers no payment guarantee and no purchase protection. Any protection your card issuer gives you is between you and your card issuer.

5.3 What "approving" a milestone means

If your project is broken into milestones, your provider marks one submitted and you approve it. Approving records your acceptance of that portion of work. Where payment is taken through eznest, approving is also the moment your saved card is charged, and it is the only thing that charges it. Where payment is made directly to your provider, approving charges nothing.

A milestone you approved before payment could be taken through eznest for it is not charged later.

5.4 Nothing is approved without you

eznest does not approve a milestone for you. A submitted milestone waits until you act on it, and no milestone is approved or charged because time has passed or because you did not respond. Approval can be blocked while a cooling-off period is running on the project (§7.1) or while a dispute is open on it (§8.1).

A seasonal plan's dated payments are not approvals. Each is charged on its date because your household's billing owner accepted that when accepting the plan's billing terms (§5.7), and none is charged unless those terms were accepted. A visit beyond a plan's season snowfall cap is an approval: it is charged only if the person entitled to approve its invoice approves that visit (§5.7), and never because time has passed.

5.5 Taxes, deposits and holdback

Your provider is responsible for charging and remitting HST on their work. eznest calculates, collects and remits no tax on your project.

If you and your provider agree a deposit, that is between you. eznest does not collect a deposit, does not cap it, and does not hold it. A payment is taken through eznest only as the charge for a milestone or invoice that you approved or paid, or for a seasonal-plan payment under billing terms your household accepted (§5.7). Ontario's Consumer Protection Act, 2002 governs what a contractor may require from you in the circumstances it covers; nothing here limits it.

Where statutory holdback applies to your project under Ontario's Construction Act, eznest may display a calculated figure for reference. That is arithmetic on numbers you and your provider entered. eznest does not hold back, retain, or release holdback funds, and the obligation to deal with it correctly sits with you and your provider under your contract.

5.6 Change orders

Once work is agreed, a provider can propose a change to scope or price. It takes effect only when you approve it. Nothing you did not approve changes what you owe. Where payment is taken through eznest, approving a change that adds to the price charges the added amount in the same way as a milestone (§5.2).

A change that adds to the price cannot be approved while a cooling-off period is running on the project (§7.1). If you and your provider agree a reduction rather than an increase, eznest records the reduced scope and refunds nothing on its own. Settling money already paid is between the two of you, or through a refund your provider issues from within eznest, because we hold none of it.

5.7 Seasonal plans

A seasonal plan is a standing arrangement with one business for one of your homes, most often snow clearing for a winter, under which the business attends when the conditions the plan states are met rather than when you book a visit. The plan is a contract between your household and the business. eznest is not a party to it (§1), and eznest adds no fee of its own to anything you pay for it (§5.1).

Joining a plan charges nothing. Your household joins a plan by accepting its service terms, either from the list of plans that cover your home or from a business's invitation, and a business can also put your home on its plan once you have accepted one of its quotes. Being on a plan puts your home on the business's round. It does not charge you and does not save a card.

The billing terms, and who accepts them. A plan's payments are taken through eznest only after your household's billing owner accepts the plan's billing terms. eznest offers billing terms for a plan only once eznest has switched plan billing on and the business has set the plan's payment dates and stated its tax. Until then, nothing for a seasonal plan is charged through eznest, and your household pays the business directly, outside eznest, as you and the business agree. The billing terms list each payment with its date, its amount, the tax as the business states it, and its total. They say that each payment is charged automatically on its date, give the price of a visit beyond the plan's season snowfall cap if the plan has one, say what leaving the plan does, and say whom to contact. Only your household's billing owner can accept them; any other member of the household can read them. Accepting them is your household's authorisation for each listed payment to be charged on its date. When you accept, you add a card on Stripe's hosted page, authorised for that business and that plan (§5.2). eznest keeps an exact copy of the terms as they were accepted, with who accepted them and when, and you can read it again on the plan's billing page. eznest also emails a copy to the billing owner, unless email to that address has been stopped. The payments, dates and prices you accepted stay as accepted if the business later changes the plan.

Each payment is charged on its date. On each payment's date, eznest issues an invoice for it and charges its total to the card saved for the plan. Charging begins no earlier than 9 a.m. that day in the business's time zone. A payment whose date had already passed when the billing owner accepted is charged shortly after acceptance, as the billing terms say. Each charge is a direct charge on the business's own Stripe account, as in §5.2: the business is the merchant, eznest holds none of the money, and nothing of ours is added to the amount. Nothing is charged before a payment's date.

If a payment cannot be charged. If no card is saved for the plan, or the card is declined, nothing is charged, and eznest tells the invoice's recorded payer if that person is still your household's billing owner. The payment stays due, and eznest charges it once a valid card authorisation for its recorded payer and consent is available while the plan is active; after a decline, that has to be a newer authorisation. The recorded payer can also pay a stage's invoice after signing in. A billing handover does not move an already-issued invoice to someone else's card, as described below. If eznest cannot tell whether a charge went through, it checks with Stripe using the same reference and does not charge you twice. If the business cannot take payment through eznest when a payment falls due, nothing is charged then, and the payment is charged later only if the business becomes able to take it while your plan is active.

If your household's billing owner changes. Future stages for which no invoice has been issued wait for the new billing owner to accept the plan's billing terms afresh; charging them also requires that person's own card authorisation. An invoice already issued keeps its recorded payer and the plan consent under which it was issued, even after another handover or a return to an earlier billing owner. That invoice can still be charged to its recorded payer using a valid, unrevoked card authorisation under its recorded plan consent (or, for an invoice issued under the original acceptance, a card saved for that invoice), while the plan and the payer's account remain active and the other payment conditions hold. A handover does not transfer that invoice to the new billing owner or replace its consent or card authorisation. If the required authorisation is missing or revoked, the bill stays unpaid; eznest does not use another person's card. The additional approval limits for a visit beyond the cap are below.

Visits beyond a season snowfall cap. A plan can set a season snowfall cap and a price for each visit beyond it. If it does, the billing terms state the cap, the price and its tax in one sentence, which says that each visit for a storm after the season's snowfall has reached the cap costs that price and is charged only if you approve that visit. The season's snowfall is the total the business recorded for the storms it declared in your home's area, from the first day of the season up to the day before the storm in question. The storm that brings that total to the cap or past it is still covered by the plan; each later storm is beyond the cap. A visit beyond the cap counts only once it is marked done, is tied to its storm, and was done after the billing terms were accepted. A replacement visit the business books after rescheduling a storm visit, and a visit eznest has no record of being marked done, are never counted, so you are never asked to approve them.

How a visit beyond the cap is approved. For each such visit, eznest issues an invoice for separate approval. The request shows the storm's date, its snowfall, the season's total before it, the cap, and the price, tax and total as the billing terms state them. Only the invoice's recorded payer who first accepted the plan's billing terms can approve or decline it, while still an active member of the household and while the plan is active. Changing the household's billing owner does not by itself prevent that person from answering an already-issued invoice. A new billing owner cannot answer for the earlier payer, and an overage invoice issued to someone other than the original accepter cannot be approved by anyone, so eznest never charges it. Approval immediately attempts to charge the approving payer's card authorised under that invoice's recorded plan consent, as a direct charge on the business's Stripe account; it never uses the new billing owner's card instead.

If an approved visit has not been charged. The same recorded payer who originally accepted the terms can try the charge again while still an active household member and while the plan is active, if no attempt has been made or the last attempt was definitively refused. After a card decline, a newer card authorisation under the invoice's recorded plan consent is required. A card saved under a later billing takeover does not authorise this earlier bill, even if the same person becomes billing owner again. Without a valid authorisation for that consent, the bill stays unpaid. There is no automatic retry of an overage approval. If a charge's outcome is still being checked, another attempt is blocked until that outcome is resolved; a successful charge is not repeated.

Declining a visit. The answer is recorded once and cannot be changed from approval to decline or from decline to approval. eznest tells the business when a visit is declined. eznest never charges a declined visit and sends no reminder for it. Whether you owe the business for a declined visit in some other way is between you and the business, and eznest does not decide it. A visit beyond the cap is never charged because time has passed or because you did not answer.

Leaving a plan. Your household can leave a plan at any time, from the plan. When it does, the plan stays on your record marked ended, the business is told, your home leaves its future rounds, and the plan's saved-card permission ends. From then on eznest makes no further charge for that plan: no dated payment and no visit beyond the cap. Leaving does not by itself refund a payment already charged; ask the business about a refund. A refund the business makes through eznest goes back to the card you paid with and comes out of the business's Stripe account (§5.2). The business can also end your home's place on its plan, with the same effect on charges. Nothing in this Agreement takes away a right you have under Ontario's Consumer Protection Act, 2002 to cancel or to be refunded (§7).

Questions about a plan. For the service, the plan's terms or a payment already made, contact the business. For help using eznest, write to support@eznest.ca.

6. Contract documents

For work that came through eznest, the Platform prepares the written agreement from the approved agreement template for that kind of work and a schedule frozen from the quote you accepted: the parties, scope lines, price, tax declaration and deposit terms as they stood at acceptance. The schedule's fee clause says that eznest's fee is paid by the business and is not added to the price, and it names no rate or amount. An agreement eznest prepared before version 2.3.5 of this Agreement keeps the words it was prepared with, and eznest does not rewrite the words of an agreement already prepared or signed. Both sides sign that agreement inside eznest. A change to that work is handled as a change order, which becomes a new agreement version. An agreement that eznest prepared from an accepted quote can be changed only by a change order; it cannot be replaced by an uploaded PDF. Eznest does not supply legal advice and is not a party to that agreement.

For a provider's own client, the provider may upload the agreement as a PDF, and that exact file is the version both sides sign. If a provider-uploaded agreement needs correction, the provider may upload a replacement version when no signing process is actively under way, and prior versions and signature evidence stay in the record.

The native signing process records the exact agreement version, both parties, the roles each signer held, electronic-records consent, intent to sign, signing timestamps, signature evidence and a cryptographic fingerprint of the signed content. When every required party has signed, eznest keeps the signed copy and audit certificate for both parties.

You remain free to use your own contract.

7. Your statutory rights

Nothing in this Agreement takes away a right you have under Ontario's Consumer Protection Act, 2002, or any other consumer-protection law that applies to you. Where anything here conflicts with such a law, that law wins and the rest of this Agreement stands.

7.1 Cooling-off

Ontario law gives you a cooling-off period to cancel certain direct agreements — broadly, contracts for more than $50 negotiated or entered into somewhere other than the supplier's place of business, such as your home.

That right comes from the statute, not from eznest, and you have it whether or not it is reflected in the app.

The Platform tracks a cooling-off window for work you sign through eznest. When a marketplace agreement is signed in eznest, eznest records a cooling-off window for the project automatically. You do not need to tell us anything. The window is counted from the day the agreement was signed, using the date in Toronto, and runs for the number of days that applies in your jurisdiction. Where that number is zero, eznest records no window. While the window runs, the Platform blocks milestone approval and approval of a change order that adds to the price on the project (§5.4 and §5.6).

On an older project page, while the project is awarded or under way, you can instead record that its agreement was signed at your home, and eznest then records a window for that project, counted from the day you record it. For an agreement that is not a marketplace agreement, including a provider's own client's agreement even when signed in eznest (§6), and any agreement made away from eznest, eznest records no window. The window we record is a convenience. Whether eznest records a window or not, your legal right is entirely unaffected.

To cancel within your cooling-off period, tell your provider in writing. Marking something in eznest is not notice to your provider.

If you record a cancellation in eznest within your cooling-off period and a milestone or invoice for the project was charged through eznest, eznest opens a refund for the principal charged on each of them and refunds it to the payment method you paid with. Your provider's approval is not needed and your provider cannot refuse it. The refund comes out of your provider's Stripe account (§8.2). Recording a cancellation in eznest does not replace written notice to your provider.

8. Disputes with a provider

8.1 What we do

You or your provider can open a dispute on a project. One at a time. The person who opened it can withdraw it.

While a dispute is open, the Platform pauses milestone approval on that project. That is a real and immediate effect, and it is the main thing a dispute does.

An eznest administrator reviews what both sides recorded and records an outcome with its reasoning. Where the dispute is about one milestone or one invoice you paid through eznest, the outcome can be in your favour, in your provider's favour, a split, or still under review, and an outcome in your favour or a split refunds that payment (§8.2).

Once the work record is in operation, an outcome in your favour or a split is one of the events that can count against your provider's work record, as §3.5 describes. Opening a dispute or withdrawing it does not count against your provider, and neither does an outcome in your provider's favour or a dispute still under review.

8.2 Money, and what we do not do

Our outcome is a recorded view. It is not binding on anyone. The only way it moves money is a refund of a payment we processed.

• When a refund can happen. The dispute must be about one milestone or one invoice that you paid through eznest. A dispute about work you paid for directly, outside eznest, cannot produce a refund, because we processed nothing.
• Who decides it. Only an eznest marketplace administrator can record an outcome that refunds money, and they record a written reason with it.
• How much. If the outcome is in your favour, we refund the whole principal of that milestone or invoice that has not already been refunded. If it is a split, we refund the amount the administrator states, which is less than that. If it is in your provider's favour, or still under review, nothing is refunded.
• Where it comes from and goes. The refund goes back to the payment method you paid with. It is paid from your provider's Stripe account, which your provider agreed to in its Provider Terms, and we then return our own fee on that payment to them in proportion. We hold no funds, so we do not pay a refund from money of our own.
• When it is final. The dispute stays under review until Stripe confirms the refund. If Stripe refuses it, we keep that on record and the dispute is not closed.
• What it does not include. Stripe does not return the card-processing cost of the original payment to your provider, and a refund does not decide any other claim between you and your provider.

Apart from that refund:

• We do not arbitrate or adjudicate.
• We do not mediate to a binding result, and we do not provide or pay for a mediator.
• We do not refer you to arbitration or any alternative dispute resolution service — no such arrangement exists.
• We do not award damages or compensation, or order anyone to pay.
• We do not enforce our own outcome.

Your real remedies are the ones you had anyway — your contract with your provider, Ontario's consumer-protection framework, the applicable trade regulator, your card issuer, and the courts including Small Claims Court. Nothing here replaces them, and using our dispute process does not use up any of them or extend any deadline.

We will provide you with the records we hold about your project if you need them.

8.3 Disputes with us

If you have a complaint about eznest itself, write to support@eznest.ca, or to privacy@eznest.ca for anything about your personal information. We will respond. We would much rather sort it out with you than have it go anywhere else.

9. Reviews

You can review a provider you actually hired, once the work has reached completion. You get one review per project. Your provider gets one response.

We do not gate reviews by what they say. A one-star review takes exactly the same path as a five-star one: no extra confirmation, no delay, no routing to the provider first, no filtering. We will never ask you to reconsider a negative review, and we will never quietly suppress one.

We may remove or hide a review that breaks the Acceptable Use Policy — because it is defamatory, contains someone's personal information, is not about the work, or is fraudulent. We will not remove one because a provider dislikes it. If we remove yours, we will tell you why.

Reviews are your opinion, not ours. We do not verify factual claims inside a review.

10. Your content

What you post is yours. Your project descriptions, photos, documents, messages and reviews remain yours.

You give us permission to store, copy, display and process that content as needed to run the Platform for you — to show your project to providers who can bid, to deliver your messages, to render your documents, to publish your reviews. That permission lasts as long as we hold the content and covers nothing else. We do not use your content for advertising, we do not sell it, and we do not use it to train AI models.

You are responsible for what you post: that you have the right to post it, that it is not somebody else's confidential or personal information you have no basis to share, and that it complies with the Acceptable Use Policy.

11. Suspension and termination

You can leave at any time, from Settings → Account.

We may suspend or close your account if you break this Agreement or the Acceptable Use Policy, if we are required to by law, or if your use of the Platform puts other people or the Platform itself at risk. Where we reasonably can, we will tell you why and give you a chance to put it right first. Suspension is immediate where someone's safety is at stake.

If we close your account, you remain able to obtain your data and to raise a complaint. Your existing agreement with a provider is unaffected — it is not ours to end.

We may stop offering the Platform, or any part of it. If we do, we will give you reasonable notice and time to export your data.

12. Liability

What we are responsible for: operating the Platform honestly and with reasonable care, and handling your personal information as set out in our Privacy Policy.

What we are not responsible for: the acts, omissions, work, conduct, honesty, safety or solvency of any provider; any agreement between you and a provider; any damage, loss, injury or cost arising from work performed; and any decision you make about whom to hire. We are also not responsible for a refund that Stripe refuses, or for a provider's Stripe account being unable to fund a refund. If that happens, your remedies in §8.2 remain.

To the fullest extent the law allows, and subject always to §12.1, eznest is not liable for indirect, incidental, consequential, special or punitive damages, or for lost profits or lost data.

12.1 What we do not limit

Nothing in this Agreement excludes or limits our liability for:

• death or personal injury caused by our negligence;
• fraud or fraudulent misrepresentation;
• anything else that cannot lawfully be excluded, including rights and remedies under Ontario's Consumer Protection Act, 2002.

To the maximum extent permitted by law, eznest's aggregate liability to you for claims arising from this Agreement is limited to CA$1,000. This limit does not apply to the matters listed in §12.1.

13. Changes to this Agreement

If we make a minor change, we update this page and its date.

If we make a material change — one that changes what you get, what you owe, or what you can do about it — we will tell you at least 30 days before it takes effect, explain what changed, and where the law requires it, ask you to accept it again rather than assume you have.

If you do not accept a material change, close your account before it takes effect. Work already under way stays governed by the version in force when you started it.

v2.3.6 — 2026-11-05 (minor change, effective on publication). This version states in §1.1 that the age of majority rule applies to the person who holds an account and accepts this Agreement, and in §2 that a child may use eznest inside an adult account holder's household without being a party to this Agreement or to the Privacy Policy, that the account holder is responsible for that use, and what a child's profile is, what it can reach, that eznest AI is off for it until the account holder switches it on, and what the account holder controls. It adds no charge and no duty: the account holder was already responsible for household members and for a young person's account (§2), and this states how that works from what the Platform does today. It changes nothing you get, owe or can do. As a minor change, it takes effect on publication. No one is asked to accept this Agreement again for this version.

v2.3.5 — 2026-10-29 (minor change, effective on publication). This version states in §6 what the fee clause in the schedule of an agreement eznest prepares from an accepted quote now says: that eznest's fee is paid by the business and is not added to the price, with no rate or amount. An agreement eznest prepared earlier keeps the words it was prepared with, and eznest does not rewrite an agreement already prepared or signed. It adds no charge and no duty: you already pay nothing to eznest (§5.1), and this changes nothing you get, owe or can do. As a minor change, it takes effect on publication. No one is asked to accept this Agreement again for this version.

v2.3.4 — 2026-10-23 (minor change, effective on publication). The appendix row on reporting now records that a signed-in person can report a message, a review, a business profile, a project’s photos or a public business listing on the eznest website, and that the report opens a Trust & safety request naming it. It adds no charge and no duty: it states what the Platform already lets you do and changes nothing you get, owe or can do. As a minor change, it takes effect on publication. No one is asked to accept this Agreement again for this version.

v2.3.3 — 2026-10-18 (minor change, effective on publication). This version corrects §7.1, which said eznest starts a cooling-off period only if you flag a project as a direct agreement. It states that eznest records a cooling-off window when a marketplace agreement is signed in eznest, counted from the signing date, and that while it runs it blocks milestone approval and approval of a change order that adds to the price; that on an older project page you can record that the agreement was signed at your home; and that for any other agreement that is not a marketplace agreement, including a provider's own client's agreement and any agreement made away from eznest, eznest records no window. It also corrects §5.6 to say that a change that adds to the price, rather than every change, cannot be approved while a cooling-off period runs. It adds no charge and no duty: it states what the Platform already does and changes nothing you get, owe or can do. As a minor change, it takes effect on publication. No one is asked to accept this Agreement again for this version.

v2.3.2 — 2026-10-18 (minor change, effective on publication). This version corrects §4.1, which said you do not confirm or decline a visit in the app. It states that you can confirm, reschedule or cancel an appointment a provider proposes; that you can approve or decline a visit beyond a seasonal plan's season snowfall cap; that for a booking you can confirm or decline a window the provider's business proposes, accept or decline a different time it offers in answer to your request, ask for another time and withdraw that ask, accept or decline another time the business asks for, and end a booking whose visit the crew could not get into; and that a job visit's status is the provider's report. It adds no charge and no duty: it states what the Platform already lets you do and changes nothing you get, owe or can do. As a minor change, it takes effect on publication. No one is asked to accept this Agreement again for this version.

v2.3.1 — 2026-10-18 (minor change). Sections 3.1 and 3.2 and the second item of the short version said that eznest verifies one thing, an email address, and does not verify business registration. They left out that, once payments through eznest are on, eznest records Stripe's outcome on a provider's connected account as the provider's business-registration evidence. This version says so, and says that it is Stripe's determination on records eznest cannot see and that it says nothing about licences, insurance or identity. It states what the Platform already does and changes nothing you get, owe or can do, so it is a minor change. No one is asked to accept this Agreement again for this version.

v2.3 — 2026-10-18 (material change). This version describes how a seasonal plan is paid through eznest (§5.7): the billing terms your household's billing owner accepts, that each dated payment is then charged on its date to the card saved for that plan, that a visit beyond a plan's season snowfall cap needs separate approval from the person entitled to approve its invoice (§5.7), and what leaving a plan does. It describes a way you can be charged, so it is a material change. It takes effect as the Effective line at the top of this Agreement states: on publication if eznest publishes it before 1 December 2026 and before the first business or household that is not eznest's own test account opens an account on eznest, and otherwise thirty days after eznest gives you notice of it. No one is asked to accept this Agreement again for this version. Whenever your household joined a plan, nothing for it is charged through eznest until your household's billing owner accepts that plan's billing terms.

v2.2 — 2026-10-16 (material change). This version describes the work record, a separate measure of the work a provider has completed on eznest, which eznest shows beside the provider's credentials from the date it puts the work record in operation under the Provider Terms of Service (§3.5). It changes nothing you owe and nothing you can do, and until the work record is in operation it changes nothing you see. It takes effect as the Effective line at the top of this Agreement states: on publication if eznest publishes it before 1 December 2026 and before the first business or household that is not eznest's own test account opens an account on eznest, and otherwise thirty days after eznest gives you notice of it. No one is asked to accept this Agreement again for this version.

v2.1.1 — 2026-10-14 (minor change). This version states that an agreement eznest prepared from an accepted quote can be changed only by a change order and cannot be replaced by an uploaded PDF. It states the rule the Platform already enforces and changes nothing you get, owe or can do. No one is asked to accept this Agreement again for this version.

v2.1 — 2026-10-14 (material change, effective on publication). This version corrects the description of contract creation and signing. It says that marketplace work is prepared from the approved template and accepted quote and signed inside eznest, that provider-owned relationships may use an uploaded PDF, and that signed copies and audit certificates are kept for both parties. It took effect on publication, on 2026-10-14, under the rule stated at the top of this Agreement. No one is asked to accept this Agreement again for this version.

v2.0 — 2026-10-12 (material change, effective on publication). This version describes payments that run through eznest. It changes what you owe and what you can do about it. It took effect on publication, on 2026-10-12, under the rule stated at the top of this Agreement: until 1 December 2026, or until the first business or household that is not eznest's own test account opens an account on eznest, whichever comes first, eznest publishes changes to this Agreement with effect on publication, and from then on the notice described in this section applies. No one is asked to accept this Agreement again for this version. The summary of what changed is at the top of this Agreement. This change applies to work already under way. From 2026-10-12, approving a milestone of a provider whose business takes payment through eznest charges it, or needs a saved card, as §5.2 describes, whenever the work began. Before that date nothing was charged through eznest.

v1.2.1 — 2026-10-08 (name only). The assistant built into eznest is now called eznest AI; version 1.2 called it Nestor. This is a minor change: only the name changed, so the effective date is unchanged and no one is asked to accept this Agreement again.

14. General

Governing law. This Agreement is governed by the laws of Ontario and the federal laws of Canada that apply there. The courts of Ontario have jurisdiction. If you are a consumer, this does not deprive you of the protection of the mandatory law of your own province, or of your access to Small Claims Court.

No arbitration clause. We have not asked you to give up the right to go to court, and this Agreement contains no mandatory arbitration or class-action waiver.

Assignment. You may not transfer this Agreement. We may transfer it as part of a corporate reorganisation, merger or sale, on notice to you.

Severability. If a provision is unenforceable, the rest stands.

Entire agreement. This Agreement, the Acceptable Use Policy and the Privacy Policy are the whole agreement between you and eznest about the Platform. They do not affect your contract with a provider.

Language. This Agreement is in English. A French version will be published when we open to Quebec. Les parties conviennent que la présente convention soit rédigée en anglais.

15. Contact

Eznest Technologies Inc. Corporation number 1801532-5 (Canada Business Corporations Act) 226 Kinloch Crt, Nepean, Ontario K2J 5S9, Canada

General and support — support@eznest.ca Privacy — privacy@eznest.ca (Privacy Officer: Niruban Kandasamy)

Our name, address and contact details are set out above so you have them in writing, as Ontario's Consumer Protection Act, 2002 requires for an agreement made online.

Appendix — Current capability status

We keep this list because a marketplace agreement that describes capabilities the product does not have is worse than no agreement. It records what each listed capability does today, including what is on, unavailable, not offered, not built, or handled outside eznest. When a row changes, this Agreement and the notice you receive will change with it.