snappic

Privacy policy

Last updated: October 13, 2026

Snappic is a Chrome extension and self-hosted backend for capturing, annotating and sharing screenshots. This policy explains what the extension does with your data, what the backend stores, and what we do not do.

What the extension does

• Captures the visible area of the browser tab only when you explicitly click the toolbar button or trigger the capture command.
• Opens an in-page annotation overlay (pen, rectangle, arrow, text, highlight) rendered inside a Shadow DOM so it cannot read or modify the host page.
• When you press Upload, sends the resulting PNG to the backend URL you configured in the extension's options page.
• Stores your settings (backend URL, optional auth token) and a short local history of your recent uploads in the browser's own chrome.storage.local. This never leaves your device.

What the extension does not do

• It does not read the content of any web page you visit.
• It does not run on any tab until you explicitly ask it to capture.
• It does not contain analytics, tracking pixels, remote code, or third-party SDKs.
• It does not transmit anything to servers other than the backend URL you configure.

What the backend stores

When you upload a screenshot, the Snappic backend at one-link.cloud stores:

• The uploaded image bytes.
• The image's metadata (slug, size, dimensions, MIME type, upload timestamp, uploader IP address for rate-limit auditing).

Images are stored on S3-compatible object storage and served through a CDN. The public /image/<slug> share URL is unlisted but not secret — anyone who knows or guesses the slug can view the image. Treat shared links the same way you treat a Google Drive "anyone with the link" URL.

Permissions, and why we ask for them

• activeTab — capture the pixels of the current tab after you click Capture.
• scripting — inject the annotation overlay into the current tab after capture.
• storage — remember your backend URL, optional auth token, and recent-uploads history across browser sessions.
• downloads — write an annotated image to disk when you click Save.
• clipboardWrite — auto-copy the share URL to your clipboard after upload.
• Host permissions (<all_urls>) — the annotation overlay must mount inside whatever tab you choose to capture, which can be any website.

Third parties

The backend is self-hosted. The only third parties involved are the object-storage provider that holds image bytes and the CDN that serves them to recipients of your share links. We do not sell, rent, or share uploaded images or metadata with anyone else.

Data retention and deletion

Uploaded images persist until explicitly removed by the backend operator. If you want a specific image deleted, contact the address below with the share URL.

Security

All uploads use HTTPS. Images are served from the same TLS-protected domain or the configured CDN. The extension bundles no remote code — all logic ships inside the signed Chrome Web Store package.

Contact

Questions, deletion requests, or security reports: coders.any@gmail.com.