RavenTrack

Legal · Terms of Use

RavenTrack Terms of Use

These Terms govern the RavenTrack website, web application, mobile applications and related financial-record automation services provided by Raven in The Nest Inc., an Ontario corporation, at 1304 Woodbine Ave #1, East York, ON M4C 4E7, Canada (Raven, we or us).

Raven is offered for business use by companies and sole proprietors. The agreement for a Customer consists of these Terms, Schedule A (Data Processing Terms) and any accepted Order. An individual using the Service for a Customer is an Authorized User.

Version 23 October 2026Governed by Ontario lawBusiness use in Canada and the United States
Contact Legal

Read before accepting

Important subscription and risk terms

A summary of key points. The full sections below, including Sections 16 and 17, govern.

Monthly renewal and trial conversion

Unless an accepted Order states otherwise, an eligible new Customer receives three calendar months without subscription fees, followed by monthly paid subscriptions that renew automatically. The paid price, first paid date and any setup-cost recovery must be disclosed and expressly accepted before trial conversion is authorized.

Cancellation and setup costs

Cancel before the next renewal starts to stop future monthly subscription fees. A separately disclosed, agreed and unrecovered setup fee may become due when you cancel, including during a trial if that condition was expressly accepted beforehand.

Automatic posting

An authorized Customer user may enable rules that post accounting records without a separate review of each record. The Customer is responsible for those instructions, permissions and reconciliation.

Liability

Subject to the exceptions in Section 17, Raven's total aggregate liability is limited to subscription fees actually paid for the affected Service during the three calendar months before the first event giving rise to liability. If no subscription fees were paid in that period, including during a free trial, the cap is CAD $100. Read Sections 16 and 17 before accepting.

01

Agreement and acceptance

1.1

Customer acceptance. The Customer accepts this agreement when an authorized representative signs an Order, affirmatively accepts these Terms electronically, or uses another legally valid acceptance method. That representative confirms authority to bind the Customer. A sole proprietor accepts for their own business. Raven may require identity, business and authority verification before activation.

1.2

User acceptance. Authorized Users must comply with the account, security, acceptable-use, intellectual-property and other provisions applicable to their use. Accepting for an employer or other company does not create a personal guarantee of that company's fees. Users remain responsible for their own unlawful conduct and any personal obligations they validly accept.

1.3

Orders and priority. An Order is a quote, pilot letter, service order or electronic checkout record issued or approved by Raven and accepted by the Customer. It identifies the Customer, commercial terms and purchased scope. An Order changes these Terms only where it expressly identifies the provision being changed and Raven accepts that change. A separately executed DPA takes priority for personal-data processing; otherwise Schedule A controls that processing. Section 17 governs contractual liability under Schedule A unless an executed agreement expressly changes it. Mandatory law always prevails.

1.4

Public website. Public website material is for general information. Website access does not create a paid subscription. Website users must respect the acceptable-use and intellectual-property provisions to the extent those provisions are validly made applicable to and accepted by them. Business subscription obligations require the Customer acceptance described above.

02

Eligibility and subscription scope

2.1

Business accounts. The Service is currently for business and sole-proprietor use in supported locations in Canada and the United States. All Authorized Users must be at least 18. Personal, family and household subscriptions are outside the current offering. No mandatory legal protection is waived merely because an account is described as a business account.

2.2

One company. Each subscription covers one identified Customer company or sole-proprietor business. Related entities require separate subscriptions unless an Order expressly permits otherwise. One individual may use separate authorized accounts for different Customers. An account does not give access to another Customer's information.

2.3

Users and limits. The Customer may invite only user types supported by its plan. Outside accountants, subcontractors and homeowners are not included unless Raven makes that access available and authorizes it. User, document, storage, integration and processing allowances and any overage prices must be stated in the accepted Order or plan. Raven will seek agreement before imposing a new charge for previously undisclosed overages.

2.4

Access licence. During the applicable subscription or trial, Raven grants a limited, non-exclusive, non-sublicensable right to use the purchased Service for the Customer's internal business purposes, subject to this agreement. No resale, white-labelling or service-bureau rights are granted. Access may be suspended or ended only as this agreement permits.

03

Accounts and customer instructions

3.1

Administration. The Customer appoints its account owner and administrators, assigns roles and approval limits, invites permitted users, and promptly removes access when it is no longer appropriate. Permissions available to administrators, accountants, bookkeepers and other roles depend on the product controls and plan. The Customer is responsible for checking those settings.

3.2

Security and authority. Each person must use their own account, protect credentials and devices, and promptly report suspected unauthorized access to support@raventrack.ai. The Customer is responsible for instructions issued through its authorized accounts and for its users' compliance. This responsibility does not excuse Raven's own breach of its security obligations.

3.3

