Logo
One-Click Save to Notion

Privacy Policy

Last Updated: June 12, 2026

1. Introduction

Your privacy is of paramount importance to us. This Privacy Policy describes how One-Click Save to Notion ("we", "us", "our", or "Software") handles data in connection with the One-Click Save to Notion Chrome Extension (the "Extension") and our website.

Unlike standard web clippers, our Extension uses a secure, minimal serverless verification endpoint to validate purchase status. We never collect or store your browser history, bookmarks, or Notion API keys.

2. Zero Data Collection & Transmission

We do not collect, monitor, store, sell, or share any of the following personal or sensitive information:

  • Notion Tokens: Your Notion Internal Integration Token is stored only on your local device. We never transmit it to any server other than the official, secure Notion API endpoint (https://api.notion.com).
  • Notion Page IDs & Workspaces: The titles and Page IDs of your Notion pages are only retrieved and displayed locally on your browser.
  • Bookmarked URLs: When you click the Extension icon, the active tab's URL is fetched and sent directly to the Notion API. We never log or record what websites you bookmark.
  • Browsing Activity: We do not track the websites you visit or build profiles based on your browsing behavior.

3. Local Browser Storage

The Extension uses chrome.storage.local inside Google Chrome to store your configuration parameters. This includes:

  • Your Notion Internal Integration Token (encrypted/hidden locally).
  • The selected Notion Page ID where bookmarks should be saved.
  • Your Pro License Key (if upgraded).
  • Save statistics (e.g., number of saves) used to verify trial status.

This data never leaves your computer, except when sending request payloads directly to Notion's API. You can clear this stored data at any time by right-clicking the Extension and selecting "Remove from Chrome", or by deleting settings inside the configuration page.

4. Third-Party Services

We partner with third-party service providers to handle payments and downloads. These partners collect data according to their own policies:

  • Gumroad (Payment Processing): If you purchase a Pro Lifetime License, checkout is handled by Gumroad.com. Gumroad handles customer payment processing and license key distribution. We do not store or access your payment card numbers. Please refer to Gumroad's Privacy Policy for more details.
  • Google Web Store: The Extension is distributed through the official Google Chrome Web Store. Google collects standard usage metrics, downloads statistics, and installation counts. Please refer to Google's Privacy Policy.

5. License Key Security

Our Pro Lifetime version uses a secure serverless validation service to verify the status of your purchase. The verification request transmits only your unique, randomly-generated device ID and the license key to our secure serverless endpoint. Our database stores only the activation details (device ID, license key, and purchase status) and never collects any personal information or Notion workspace credentials. An offline fallback mechanism is also built in to ensure you can continue using the extension even if the validation server is temporarily unreachable.

6. Data Retention

Since we do not collect or store user data on any databases or servers, we do not retain your personal information. Any local settings data is retained in your browser's local sandbox storage until you uninstall the Extension or manually clear your browser's extension cache.

7. Security Practices

We follow strict secure coding guidelines when building the Extension:

  • All API calls to Notion are encrypted via HTTPS (TLS 1.2/1.3).
  • We request minimal Manifest V3 permissions: storage (to remember configurations) and activeTab (to read the current active page URL only when you click the extension icon). We do NOT request permissions to read data on all websites.
  • The Extension is built with TypeScript and compiles directly using tsc, ensuring no unverified third-party libraries or build bundler injections are present.

8. Changes to this Policy

We may update this Privacy Policy from time to time to reflect modifications in our software or regulatory standards. If we make any changes, we will post the new version on this website and update the "Last Updated" date at the top of this page.

9. Contact Us

If you have any questions about this Privacy Policy or how your data is handled, please feel free to reach out to us at: