Hatchclip for Notion privacy

This policy is the one to give Notion and the Chrome Web Store for Hatchclip for Notion. It is written by Tabhatch. Questions go through the support form. The company-wide policy is on the company privacy page.

What the extension does

Hatchclip for Notion saves a page, a selection, an AI chat, or a YouTube title and transcript into your Notion workspace. The conversion happens in the browser. The resulting blocks are sent to api.notion.com from the extension, using the access token stored in chrome.storage on your computer.

What stays on your computer

• The Notion access token, workspace name, and workspace id.
• An install token that lets our server recognise that Notion user without holding the Notion token.
• Saved templates, the last destination, and a cached copy of database fields.
• The last Pro check (active or not, plan, and period end).

What reaches Tabhatch

• During connect: the one-time Notion OAuth code. We exchange it for a token and return the token to the extension. We do not store it.
• During a Pro check or checkout: the install token, which contains your Notion user id, workspace id, and the product slug. It does not contain page content, page URLs, or the clip.
• Stripe receives the checkout. We store the Stripe customer id, subscription id, plan, status, and period end next to that Notion user id.

What we do not collect

No analytics, no advertising identifiers, no browsing history, and no remote code. Permissions are activeTab, storage, scripting, contextMenus, and identity, plus optional host access to api.notion.com and tabhatch.com that the extension requests when you connect or clip.

Retention and deletion

Disconnecting inside the extension deletes the local token and templates from chrome.storage. Use the support form to ask us to delete the entitlement record. Stripe retains payment records under its own policy.

Children

The extension is not directed at children under 16.

This version is dated 18 October 2026.