Changes and disputes. Raven may rely on authenticated administrator instructions for routine account management. Changes to ownership, banking-related access or other sensitive settings may require additional verification. If account authority is disputed, Raven may restrict affected access while seeking reasonable evidence or joint instructions.

04

Service functions and accounting responsibility

4.1

Current functions. Available functions may extract receipt and supplier-bill information, match card transactions, suggest projects and cost codes, split allocations, route approvals and synchronize permitted records with connected accounting systems. Features vary by plan, release, device and integration. Only features made available or expressly promised in an accepted Order form part of the purchased scope.

4.2

Financial records only. Raven records and organizes financial information. It does not currently hold or transfer customer funds, initiate supplier payments or employee reimbursements, provide banking services, or act as an accountant, tax preparer, auditor, lawyer or fiduciary. Accounting-record authorization is not payment authorization.

4.3

Review and reconciliation. The Customer remains responsible for its books, source records, taxes, filings and compliance. It must check suppliers, amounts, dates, currencies, taxes, projects, cost codes, allocations, attachments and possible duplicates before manual approval, and review the operation and results of any automatic rules. It must reconcile its accounting system regularly, retain records required by law, and promptly report suspected errors.

4.4

Posting and corrections. The Service may create purchases or supplier bills and enrich an existing matching card charge with receipt details. Raven does not provide a function to delete accounting records from QuickBooks. Corrections to records already posted are made in the accounting system, with the Customer responsible for corresponding reconciliation. Product controls intended to preserve bank-source amounts, dates and accounts do not remove the need to verify the resulting records.

4.5

Failures and duplicates. Raven may retry failed synchronization and use reference and invoice checks intended to reduce duplicate postings. Those controls do not guarantee that every duplicate, mismatch, missing record or delay will be prevented. The Customer must review failure notifications and accounting results and must not repeatedly resubmit transactions without checking their status.

05

AI and automatic posting

5.1

AI output. AI Output means extracted fields, classifications, matches, suggestions, summaries and other machine-generated results. AI Output may be inaccurate, incomplete, outdated or unsuitable for a particular purpose. Confidence indicators help prioritize review and are not accuracy guarantees. Output is not professional advice and may not be unique or independently protectable intellectual property.

5.2

Authorized rules. An authorized user may enable automatic posting or standing approval rules where available. Doing so instructs Raven to process and post records satisfying those rules without separate human approval of each record. The Customer must ensure the enabling user has authority and must define, test and monitor the permitted transactions, limits and exceptions.

5.3

Rule changes. The Customer may change or disable available rules through the product or request assistance from support. Disabling a rule stops future processing under that rule once the change takes effect; it does not undo completed postings, and instructions already transmitted to a connected system may need correction there. Suspected unauthorized rules must be reported immediately.

5.4

Data processing and permission. AI processing is subject to Schedule A, the Privacy Policy and any separately required disclosures or permissions. The Customer must give required notices and establish a lawful basis for processing information about its users and other people. Raven remains responsible for permissions and disclosures applicable to its own activities. Acceptance of these Terms does not replace a separate consent or permission required by law or an app store.

06

Connected systems and email intake

6.1

Authorized connections. The Customer may connect only systems it is authorized to connect and only through a method permitted by the relevant provider. Provider approval required for a production connection must be obtained before Raven makes that connection available for production use. These Terms do not represent that QuickBooks, Buildertrend or any other provider has approved a connection or endorsed Raven.

6.2

Access scope. Connecting a system instructs Raven to access the information and perform the actions described in the connection flow and purchased scope, including permitted posting under manual or automatic approval settings. The Customer must review the permissions and maintain the relevant third-party subscription. It must not provide shared credentials or permit automated access contrary to provider restrictions. Possessing a login does not establish the provider's permission for automation.

6.3

Provider changes. Connected systems are governed by the Customer's agreements with their providers. Their outages, limits, changes or withdrawal of access may affect Raven. Raven may restrict a connection if approval, security or legal compliance is uncertain. Raven remains responsible for its own contractual and legally required handling of data when using service providers.

6.4

Disconnection. The Customer may request or use available controls to disconnect a system and should also revoke Raven's authorization in that provider's settings where available. Disconnection ends the related authorization for new access once implemented, but cannot undo completed transfers or provider-side transactions. Previously imported records remain subject to the agreed retention and deletion provisions. Raven will not retain connection credentials for further access after the authorization has ended, except secure residual copies or records required for a lawful purpose.

6.5

Email intake. Email intake applies only when Raven has enabled it for the Customer. The Customer configures and controls forwarding in its own email system and must limit it to authorized business records. Unrelated correspondence and prohibited information must not be forwarded. Handling of message content, attachments and rejected emails must follow the disclosed Privacy Policy and actual enabled configuration. A proposed or staging-only intake feature is not a commitment of current production availability.

07

Monthly subscriptions and the free trial

