# Acceptable use policy

**Last updated:** April 29, 2026

**Legal entity:** Brickspace Lab Inc. (“**Brickspace Lab**”)

This Acceptable Use Policy (“**AUP**”) applies to all users of Brickspace Lab’s websites, products, and services, including **Slab**, **Catalog**, APIs, developer tools, and support channels (the “**Services**”). It is incorporated into our [**Terms of service**](/legal/terms-of-service.md).

We may suspend or terminate access for violations.

***

## 1. Lawful use only

You may use the Services **only** in compliance with applicable laws and regulations, including those governing ecommerce, consumer protection, sanctions, export controls, intellectual property, privacy, and anti-spam.

You must **not** use the Services:

* to sell or promote **illegal** goods or services;
* to facilitate fraud, phishing, malware, or deceptive practices;
* to infringe others’ intellectual property or privacy rights; or
* to circumvent regional restrictions or sanctions.

***

## 2. Shopify ecosystem compliance

You must comply with **Shopify’s Acceptable Use Policy**, **Terms of Service**, **Partner Program** rules (if applicable), **API license terms**, Theme Store rules, and checkout restrictions. We may take action if your use exposes Brickspace Lab to breach of Shopify’s policies.

***

## 3. Accounts, access, and resale

You must **not**:

* share credentials or multi-factor authentication factors outside your authorized team;
* purchase access for the purpose of **reselling** seats or tokens **without** a written partnership agreement with Brickspace Lab;
* probe, scan, or test our systems without authorization (**no** unauthorized penetration testing);
* circumvent authentication, licensing, or entitlement checks.

***

## 4. APIs, automation, and developer tools

Where Catalog or other Services expose APIs or CLIs:

* respect **documented rate limits** and quotas;
* do not **overload**, **scrape**, or **mirror** our proprietary libraries or admin interfaces to replicate Catalog’s commercial offering;
* do not distribute API keys or tokens in public repositories or client-side code beyond what documentation permits;
* follow security disclosure practices if you discover vulnerabilities (**contact <hello@brickspacelab.com>**).

***

## 5. Content and storefront responsibility

You are responsible for **your** storefront content (products, descriptions, images, claims). Brickspace Lab does not pre-screen merchant content. We may cooperate with lawful requests from authorities or Shopify.

***

## 6. Abuse of support

You must **not** harass staff, submit fraudulent tickets, or misuse emergency channels. Reasonable use of support is expected per fair use stated on **<https://brickspacelab.com>**.

***

## 7. Competitive misuse

You must **not** use the Services to build or train a **directly competing** theme marketplace, preset marketplace, or developer tooling that reproduces Brickspace Lab’s proprietary assets or datasets, except as permitted by law.

***

## 8. Enforcement

We may investigate suspected violations, remove content we are legally required to remove, suspend accounts, terminate Services, and cooperate with law enforcement where appropriate.

***

## 9. Reporting

Report violations or security concerns to **<hello@brickspacelab.com>** with “AUP report” in the subject.

***

## 10. Changes

We may update this AUP; continued use after posting changes constitutes acceptance where permitted by law.

***

**<hello@brickspacelab.com>**

121 Mississaga Street East\
Orillia, Ontario L3V 1V6\
Canada

Tel. 705-259-7528


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.brickspacelab.com/legal/acceptable-use-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
