Clipper

Privacy policy

Last updated: 17 November 2026

Clipper is a browser extension that lets you highlight web pages, write notes and save them to Notion. This policy explains what data the Clipper extension and the website clipper.so handle, why, and what your choices are.

Who we are

Clipper is made by Daniel Wirtz, a sole proprietorship (eenmanszaak) registered with the Dutch Chamber of Commerce (KvK) under number 81308388, based in Utrecht, the Netherlands ("we", "us"). We are the controller for the personal data described here.

Contact: support@clipper.so

Summary

  • Your highlights, notes, settings and Notion connection stay in your browser.
  • What you save goes from your browser straight to your own Notion workspace.
  • Clipper uses your own Notion login in this browser to save. Our server is not involved in connecting or saving.
  • A Clipper account is optional. You need one only to buy or use Clipper Pro. It is kept on Clipper's own server (clipper.so), separate from any other product of ours, and payments go through Polar.
  • Clipper sends anonymous usage events without page addresses or content. You can turn them off.
  • If you write to us through the Help or Feedback form, we keep your message to answer it.
  • We do not sell your data, show ads or use your data for anything else.

Data stored in your browser

Clipper keeps the following in your browser's extension storage, on your device only:

  • the highlights, notes and editor content for pages you use Clipper on;
  • your settings and templates, and the Notion database and field values you last used;
  • your Notion connection: which Notion user to save as (a Notion user id) and the workspace's id, name and icon. There is no password, token or cookie in it;
  • a random install id used for usage events (see "Usage analytics");
  • if you sign in to a Clipper account (see "Account and Pro"): your account's session token, name, email address and profile picture address, and your plan (Free or Pro, and until when Pro is paid).

We cannot see this data. It is deleted when you remove Clipper from your browser. Disconnecting Notion in Clipper deletes the stored connection. It does not log you out of Notion.

Connecting Notion

Clipper saves with the Notion login you already have in this browser. There is no OAuth, no separate sign-in and no access token. When you click Connect Notion, Clipper:

  • checks whether Notion's sign-in cookie (token_v2) exists in your browser, on app.notion.com or, for older Notion logins, www.notion.so. It only checks that the cookie is there. It never reads the cookie's value into its own storage, logs, error reports or usage events, and never sends it to us or anyone else;
  • asks Notion's web app which workspaces your Notion login (or each login, if you are logged in to more than one Notion account) can use, and shows you their names, icons and, with more than one account, the account's email address. Clipper keeps only the user id and workspace you pick (see above).

If you are not logged in to Notion, Clipper shows Log in to Notion, which opens Notion's own login page in a new tab. Clipper never sees your Notion password.

For this, Clipper's browser permissions include cookies and Notion's web app (notion.so and notion.com). It uses them for nothing else.

Data sent to Notion

Clipper talks to Notion's web app (app.notion.com, or www.notion.so for older logins) directly from your browser, as you. Your browser attaches your Notion login to these requests itself:

  • When you click Save to Notion, it sends the page's title, address and details (such as author, site name and published date), the text you highlighted, your notes and the field values you chose, to create a page in the database you picked. The page body is the note in the editor and, when your template includes the page content (the @Content variable, as in the Read Later and Web Clips starters), the page's readable text and image addresses. If you type a new option for a select or multi-select field, Clipper adds that option to the database. Nothing is sent unless you click Save to Notion.
  • To show where you can save, it searches your workspace for databases and reads their fields.

Clipper can do in Notion only what your Notion login can do, and only does what is described here. Data in your workspace is governed by Notion's privacy policy.

Starter templates

When you set up Clipper, you can pick a starter database (Web Clips, Bookmarks or Read Later) and a workspace to put it in. Clipper then uses your Notion login in this browser to copy the template you picked into the workspace you picked, the same way Notion's own "Duplicate" button does. To do this it:

  • checks Notion's sign-in cookie, as above;
  • asks Notion's web app which workspaces you can add pages to, and shows you their names and icons;
  • asks Notion to copy the template into your private pages in that workspace, and reads back the new database's id and name.