7.1

Monthly renewal. Unless an accepted Order states otherwise, paid subscriptions renew automatically for successive one-month periods at the disclosed price until cancelled under Section 8. The billing anniversary and first paid date are identified in the Order or activation confirmation. If an anniversary date does not exist in a month, renewal occurs on that month's last day. Billing dates use America/Toronto time unless the Order specifies otherwise.

7.2

Three month trial. Unless separately agreed, an eligible new Customer receives three calendar months without subscription fees starting on the activation date confirmed by Raven. The Order or activation confirmation must state the exact trial end date and first paid date. An extension or different pilot arrangement requires Raven's agreement. Separately agreed setup work is governed by Section 8 and must be disclosed even if subscription fees are waived.

7.3

Conversion authorization. The trial converts automatically to a monthly paid subscription only if the Customer has first expressly accepted the recurring price, currency, first paid date, renewal frequency, cancellation method and any setup-cost recovery. Raven will provide a reminder at least 15 days before the first paid date, or earlier if required by law. If the required paid terms were not disclosed and accepted, the trial ends or access is restricted pending a new agreement; silence alone does not authorize an undisclosed price or payment debit.

7.4

Fees and invoices. The Order specifies prices, currency and agreed charges. Unless stated otherwise, fees are in Canadian dollars, monthly subscription fees are billed in advance, and invoices are due 15 calendar days after issue. Applicable taxes are additional. Automatic subscription renewal does not itself authorize a debit from a payment account. A recurring payment method requires separate express authorization. Payment processors and app stores may impose their own applicable billing terms.

7.5

Changes and disputes. Raven may change recurring prices on at least 30 days' written notice, effective at the first renewal after that notice period and subject to any further consent required by law. The Customer may cancel before the new price applies. Billing disputes should be reported promptly; undisputed amounts remain due. No undisclosed late-payment fee or payment-processing surcharge will be imposed through these Terms.

08

Cancellation and setup cost recovery

8.1

Stopping renewal. An account owner or authorized administrator may cancel renewal at any time before the next renewal starts by emailing support@raventrack.ai from the account email or using a cancellation control where available. No additional 30-day cancellation notice is required for the standard monthly plan. A timely email is effective when received; it is not dependent on Raven processing it before renewal. Raven will acknowledge the cancellation.

8.2

Effective end. Cancellation ordinarily takes effect at the end of the current paid month, or at the trial end if cancelled during a trial. The Customer may request earlier disconnection, but that does not create an automatic refund. App-store-billed subscriptions must also be cancelled through the store where its billing arrangements require that step. Raven will provide the applicable instructions and comply with any mandatory alternative cancellation requirements.

8.3

Agreed setup fee. Setup or onboarding work may have a separately agreed fee. If Raven defers that fee or makes a discount conditional on a disclosed recovery period, the accepted Order must specify the fee, currency, recovery period, reduction formula and exact circumstances in which a remaining amount becomes due. The charge applies only to setup services actually provided and must be reasonably related to their agreed value and unrecovered setup costs.

8.4

Early termination charge. If the Customer cancels, or Raven terminates for an uncured Customer breach, during an agreed setup-recovery period, the remaining amount calculated under that accepted Order becomes due. This setup-cost recovery is the standard early termination charge. It must not exceed the disclosed agreed setup fee less amounts already paid or credited toward recovery, and Raven will not recover the same setup costs twice. There is no separate penalty or obligation to pay future monthly subscription fees under the standard monthly plan.

8.5

Trial cancellations. Any setup charge payable on cancellation during the three-month trial must have been conspicuously disclosed and expressly accepted before the trial began. If no setup fee and recovery arrangement were agreed, no setup-recovery or early termination charge is payable. A fee cannot be created retrospectively by an invoice or an undisclosed internal cost calculation.

8.6

Refunds. Except where required by law, expressly agreed, or provided under Sections 12 or 15, fees for a paid month already started are non-refundable and are not prorated for voluntary cancellation. Refund, cancellation and other non-waivable statutory rights remain intact. Valid fees for completed setup work remain payable, but setup recovery does not apply when the Customer terminates for Raven's uncured material breach or Raven ends the standard subscription for its own convenience.

09

Customer Data and permitted use

9.1

Rights in data. As between the parties, the Customer retains its existing rights in Customer Data and the rights it can lawfully hold in the records and AI Output generated specifically from that data. Customer Data includes records, documents, attachments and personal information submitted by the Customer or imported on its instructions. Rights belonging to individuals, suppliers, providers and other third parties are preserved.

9.2

Service licence. The Customer grants Raven and its authorized service providers the limited rights to host, copy, transmit, process, display and organize Customer Data necessary to provide, secure and support the Service, carry out lawful Customer instructions and satisfy legal obligations. These rights last only as necessary for those purposes and the permitted retention period. They do not transfer ownership or permit unrelated exploitation of Customer Data.

