ss-captureTrust, Google, and the law
Written so users, school and company IT, Google’s app review, and Indian authorities can see the same facts.
The problem many people hit
A lot of people and organisations use a Google Workspace / school / company account. They need to capture a screen, keep the file in their own Drive, and send a normal shareable link. Third-party hosts are often blocked, extra logins are banned, or IT will not allow “another company’s cloud.” Personal Gmail may be blocked on the same machine.
ss-capture is built for that case: after you save, if Drive is connected, the image or video is stored in your Google account and a link is generated from that account. We are not the host of that file.
What happens after Save
- Always: the file is written on your PC first (local).
- If Google Drive is on: the same file is uploaded to your Drive folder. The share/copy link is your Drive (or local) URL. Personal, school, and organisation accounts all stay under Google’s controls and your admin’s rules.
- If only Local is on: a local link can still be copied on your machine. Nothing is sent to us.
- Cutcompress: not available yet. The button in Settings says Coming soon.
What we can and cannot see
| What you connect | Do we receive the image or video? | What we may hold |
|---|---|---|
| Nothing (Local only) | No | Nothing from your captures |
| Google Drive (personal, school, or work) | No. The file stays in your Google account. We cannot browse your Drive from our servers. | We do not store the media. Sign-in tokens stay on your PC. |
| Cutcompress storage (coming later, opt-in) | Yes, only if you turn it on in a future build. | The file you uploaded, plus size, count, and type (image vs video) so we can plan disks. We will not publish or sell the content. |
For Google app verification
ss-capture requests Google access only to upload a file the user just captured into a folder the user owns, and to produce a link the user can copy. That is the limited, user-visible purpose.
- We do not read a user’s email, contacts, or unrelated Drive files.
- We do not use Drive data for ads.
- We do not transfer Drive file contents to our servers.
- The user can disconnect in Settings. They can also revoke the app in their Google Account security page.
- This site’s Privacy policy is the public disclosure for that access.
When we apply for Google verification / marketplace listing, reviewers can use this page and the privacy policy as the official description.
For government and cyber-crime authorities
ss-capture is a lawful desktop utility for capturing your own screen. We do not operate a hidden upload path. We do not intercept other people’s devices. We do not run a public gallery of user screenshots.
- Content on the user’s disk or in the user’s Google Drive is controlled by that user (and, for Workspace, their organisation and Google).
- We cannot produce another person’s Drive files because we do not host them.
- If Cutcompress storage is launched and a user has opted in, we will respond to a valid legal process under Indian law for data we actually hold. We will not volunteer private screen contents for marketing or to third parties.
- Users must not use the app to capture or share data they have no right to record. That remains the user’s responsibility.
When Cutcompress storage actually ships
It is not on today. Do not worry about it for the current installer.
When we switch it on we will:
- Update this page, the Privacy policy, and the Terms first.
- Publish a new desktop build.
- Ask you to download that build and reinstall if you want the new storage option.
- Show the new policy in the app so you can read it before connecting.
Old builds will not silently start uploading to us.