Clipper keeps the new database's id and name in your browser as the place to save to.

Account and Pro

Clipper is free to start. Clipper Pro ($8, €8 or £7 a month; $72, €72 or £65 a year) adds unlimited templates, AI prompts, PDF highlighting, screenshots and colour blocks. Pro needs an account, and you only need an account for Pro.

Your Clipper account lives on Clipper's own server (clipper.so) and its own database, run by us. It is not shared with Markway, our other extension: a Markway account or Markway Pro does not carry over to Clipper. When you click Sign in or Upgrade in Clipper:

  • Clipper opens the sign-in page, where you sign in with Google or with your email address and a password. The account keeps your name, email address, profile picture address (from Google), and your plan. Signing in sets a session cookie on clipper.so and sends you to clipper.so/extension/connected with a one-time code that expires after two minutes and works once; Clipper swaps it for a session token, which it keeps in your browser. The server keeps a record of each session (its expiry, and the IP address and browser it was created from) until it expires or you sign out.
  • To show your plan, Clipper asks clipper.so whether you have Pro, sending the session token. To show Pro's price in your currency, it asks clipper.so for the price; our host tells the server which country the request comes from, and we don't keep it.
  • Upgrade opens a checkout page by Polar Software Inc. (polar.sh), our merchant of record, who handles the payment, invoices and taxes. We never see your card details. Polar tells our server which account bought Pro and until when it is paid. Polar is told your account's email address and name, and an internal account id, when you create an account, so the checkout belongs to you. When you start a checkout, our server passes Polar your IP address, so Polar can show the price in your currency. Manage subscription opens Polar's customer portal.
  • AI prompts (Pro) send the prompt you wrote and the page text it asks about to our server, which sends them through Vercel's AI Gateway to an AI model provider to answer, and returns the answer. We don't keep the prompt, the page text or the answer; we keep only an hourly count of AI requests per account, to limit abuse.

Signing out deletes the session token, your account details and plan from Clipper's storage. To delete your account, email support@clipper.so. We keep billing records as long as tax law requires.

Help and feedback

In Clipper you can send us a help request (Settings › Help) or feedback (the Feedback? button):

  • Help sends the message you write and the email address you enter.
  • Feedback sends only the text you write.

Nothing else is attached: no page address, highlights, notes, Notion data or account details. Our server (clipper.so/api/notion/help and /feedback) stores each message in our own Notion workspace, where we read and answer it, and sends the message text (never your email address) to OpenAI to generate a short title for it. Notion Labs, Inc. and OpenAI act as our processors for these messages. The server itself stores nothing and does not log your message; if saving fails, it logs the error.

We use them only to answer your request and improve Clipper. We keep them until the request is handled and delete them within 12 months. You can also simply email support@clipper.so.

Usage analytics

To see which features are used and to find problems, Clipper sends anonymous usage events, such as "the panel was opened" or "a page was saved to Notion". Each event can carry only:

  • counts, true/false values and fixed codes from a list in Clipper's code (for example the number of highlights, a highlight colour, or the export target "notion-oauth");
  • Clipper's version (clipper_version) and whether it is a store build (store_build);
  • the random install id;
  • the technical details PostHog's library adds itself: browser and operating system name and version, device type, browser language, time zone, user-agent string and library version.

Events never include the address, domain or title of a page, the text you highlight or write, or anything from your Notion workspace. In the versions published in the stores, Clipper may also send an error report when something breaks: the error type and message and a technical stack trace, with web addresses removed.

When a save to Notion or a starter-template install fails, Clipper sends a save_failed event with the operation, a fixed error code, Notion's HTTP status and your browser name, plus (in store builds) an error report with the same details. Neither contains cookies, page content, Notion ids or web addresses. Both follow the Anonymized tracking switch.