9.3

Customer authority. The Customer must have the rights and lawful authority needed to submit and process the information and must provide notices and obtain consents where required. This includes employee and project-contact information and authorized processing outside Canada. The Customer must not instruct Raven to violate another party's rights or applicable law.

9.4

Restricted information. Do not intentionally upload Social Insurance or Social Security Numbers, full payment-card numbers or security codes, bank-login credentials, health records, biometric identifiers or other highly sensitive information unnecessary for the purchased Service. Masked payment-card details and ordinary business financial records may be processed within the disclosed scope. Raven does not promise to detect or block all restricted information. If it is submitted accidentally, contact privacy@raventrack.ai so the parties can arrange appropriate restriction, redaction or deletion.

9.5

Improvement and catalogue. Identifiable Customer Data is not licensed for general-purpose model training, unrelated AI experiments, cross-customer benchmarking or external publication. Any materially different reuse requires a separate written agreement and any additional lawful basis or consent required. Raven may operate a shared catalogue of lawfully obtained public or licensed supplier product facts, but must not populate it with private Customer prices, receipts or project information. Ordinary operational metrics may be used to run and secure the Service subject to the Privacy Policy and applicable law.

10

Privacy, security and service providers

10.1

Processing terms. Schedule A is part of this agreement and sets the contractual instructions and safeguards for personal information processed for the Customer. The Privacy Policy at www.raventrack.ai/privacy explains information handling and individual rights. A privacy notice is not a substitute for any separate required permission, and these Terms do not authorize future uses merely because a feature may be developed.

10.2

Location. Raven's primary service hosting is in the AWS Canada Central region in Montreal. Authorized AI and other outside providers, connected customer systems and permitted support activities may process or retain information outside Canada as accurately disclosed in the Privacy Policy and applicable processing terms. These Terms do not promise that every third-party copy or processing operation remains exclusively in Canada.

10.3

Safeguards and access. Raven will maintain reasonable administrative, technical and physical safeguards appropriate to the information and applicable law. Access by staff and contractors must be limited to legitimate service, security, support or legal needs and subject to appropriate confidentiality and access controls. A support viewing feature does not imply that all infrastructure administration is technically read-only. No independent certification, specific control or recovery time is promised unless expressly identified in an accepted written commitment.

10.4

Providers and changes. The Customer authorizes the service providers identified in the applicable provider list and Privacy Policy, together with appropriate replacements and additions needed for the permitted processing. Raven retains operational choice of providers, subject to applicable law, its confidentiality and safeguard obligations, and any executed DPA. No fixed advance-notice period applies unless required by law or that DPA. Raven must keep material disclosures current and give notice, obtain authorization or provide an objection process where legally or contractually required. A provider change does not authorize a new unrelated use of Customer Data.

10.5

Affiliates and transactions. Shared founders do not give Peytec, Norseman or another business access to a Customer's data. Necessary disclosures to confidential professional advisers or in a financing, restructuring or business sale must be limited to an appropriate purpose and lawful scope, with protections described in the Privacy Policy and Schedule A where applicable.

11

Acceptable use

11.1

Prohibited conduct. The Customer and Authorized Users must not use the Service unlawfully; infringe intellectual-property, confidentiality or privacy rights; submit malware or fraudulent documents; attempt unauthorized access; bypass permissions or usage controls; conduct penetration or load testing without Raven's written permission; interfere with other users; or use the Service to facilitate unlawful surveillance or discrimination.

11.2

Platform restrictions. Do not share individual logins, resell or sublicense access, remove proprietary notices, copy protected software or documentation, scrape the Service through unauthorized automation, or reverse engineer it except to the extent applicable law expressly permits. A statutory exception remains available only within its lawful scope. Raven may enforce reasonable technical controls without imposing undisclosed usage charges.

11.3

Reports. Report suspected security vulnerabilities privately to support@raventrack.ai or legal@raventrack.ai. Raven may investigate suspected misuse proportionately, preserve relevant evidence, and take the suspension actions permitted by Section 15.

12

Changes, availability and support

12.1

Evolving service. Raven may update features, interfaces, models and technical methods. Roadmaps, demonstrations and discussions of future functions are not delivery commitments unless expressly included in an accepted Order. Raven will give reasonable notice of a material reduction in purchased core functionality where practicable. Security, legal or third-party access problems may require immediate changes.

12.2

Material reductions. If Raven permanently removes a purchased core function during a prepaid paid period and cannot provide a reasonably equivalent replacement, the Customer may terminate the affected Service and receive a proportionate refund of unused prepaid subscription fees for that Service. This does not create an obligation to retain an unlawful or unapproved integration.

12.3

