Privacy policy

Nothing identifying. There is no analytics script, no advertising pixel, no session cookie and no account requirement to view, configure or download any free component.

Our web host records standard request logs (IP address, user agent, the path requested, and a timestamp) because every web server does. Those logs are used to diagnose errors and to understand aggregate traffic. They are not sold, not shared, and not used to build a profile of you.

A widget rendered inside Notion runs in a sandboxed frame with no URL and no network access. It cannot:

• read the Notion page it is embedded in, or any database on it;
• send a request to us, to an analytics service, or to anyone else;
• load a third-party script, font, image or beacon;
• access cookies, or any storage outside its own origin.

What it can do is store data in your browser's localStorage, under a key namespaced notion-arena.<component>.v1. That data stays on your device. It is not synced to teammates, not uploaded to us, and removed when you clear site data.

Our widgets contain no external requests by construction: the authoring checklist requires a grep for http://, https:// and @import to return zero hits before a component ships.

If you install a native recipe through POST /api/install, you supply an integration token so we can make Notion API calls on your behalf. That token is:

• held in memory for the duration of the request only;
• never written to a database, a log or a file;
• never used for anything other than the requests in the plan you approved;
• not required at all for mode: "plan", which is why plan mode exists.

We recommend an internal integration scoped to the minimum pages it needs, and rotating the token if you ever suspect it has been exposed. You can revoke it at any time from your Notion workspace settings, which ends our access immediately and completely.

When you configure a widget on this site, the values you type go into the URL query string so the preview can update. That means labels and settings appear in the request path, and therefore in host request logs.

Do not put sensitive information into widget parameters: a client name you would not want in a log, a private note, anything that looks like a credential. Parameters are meant for display text, numbers, colours and dates.

One, and it is not a cookie in the tracking sense: the light/dark appearance preference is stored in your browser's localStorage so the site does not flash the wrong theme on load. There is no cookie banner because there is nothing to consent to.

There are no accounts yet. Pro is free during the beta and no payment details are collected. When billing starts, a payment processor will handle card details (we will not see or store your card number) and this policy will be updated before that happens, with the previous version still reachable.

The Notion API, when you install a recipe. Requests go directly from our server to api.notion.com with your token, and are governed by Notion's own privacy terms.

Our hosting and web infrastructure providers, who process request logs on our behalf under their standard data-processing terms.

No advertising networks, no data brokers, no analytics vendors, no behavioural profiling, and no sale of any data, because there is effectively no data to sell.

Host request logs are retained for a short operational window and then rolled off. Tokens are not retained at all. Component files you download are yours and we keep no record of which ones you took.

Because we hold almost nothing about you, there is almost nothing to exercise rights over. If you have an account once billing exists, you can request a copy of it or have it deleted, and we will do so within 30 days. If you believe we hold something about you that is not described here, tell us and we will check rather than deflect.

This service is not directed at children under 13, and we do not knowingly collect data from anyone under 13. Widgets run inside Notion workspaces, which have their own age requirements.