Skip to content
Notion Arena

Terms of service

Last updated 11 October 2026

Plain terms, because the product is small and so is the surface area for disagreement. If something here is unclear, that is our failure to write it well: ask and we will rewrite it.

1What this service is

Notion Arena publishes components for Notion workspaces in three forms: a hosted URL that Notion can embed, a downloadable HTML file you upload to Notion as an HTML block, and a set of API calls that create databases, views and pages inside your workspace.

Notion Arena is an independent project. It is not made by, endorsed by, or affiliated with Notion Labs Inc. “Notion” and the Notion API are trademarks of Notion Labs Inc. and are used here to describe compatibility.

2Your Notion credentials

The install API accepts a Notion integration token so it can write to your workspace on your behalf. That token is used for the requests you asked for and is not stored, logged or reused after the request completes.

You are responsible for the scopes you grant your integration and for which pages you connect it to. Use an internal integration scoped as narrowly as the task allows. We will never ask for a token to show you a plan: mode: "plan" requires no credentials at all, and you should be suspicious of any tool that claims otherwise.

3What we guarantee, and what we do not

Downloadable HTML files are self-contained: no external requests, no dependencies, no licence check at runtime. Once you have the file it works, and it keeps working whether or not this site exists.

Hosted embed URLs are provided as-is with no uptime commitment. If we stop serving them, blocks using them will render blank. This is a real downside of hosted delivery and the reason every widget is downloadable. For anything you are selling, archiving or depending on, download the file.

Notion can change its API, its block types or its sandbox behaviour at any time. We track those changes and update components, but we cannot warrant that a given component will keep behaving identically across Notion versions.

4What you can do with components

Free components: use them anywhere, including in workspaces and templates you charge for. No attribution required, no licence key, no callback.

Pro components: the same rights while your subscription is active. Files you downloaded during an active subscription keep working afterwards: we do not disable anything retroactively.

You may modify any component you have a copy of. You may not present a modified component as an official Notion Arena release, and you may not resell the catalog itself as a competing component library.

5State and data

Widgets that remember anything do so in your browser's localStorage, scoped to the sandbox the block runs in. That data never reaches our servers and is not synced between your devices or your teammates. Clearing site data removes it.

Because a sandboxed HTML block has no network access, no widget can send your Notion data anywhere: not to us and not to anyone else. This is a property of Notion's sandbox rather than a promise we make, but it holds.

6Payments

Pro is free during the beta and no payment details are collected. When billing starts, anyone using Pro during the beta will be told before any charge is made, and will keep access for the notice period regardless.

Subscriptions renew monthly and can be cancelled at any time; access continues to the end of the paid period.

7Acceptable use

Do not use the install API to write to workspaces you do not control, do not use embed URLs to serve content that violates Notion's own terms, and do not attempt to route around Notion's rate limits using this service as a proxy. Abuse of the install endpoint gets the caller blocked, not the component removed.

8Liability

The service is provided without warranty of any kind, to the maximum extent permitted by law. Our total liability for any claim arising from your use of Notion Arena is limited to the amount you paid us in the twelve months before the claim, which, during the beta, is nothing.

In particular: an install that creates databases in the wrong place, a recipe that overwrites an existing property, or a formula that computes something you did not intend are outcomes we help you avoid by publishing the plan first, but they remain your workspace and your decision to run.

9Changes

If these terms change materially, the date at the top changes and the previous version stays reachable. Continued use after a change is acceptance of it.

Questions about these terms, or about whether a specific use is covered: open an issue on the repository. Public questions get public answers, which is better for everyone than a private inbox.