Privacy Policy
Last updated: October 23, 2026
MockShot Studio (the "Service") handles user information in accordance with this policy. The Service includes the browser editor at https://mockshot.studio, the Mac app distributed on the Mac App Store, and the related product site https://learn.mockshot.studio. Where a section below applies to a specific version only, that limitation is intentional.
1. Operator
The operator of the Service can be reached at [email protected]. See the Contact page for details.
2. Editing data (screenshots and projects)
In the browser version and the Mac app, the screenshots, text, layout, and other editing content you work with are processed on your own device. We provide no upload feature for collecting or storing them on our servers. In the Mac app, projects can be saved as local .mockshot files in locations you choose.
3. Billing and credit balance (browser version only)
PNG export in the browser version runs on credits. We process and store the email address you enter in order to associate purchases and balances with you, and to restore access by magic link. There are no password-based accounts.
Payments are processed through Stripe. Card details are not stored on our servers; they are handled within Stripe's systems. The balance ledger is stored on our infrastructure (for example, Cloudflare).
We may use an email delivery provider (for example, Resend) to send magic links.
4. Mac App Store purchases (Mac app only)
In the Mac App Store build, the first three PNG export operations are free; further exports require a one-time in-app purchase (non-consumable) titled Pro — Unlimited Exports, sold through Apple via StoreKit 2.
Payment card and Apple ID details are handled entirely by Apple; we do not receive or store them. Whether you own Pro is determined on your Mac through StoreKit entitlements. We do not maintain a separate billing account for Mac app purchases.
5. In-app feedback (Mac app and browser editor)
The Mac app and the browser editor include an optional feedback form in the lower-left area of the editing UI. Nothing is sent unless you choose to submit the form.
When you submit, your message and optional display name (or "Anonymous" if left blank) are sent to our API at api.mockshot.studio, which creates a GitHub Issue in the MockShotMaker project repository. If that repository's issues are publicly visible, anyone who can view the repository can read the issue title, your message, and the metadata listed below.
Also submitted: a randomly generated installation identifier stored in the app (UUID), app version, whether you are on the Mac app or the browser, a truncated user-agent string, interface language, window size, color theme preference, the number of slides in your project, the active device preset id, and up to five recent error messages from the session (file paths and document contents are stripped and are not included).
If you attach a screenshot, it is uploaded as a private GitHub Gist; the Issue body contains only a link to that Gist. Screenshots may show your on-screen UI; attach them only if you are comfortable sharing that view with us and, when the Issue is public, with anyone who can read the repository's issues.
6. Local data on your Mac (Mac app only)
The Mac App Store app stores some data only inside Apple's sandbox for the app (your user Library application-support directory). This data is not transmitted to us.
This includes mas-export-gate.json, which records how many of the three free PNG exports you have used (integrity-protected with a local signature), and mas-iap-catalog-cache.json, which caches Pro entitlement status and StoreKit display name and price for faster startup. Pro entitlement remains authoritative through StoreKit on your device; the cache is refreshed when StoreKit data changes.
7. Analytics (browser version and product site)
To improve the Service, we may use analytics tools (for example, Google Analytics 4) on the browser editor and marketing site. Device and browser information, and events such as export actions, may be collected. The Mac app does not send analytics to us.
8. Cookies and similar technologies (browser version)
We may use cookies or similar technologies in the browser version to maintain billing sessions, verify that the site is working, store preferences (for example, keeping your theme and interface language locally), and run analytics. You can refuse or delete cookies in your browser settings, but balance restoration and some features may then be unavailable.
9. International data transfers
Where the third-party providers we use for browser payments, email, analytics, in-app feedback (GitHub), and Mac App Store billing (Apple) operate servers outside your country, the related data may be processed outside it. Please also review each provider's own policy.
10. Contact
For questions about this policy, contact [email protected].
11. Revisions
We revise this policy as needed. When there is a material change, we will update the date shown on this page.