Last updated: 2026-10-12
Privacy Policy
StoreShot is an open-source screenshot tool. This policy covers this website (usestoreshot.com) — the CLI itself runs entirely on your own machine and collects nothing.
What stays on your device
On this deployment, the whole pipeline runs in your browser: screenshot uploads are read locally, analysis is deterministic (colors, dimensions, duplicates), designs are rendered in-page, and ZIPs are assembled on-device. Your screenshots, app name, and marketing copy are not uploaded to any server from this site.
The browser also keeps two kinds of local state — never transmitted:
- IndexedDB — a temporary handoff of your project when you choose “Fine-tune in the editor.” Same origin, cleared by your browser's normal storage controls.
- sessionStorage — small UI preferences (dismissed guides/hints). No cookies are set by this site.
Analytics — Plausible
We use Plausible for aggregate traffic statistics. It sets no cookies, stores no persistent identifier, and does not track you across sites. Events carry only: page paths (query strings stripped), the event name, and a small whitelist of metadata — target store, template id, output profile id, image count, elapsed-time bucket, locale id, outbound link host, and a sanitized error category.
Analytics never receives screenshot data, image URLs, filenames, app names, descriptions, text you type, or anything that identifies you. If the script is blocked or unconfigured, the site works identically and sends nothing.
Optional AI analysis
Deployments of this site may configure a vision-model API key (Anthropic or OpenAI-compatible) to analyze uploaded screenshots. On this deployment no key is configured — analysis is fully on-device and nothing leaves your browser. On a deployment where it is enabled, up to eight small thumbnails plus your optional app name/description would go to that provider's API via the site's own endpoint, subject to that provider's privacy policy; the page discloses this at the top of the generator.
Advertising — Google AdSense
An ads.txt record for Google AdSense is published on this domain in preparation for serving ads. Advertising code is currently not loaded on this site. If ads are enabled in the future, Google and its partners may use cookies or similar technologies to serve and measure ads, including personalized ads where permitted. You can control personalization via Google Ad Settings and read how Google uses information. A certified consent prompt will be presented where required (e.g. EEA/UK/Switzerland) before personalized ads are enabled.
What we never collect
- Screenshot files, thumbnails, or image URLs via analytics
- App names, descriptions, filenames, or typed copy via analytics
- Account data — there are no accounts
- Persistent identifiers, fingerprints, or cross-site tracking
- API keys, tokens, or query-string contents
We do not sell or share personal data. The only data leaving this site is the aggregate, anonymous event stream described above.
Contact & changes
Questions about this policy: the contact page lists the current channels (GitHub issues and discussions). Changes to this policy are posted here with an updated date.