Security & privacy
Private by default. Secure when you share.
Every screenshot stays on your device until you share it. When you do, it is encrypted in your browser first, and only the people you pick receive the key: not Screshot, not our storage provider. This page explains how it works and how to check it yourself.
0
Screenshots uploaded unless you choose to share
0
Network requests when you capture, blur, copy or download
5
Chrome permissions, all without install warnings
AES-256
End-to-end encryption on every shared screenshot
Data flow
What happens when you take a screenshot
- 1
You start a capture
By clicking the icon, using a shortcut or the right-click menu. Only then does Chrome give Screshot temporary access to that one tab (activeTab).
- 2
Chrome renders the image locally
The visible area is captured by Chrome itself. For a full page, Screshot scrolls the tab, pauses sticky headers and input, stitches the parts in memory, then restores the page exactly as it was.
- 3
The image opens in a local extension page
The editor and the full-page viewer are pages packaged inside the extension (chrome-extension://). They load no remote code, fonts or analytics.
- 4
You choose where it goes
Copy to the clipboard, download a file, or share an end-to-end encrypted link. Closing the tab discards the image. The extension never keeps a copy.
Permissions
Every permission, and why it is needed
activeTab- Used forCapture the tab in front of you, only at the moment you click the icon or use a shortcut.
- What it cannot doRead other tabs, run in the background, or see your browsing history.
scripting- Used forRead the zoom level of the tab you capture, so blur fits the size of its text, and scroll that tab during a full-page capture, then put it back exactly as it was.
- What it cannot doRun on any page you did not ask Screshot to capture.
contextMenus- Used forAdd "Capture visible area" and "Capture full page" to the right-click menu on the Screshot icon.
- What it cannot doChange menus on web pages or read what you click.
storage- Used forKeep your Screshot sign-in, the extension’s settings and the counts that decide when to ask you for a rating on the Chrome Web Store on this device, in the extension’s own storage. The settings and counts are never sent; the sign-in is used only to talk to Screshot when you share.
- What it cannot doRead cookies, passwords or anything websites store.
identity- Used forOpen Google sign-in in its own window when you choose to share, without leaving the editor.
- What it cannot doSee your Google password or sign you in to anything but Screshot.
Screshot requests no host permissions (such as "Read and change all your data on all websites") and no access to history, cookies or downloads.
Pages the extension opens
Capturing and editing send no data. Screshot opens two pages on screshot.com as normal browser tabs:
- A welcome guide after a manual install. It is skipped when IT installs Screshot by policy.
- An optional one-question survey after uninstall, which includes only the extension version.
The screshot.com website uses no analytics or advertising cookies; visits are counted in aggregate by Cloudflare without cookies. See the privacy policy.
Verify it yourself
- Open
chrome://extensions, turn on Developer mode and click Details on Screshot to see its permissions. - Click Inspect views: service worker and open the Network tab.
- Take a visible and a full-page screenshot. No requests leave the browser.
- Click Share. The upload is a file of encrypted bytes that starts with
SCE1, not an image.
Share by link
End-to-end encrypted sharing
Share links are for the moments when a paste is not enough. Everything above stays true for capture, blur, copy and download. Sharing is a separate choice, made one screenshot at a time, and the screenshot is encrypted before it leaves your device.
Encrypted before it leaves your device
- Each shared screenshot gets its own random key (AES-256-GCM)
- The image and its thumbnail are encrypted in your browser, then uploaded
- Our servers and storage (Cloudflare R2) hold only the encrypted files, never the key
Keys only you can unlock
- Your account has its own key pair (ECDH P-256), created in your browser
- Its private key is stored encrypted; you unlock it with a passkey or your recovery code
- Screshot can't unlock it and can't reset it for you
The key goes only to the people you choose
- Only me: the key is wrapped for your key alone
- Invited people: wrapped for each invitee's own key, in your browser
- Workspace: wrapped for each member of the team who has turned on encryption; anyone who leaves the team loses access
- Anyone with the link: the key sits in the link after the #, which browsers never send to a server
Change your mind at any time
- Switching who can view takes effect at once and never uploads the image again
- Removing someone deletes their copy of the key
- Image addresses expire within minutes, and access is checked every time a link is opened
What Screshot can and can't see
Can't see: the image, its thumbnail, or any key that opens them.
Can see, because sharing needs it: your account email and name, each screenshot's title, size, dimensions and dates, its sharing mode, the email addresses you invite, and view counts. From extension 3.0, titles start as “Screenshot” with the date and time (earlier versions used the page’s title); rename a screenshot if its title is sensitive. Titles aren’t encrypted because Screshot puts them in the emails it sends (invites, access requests, mentions and notices about a hidden screenshot) and uses them to search your screenshots.
Where our protection ends
End-to-end encryption keeps the image unreadable to us and to our storage. It does not cover everything. These are the limits, in one place.
- The code that encrypts and decrypts comes from us: the extension, which the Chrome Web Store reviews before each version, and the pages on screshot.com. You are trusting that code to do what this page says.
- Anyone with the link puts the key in the link. Anyone who gets the link, or can read the message it was sent in, can open the screenshot. For sensitive content, use Invited people or Workspace.
- We see the details sharing needs, not the image: your account, titles, sizes, dates, the sharing mode, invited emails and view counts. The full list is under "What Screshot can and can't see" on this page.
- Anyone who can open a screenshot can save it or capture their own screen. Taking access away stops new opens, not copies already made.
- If you lose every passkey and your recovery code, your shared screenshots are lost for good. Nobody can reset them, including us.
- Deleted data stays in our encrypted backups until they expire, within 31 days.
- Blur replaces the original pixels, but coarse colors stay in the image, so short text, such as a few digits, can sometimes be matched by guessing. Leave passwords, keys and card numbers out of your selection instead of blurring them.
- Full-page captures can't be blurred. Copy, Download and Share use the whole page as captured, so check it first, or capture only the area you need.
- Abuse reports: a reporter can choose to send the key with the report so moderators can review it. Without it, nobody at Screshot can.
A screenshot in the trash is erased from our database and storage after 30 days, or at once with Delete forever. Copies in our encrypted backups expire within 31 days. What we store and for how long is in our privacy policy.
Compliance
Screshot does not currently hold SOC 2 or ISO 27001 certification. Capturing and editing transmit nothing. When people share, Screshot stores their account details and the screenshots they choose to share, end-to-end encrypted, so it cannot read the content of those screenshots. If your review needs more detail, we are happy to answer your questionnaire.
Responsible disclosure
Found a security issue? Email security@screshot.com with the steps to reproduce. Please give us a reasonable time to fix it before sharing it publicly.