Terms of Service

1. Supplier and eligibility

sqlbook is a product by Sitelabs, the trading name of Christopher John Pattison, a sole trader registered in the Netherlands. “Sitelabs”, “we”, “us” and “our” mean that supplier.

sqlbook is intended for professional and business use by people aged 18 or older. You must have authority to act for the business whose workspace you administer. A “Customer” is the business or professional that agrees a pilot order with Sitelabs; an “Authorized User” is someone the Customer permits to use its workspace. Users must follow these terms when using the service. Creating an account or accepting an invitation does not itself purchase a pilot or authorize a charge.

2. Your pilot agreement

A paid pilot starts only when Sitelabs and the Customer sign or expressly accept a separate order identifying the Customer, start date, fees, payment dates, agreed scope and any specific deliverables. Unless the order expressly says otherwise, the pilot lasts three months from its agreed start date, has no automatic renewal and ends at the end of that period. Continuation requires a further agreement.

The order must identify and include the dated versions of these terms and the Data Processing Agreement (“DPA”) before acceptance. The order, those terms and the DPA form the pilot agreement. The DPA prevails on conflicting provisions about processing personal data. Express commercial exceptions in an accepted order prevail over these terms; Customer purchase-order terms do not apply unless Sitelabs expressly accepts them.

Prices, taxes, invoicing, payment dates and any agreed cancellation or refund arrangements are set out in the order. There is no right to end a fixed-term pilot for convenience or receive a refund merely because it is used less than expected, unless the order or mandatory law provides otherwise. The Privacy Policy explains our handling of personal information; acknowledging it does not give blanket consent to unrelated processing.

3. Accounts and workspaces

Give accurate account and contact information, protect access to your sign-in email and promptly report suspected unauthorized access. Do not share sign-in credentials or let another person use your identity.

The Customer controls its workspace and the users, permissions, datasource connections and publication audiences it authorizes. Owners and Admins have management rights according to their role. The Customer is responsible for Authorized Users’ use of its workspace and must promptly remove access that is no longer authorized.

Leaving a workspace or deleting an individual account does not necessarily delete queries, uploaded sources, dashboards or other content belonging to a surviving workspace. Retained attribution is removed or redacted under the deletion process described in the Privacy Policy.

4. Content and confidentiality

As between the parties, the Customer retains its rights in its data, files, queries, prompts, dashboards and other content. The Customer authorizes Sitelabs to access, store, copy, transmit and otherwise process that content to provide the service, carry out authorized instructions, protect the service and meet legal obligations. Processing of Customer Personal Data is governed by the DPA.

The Customer must have the rights, lawful basis and permissions needed to connect sources, import personal data, invite users, request AI processing and share results. Use appropriately limited datasource credentials and disclose only information needed for the chosen feature. Do not submit special-category personal data, criminal-offence data or other highly sensitive regulated data unless its processing has first been expressly agreed in writing.

Each party will protect the other’s non-public business information with reasonable care and use it only for the agreement. Disclosure is permitted to people and providers who need it to perform the agreement and have appropriate confidentiality duties, as authorized by the Customer, or as legally required. These duties do not cover information independently developed, lawfully obtained without a confidentiality restriction, already lawfully known, or publicly available without a breach. They continue after the pilot ends.

Sitelabs retains its rights in sqlbook, its software and service materials. The Customer receives permission to use the hosted service during the agreed pilot, subject to the agreement. No rights to the underlying source code are granted. The Customer may use outputs subject to applicable law and third-party rights; AI outputs may resemble outputs supplied to others.

5. Acceptable use

Do not use sqlbook to break the law, infringe rights, disclose data without authority, send malicious content, bypass permissions or query-safety controls, obtain another workspace’s data, overload the service or interfere with its operation. Do not probe or test security without prior written authorization. Do not resell access or misrepresent the service as your own without our written agreement.

The Customer will indemnify Sitelabs against third-party claims and reasonable resulting costs arising from Customer content that infringes rights or from the Customer’s unlawful or unauthorized use, to the extent attributable to the Customer rather than Sitelabs’ breach. Sitelabs will notify the Customer promptly, allow it to defend the claim with suitable counsel and provide reasonable cooperation at the Customer’s expense. No settlement may impose an admission or non-monetary obligation on Sitelabs without its consent.

6. Connected services and sharing

Customer-selected databases, Google Sheets, Stripe, HubSpot and other connected services remain subject to their own terms, permissions and availability. The Customer must authorize our access and remains responsible for the original source and its credentials. Live database queries read selected data; uploaded and synchronized sources create stored workspace copies. Deleting a copied sqlbook datasource does not delete its original third-party source.