The Report this link next to an error opens an email to support@clipper.so in your own email app, filled in with Clipper's version, the error code, the part of Clipper it happened in, the time, and your browser and operating system names. Nothing is sent unless you send that email yourself.

These events go to PostHog in its EU cloud (Frankfurt, Germany), into a project used only for Clipper. Every event asks PostHog not to derive a location from your IP address ($geoip_disable) and not to create a person profile ($process_person_profile: false). PostHog still receives your IP address with each request, as every web server does. We keep events for at most 24 months.

Your choice:

  • Chrome and other Chromium browsers: usage events are on by default. Turn them off in Clipper under Settings › General › Anonymized tracking. This stops all events and error reports and deletes the install id, so if you turn them on again you start with a new, unlinked id.
  • Firefox: nothing is sent unless you allow "Technical and interaction data" when installing Clipper or later in the add-on's permissions. The same switch in Settings also applies.

The website clipper.so

  • Cookies: the public marketing pages set no cookies and store nothing in your browser. There are no analytics, advertising or tracking scripts on the site. Fonts are served from clipper.so itself. Signing in to a Clipper account (see "Account and Pro") sets a session cookie on clipper.so, used only to keep you signed in.
  • Hosting: clipper.so, including the server parts above and the changelog page Clipper's Settings shows, is hosted by Vercel Inc. Vercel keeps short-lived technical request logs, including your IP address, to operate and secure the service.

Legal bases

Under the GDPR we rely on:

  • Contract, Art. 6(1)(b): to provide what you ask for: connecting to your Notion workspace, saving to Notion, a Clipper account and Clipper Pro (including payments through Polar), and answering your help requests.
  • Legitimate interest, Art. 6(1)(f): anonymous product analytics and error reports to improve Clipper, with an easy opt-out; feedback you send us; and request logs to keep the service secure.
  • Consent, Art. 6(1)(a): analytics on Firefox. You can withdraw consent at any time.

International transfers

Some of our processors are based in the United States, including Vercel, OpenAI, Notion and Polar. Where personal data goes outside the European Economic Area, it is protected by the EU-US Data Privacy Framework where the provider takes part in it, or by the European Commission's Standard Contractual Clauses.

How long we keep data

  • In your browser: until you delete it, disconnect Notion or remove Clipper.
  • Clipper accounts (name, email address, plan, and session records: expiry, IP address and browser): until you delete the account, the session expires, or you sign out. Hourly AI request counts, used only to limit abuse, are not kept beyond that purpose. Billing records are kept as long as tax law requires. Vercel's request logs are kept only briefly.
  • Help and feedback messages: until handled, deleted within 12 months.
  • Usage events and error reports: at most 24 months.

Your rights

You have the right to access, rectify and erase your personal data, to restrict or object to its processing, to data portability, and to withdraw consent at any time. To use them, email support@clipper.so. Usage events are anonymous, so we usually cannot link them to you; turning analytics off deletes the install id.

You also have the right to complain to a data protection authority. In the Netherlands this is the Autoriteit Persoonsgegevens.

What we do not do

  • We do not sell or rent your data.
  • We do not use your data for advertising, and Clipper shows no ads.
  • We do not use your data to determine creditworthiness or for lending.
  • We do not keep a browsing history. A page's address leaves your browser when you save it to Notion, and only then unless you include it in a Pro AI prompt (for example with a URL variable).
  • Clipper does not load or run remote code.

Chrome Web Store User Data Policy

Clipper's use and transfer of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements:

  • Data is used only to provide and improve Clipper's single purpose: saving highlights and notes from web pages to Notion.
  • Data is not transferred to anyone except as needed for that purpose, to comply with the law, or as part of a merger or acquisition.
  • No one reads your data, except with your consent, for security reasons, or to comply with the law.
  • Data is not used for advertising or to determine creditworthiness, and it is not sold.

Children

Clipper is not directed at children under 16, and we do not knowingly collect their data.

Changes to this policy

When this policy changes, we update this page and the date at the top. If a change is significant, we will also say so on clipper.so.