Privacy Policy
Last updated 25 October 2026
The short version
Your screenshots never leave your browser — SatinShot has no upload endpoint and no image storage. The only personal data we hold is what you give us when you sign in: an email address, and a display name and avatar if your provider sends them.
Your screenshots
Framing, resizing and PNG encoding all happen locally, in the browser tab. The finished ZIP is assembled on your machine and saved straight to your downloads folder. At no point are your images sent to our server, and we have no way to see them.
If you start a download while signed out, the set you were working on is kept in your browser’s own storage (IndexedDB) so it survives the trip to the sign-in page. It is removed as soon as it is restored, and in any case within an hour. It never leaves your device.
What we store about you
- Your email address. It identifies your account and is how we reach you — for example when Apple changes the required screenshot sizes, which happens most Septembers.
- Your name and avatar, if you sign in with GitHub or Google and they provide them. Shown to you, nowhere else.
- Sign-in records. Which providers you have linked, your active sessions, and the tokens those providers issue.
- Your download count. A single number, so we can apply the free-plan limit.
- Payment references, once paid plans launch: a customer and subscription id from our payment provider, and the date your access runs until. Card details never reach us — the payment provider handles them.
We do not store passwords, because SatinShot has none. You sign in with GitHub, Google, or a one-time link sent to your email.
Analytics
We measure with three tools. One needs no cookies and runs for everyone; the other two set cookies, so they load only if you accept. Until you answer, and if you decline, they are not loaded at all — not loaded and blocked, not loaded and asked for forgiveness afterwards.
- Our own Plausible instance, on our own server. It sets no cookies and collects no personal data: page views and a handful of product events (a set uploaded, an account created, a set downloaded) as anonymous counts.
- PostHog (only if you accept), on its European servers. It tells us how those counts come about — which pages and controls people use, and in what order. For this it keeps a random id in a cookie in your browser, so a second visit is not mistaken for a new person. If you are signed in, we attach your account id, name and email to that id. It also records the session: page layout, scrolling, clicks and mouse movement, so we can see where the tool gets in people’s way. Anything you type is masked before it leaves your browser, and the previews of your screenshots are not recorded. Recordings are kept for 30 days.
- Google Analytics and Google Ads (only if you accept), loaded through Google Tag Manager. We use them to tell whether advertising brings people who actually finish a set, which the other two cannot measure. When you create an account after arriving from one of our ads, we tell Google Ads that a sign-up happened — the fact alone, without your name or email. It stores cookies (_ga and _ga_…) in your browser, and the data goes to Google, who may use it for advertising measurement across the sites that use their tools. We do not send it your name, your email or your screenshots.
The screenshots you drop into SatinShot are never part of any of this, the session recording included — they stay in your browser.
Your choice
You can change it at any time, here. Declining stops those two tools from loading the next time a page opens; cookies already stored in your browser you can clear in your browser settings, as with any site.
Who else sees your data
We never sell your data. We do share analytics data with Google, as described above, to measure advertising — and with nobody else. The rest is handled only by the services that make the product work:
- GitHub and Google — only if you choose them to sign in, and only to confirm who you are.
- Resend — delivers the sign-in links and account email.
- PostHog — product analytics, hosted in the European Union.
- Google — Analytics, Ads and Tag Manager, for measuring advertising.
- Our own server, rented from Hostinger and located in Frankfurt, Germany, where the database lives.
How long we keep it
For as long as your account exists. Ask us to delete it and we remove your account row and everything attached to it — sessions, linked providers, download count. Encrypted database backups are kept for seven days, so deleted data disappears from those within a week.
Your choices
You can ask us for a copy of your data, ask us to correct it, or ask us to delete your account entirely. Write to hello@satinshot.com from your account address and we will act on it.
Changes
If this policy changes in a way that affects what we collect or who sees it, we will email account holders before it takes effect. The date at the top always reflects the current version.
Questions about any of this: hello@satinshot.com. See also our Terms of Service.