SaysData Cloud Service Agreement — Cover Page
Version: 2026-10-19
This Cover Page and the Common Paper Cloud Service Agreement Standard Terms Version 2.1 (the "Standard Terms") form the agreement between Provider and Customer (the "Agreement"). The Standard Terms are incorporated by reference. Capitalized words not defined here have the meanings given in the Standard Terms.
The Plans & Limits and Data Sources pages, each in the version in effect under Additional Terms §8, are part of this Cover Page. On those pages, "you" means Customer, "we" means Provider, and "outputs" means Outputs.
Order of precedence. If this Cover Page conflicts with the Standard Terms, this Cover Page controls. If the Plans & Limits or Data Sources page conflicts with the rest of this Cover Page, the rest of this Cover Page controls.
Parties and acceptance
Provider: 17237324 Canada Inc., a corporation incorporated under the laws of Canada (corporation number 1723732-4), operating SaysData.
Account: a SaysData organization account. A User's personal sign-in is not an Account. Each Account has its own Agreement and Framework Terms; ending one does not end another. In this Cover Page, "account" means an Account.
Customer: the company or person who accepts this Agreement for the account. If the person accepting is doing so on behalf of a company or other organization, "Customer" means that organization.
Account owner: the User who created Customer's account or, after a transfer of ownership made with Provider, the User it was transferred to. Of Customer's Users, only the account owner may delete Customer's account. Customer may ask Provider to transfer ownership to another User; Provider may require reasonable evidence of Customer's authority.
Acceptance: A person accepts this Agreement for an account by creating it, in the version posted at that time. If they create it on behalf of a company or other organization, they represent that they are authorized to accept this Agreement on its behalf.
Business use: Customer will use SaysData only for business or professional purposes, not for personal, family, or household use.
Users' actions: Standard Terms §1.3 makes Customer responsible for a User's actions and compliance only when they are taken in or through Customer's account, or involve Outputs obtained through it.
Privacy: Provider's Privacy Policy describes how Provider handles personal information. The Privacy Policy is not part of this Agreement.
Order Form
| Variable | Value |
|---|---|
| Cloud Service | SaysData: a service for searching, describing, and querying statistics from the publishers listed on the Data Sources page. It is provided through SaysData's MCP server and the web application at saysdata.com. |
| Beta | The entire Cloud Service is a Beta Product under Standard Terms §12.7. |
| Order Date | The date Customer's account is created. Adding or removing Paid seats updates this Order Form; it does not start a new one. |
| Subscription Period | One month, renewing automatically. Whenever Customer goes from no Paid seats to one or more, a new Subscription Period starts that day (UTC). A Paid seat added during a Subscription Period takes effect immediately, and its Fees for the rest of that period are prorated. |
| Non-Renewal Notice Date | Any time before the current Subscription Period ends. |
| Plans | The plans on the Plans & Limits page. Each User is on the Free plan unless they hold a "Paid seat" in Customer's account: a seat on any plan on that page that has a price. Provider may also give a User a Paid seat, or raise or remove their limits, at no charge, and may end any such grant at any time. |
| Fees | For each Paid seat, except one Provider gives at no charge, the price on the Plans & Limits page for that seat's plan, in the currency stated there (Standard Terms §4). |
| Payment Process | Automatic payment, monthly in advance and when a Paid seat is added, charged to the payment method on file through Provider's payment processor. If a payment fails, Provider may end any Paid seats that payment was for, and their Users move to the Free plan. |
| Use Limitations | The limits on the Plans & Limits page, applied to each User according to their plan, or as Provider raises or removes them under Plans. Each User must be one individual, at least 18 years old, among Customer's personnel (Additional Terms §4), using the Cloud Service through Customer's account with their own sign-in. Sign-ins must not be shared, and no individual may use more than one sign-in in Customer's account. Customer must not circumvent the limits, for example by creating extra accounts or sign-ins to get more free usage. Circumventing them breaches Standard Terms §2.1(b) but, on its own, not Standard Terms §2.1(a). |
| Technical Support | Email support at [email protected], when available. No response-time commitment. |
| Service Level Agreement | None. Provider makes no availability or uptime commitment. |
Key Terms
| Variable | Value |
|---|---|
| Effective Date | The date Customer's account is created. |
| Governing Law | The laws of the Province of Ontario and the federal laws of Canada applicable in Ontario. |
| Chosen Courts | The courts of the Province of Ontario sitting in Ottawa. |
| General Cap Amount | The Fees paid or payable by Customer under this Agreement in the 12 months before the event giving rise to the claim. If Customer paid and owed no Fees in that period, the amount is zero. |
| Increased Claims | None. |
| Increased Cap Amount | None. |
| Unlimited Claims | Only the following, and only for Customer: (a) its obligations under Standard Terms §9.2 (Protection by Customer); (b) its breach of Standard Terms §2.1(a) (Restrictions on Customer), Standard Terms §3 (Privacy & Security), Additional Terms §5(a), or Additional Terms §11; and (c) its obligation to pay Fees. No obligation of Provider is an Unlimited Claim. Standard Terms §8.2 (Damages Waiver) does not apply to Unlimited Claims. |
| Provider Covered Claims | None. |
| Customer Covered Claims | Any claim by a third party arising from: (a) Customer Content, or Requests that were Customer Content before they were de-identified; (b) use of the Product by Customer or its Users in breach of this Agreement; (c) Outputs obtained through Customer's account, including their use, publication, or distribution, or anyone's reliance on them; or (d) use of an English-only service and English-only terms by Customer or its Users, or an untrue representation by Customer under Additional Terms §11, including any resulting fine or penalty. This includes a claim alleging that an Output was wrong or that Provider was negligent. |
| Additional Warranties | None. |
| DPA | None. Provider does not offer a data processing agreement. Despite Standard Terms §3.1 and §3.2, Customer may provide the contact, sign-in, and billing details (including payment details given to Provider's payment processor) needed to run its account. Customer must not otherwise submit Personal Data governed by the GDPR. |
| Notice Address | Provider: [email protected]. Customer: the account owner's email address; Provider may also send its notices to Customer's administrators. Despite Standard Terms §12.9, an email notice is given when sent, unless the sender receives a delivery-failure message. Customer must keep its Notice Address current, and its notices must be sent from the account owner's email address or, if there is no account owner or the account owner cannot act, in a way Provider reasonably accepts. |
Additional Terms
In these Additional Terms, "§" alone means a section of these Additional Terms.
1. Outputs
"Outputs" means what the Cloud Service returns (search results, dataset descriptions, query results, tables, and figures) and anything produced from it by Customer's AI assistant or other software.
Subject to §3 and §4, Customer may use, publish, and distribute Outputs for any lawful purpose; Standard Terms §1.1 (internal business purposes), §2.1(a)(ii), and §2.1(a)(iv) do not restrict this. Standard Terms §2.1(a)(vii) (no competing service) also applies to Outputs as if they were part of the Product, except where a publisher's licence forbids that restriction on its data.
Outputs are not exclusive to Customer; others may receive the same or similar Outputs. Customer is responsible for its use of Outputs, including Outputs it shares with others.
2. Outputs will sometimes be wrong — Customer must verify them
Errors will occur. They can come from the Cloud Service, from the publishers' data, from the Requests Customer's AI assistant sends, and from how that assistant interprets what the Cloud Service returns. Provider tries to reduce errors but cannot prevent them.
Therefore:
- Customer must verify Outputs before relying on them.
- Outputs are not financial, investment, legal, tax, medical, or other professional advice.
- To the maximum extent permitted by Applicable Laws:
- Provider makes no warranty that any Output is accurate, complete, or current; and
- Provider has no liability, whether in contract, tort (including negligence), or otherwise, for errors in Outputs or for any decision made or action taken based on Outputs.
This section adds to Standard Terms §7 (Disclaimer of Warranties) and §8 (Limitation of Liability).
3. Data sources
The data in the Cloud Service comes from the third-party publishers listed on the Data Sources page. Each publisher's licence governs its data. Customer must comply with those licences when it uses Outputs, including their attribution and no-endorsement requirements.
Provider does not own the publishers' data and makes no warranty about it. The publishers do not endorse Provider, Customer, or any Output. The publishers' licences are not part of this Agreement; Customer's duty to comply with them is.
4. Customer's AI assistant
Customer may connect an AI assistant or other software to the Cloud Service to act for its personnel; doing so does not breach Standard Terms §1.3 or §2.1(a)(ii). Software connected through a User's sign-in may act only for that User. Everything that software does through Customer's account is Customer's action. "personnel" means Customer itself if it is an individual, and Customer's employees, contractors, volunteers, directors, and officers, and the owners and partners who work in Customer's business. Only personnel, and software acting for them, may send Requests. Customer must not let anyone else get answers from the Cloud Service, whether directly, through software Customer makes available to them (such as a chatbot, app, or API), or by relaying their questions and the responses without personnel deciding what to ask and what to share. Personnel may use Outputs to answer others' questions (for example, a client's) and share them under §1 if they make those decisions; doing so is an internal business purpose under Standard Terms §1.1. A breach of this paragraph is a breach of Standard Terms §2.1(a)(ii).
That software is a third-party product, not part of the Product. Provider is not responsible for:
- what the software sends to the Cloud Service;
- how it interprets or presents what the Cloud Service returns;
- what it does with Customer Content or Outputs.
5. Requests and machine learning
(a) Requests. "Requests" means the searches, queries, and other instructions sent to the Cloud Service through Customer's account. Uploading a dataset or file is not a Request (§5(e)). The content of Requests is Customer Content, not Usage Data; the fact and number of Requests is Usage Data. Customer must not include Personal Data in Requests.
(b) Product improvement. Provider may analyze Requests to operate, secure, support, and improve the Product.
(c) Machine learning. Provider will use Requests to develop, train, or enhance artificial intelligence or machine learning models only if they are both aggregated and de-identified. For this section and Standard Terms §1.6 (Machine Learning):
- A Request is aggregated when it is pooled with Requests from other customers.
- A Request is de-identified when Provider has removed identifiers from it (such as the names and contact details of Customer and its Users, account and organization identifiers, IP addresses, precise timestamps, and contact details in its text); Provider does not know or reasonably believe that it still identifies Customer, a User, or a client or other person for whom it was sent, or that it contains Personal Data; and nothing links it to other Requests from the same account except, at most, a random identifier that Provider creates for one session and does not keep with any record identifying Customer or a User.
(d) De-identified Requests. A de-identified Request is no longer Customer Content or Customer's Confidential Information. Provider may keep, use, publish, sell, and license aggregated, de-identified Requests, together with what the Cloud Service returned for them, de-identified in the same way, including after this Agreement ends, subject to §5(c) and §5(e). Customer is responsible for keeping out of Requests anything that it, or a client or other person for whom it sends Requests, needs kept confidential even without identifiers.
(e) Uploaded data is never used for training or sold. Standard Terms §1.6 does not apply to datasets or files Customer uploads ("Uploaded Data"), or to anything derived from their contents. Provider will not use either to develop, train, or enhance artificial intelligence or machine learning models, and will not publish, sell, or license either. Provider will not use a Request that involves Uploaded Data or anything derived from it to develop, train, or enhance artificial intelligence or machine learning models, or publish, sell, or license it, and §5(d) does not apply to it.
(f) Providing the service is not training. Using a model to provide the Cloud Service to Customer (for example, indexing Customer's data so Customer can search it) is not developing, training, or enhancing that model.
6. Ending this Agreement and deletion
(a) Removing Paid seats. Customer may remove Paid seats at any time. A removed seat ends at the end of the current Subscription Period, and its User moves to the Free plan. A Paid seat stays with its User until it ends; giving a Paid seat to another User means adding a new seat. A User's Paid seats end no later than the end of the Subscription Period in which that User leaves, or is removed from, Customer's account, or their sign-in is deleted. Removing seats, including all of them, is not notice of non-renewal of this Agreement.
(b) Deleting the account. If Customer deletes its account, or Provider deletes it at Customer's request, this Agreement ends immediately. A User deleting their own sign-in does not delete Customer's account.
(c) No refunds. Except under §7 or Standard Terms §5.4, Provider does not refund Fees when a Paid seat ends, or Customer's account is deleted, before the end of a Subscription Period, for any reason.
(d) Deletion. When this Agreement ends, Provider will delete Customer Content within 60 days. Exceptions:
- copies in backups and logs, which are deleted on their normal cycle;
- the sign-in and contact details of a User who still has a SaysData sign-in; and
- records Provider must keep by law (such as billing records), or reasonably needs to establish, exercise, or defend a legal claim, for as long as that need lasts.
Standard Terms §10 continues to apply to anything kept. This §6(d) replaces Standard Terms §5.5(b) and, for Customer Content, Standard Terms §5.5(c).
(e) Framework Terms. Whenever this Agreement ends, its Framework Terms end with it, despite Standard Terms §5.2. Standard Terms §5.6 (Survival) and §12 of these Additional Terms still apply.
7. Discontinuing the service
If Provider ends Customer's Paid seats or access to the Cloud Service before the end of a prepaid Subscription Period, other than at the request of Customer, or of a User for their own sign-in, it will refund the unused portion of the Fees for what it ended. This does not apply if Provider does so because Customer breached this Agreement, or under Standard Terms §12.13. A suspension under Standard Terms §2.2 does not end access.
8. How this Agreement changes
Despite Standard Terms §12.2, Provider may change this Agreement as set out in this section. Customer does not need to sign or accept a change for it to take effect.
(a) Data Sources page. Provider may change the Data Sources page at any time, including adding or removing sources and updating licence summaries. These changes take effect when posted.
(b) Changes that neither reduce Customer's rights nor add to its obligations. Examples are higher limits, lower Fees, or a new plan that existing seats are not moved to. These take effect when posted.
(c) Changes that reduce Customer's rights or add to its obligations. This covers any other change to this Cover Page (other than the Data Sources page), to the Plans & Limits page, or to the version of the Standard Terms.
- Provider will give at least 30 days' notice by email to Customer's Notice Address.
- The change takes effect at the start of the first Subscription Period that begins after the notice period.
- Customer may end this Agreement before then.
- If Customer continues using the Cloud Service after the change takes effect, it has accepted the change.
(d) Versions. Each version of this Cover Page, the Plans & Limits page, and the Data Sources page is posted at its own dated address.
9. Public terms
Standard Terms §10 (Confidentiality) does not apply to this Cover Page, the Plans & Limits and Data Sources pages, or the existence of this Agreement.
10. Sanctions
Standard Terms §12.13 (Export Controls) also applies to Canadian export control and sanctions laws.
11. English only; not offered in Quebec
The Cloud Service, its documentation, and this Agreement are available in English only, apart from the French version of this section. SaysData is not offered to any customer whose principal place of business (or, for an individual, principal place of business or residence) is in Quebec. Customer represents that its principal place of business (and, for an individual, residence) is outside Quebec, and will promptly tell Provider if that changes. If it changes or was untrue, Provider may end this Agreement on notice. Customer's Users may be located anywhere, but Customer is responsible for ensuring that its Users' use of an English-only service complies with the laws that apply to Customer and to them. If the English and French versions of this section differ, the English version controls.
Anglais seulement; non offert au Québec. Le Service infonuagique, sa documentation et la présente convention sont offerts en anglais seulement, à l'exception de la version française du présent article. SaysData n'est offert à aucun client dont le principal établissement (ou, s'il s'agit d'une personne physique, le principal établissement ou la résidence) se trouve au Québec. Le Client déclare que son principal établissement (et, s'il s'agit d'une personne physique, sa résidence) se trouve à l'extérieur du Québec et s'engage à aviser sans délai le Fournisseur de tout changement à cet égard. En cas de changement, ou si cette déclaration s'avère inexacte, le Fournisseur peut résilier la présente convention par simple avis. Les Utilisateurs du Client peuvent se trouver en tout lieu, mais il incombe au Client de s'assurer que l'utilisation par ses Utilisateurs d'un service offert en anglais seulement est conforme aux lois applicables au Client et à ses Utilisateurs. En cas de divergence entre les versions anglaise et française du présent article, la version anglaise prévaut.
12. Survival
Sections 1–7, 9, 10, and 11 of these Additional Terms survive the end of this Agreement.
13. Technical protections
Provider may set, change, and apply technical limits and protections, such as limits on the rate or concurrency of Requests, query size, run time, and downloads from data providers, to operate the Cloud Service, including keeping it secure, healthy, and available. They never reduce a User's monthly allowances on the Plans & Limits page, and a Request refused under them never counts toward those allowances. The Documentation describes the main ones. Changes to them take effect when made and are not changes under §8(c).
The Common Paper Cloud Service Agreement Standard Terms are published by Common Paper, Inc. under the CC BY 4.0 licence.