This policy explains what data Screshot handles in the Screshot Chrome extension (the "Extension") and on the website www.screshot.com (the "Website"). The short version: capturing, blurring, copying and downloading send no data. If you choose to share a screenshot by link, it is end-to-end encrypted on your device first: we store it, but we cannot see it. The Website uses no analytics or advertising cookies.
1. Who is responsible
The controller of the personal data described here is Huynh Cat Tuong, an individual developer based in Ho Chi Minh City, Vietnam, who builds and runs Screshot. Contact for anything about privacy: contact@screshot.com.
2. The Extension
What the Extension does not collect
The Extension does not collect, transmit or store:
- the screenshots you take, unless you choose to share one (see section 4);
- your browsing history, the pages you visit, or what you type;
- usage statistics, analytics, crash reports or device identifiers.
Screenshots are captured by Chrome and edited in a page packaged inside the Extension. When you copy or download one, it goes only to your clipboard or disk. Closing the tab discards the image. The Extension contacts the Website only when you sign in or share a screenshot, and it keeps only your sign-in on your device, in its own storage.
Permissions
The Extension requests the following Chrome permissions, and uses them only for the purpose described:
| Permission | Purpose |
|---|---|
| activeTab | 截取你面前的标签页，仅限于你点击图标或使用快捷键的那一刻。 |
| scripting | 在整页截取期间滚动你正在截取的标签页，然后将其恢复原样。 |
| contextMenus | 在 Screshot 图标的右键菜单中添加 “Capture visible area” 和 “Capture full page”。 |
| storage | 在此设备上，于扩展程序自己的存储中保持你的 Screshot 登录状态。 |
| identity | 在你选择分享时，在单独的窗口中打开 Google 登录，无需离开编辑器。 |
Pages the Extension opens
- After a manual install, the Extension opens a welcome page on the Website. It does not do this when your organization installs it by policy.
- After you uninstall it, Chrome opens a short survey page on the Website. The address includes the Extension's version number and nothing else.
These pages are part of the Website and are covered by section 3.
3. The Website
Visit counts
We use no analytics or advertising cookies. Cloudflare, which delivers the Website, counts page views for us in aggregate (Cloudflare Web Analytics): it sets no cookies and does not identify you or follow you across sites. Like any web host, Cloudflare receives your IP address and browser details to deliver each page; we don't store them. The only cookies are the ones signing in needs; see the Cookie Policy.
Your language
The Website is available in several languages. If you pick one, or dismiss the suggestion to switch, your browser remembers it (local storage); it is not sent to us. If you choose a language in Settings while signed in, we store it with your account (see section 4).
Survey answers and forms
If you answer the uninstall survey, the reason you pick and the Extension version are added to a daily total; we don't store who answered. If you send the deployment help form, we store what you enter (name, work email, company, team size, topic and message) in Sanity, the content service that runs our blog, in records that are not publicly readable. We use it only to reply and to help with your rollout, and delete it when you ask. Other contact links open your own email app with a message you can review before sending.
Emails you send us
If you email us, we receive your email address and whatever you include in the message. We use it only to reply and to help with your request, and we do not add you to marketing lists.
Former cloud sharing waitlist
We no longer collect waitlist signups. Signups made before sharing launched (an email address and, if given, company name and team size) are kept in Sanity in records that are not publicly readable, and deleted when you ask, or within 12 months after sharing launched.
4. Share by link
Sharing is optional. Nothing below applies unless you sign in and share a screenshot.
End-to-end encryption
When you share, the screenshot and a small thumbnail are encrypted in your browser with a key made for that screenshot. We receive and store only the encrypted files. The key is given only to the people you choose: wrapped for your own account key, wrapped for each person you invite, or placed in a public link after the "#", a part of the address that browsers do not send to us. Your account key is itself stored encrypted, and only your passkey or your recovery code can unlock it. We cannot open your shared screenshots, and we cannot recover them if you lose both your passkeys and your recovery code.
What we store when you share
- Your account: the email address, name and profile picture address from your Google account, and Google's identifier for it, and the language you choose in Settings, if you choose one. Sign-in uses Google only; we never see your password.
- Encryption keys: your public key, your private key in encrypted form, and for each passkey or recovery code a wrapped (encrypted) copy of the key that unlocks it. None of these lets us decrypt anything.
- Shared screenshots: the encrypted image and thumbnail, and their title, file size, dimensions, sharing mode, dates and view count. Titles start as the captured page's title, and you can rename them. We store the address of the captured page only if you turn that on in Settings.
- Invitations and requests: the email addresses you invite, who invited them, requests for access with their optional message, and, for screenshots shared with invited people, which signed-in invitees opened them.
- Workspaces and comments: the team workspaces you create or join, their name, members and roles, and pending invitations. Comments on screenshots are end-to-end encrypted like the screenshots; we store who wrote them and when, not what they say. Owners and admins of a workspace see its members, their roles and pending invitations.
- Sessions and devices: the browsers and extensions signed in to your account, with a browser and system label (such as "Chrome on Windows") and when they were last used, so you can sign them out.
- Security records: a log of actions on your screenshots (such as a change of sharing mode), and abuse reports made about them. A report can include the reporter's email if they give it, a one-way hash of their IP address, and the screenshot's key if the reporter chooses to send it so our moderators can review the content.
Data other people give us about you
If someone invites you to a screenshot or a workspace, we receive your email address from them, and we email you the invitation. If you don't have an account, we keep only the invitation, until it is withdrawn or the screenshot or workspace is deleted.
Reports and hiding
Anyone can report a shared screenshot. A screenshot reported as child sexual abuse material is hidden at once; any other screenshot is hidden automatically once three different people or devices report it. In both cases a moderator then reviews the report. We email the owner when a screenshot of theirs is hidden; they can reply to that email, or write to contact@screshot.com, if they think it is a mistake. Because screenshots are end-to-end encrypted, a moderator can see the content only if a reporter chose to send its key.
How long we keep it
- Screenshots stay until you delete them. In the trash they are erased after 30 days, or at once with Delete forever.
- Deleting your account (Settings) erases at once your screenshots, keys, sessions, the team workspaces you own, invitations and shares addressed to your email, and your email on abuse reports you filed.
- Sign-in sessions expire after 30 days. Signed-out devices are listed for 30 days, then erased; one-time sign-in codes are erased a day after use or expiry.
- Records of which invitees opened a screenshot: 90 days. Access requests: 90 days. Workspace activity log: one year.
- Abuse reports: once a moderator has closed a report, the reporter's email and any screenshot key sent with it are erased after 30 days, and the report itself after one year.
- Backups: our database is backed up continuously and every day, encrypted before it leaves the server. Daily copies of the server disk are kept for 7 days, database backups for up to 30 days. Data erased from our systems therefore remains in encrypted backups until they expire, at most 31 days later.
Emails we send
When you invite someone, we email them a link on your behalf, with your name or email and the screenshot's title. When someone asks for access to your screenshot, we email you. We also email you if a screenshot of yours is hidden after a report, and to confirm that your account was deleted. We send no marketing email.
5. Service providers
The Extension uses no service providers. The Website and sharing use these providers, which process data only on our instructions, to provide their service to us:
| Provider | What for | Where |
|---|---|---|
| Amazon Web Services | The servers that run sharing (database and API), backups of the server disk, and the emails above | Frankfurt, Germany |
| Cloudflare | Delivering the Website and the API (it receives every request, including your IP address), aggregate visit counts, and storage and delivery of the encrypted screenshots and of encrypted database backups | Global network; encrypted screenshots and database backups stored in the European Union |
| Sign-in with your Google account | Google's own policy applies to your Google account | |
| Sanity | The deployment help form and the former waitlist | Sanity's data centers |
Our email provider receives the messages you send to contact@screshot.com.
6. Why we may process it (legal bases)
- To provide the service you ask for (GDPR Art. 6(1)(b), contract): your account, sign-in, your language choice, storing and delivering the screenshots you share, invitations, comments, workspaces and the emails that go with them.
- Legitimate interests (Art. 6(1)(f)): keeping the service secure and available (sessions, device list, rate limits, the activity log, backups), handling abuse reports, answering messages and forms, and improving the product from aggregate counts that do not identify anyone. You can object to these at any time (see section 9).
- Legal obligations (Art. 6(1)(c)): acting on reports of illegal content and answering lawful requests.
We don't rely on consent for anything today. If we ever do, we will ask first and you can withdraw it at any time.
7. International transfers
The servers, database and backups are in the European Union (Frankfurt), and encrypted screenshots are stored in the European Union. Amazon Web Services, Cloudflare and Google are companies based in the United States, and Cloudflare's network delivers pages from the location nearest to you. Screshot is run from Vietnam, and the people who operate it may access these systems from there; Vietnam does not have an adequacy decision from the European Commission.
Where a transfer outside the European Economic Area takes place, we rely on the data processing terms each provider offers, which use the European Commission's Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework. Shared screenshots and comments are end-to-end encrypted before they leave your device, so no provider, and no one operating Screshot, can read them wherever they are stored or accessed from.
8. Sharing and selling
We do not sell or rent personal data, show advertising, or use your screenshots to train AI. Apart from the service providers named in this policy, we do not share data with third parties, unless the law requires us to.
9. Your rights
If you are in the European Union, the United Kingdom or another country with similar laws, you have the right to access your personal data and get a copy, to have it corrected or erased, to restrict or object to its processing, and to receive the data you gave us in a machine-readable format (portability).
If you use sharing, you can download a copy of your data and delete your account yourself in Settings on the Website. For anything else, email contact@screshot.com from the address of your account; we answer within one month. Because shared screenshots are end-to-end encrypted, we can only give you the encrypted files and their details; your own browser, with your keys, can open them.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU country where you live or work. We would appreciate the chance to address your concern first.
10. Children
Screshot is not directed at children under 13, and we do not knowingly collect personal data from them.
11. Changes to this policy
If the Extension's permissions or our data handling change, we will update this policy before releasing that change and update the date at the top of this page.
12. Contact
Questions about privacy: contact@screshot.com. For technical details, see our Security overview.