Publisher: Maniastra, sole operator, based in Poland Extension: Clipwise (Chrome extension) Version covered: 1.0.0 Last updated: 27 September 2026 Contact for privacy questions: support@maniastra.com
Summary
Clipwise has no backend server. There is no account, no login, and no server-side component of any kind. We do not collect, receive, transmit, see, or store any of your data, because there is nowhere for it to be sent to us.
Everything Clipwise stores stays on your own device in chrome.storage.local. The only network destination the extension ever contacts is api.notion.com, and requests to it are made directly by your browser using a Notion integration token that you create and paste in yourself.
What Clipwise stores, and where
All of the following is written to chrome.storage.local, which is local browser storage on the machine you installed the extension on. None of it is synced to us, and none of it leaves your device except as described in "What is sent to Notion" below.
| Data | Why it exists | Where it lives |
|---|---|---|
| Your Notion internal integration token(s) | Required to authenticate requests to the Notion API on your behalf | chrome.storage.local on your device |
| Account labels you choose for each token | So you can tell your workspaces apart in the popup | chrome.storage.local on your device |
| Your default database ID per account | So the keyboard shortcut and popup can target it without asking again | chrome.storage.local on your device |
| Cached database schemas (property names and types) | To build the property form without re-fetching on every clip | chrome.storage.local on your device |
| Queued offline clips, including the full extracted page content | So a clip whose network request failed can be retried instead of lost | chrome.storage.local on your device |
| Extension preferences | To remember your settings | chrome.storage.local on your device |
Clipwise does not use chrome.storage.sync, so this data is not copied between your devices through your Google account by the extension.
You can delete all of it at any time by removing the extension from Chrome, or selectively by deleting accounts and queued clips from the Clipwise options page.
What is sent to Notion
When you clip a page, your browser sends a request directly to https://api.notion.com. That request contains:
- The content extracted from the page you chose to clip, converted to Notion blocks (text, headings, lists, tables, code blocks, image URLs, links).
- The property values shown in the popup form — for example title, author, date, source URL, and any values you typed or changed.
- The ID of the database you selected as the destination.
- Your Notion integration token, in the
Authorizationheader, so that Notion can verify the request is yours.
This traffic goes from your browser to Notion over HTTPS. It does not pass through any server operated by Maniastra, and no copy of it is sent anywhere else. The extension declares exactly one host permission in its manifest — https://api.notion.com/* — which means Chrome itself prevents the extension from making network requests to any other host. You can verify this in the extension's manifest.json.
Once data reaches Notion, it is held by Notion under Notion's own privacy policy and your own agreement with Notion. Maniastra is not a party to that relationship.
What Clipwise reads from web pages
Clipwise reads a page only when you explicitly clip it — by clicking the toolbar icon, pressing the keyboard shortcut (Ctrl+Shift+S, or Command+Shift+S on macOS), or using a right-click context menu entry.
The content script that performs extraction is injected on demand at that moment. It is not declared to run on all URLs, so on every page you do not clip, Clipwise executes nothing and reads nothing.
When it does run, it reads the page's visible content, its metadata (title, author, publication date, canonical URL, site name), and your text selection if you made one. It does not read cookies, passwords, form inputs, local storage of the site, or browsing history. It does not modify the page. It does not archive pages, and it does not touch any data other than the page you asked it to clip.
What Clipwise does not do
To be explicit, Clipwise contains:
- No backend server. There is no Maniastra server involved in any part of the extension's operation.
- No analytics. No Google Analytics, no product analytics, no event tracking, no usage counters.
- No telemetry. No crash reporting, no error reporting service, no performance beacons.
- No tracking. No advertising identifiers, no fingerprinting, no cookies set by the extension, no cross-site tracking.
- No account system. No sign-up, no login, no email address collected, no password.
- No third-party SDKs that transmit data.
- No selling, renting, or sharing of data, which is trivially true because no data reaches us in the first place.
- No remote code. The extension runs only the JavaScript shipped in its package, under a content security policy restricted to
'self'.
Chrome Web Store disclosures
For the Chrome Web Store privacy declarations, Clipwise:
- Does not collect or transmit personally identifiable information to the developer.
- Does not collect health, financial, authentication, personal communications, location, or web history information for the developer.
- Handles "website content" solely to perform the user-initiated clip, sending it only to the user's own Notion workspace at the user's request.
- Handles the user's Notion integration token as a credential stored locally and transmitted only to
api.notion.comfor authentication. - Does not use or transfer any data for purposes unrelated to the extension's single purpose.
- Does not use or transfer any data to determine creditworthiness or for lending purposes.
- Does not sell data to third parties.
GDPR
Maniastra does not receive, process, or store any personal data through Clipwise. Because no personal data reaches the developer, there is no processing activity by Maniastra for which a lawful basis, consent, or a data processing agreement would be required, and there is no controller-processor relationship between you and Maniastra arising from your use of the extension.
Your data relationship is with Notion directly. The content and metadata you clip are stored in your own Notion workspace, and Notion is the party processing it. Rights of access, rectification, erasure, restriction, portability, and objection in respect of that data are exercised against Notion under Notion's privacy policy, or by editing or deleting the pages yourself in Notion.
In respect of the data Clipwise keeps on your device — your token, your settings, and any queued clips — you are in sole control. Deleting the extension removes it; the options page lets you remove individual accounts and queued clips.
If you believe Maniastra nonetheless holds personal data about you, write to support@maniastra.com and we will respond.
Children
Clipwise is a productivity tool and is not directed at children. It collects no data from anyone, including children.
Security
Your integration token is stored in chrome.storage.local, which Chrome isolates to the extension and which is not readable by web pages. Requests to the Notion API are made over HTTPS. Because there is no server and no account, there is no remote database of credentials that could be breached.
The token is a Notion internal integration secret that you create yourself at notion.so/profile/integrations. Its access is limited to the databases you explicitly connect it to in Notion. If you want to revoke Clipwise's access to your Notion workspace, delete or regenerate the integration in Notion's integration settings; that takes effect immediately and independently of this extension.
Changes to this policy
If a future version of Clipwise changes what data it handles or where it sends it, this policy will be updated before that version is published, and the "Last updated" date above will change. Any version that introduced a server, analytics or telemetry would be a material change and would be described here explicitly.
Contact
Privacy questions, data requests, and complaints:
Maniastra — sole operator, Poland.