A Google Sheets connection reads the specific spreadsheet selected through Google Picker and imports approved ranges into a private workspace replica. Google’s selected-file permission includes write access, but sqlbook implements read operations and does not edit the spreadsheet. Refresh is manual by default. Optional change detection marks an update as available; it does not automatically import changes. Structural changes require review before a replacement is approved. A previously approved copy can remain queryable when provider access is lost.

The Customer controls sharing and must check the results and audience before publication. Public content can be accessed publicly; link-access content can be accessed by someone who obtains the relevant link. Links can be forwarded, and revoking publication cannot recall copies already obtained. Remote images, embeds and linked services can make a viewer’s browser contact those third parties.

7. AI and analysis

Requested AI features may send relevant prompts, history, schema, SQL, selected results, images and other context to OpenAI as described in the Privacy Policy. Connecting a datasource does not itself send its complete contents to AI. The Customer is responsible for authorizing the content supplied to those features.

AI-generated SQL, text and analysis can be wrong, incomplete or outdated. Check queries, source freshness, results and suitability before relying on or sharing them. sqlbook does not provide legal, medical, financial or other regulated professional advice, and must not be relied on as the sole basis for a decision affecting a person’s rights or safety.

8. Service operation

sqlbook pilots evaluate a developing service. Features can contain defects, require maintenance or be interrupted by technical faults or third-party outages. We may update the service, but will not materially reduce the expressly agreed pilot scope without agreement unless necessary for law or security. We will inform the Customer of material interruptions or changes where reasonably practicable.

Except for express commitments in the accepted order and obligations that cannot be excluded by law, the pilot service is provided “as is” and “as available”. We do not promise uninterrupted availability, error-free or accurate outputs, fitness for a particular purpose, a particular business outcome, or a service-level agreement. The Customer must retain its original source data and suitable backups. Force majeure excuses performance to the extent and for the period permitted by Dutch law; it does not excuse payment for service already provided.

9. Suspension, termination and data return

We may suspend affected access to address a security threat, unlawful use, a material breach or overdue payment. Where lawful and safe, we will give notice and a reasonable opportunity to remedy the issue, limit suspension to what is needed, and restore access after it is resolved.

Either party may terminate for a material breach that remains unremedied 14 days after written notice. Immediate termination is permitted where continued performance would be unlawful, the breach cannot reasonably be remedied, or action is necessary to contain an immediate serious security threat. Rights to terminate under mandatory law are preserved.

Before the pilot ends, the Customer should use existing export and download controls and contact us to arrange assistance returning other Customer Personal Data. At the end of processing, return or deletion will follow the Customer’s instructions under the DPA, subject to legally required retention and expiring backups. There is no additional post-contract retrieval or service-access window. Incurred payment obligations and provisions intended to survive, including confidentiality, liability and disputes, continue after termination.

10. Liability

To the maximum extent permitted by applicable law, Sitelabs’ total aggregate liability arising out of or in connection with an affected pilot, these terms and its DPA, across all claims and causes of action, is limited to the total pilot fees actually paid by the Customer to Sitelabs for that affected pilot, excluding taxes. Multiple claims or incidents do not increase that single cap. There is no separate increased contractual cap for confidentiality or data-protection claims.

To the extent permitted by law, Sitelabs is not liable for indirect or consequential loss, lost profit or revenue, lost savings or business opportunities, business interruption, or loss arising from reliance on unchecked AI outputs or source data the Customer controls. The Customer must take reasonable steps to prevent and mitigate loss.

These exclusions and limits do not apply to fraud, intentional misconduct, deliberate recklessness or any liability that applicable law does not permit to be excluded or limited. They do not restrict a data subject’s statutory rights, a regulator’s powers, or a party’s mandatory liability under data-protection law. The Customer’s payment obligations and indemnity obligations are not limited by Sitelabs’ cap.

11. Changes, assignment and disputes

We may publish revised terms for future agreements. A website update does not automatically amend a signed pilot: its accepted dated versions continue to apply unless both parties agree a change or mandatory law requires it. Material privacy-practice changes will be communicated where required by law.

A future company does not automatically replace Christopher John Pattison as the supplier. Any transfer of the agreement must follow applicable law and the required customer agreement or notice. The Customer may not transfer its agreement without Sitelabs’ written consent, except where mandatory law provides otherwise.

Dutch law governs the agreement. Disputes are subject to the competent courts for Sitelabs’ registered business location in the Netherlands, unless mandatory law requires another forum. If a provision is unenforceable, the remaining provisions continue to apply to the extent permitted by law. A failure to enforce a provision once is not a waiver of future enforcement.

Send contract, service or privacy notices to hello@sqlbook.com. We will use the Customer’s contact address in its order for contractual notices. The English version is the version supplied for acceptance.