Terms of Service
Effective date: to be set
Welcome to Qove
These Terms of Service (these “Terms” or this “Agreement”) are an agreement between you (“you” or “Customer”) and BetterFutureLabs, LLC, the Delaware limited liability company that operates the Qove™ quality-assurance platform (“Qove,” “Provider,” “we,” “us,” or “our”). In the Exhibits, “Provider” means us and “Customer” means you.
Qove maps how real users move through your web application and then automatically writes, runs, and maintains end-to-end tests from those journeys. By creating a Qove account, installing our Monitoring Snippet, or otherwise using the Service, you agree to these Terms. If you are agreeing on behalf of a company or other organization, you confirm that you have authority to bind it, and “you” means that organization.
If you and we also sign an Order Form or another written agreement, that document applies together with these Terms. If anything conflicts, the order of precedence in Section 17.8 decides which wins. Please read Section 13 (Limits on Liability) and Section 17 (Legal Terms) carefully — they affect your legal rights.
1. Definitions
A few terms we use throughout:
“Affiliate” — any entity that controls, is controlled by, or is under common control with a party.
“Authorized Users” — your employees, contractors, and Affiliates whom you allow to use the Service for your internal business purposes.
“Committed Term” — a subscription with a fixed minimum duration (for example, an annual / twelve-month commitment) that you select in your Order Form. A Committed Term auto-renews and locks your pricing for the term, as described in Sections 5.7 and 14.
“Credit” — the unit of usage for the Service. One (1) Credit is consumed per Test Case Execution, as described in Section 5.
“Customer Application(s)” — the web application(s) and environments you own or control and choose to connect to Qove by installing the Monitoring Snippet.
“Customer Data” — the data the Service collects from your Customer Applications through the Monitoring Snippet, plus the test-account credentials and other materials you give us. It does not include Aggregated / De-Identified Data (Section 6.10).
“Monitoring Snippet” — or “Snippet,” the lightweight client-side script we provide for you to install in your Customer Applications to map user journeys (see Exhibit D).
“Order Form” — an ordering document (including the form in Exhibit A) — or, for self-serve customers, the plan you select online — that sets out your Credits, pricing, and term and incorporates these Terms.
“Pricing Page” — the Qove pricing page at [qove.com/pricing] (or a successor URL), once published and as updated from time to time, listing our current Credit prices, monthly plan tiers, and volume discounts.
“Service” — the Qove platform and everything we make available to you, including the Snippet, journey mapping, automated test generation, self-healing execution, the containerized test runner, the dashboards, and the Qove skill (see Exhibit D).
“Test Artifacts” — the test cases, test scripts, and journey maps the Service generates for you.
“Test Case Execution” — a single run of one test case against one of your environments.
“Personal Data” — information relating to an identified or identifiable person, as defined under applicable Data Protection Laws.
“Data Protection Laws” — the privacy and data-protection laws that apply to each party's activities under these Terms.
2. The Service and Your License
2.1 What you can do. Subject to these Terms and your Order Form, we grant you a non-exclusive, non-transferable, worldwide right, during your subscription, to (a) access and use the Service for your internal business purposes, (b) install and run the Monitoring Snippet in your Customer Applications, and (c) download and run our test-runner container in your own environments and CI/CD pipelines.
2.2 What we can do with your data. You give us a limited license to receive, host, and process your Customer Data only as needed to provide, secure, and (subject to Section 6) improve the Service. We will not use Customer Data for anything else.
2.3 Tools we provide. We will make available to you the Monitoring Snippet, the test-runner container (including flags to tune parallelism), the generated Test Artifacts, and the Qove skill packaged with your journey data, each as described in Exhibit D.
2.4 Updates. We improve the Service over time. We will not materially reduce its core functionality during a paid term, and we will use reasonable efforts to give you advance notice of changes that materially affect the Snippet or the test runner.
2.5 Your team and Affiliates. Your Affiliates and Authorized Users may use the Service under your account, and you are responsible for their compliance with these Terms.
2.6 Early-access features. We may offer optional beta or roadmap features (for example, source-control integrations or requirements-based test import). These are clearly labeled, optional, and provided “as is” until generally released.
3. Free Evaluation (Proof of Concept)
3.1 It's free. Your first engagement is a no-fee proof of concept (the “Evaluation Period”), lasting for the time stated in your Order Form — typically about two to four weeks, enough to install the Snippet, integrate your CI/CD, and let Qove map journeys (which usually needs an initial listening period of about seven days). No Credits are consumed and no fees are charged during the Evaluation Period.
3.2 What it's for. The Evaluation Period lets you install the Snippet in a non-production environment, try the Service, and gauge your likely usage before committing.
3.3 No commitment. Either of us may end the Evaluation Period at any time, for any reason, with no penalty and no further obligation. You are never required to buy.
3.4 No surprise charges. You are not charged unless and until you select a paid plan or sign an Order Form. When you do, you can choose either a month-to-month subscription or a Committed Term (for example, an annual commitment) — see Section 14. Nothing converts to paid automatically.
3.5 Protections still apply. Even though the Evaluation Period is free, our commitments in Section 6 (Your Data), Section 7 (Production Safety), Section 10 (Confidentiality), and Exhibit B (Data Processing Addendum) apply in full during it.
4. Your Responsibilities
4.1 You control deployment. You decide whether, where, and when to install the Snippet. As a best practice, we recommend installing it first in a non-production environment (such as QA or staging), confirming you're happy, and only then promoting it to production. Those rollout decisions are yours.
4.2 Use isolated test accounts. You will give us test-environment account credentials that are kept separate from real end-user accounts.
4.3 Your environment. You're responsible for your applications, infrastructure, source control, CI/CD, and the hardware you choose to run the test container on.
4.4 End-user notices. As between us, you're responsible for any privacy notices to, or consents from, your end users that the law requires for your use of the Service in your applications.
4.5 Acceptable use. You won't (a) resell or provide the Service to third parties except as allowed; (b) reverse engineer or copy the Service except where the law permits; (c) use it to build a competing product; (d) install the Snippet on properties you don't own or control; or (e) use the Service unlawfully.
5. Credits, Pricing, and Payment
5.1 How pricing works. The Service is priced in Credits — one (1) Credit per Test Case Execution (so a 50-test suite uses 50 Credits per run). The current standard price is US$0.75 per Credit; your plan tier and any volume or Committed-Term discounts are set out in your Order Form. For the most up-to-date pricing, see our Pricing Page at [qove.com/pricing]. Once pricing is published on the Pricing Page, it is the authoritative source of current pricing: the price then published there (or, if you have one, the rate set in your Order Form) applies and supersedes any figure stated in these Terms, so the most recent published pricing controls. On a Committed Term, your pricing is locked for the term under Section 5.7, and a rate set in your Order Form controls over the Pricing Page for your subscription.
5.2 Free evaluation. No fees are due and no Credits are consumed during the Evaluation Period (Section 3).
5.3 Monthly Credits; no carryover. Each monthly plan tier includes a set number of Credits per billing cycle. Unused Credits expire at the end of each monthly billing cycle and do not carry over.
5.4 Card on file; auto-recharge. You'll keep a valid payment card (or other accepted method) on file. You authorize us and our payment processor to charge it on a recurring basis for (a) your monthly plan-tier fee and (b) Auto-Recharge: whenever your available Credit balance falls below the Replenish Threshold in your Order Form, we automatically charge your card to add the Replenish Amount of Credits at your then-current per-Credit rate. You can set an optional monthly Auto-Recharge cap. We'll use reasonable efforts to notify you at low balance and on each Auto-Recharge. If a charge fails, we'll let you know, you'll promptly update your method, and we may pause Test Case Executions until your balance is restored.
5.5 We don't charge for our failures. If a Test Case Execution fails to complete because of an error or outage on our side (as opposed to a test failure in your application), no Credit is consumed — or we credit it back.
5.6 Taxes. Fees exclude taxes. You're responsible for applicable sales, use, and similar taxes, except taxes on our net income.
5.7 Price changes. We may update our pricing from time to time — on the Pricing Page once it is live, or otherwise by notice to you. For month-to-month plans, an updated price takes effect on at least thirty (30) days' notice and applies to your next billing cycle. For a Committed Term, your pricing is locked for the term and may change only at renewal, on at least thirty (30) days' notice. The price for any billing cycle is the one then published on the Pricing Page (or set in your Order Form).
6. Your Data and Privacy
6.1 Roles. For Personal Data, you are the controller (or business) and we are the processor (or service provider). We process Personal Data only on your instructions (including these Terms) and only to provide the Service. We do not sell or share Personal Data, and we won't use it for anything other than running the Service.
6.2 What we collect. The Snippet captures only what's needed to map journeys: page URL and title, viewport, user-agent, structural events (clicks, navigation, page exits, and form-submission events), and which form fields a user interacted with. Exhibit D has the full list.
6.3 What we mask and exclude. By default, the Snippet masks and never transmits the values people type into sensitive form fields — including passwords, authentication, and identity, health, payment/financial, contact, and other personal details. By default it does not touch cookies, tokens, local storage, or session storage. You can mask anything else with our custom-mask attribute (Exhibit D).
6.4 No expansion without your OK. We won't expand what we collect (for example, to capture extra fields, tokens, or storage) without your prior authorization, which you can give in an Order Form and revoke at any time going forward.
6.5 Test credentials only. The only login credentials we store are the isolated test-account credentials you give us. We don't collect your end users' usernames or passwords.
6.6 Data retention. By default we keep the journey events we collect for the length of your subscription (so we can keep improving your journey maps and tests) and delete them within thirty (30) days after your subscription ends (Section 6.7). You can choose a shorter custom retention period in your Order Form or by written request, and we'll honor it. We won't keep Customer Data longer than needed for the purposes in these Terms or as the law requires.
6.7 Deleting your data. You can ask us to delete your Customer Data at any time. We'll delete it from our production systems within thirty (30) days, except for routine backups (purged on their normal cycle) and Aggregated / De-Identified Data. We keep a defined process for these requests and will confirm when it's done.
6.8 Security. We maintain administrative, technical, and physical safeguards to protect Customer Data, including encryption in transit and at rest, least-privilege access controls, and logging and monitoring (see Exhibit B).
6.9 If there's a breach. We'll notify you without undue delay, and within seventy-two (72) hours, after confirming a security breach that exposes your Customer Data, and we'll reasonably cooperate with your response to the extent required by applicable law.
6.10 Aggregated / de-identified data. We may create and use aggregated and de-identified data from running the Service to operate and improve it, as long as it can't reasonably identify you or any individual and isn't disclosed in a way that identifies you.
6.11 Subprocessors. We may use subprocessors to help run the Service under terms at least as protective as these. We stay responsible for them, keep a current list available, and give notice of material changes.
6.12 Data Processing Addendum. Exhibit B (DPA) is part of these Terms and controls if anything conflicts about Personal Data.
7. Installing the Snippet — Production Safety
7.1 Built to be light. The Snippet is a small script that loads in the page head and queues and batches events (typically one network request per ~100 events).
7.2 Roll it out in stages. We recommend — and will help with — a staged rollout: non-production first, then lower-risk production, then your most critical properties.
7.3 Remove it anytime. You can remove the Snippet from any application at any time, which immediately and completely stops collection. We don't need access to your production systems to make that happen.
7.4 If something goes wrong in production. If the Snippet is reasonably suspected of causing or threatening a production issue, we'll treat it as Severity 1 under Exhibit C, help you promptly, and provide rollback guidance. You can also remove the Snippet yourself at any time for immediate mitigation (Section 7.3).
8. Support and Service Levels
8.1 How to reach us. We set up a dedicated shared channel (for example, a joint Slack channel) for onboarding and ongoing support. Our team is globally distributed and we make commercially reasonable efforts to respond at any time.
8.2 Response targets. We use commercially reasonable efforts to meet the severity-based response targets in Exhibit C.
8.3 Onboarding help. We'll help you install the Snippet, build your first test suite, and wire the Service into your CI/CD.
8.4 Availability. We make commercially reasonable efforts to keep the hosted parts of the Service available, per the target in Exhibit C, excluding scheduled maintenance and events outside our reasonable control.
9. Who Owns What
9.1 We own Qove. We own all rights in the Service, the Snippet, the test runner, our software, models, and know-how, and all improvements — everything except your Customer Data and Customer Materials.
9.2 You keep your tests. The Test Artifacts we generate for you are yours to keep. We grant you a perpetual, irrevocable, royalty-free license to use, modify, and retain them for your internal business purposes, and that license survives even if these Terms end.
9.3 You own your data and apps. You own your Customer Data and your applications and other materials you provide (“Customer Materials”). You grant us only the licenses written into these Terms.
9.4 Feedback. If you send us suggestions, we may use them freely, but we won't identify you as the source without your consent.
10. Confidentiality
10.1 What's confidential. “Confidential Information” is non-public information one of us shares that is marked confidential or that should reasonably be understood to be confidential. Your Customer Data is your Confidential Information, and the terms of any Order Form are confidential to both of us.
10.2 How we treat it. Each of us will use the other's Confidential Information only to perform under these Terms, protect it with at least reasonable care, and share it only with people and advisors who need it and are bound by confidentiality.
10.3 Exceptions. Confidential Information doesn't include information that becomes public through no fault of the recipient, was already known without a duty of confidence, is independently developed, or is rightfully received from someone else. If the law compels disclosure, the recipient will give reasonable prior notice where allowed.
11. Our Promises and Disclaimers
11.1 Authority. Each of us has the authority to enter into these Terms.
11.2 The Service will work as described. We warrant that, during your subscription, the Service will perform materially as described in the Documentation. If it doesn't, your exclusive remedy is for us to use commercially reasonable efforts to fix it, and if we can't within a reasonable time, you may terminate the affected subscription and get a refund of any prepaid, unused fees for the affected period (if any).
11.3 No malicious code. We won't knowingly put any virus, malware, or other intentionally harmful code into the Service or Snippet, and we use industry-standard measures to prevent it.
11.4 Compliance. Each of us will comply with the laws that apply to it under these Terms, including Data Protection Laws.
11.5 Everything else is “as is.” EXCEPT AS EXPRESSLY STATED IN THESE TERMS, THE SERVICE IS PROVIDED “AS IS,” AND WE DISCLAIM ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DON'T WARRANT THAT THE SERVICE WILL CATCH EVERY DEFECT OR THAT RESULTS WILL BE ERROR-FREE; IT'S A QUALITY-ASSURANCE AID AND DOESN'T REPLACE YOUR OWN JUDGMENT ABOUT YOUR RELEASES.
12. Indemnification
12.1 What we cover. We'll defend you against third-party claims that the Service, as we provide it and as used under these Terms, infringes that party's intellectual-property rights, or that arise from our breach of Section 6 (Your Data) or Exhibit B, and we'll cover damages and reasonable costs finally awarded or agreed in settlement. If the Service becomes the subject of an infringement claim, we may obtain the right to keep using it, modify it to be non-infringing, or terminate the affected subscription and refund any prepaid, unused fees (if any).
12.2 What you cover. You'll defend us against third-party claims arising from (a) your Customer Materials or Customer Data — including a claim that you lacked the rights or consents for us to process them — or (b) your use of the Service in breach of these Terms or the law, and you'll cover damages and reasonable costs finally awarded or agreed in settlement.
12.3 How it works. The party seeking indemnity will give prompt notice, let the other control the defense and settlement (with no settlement that imposes liability or an admission on the indemnified party without consent), and reasonably cooperate. This Section is each party's sole remedy for the third-party claims it covers.
13. Limits on Liability
13.1 No indirect damages. Except for the Excluded Matters below, neither of us is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, or data, even if warned they were possible.
13.2 The cap. Except for the Excluded Matters, each party's total liability under these Terms is limited to the greater of (a) the fees you paid or owe in the twelve (12) months before the event, or (b) during the Evaluation Period or any other period with no fees paid, fifty thousand U.S. dollars (US$50,000).
13.3 Excluded Matters. Section 13.1 and 13.2 don't apply to: (a) the indemnities in Section 12; (b) your payment obligations; (c) either party's breach of Section 10 (Confidentiality); (d) our breach of Section 6 (Your Data) or Exhibit B, or a security incident caused by our failure to meet our security obligations; or (e) gross negligence, willful misconduct, or fraud. For (c) and (d), each party's liability is capped at two (2) times the amount in Section 13.2; (a), (b), and (e) are not capped.
13.4 Why these limits exist. These limits reflect how we've allocated risk and the pricing of the Service, and they apply even if a limited remedy fails its essential purpose.
14. Term, Cancellation, and Renewal
14.1 Term and renewal. These Terms start when you accept them and continue through the Evaluation Period and the subscription you choose in your Order Form. You may subscribe either (a) month-to-month or (b) on a Committed Term (for example, an annual / twelve-month commitment). A month-to-month subscription continues until cancelled under Section 14.3. A Committed Term automatically renews for equal terms unless either of us gives written notice of non-renewal at least thirty (30) days before the current term ends. Renewal pricing follows Section 5.7.
14.2 Termination for cause. Either of us may terminate these Terms or an Order Form if the other materially breaches and doesn't cure within thirty (30) days after written notice.
14.3 Cancellation. (a) Month-to-month. Either of us may cancel at any time on written notice (including via the support channel); cancellation takes effect at the end of the current monthly billing cycle, and you're responsible for charges through that date. (b) Committed Term. A Committed Term runs to the end of its term; you can prevent renewal under Section 14.1(b) or terminate early as set out in your Order Form. (c) Evaluation. Either of us may end the Evaluation Period at any time, without penalty (Section 3.3).
14.4 What happens when it ends. When these Terms or a subscription end: (a) your access stops and you'll remove the Snippet from your applications; (b) we'll return or delete your Customer Data per Section 6 and Exhibit B; (c) you keep your perpetual license to the Test Artifacts (Section 9.2); (d) any unused or remaining Credits are forfeited and non-refundable, and you remain responsible for amounts accrued through the end date; and (e) despite (d), if you terminate for our uncured material breach under Section 14.2, we'll refund the value of any Credits you purchased but haven't used.
14.5 What survives. Sections 1, 5 (for amounts owed), 6, 9, 10, 11.5, 12, 13, 14.4, 14.5, 15, 16, and 17 survive termination, along with anything else that by its nature should.
15. Insurance
These Terms do not require Provider to carry any specific insurance. Where a particular engagement requires specific coverage (for example, cyber or professional-liability / errors-and-omissions insurance), that requirement will be addressed in the applicable Order Form.
16. Assignment and Entity Transfer
16.1 General. Neither of us may assign these Terms without the other's consent (not unreasonably withheld), except that either may assign, in whole and without consent, to an Affiliate or to a successor in a merger, acquisition, reorganization, or sale of substantially all assets, where the assignee assumes all obligations.
16.2 Qove entity transfer. You acknowledge that Qove is currently operated as a product of BetterFutureLabs, LLC We may assign and transfer these Terms and any Order Form, without your further consent, to a new Affiliate or successor entity set up to operate the Qove product line (for example, an entity such as “Qove, Inc.”). The transfer takes effect on written notice to you; nothing else is required from you. The new entity assumes all of our obligations, these Terms (including all data-protection and confidentiality commitments) stay materially the same and bind the new entity, and your rights are unaffected.
16.3 Binding effect. Subject to this Section, these Terms bind and benefit the parties and their permitted successors and assigns. Any assignment that violates this Section is void.
17. Legal Terms
17.1 Governing law; venue. These Terms are governed by the laws of the State of Delaware, without regard to conflict-of-laws rules. The parties consent to the exclusive jurisdiction of the state and federal courts in Delaware, subject to Section 17.2.
17.2 Working it out first. Before going to court (except for injunctive relief), we'll both try in good faith to resolve any dispute by escalating to each side's senior management for thirty (30) days.
17.3 Notices. Legal notices must be in writing, sent to the addresses in the Order Form (with an email copy), and are effective on receipt. Day-to-day notices can go through the shared support channel.
17.4 Force majeure. Neither of us is liable for failure or delay caused by events beyond our reasonable control, as long as we work reasonably to mitigate.
17.5 Independent contractors. We're independent contractors; these Terms create no partnership, joint venture, or agency.
17.6 No third-party beneficiaries. These Terms don't give rights to anyone who isn't a party.
17.7 Publicity. We may identify you as a Qove customer and use your name, logo, and any feedback or testimonials you provide in our marketing, website, social, and investor materials. We will honor any written request to stop using a specific item.
17.8 Entire agreement; order of precedence. These Terms, together with any Order Form and the Exhibits, are the entire agreement and replace any prior understandings on this subject. If there's a conflict, this order controls: (1) your signed Order Form (for commercial terms); (2) Exhibit B (DPA) (for Personal Data); (3) these Terms; (4) the other Exhibits.
17.9 Changes to these Terms. We may update these Terms from time to time. If a change is material, we'll post the updated Terms with a new effective date and give reasonable notice (such as by email or in-product). Changes apply going forward from the stated date. If you're on a Committed Term or have a signed Order Form, the version in effect when you signed governs that term, and material changes won't apply to you until your next renewal unless we agree otherwise or the law requires it. If you don't accept a change, you may stop using the Service and cancel under Section 14.
17.10 Amendments and waiver. Any change you and we negotiate must be in writing and signed by both of us. A waiver counts only if it's in writing and isn't a continuing waiver.
17.11 Severability. If any provision is unenforceable, it's modified to the minimum extent needed and the rest stays in effect.
17.12 How you accept; electronic records. You accept these Terms by creating an account, selecting or paying for a plan (including through our online checkout), installing the Snippet, using the Service, or signing an Order Form. Accepting online forms a binding agreement enforceable to the same extent as a signed writing. These Terms and any Order Form may be accepted or signed electronically and in counterparts, each of which is an original.
Accepting these Terms
You accept these Terms when you create a Qove account, install the Monitoring Snippet, or use the Service. If you've asked us for a signed contract or negotiated terms, you and we may also sign the Order Form in Exhibit A, which serves as the signature page for these Terms and sets your commercial terms.
Exhibit A — Order Form
This Order Form is governed by and incorporates the Qove Terms of Service between BetterFutureLabs, LLC (operator of Qove) and the Customer below (the “Agreement”). Capitalized terms have the meanings given in the Agreement. Self-serve customers accept equivalent terms by selecting and paying for a plan online (Section 17.12); this form is for customers who ask for a signed contract or negotiated terms.
| Field | Detail |
|---|---|
| Customer | [Customer Legal Name], [address] |
| Provider | BetterFutureLabs, LLC (Qove™), [address] |
| Order Effective Date | [____________, 20__] |
| Evaluation Period | No-fee proof of concept of approximately two (2) to four (4) weeks, beginning on installation in Customer’s QA/non-production environment. No Credits consumed; no fees charged. |
| Pricing Model | Credits. One (1) Credit = one (1) Test Case Execution. List price: US$0.75 per Credit. |
| Monthly Plan Tier | ____ Credits included per month for US$____ per month, at the applicable per-Credit rate below. |
| Standard Price | US$0.75 per Credit (current standard), unless a custom rate is set in this Order Form. Once live, the Pricing Page at [qove.com/pricing] is the authoritative source of current pricing (Section 5.1). For committed terms, the rate set here is locked for the term. |
| Volume Discount | Based on average monthly spend — see the discount table below. Thresholds may be adjusted in this Order Form without amending the Agreement. |
| Credit Carryover | Unused Credits expire at the end of each monthly billing cycle and do not carry over. |
| Auto-Recharge | When the available Credit balance falls below [500] Credits (Replenish Threshold), Provider automatically charges the payment card on file to add [1,000] Credits (Replenish Amount) at the then-applicable per-Credit rate. Optional monthly Auto-Recharge cap: US$[____]. See Section 5.4. |
| Commitment & Term | Select one: [ ] Month-to-month (cancel anytime) [ ] 12-month commitment. Pricing per the discount table below; any additional committed-term discount: ____%. |
| Renewal | Month-to-month: continues until cancelled (Section 14.3). Committed term: auto-renews for successive 12-month terms unless either Party gives 30 days’ notice of non-renewal (Section 14.1). |
| Payment Method | Credit card on file; recurring monthly plan-tier charge plus Auto-Recharge as above (Section 5.4). |
| Cancellation | Unused or remaining Credits are forfeited and non-refundable on cancellation or expiration (Section 14.4). |
| Estimated Annual Value | Good-faith estimate of US$20,000–$30,000 per year for a team of approximately 8–10 engineers at a Customer’s typically stated release cadence. Estimate only; actual fees depend on actual usage. |
| Custom Data Retention | [Default: retained for the subscription, then deleted within 30 days / Custom period: ______] |
| Support Channel | Dedicated shared Slack channel; see Exhibit C. |
Standard Pricing & Volume Discounts
| Average Monthly Spend | Discount off List | Effective $/Credit |
|---|---|---|
| Standard (under US$2,000/mo) | — | US$0.75 |
| US$2,000+ per month | 10% | US$0.68 |
| US$3,500+ per month | 20% | US$0.60 |
| US$5,000+ per month | 30% | US$0.53 |
Note: Illustrative. Standard price is US$0.75 per Credit; the tiers above are examples and are finalized per Order Form (or, once live, the Pricing Page) — they can be adjusted there without amending the Terms (Sections 5.1 and 5.7). For a committed term the agreed rate is locked for the term; for month-to-month it tracks the then-current Pricing Page. Auto-Recharge top-ups are billed at Customer’s then-applicable per-Credit rate. Credits consumed in Test Case Executions that fail due to a Provider-side error are credited back per Section 5.5.
Agreed and accepted. This Order Form may be signed electronically and serves as the signature page for the Qove Terms of Service.
| PROVIDER: BetterFutureLabs, LLC By: ___________________________________ Name: ________________________________ Title: _________________________________ Date: _________________________________ | CUSTOMER: [Customer Legal Name] By: ___________________________________ Name: ________________________________ Title: _________________________________ Date: _________________________________ |
|---|
Exhibit B — Data Processing Addendum
This Data Processing Addendum (“DPA”) forms part of the Agreement and reflects the parties’ agreement on processing Personal Data. If anything conflicts about Personal Data, this DPA controls.
1. Roles and Processing
1.1 Customer is the controller/business and Provider is the processor/service provider. Provider processes Personal Data only to provide the Service and on Customer’s documented instructions (including the Agreement).
1.2 Provider will not sell or share Personal Data and will not retain, use, or disclose it outside the direct business relationship or for any purpose other than performing the Service.
2. Details of Processing
| Item | Description |
|---|---|
| Subject matter | Provision of the Qove quality-assurance Service. |
| Duration | The term of the Agreement, plus any deletion period under Section 6 of the Agreement. |
| Nature and purpose | Mapping end-user journeys to generate and maintain automated tests. |
| Categories of data subjects | Customer’s end users who interact with the Customer Applications; Customer’s test-account users. |
| Categories of data collected | Page URL/title, viewport, user-agent, structural interaction events (clicks, navigation, page exits, form-submission events), and the identity of form fields interacted with. |
| Data masked / excluded | Values entered into form fields (including passwords/authentication), and identity, health, payment/financial, contact, and other personal details. Cookies, tokens, local storage, and session storage are not accessed by default. |
| Sensitive data | Not intentionally collected. The Snippet is configured to mask special-category and financial inputs by default. |
3. Security Measures
Provider maintains a written information-security program with administrative, technical, and physical safeguards appropriate to the nature of the data, including:
- Encryption of Customer Data in transit and at rest;
- Role-based, least-privilege access controls and authentication for personnel;
- Network security, logging, and monitoring of Provider systems;
- Default masking of PII-identified form-input values and sensitive fields at the point of collection;
- Secure software-development and change-management practices;
- Personnel confidentiality obligations and security awareness practices.
4. Subprocessors
4.1 Customer authorizes Provider to engage subprocessors to support the Service. Provider imposes data-protection obligations on subprocessors no less protective than this DPA and remains responsible for their performance.
4.2 Provider will make its current subprocessor list available on request and provide reasonable prior notice of new subprocessors, allowing Customer to object on reasonable data-protection grounds.
5. Retention and Deletion
5.1 Provider retains Personal Data only as long as necessary to provide the Service or as required by law, subject to any custom retention period elected by Customer under Section 6.6 of the Agreement.
5.2 On Customer’s request or on termination, Provider will delete Personal Data within thirty (30) days, excepting routine backups (purged on their ordinary cycle) and Aggregated/De-Identified Data. Provider will confirm deletion in writing.
6. Breach Notification
Provider will notify Customer without undue delay and within seventy-two (72) hours of confirming a personal-data breach affecting Customer Data, with available details, and will cooperate with Customer’s response and any required notifications.
7. Assistance and Audit
7.1 Provider will provide reasonable assistance to Customer in responding to data-subject requests and in meeting Customer’s obligations regarding security, breach notification, and data-protection assessments.
7.2 Upon reasonable prior written notice and no more than once per year (absent a security incident or legal requirement), Provider will make available information reasonably necessary to demonstrate compliance with this DPA, which may be satisfied through summaries, questionnaires, or third-party reports.
8. International Transfers
To the extent Provider processes Personal Data subject to cross-border transfer requirements, the parties will implement an appropriate transfer mechanism (such as Standard Contractual Clauses), which are incorporated by reference where applicable.
Exhibit C — Support and Service Levels
1. Support Channel and Hours
Provider provides support through a dedicated shared messaging channel (e.g., a joint Slack channel) established during onboarding. Provider maintains a globally distributed team and uses commercially reasonable efforts to respond to messages at any time.
2. Severity Levels and Target Response Times
| Severity | Description | Target Initial Response | Target (aim for) |
|---|---|---|---|
| Sev 1 — Critical | Suspected production impact caused by the Snippet or Service, or the Service is down with material business impact. | Within 1 business day | 1 business hour |
| Sev 2 — High | Major feature of the Service is unavailable or significantly impaired; no production impact. | Within 2 business days | 1 business day |
| Sev 3 — Normal | Non-critical issue, question, or minor defect with a workaround. | Within 3 business days | 2 business days |
| Sev 4 — Low | General questions, feature requests, onboarding assistance. | Within 4 business days | 3 business days |
3. Production Incident Handling
Any issue reasonably suspected of causing or threatening a production impact is handled as Severity 1: Provider will respond within the Severity 1 target above, assist Customer in mitigation, and provide rollback guidance, including how to remove the Monitoring Snippet, as needed (Section 7.4 of the Agreement). The response times in this Exhibit are targets that Provider pursues using commercially reasonable efforts; Customer’s ability to remove the Snippet at any time provides immediate self-service mitigation independent of Provider’s response.
4. Availability Target
Provider targets 99.5% monthly availability for the hosted components of the Service, measured by Provider’s monitoring systems, excluding (a) scheduled maintenance with reasonable notice, and (b) events outside Provider’s reasonable control, including unavailability of third-party cloud-infrastructure providers on which the Service depends.
Exhibit D — Service Description and Technical Specifications
1. Overview
Qove is an AI-assisted quality-assurance platform that maps real end-user journeys within the Customer Applications and automatically generates, executes, and maintains end-to-end (front-end / UI) regression and feature tests. The Service comprises the components described below.
2. Components
- Monitoring Snippet. A lightweight client-side script installed in the page head that maps user journeys. It queues and batches events (typically one network request per ~100 events).
- Journey Mapping. Continuous identification of user goals (end states) and the distinct patterns by which users reach them, from collected events.
- Automated Test Generation. Generation of test cases from observed user journeys (and, where available, from imported requirements/manual test cases).
- Self-Healing Execution. AI agents adapt tests to non-breaking UI changes (e.g., a control moving location) so long as the underlying user journey is preserved; fundamentally changed or deprecated journeys surface as failures for Customer review.
- Containerized Test Runner. A Docker image Customer runs in its own environment / CI/CD, with configurable parallelism and concurrency flags (e.g., parallel virtual users and parallel test cases) to match Customer hardware.
- Insights Interface & Qove Skill. Dashboards and a downloadable skill (an industry-standard agent skill format) packaged with Customer’s journey data, enabling natural-language queries about how users actually use the application and which journeys are covered.
3. Data Captured by the Snippet
| Captured | Masked / Not Captured by Default |
|---|---|
| Page URL and title | Values entered into any form field |
| Viewport dimensions | Passwords and authentication data |
| User-agent | Identity, health, payment/financial data |
| Clicks and navigation events | Contact info and other personal details |
| Page exits | Cookies, tokens, local/session storage (not accessed by default) |
| Form-submission events and which fields were interacted with | Anything within a Customer-designated custom-mask element |
4. Custom Masking
Customer may designate any element for masking by applying Provider’s custom-mask attribute; all content within that element is automatically masked at the point of collection. Provider will not expand data collection beyond the defaults above without Customer’s prior written authorization (Section 6.4 of the Agreement).
5. CI/CD Integration
Customer runs the containerized test runner within its own pre-commit hooks and/or CI/CD pipeline and receives test results. Whether failing tests block a build is configured entirely by Customer; Provider recommends running tests informationally (developer and reviewer assess results) rather than as hard build gates for end-to-end suites.
6. Listening Period
Following installation, the Service typically requires an initial listening period of approximately seven (7) days to map journeys and build the initial test suite before meaningful test generation.