Availability and support. No uptime percentage, response-time guarantee, service credits or disaster-recovery deadline applies unless expressly agreed in writing. Raven may perform maintenance and address outages or incidents. Standard support requests go to support@raventrack.ai and are handled using reasonable efforts. Dedicated support, custom development, migration and training require separate agreement.

12.4

Preview features. Functions labelled beta, pilot, preview or experimental may change or be withdrawn and may have limited support. Their evaluation status does not waive Raven's applicable privacy and security duties, or permit unrelated use of Customer Data.

13

Intellectual property and feedback

13.1

Reserved rights. Raven and its licensors retain their respective rights in the Service, software, interfaces, documentation, methods, models, prompts, branding and improvements. The Customer receives only the access and use rights expressly granted. Third-party and open-source components remain subject to their applicable licences. These Terms do not assert that Raven exclusively owns technology it commercially licenses.

13.2

Outputs and feedback. The Customer may use and export its records and AI Output for lawful business purposes, subject to third-party rights and without acquiring rights in the underlying platform. If the Customer voluntarily provides product ideas or suggestions, it grants Raven a worldwide, perpetual, royalty-free right to use those ideas to the extent the Customer can grant that right. This feedback permission does not grant a separate right to publish or exploit Customer Data or personal information.

13.3

Publicity. Raven may not publish a Customer's name, logo, testimonial, private performance results or identifiable case study without separate permission. Each party may make truthful disclosures required by law.

14

Confidentiality

14.1

Protection. Each party must protect the other's non-public business, technical, security and financial information with reasonable care, use it only for this agreement or another authorized purpose, and disclose it only to people who need to know and are bound by suitable confidentiality duties. Customer Data is confidential to the extent its nature warrants protection. Each party remains responsible for its permitted representatives' handling.

14.2

Exceptions. Confidentiality restrictions do not apply to information the recipient can show is lawfully public without breach, already known without restriction, lawfully received without restriction from another source, or independently developed without use of the confidential information.

14.3

Legal disclosure and duration. A legally compelled disclosure must be limited to what is required, with prior notice where lawful and reasonably practicable. Confidentiality duties continue for three years after the agreement ends; trade secrets remain protected while legally qualifying as trade secrets, and personal information remains protected as applicable law requires. These duties do not justify retaining information longer than necessary.

15

Suspension, termination and remedies

15.1

Customer termination. The Customer may stop renewal under Section 8. It may also terminate for Raven's material breach if Raven does not cure it within 30 calendar days after a written notice describing the breach. If a breach cannot lawfully or reasonably be cured, a party may exercise any immediate termination right available under applicable law.

15.2

Raven termination. Raven may stop renewal on at least 30 days' written notice, or terminate for a material Customer breach that remains uncured 30 days after written notice. Raven may suspend access promptly where reasonably needed to address a security threat, unlawful activity, unauthorized integration access or material interference with the Service. It will give an explanation where lawful and practicable, limit suspension reasonably, and restore access when the basis is resolved.

15.3

Nonpayment. Raven may suspend for an undisputed invoice more than 30 days overdue after giving at least 10 days' written notice. Suspension does not erase valid accrued charges. Raven will not use a billing dispute to obstruct non-waivable individual privacy rights.

15.4

Financial effect. Subscription fees for periods before termination, taxes and properly agreed charges remain payable. No future monthly subscription fees accrue after the effective end date, apart from amounts otherwise expressly agreed for separate services. Agreed setup recovery is governed exclusively by Section 8. If the Customer terminates for Raven's uncured material breach, or Raven ends the subscription for its own convenience before a prepaid period expires, unused prepaid subscription fees are refunded proportionately.

16

Warranties and disclaimers

16.1

Express obligations. Raven will provide the Service with reasonable skill and care and perform its express safeguard and data-processing obligations. The Customer confirms it has authority to enter the agreement and issue its processing instructions. Neither party promises that every third-party right or regulatory issue is resolved simply by signing these Terms.

16.2

Disclaimers. Except for the express obligations in this agreement and rights that cannot lawfully be excluded, the website, Service and AI Output are provided as is and as available. Raven disclaims other express, implied and statutory warranties and conditions, including merchantability, satisfactory quality, fitness for a particular purpose, title and non-infringement, to the extent permitted by law.

16.3

No specific results. Raven does not guarantee error-free or uninterrupted operation, absolute security, detection of every fraud or duplicate, accurate AI Output, tax or audit acceptance, compatibility with every system, or a particular saving, revenue result or business outcome. These disclaimers do not cancel Raven's expressly agreed obligations or applicable statutory duties.

17

Limitation of liability

17.1

Excluded losses. To the fullest extent permitted by law, Raven and its directors, officers, employees, contractors and licensors are not liable for indirect, incidental, special, consequential, exemplary or punitive damages, lost profits, revenue, goodwill, business opportunities or anticipated savings, or loss or corruption of data and associated restoration costs, arising from the website, Service or this agreement. This exclusion applies whether such losses are characterized as direct or indirect and whether their possibility was disclosed.

