Privacy Policy

The clipped.page extension turns an X (Twitter) post into a single self-contained link. It reads a post only when you click its button, packs that post into the link, and then opens and/or copies the link. There is no account, no database, and nothing about you or the posts you clip is stored on any server.

When you click the button on a post, the extension reads that post's publicly visible content from the page you are viewing: author name and handle, text, image and video-thumbnail URLs, post metrics, timestamp, and any quoted post. It runs only on x.com and twitter.com.

That content is encoded directly into a clipped.page URL. Depending on your setting, the extension opens the link in a new tab, copies it to your clipboard, or both. The data lives inside the link itself — decoding the link reproduces the post.

Nothing is collected or stored server-side: no database, no accounts, no logs of the posts you clip. The only data the extension saves is your clip-button preference (open / copy / copy+open), kept in your browser via chrome.storage and synced by your browser if you have extension sync enabled.

• › activeTab and host access to x.com / twitter.com — to add the button and read the post you clip.
• › storage — to remember your clip-button preference.

The extension contains no analytics or tracking. The clipped.page website records anonymous, aggregate request counts (format requested, response status, coarse country, referrer host) with no cookies, no stored IP addresses, and no personal identifiers. Your data is never sold or shared, and nothing is sent to any third party beyond the clipped.page link you generate.

Source code and issues: github.com/zirkelc/clipped-page.