17.2

Aggregate cap. Subject to Section 17.4, the combined total liability of Raven and the persons protected by this Section for all claims arising out of or relating to the website, Service, any trial, any Order, Schedule A or this agreement will not exceed the subscription fees actually paid to Raven for the affected Service during the three calendar months immediately preceding the first event giving rise to liability. Subscription fees exclude taxes, separately priced setup or professional services, and payments to third parties. If no subscription fees were paid in that period, including during free website or trial use, the cap is CAD $100. This is one combined aggregate cap for the Customer and all claims through its account, not a separate cap per user, legal theory, related incident, Order or renewal. Related events are measured from the earliest event in the series; giving notice of a claim or making later payments does not restart the measurement period.

17.3

Scope. The exclusions and cap apply across claims in contract, tort including negligence, breach of statutory duty, confidentiality, data protection, intellectual property and any other legal theory, to the extent they can lawfully be applied. Characterizing the same event as another type of claim does not create an additional cap or avoid an applicable limit. No separate uncapped confidentiality or contractual data-processing exception is created by Schedule A.

17.4

Preserved liability. Nothing in this agreement excludes or limits liability for fraud or intentional misconduct, gross fault where exclusion is prohibited, bodily or moral injury where exclusion is prohibited, or any other liability or right that applicable law does not permit the parties to exclude or limit. Express contractual refund obligations remain payable and are not reduced by the damages cap. These provisions do not bind regulators or third parties who have not validly agreed to them and do not waive statutory privacy obligations.

17.5

Allocation. These limitations are part of the agreed allocation of risk and apply to free and paid use, to the extent enforceable. They do not cap the Customer's payment obligations or the Customer indemnity in Section 18. An increased liability commitment, insurance obligation or special remedy exists only if Raven expressly accepts it in a separate written agreement.

18

Third-party claims

18.1

Customer indemnity. To the extent permitted by law, the Customer will defend Raven and its officers, directors and employees against a third-party claim arising from Customer Data supplied without required rights or authority, the Customer's unlawful use of the Service, or its instructions to access a connected system contrary to that provider's terms, and pay damages finally awarded and reasonable defence costs or a settlement approved under this Section. This obligation does not apply to the extent a claim is caused by Raven's breach, negligence, unlawful conduct or independent choice to use an unapproved access method.

18.2

Claim procedure. Raven must give reasonably prompt notice of the claim; delay reduces the indemnity only to the extent it materially prejudices the defence. The Customer may control the defence using reasonably acceptable counsel and must provide reasonable updates. Raven will provide reasonable cooperation at the Customer's expense and may participate at its own expense. A settlement requiring Raven to admit fault, make a payment, accept a non-monetary obligation or continue unlawful conduct requires Raven's prior written consent.

18.3

Raven indemnities. Raven does not assume a separate duty to defend or indemnify the Customer for intellectual-property or other third-party claims unless an executed written agreement expressly provides it. This does not remove an otherwise valid claim for Raven's own breach, subject to the applicable limits and mandatory law.

19

Data export and end of service

19.1

End date and export request. The End Date is the effective date the Customer's subscription or trial ends, rather than the date it first gives cancellation notice. Ordinary account access ends on the End Date. The Customer may request an export by emailing support@raventrack.ai within 30 calendar days after the End Date. Raven will arrange a reasonable standard export of the Customer's available records and stored source files in a commonly usable format. Custom transformation, migration and reconstruction require a separate agreed fee.

19.2

Live deletion. The 30-day live-data deletion period starts on the End Date. Raven will delete or irreversibly de-identify Customer Data in active production systems within that period, except information reasonably required to fulfil a timely pending export request, comply with a legal hold or obligation, or retain a limited lawful security, billing or dispute record. Export-related retention must be restricted to that purpose and ended within 30 days after delivery. A timely export request will not be defeated by routine deletion while it is being fulfilled.

19.3

Residual copies. Backup copies, snapshots, file versions and provider-held residual copies expire or are deleted according to the accurate retention schedules and provider arrangements disclosed in the Privacy Policy and any executed DPA. Live deletion does not mean instant erasure of every residual copy. Residual information must remain protected, unavailable for ordinary use, and retained only for a legitimate limited purpose. If a recovery restores deleted information, applicable deletion instructions must be reapplied before ordinary processing resumes.

19.4

Records and third parties. The Customer must retain its own legally required accounting records and request export in time. Deleting Raven data does not delete transactions or files already transferred to QuickBooks or another Customer-controlled system; the Customer manages those copies under its own obligations. Limited retained records must have an identified lawful purpose and retention period. Individual privacy rights continue independently of this commercial export window.

20

Mobile apps

20.1

Device and store terms. Mobile access requires an authorized account, a supported device and compliance with applicable store and device terms. The Customer and users pay their own connectivity and device costs. Availability of a mobile feature may differ from the web Service. Permissions for camera, photos, notifications or other access must be accurately explained and handled through applicable device and consent controls.

20.2

Apple licence. Unless Raven separately supplies a compliant custom app licence, Apple's Standard Licensed Application End User License Agreement governs the software licence for the iOS app, at www.apple.com/legal/internet-services/itunes/dev/stdeula/. These Terms govern Raven's business Service and supplement, rather than replace, that software licence. Applicable Apple usage rules and mandatory platform conditions remain in force. Raven provides support for its Service; Apple is not the provider of Raven's accounting automation.

20.3

Platform compliance. An app-store purchase, if offered, remains subject to the store's applicable billing, cancellation and refund arrangements and any mandatory legal rights. These Terms do not authorize avoiding store rules, bypassing required user permissions, or substituting an email-only process where an in-app account-deletion or consent-withdrawal route is required.

21

Changes to the agreement

21.1

Notice. Raven may update these Terms by publishing a dated version. It will notify existing Customers of material changes at least 30 days before they take effect, except an earlier change required by law or reasonably necessary to address an urgent security or legal problem. Material changes will not apply retroactively to accrued disputes. Raven will obtain affirmative acceptance where law or the nature of a change requires it.

21.2

Renewal and choice. A material change to an ongoing monthly subscription ordinarily applies from the first renewal after the notice period. The Customer may cancel before that renewal. A notice does not by itself authorize new data uses, new recurring charges or the waiver of a non-waivable right. An accepted fixed commercial arrangement remains effective for its stated period unless a valid change mechanism expressly applies.

22

General terms and contact

22.1

Law and courts. This agreement is governed by Ontario law and the federal laws of Canada applicable there, excluding conflict-of-laws rules, subject to any mandatory law that applies to a party or transaction. Subject to any non-waivable venue rights, the courts located in Toronto, Ontario have exclusive jurisdiction. Either party may seek urgent protection of intellectual property or confidential information in a court with competent jurisdiction. No mandatory arbitration or class-action waiver is imposed by these Terms.

22.2

Language. Where Quebec law requires a French version of an agreement or related document, Raven must provide it and obtain any legally required express choice before relying on another-language version. This English version does not waive mandatory French-language protections. The parties' language choice must be established through the required process rather than presumed from account use.

22.3

Notices. Customer legal notices must be sent to legal@raventrack.ai and identify the Customer and relevant account. Support and cancellation requests go to support@raventrack.ai; privacy requests go to privacy@raventrack.ai. Raven may send notices to the Customer's designated account or billing email. Each party must keep its contact details current. An email notice is effective when received without a delivery-failure indication, subject to any mandatory notice rules.

22.4

Assignment and relationship. The Customer may not assign the agreement without Raven's written consent, not unreasonably withheld for a genuine business reorganization with an appropriate successor. Raven may assign it in a merger, reorganization or sale of the relevant business, with notice, provided the successor assumes its obligations and the transfer complies with applicable privacy law. Assignment does not itself authorize unrelated data use. The parties are independent contractors; no partnership, employment or fiduciary relationship is created.

22.5

Events outside control. A party is excused from delay to the extent caused by events beyond its reasonable control, provided it takes reasonable mitigation steps. This does not excuse payment already due, a failure to maintain required safeguards, or a legal reporting obligation. A prolonged inability to provide the purchased Service may give rise to termination and an unused-fee refund under the applicable provisions.

22.6

Entire agreement and survival. This agreement supersedes prior discussions about its subject. Customer purchase-order boilerplate does not modify it without Raven's express written acceptance. Unenforceable provisions are severed or narrowed only to the extent the law permits; the remainder continues. A failure to enforce a provision is not a waiver. Accrued payment obligations, permitted retention and deletion duties, confidentiality, intellectual-property rights, disclaimers, liability provisions, indemnities, dispute provisions and other terms intended by their nature to survive continue after termination.

Contracting entity

Raven in The Nest Inc.

1304 Woodbine Ave #1East York, Ontario M4C 4E7Canada
A

Schedule A

Data Processing Terms

A1

Scope and roles. These processing terms apply when Raven handles personal information on the Customer's behalf. The Customer determines the business purposes and authorized scope; Raven acts as its service provider or processor as those terms apply under relevant law. Raven may separately determine the lawful purposes for its own business contacts, billing, account administration, security and legally required records, as explained in the Privacy Policy. A role label does not override the parties' actual legal responsibilities.

A2

Processing description. Processing consists of collecting, hosting, extracting, organizing, matching, classifying, displaying, approving, synchronizing, supporting, exporting and deleting business financial and related records. It lasts for the Service and the limited permitted retention period. Data subjects may include Customer users, employees, suppliers, customers, homeowners and other project contacts. Data may include names, work contact details, optional phone numbers, account and device identifiers, IP addresses, project addresses and imported project location information, document images and metadata, amounts, transaction details, notes, support material and audit events, only within the actual enabled and disclosed scope.

A3

Instructions and limits. Raven will process personal information only on documented lawful Customer instructions, including the accepted agreement and authorized product settings, or as required by law. It will notify the Customer if it reasonably believes an instruction infringes applicable privacy law and may suspend the affected processing. It will not sell the information, share it for cross-context behavioural advertising, use it for unrelated marketing, or combine it with other customers' personal information except where necessary and legally permitted for the contracted service or security. Identifiable data is not authorized for unrelated model training, experiments or external benchmarking.

A4

Customer duties. The Customer must establish its lawful authority, provide required notices, obtain any required consents, minimize submissions, maintain appropriate permissions and respond to its data subjects. It must promptly inform Raven of relevant corrections, restrictions, legal holds and deletion instructions. The Customer's duties do not eliminate Raven's own legal duties. Information accidentally submitted outside the permitted scope must be addressed under Section 9.4.

A5

Safeguards and confidentiality. Raven will apply safeguards appropriate to the sensitivity and risks, limit access to authorized persons under confidentiality duties, and maintain procedures for incident response and secure disposal. It will make reasonable, relevant information about its safeguards available on request, without disclosing secrets, another customer's data or information that would compromise security. No SOC 2, ISO 27001, penetration-test result or specified control is incorporated as a warranty merely because it appears in an unaccepted marketing or working document.

A6

Providers and transfers. The Customer gives general authorization to engage suitable processing providers within the permitted purposes. Current AI and hosting arrangements may include AWS services, OpenAI and models supplied through Amazon Bedrock, as accurately described in the provider list and Privacy Policy. Raven must bind subprocessors to appropriate written protections for the processing, exercise reasonable diligence, and remain responsible for their performance of delegated data-protection obligations as applicable law requires. Additional or replacement providers are governed by Section 10.4. Cross-border processing must satisfy applicable legal transfer, transparency and safeguard requirements; this agreement alone does not establish that every required transfer assessment or permission has been completed.

A7

Individual requests. Raven will promptly direct requests concerning Customer-controlled information to the Customer and provide reasonable assistance with access, correction, deletion, withdrawal, objections and other applicable rights. It will not require the individual to surrender a statutory right or pay a commercial migration fee. Requests concerning Raven's independently controlled information will be handled by Raven under applicable deadlines. Any legally required direct response, verification, extension, refusal explanation or appeal process remains available.

A8

Incidents. Raven will notify the Customer without undue delay after becoming aware of a breach of security safeguards involving the Customer's personal information and provide information then available about its nature, affected information and mitigation. Notice must not be delayed until every fact is confirmed. Raven will investigate, contain, preserve relevant evidence and provide reasonable updates and assistance. The parties will coordinate regulatory and individual notifications while each retains its own legal duties. No fixed 72-hour waiting period or contractual deadline replaces a shorter applicable legal obligation.

A9

Compliance assistance. Raven will provide reasonable assistance and relevant information for legally required assessments, investigations and compliance checks relating to its processing. Where applicable law requires a contractual audit or inspection right, the parties will arrange a proportionate process using available evidence first, subject to confidentiality and safeguards for other customers. Reasonable administrative arrangements must not prevent a required audit, regulator access or remedy. Raven will inform the Customer if it can no longer meet applicable processing obligations and cooperate in appropriate remediation or stopping the affected processing.

A10

Return deletion and legal requests. Return, live deletion, residual copies, legal holds and retained records follow Section 19 and applicable law. Raven will protect retained information and limit it to the permitted purpose. On reasonable request it will confirm completion of the agreed live-data deletion, explaining lawful exceptions. Government or legal disclosure requests must be reviewed, limited to lawful requirements and notified to the Customer where permitted and practicable.

A11

Required local terms. Where a US state privacy law applies and requires service-provider, contractor or processor terms, Raven will process the information for the specific business purposes in this Schedule, provide the legally required level of protection, and permit the Customer to take the reasonable compliance-monitoring and remediation steps required by that law. The Customer may require an appropriate jurisdiction-specific addendum before the affected processing begins. No blanket claim of compliance with every jurisdiction is made by including this Schedule.

A12

Contractual liability. Section 17 applies to claims under these processing terms to the extent legally permitted. It does not waive individual rights, regulator powers, mandatory reporting duties or liability that cannot lawfully be limited. The same event does not create separate contractual caps under the main Terms and this Schedule.

Questions about these Terms?

Talk to us before you accept.

Send legal notices and contract questions to our legal team. How we handle personal information is explained in the Privacy Policy.