Welcome to AppScreenshots's Privacy Policy. This document explains how we collect, use, and protect your personal information when you use our App Screenshot Editor and related services.
We may collect the following types of information:
- Account Information: Name, email address, and contact details you provide when registering or contacting us.
- Usage Data: Information about how you interact with our website, including pages visited, features used, and time spent.
- Project Data: Screenshots, images, and design projects you create and save in our editor. This data is stored to enable project persistence across sessions.
- Uploaded Assets: Screenshots and images you upload for editing. These may be stored temporarily during your session or permanently if you save a project.
We use your information for the following purposes:
- To provide and maintain our screenshot editing services (device mockups, templates, batch export, icon generation).
- To save and sync your projects across devices.
- To notify you about changes to our services.
- To provide customer support.
- To gather analysis or valuable information to improve our services.
- Project Data: Your saved projects are stored securely and retained as long as your account is active.
- Temporary Uploads: Images uploaded but not saved to a project may be deleted after your session ends.
- Account Deletion: You may request deletion of your account and all associated data at any time.
When you explicitly use AI store-copy generation in Store Publishing, we send the product name and description you provide, usable current listing text, text extracted from mapped screenshot projects, any previous structured product brief, selected stores and locales, requested fields, and the current values of those fields to the configured AI model provider. The provider first infers a structured product brief and then generates copy drafts. App identifiers, account credentials, support/marketing/privacy URLs, screenshot files, and store-login sessions are not included in this copy-generation request.
The structured product brief may be placed in your unsaved publishing draft and is saved with the profile only when you choose Save profile; the raw supporting screenshot/listing text is not added to the publishing package. AI workflow records retain the generation scope, structured message plan, and copy results for quota accounting, idempotent retries, and failure recovery. AI results are not automatically saved to the publishing profile or sent to Apple or Google. Content can enter the store workflow only after you review fields, apply them to the draft, save the profile, and separately start store synchronization. AI output may be inaccurate and does not replace human review of product facts, language quality, or store policies.
The following describes version 0.1.1, verified in Chrome Web Store on September 17, 2026. The candidate update's additional data flows are described separately below.
You can authorize your AppScreenshots account to share your display name and publishing-profile summaries with the extension, then select a profile to retrieve its listing text and rendered screenshots. Passwords and login cookies remain on the website. A connection is bound to one website tab and a random ID retained in trusted browser-session storage. Disconnecting cancels retrieval; previously retrieved packages remain in local storage until you delete them.
AppScreenshots Store Sync processes publishing metadata and screenshot files locally in your browser profile so that you can review and save listing drafts in App Store Connect and Google Play Console. Google API supports preflight and confirmed listing writes. Commit may trigger review or publishing.
- Data handled: App identifiers, editable versions, locale mappings, listing text, screenshot files, local task checkpoints, error messages, and Google service-account or App Store Connect API credentials that you explicitly provide.
- Local storage: Imported publishing packages and screenshots are stored in extension IndexedDB. Task history is stored in extension local storage. API credentials are saved persistently in local extension storage restricted to trusted extension contexts, without application-level encryption or a separate password. They are not synced to other devices. Their protection depends on the security of this device and browser profile; use only on trusted devices. Users can replace or permanently delete credentials in the side panel. Legacy encrypted records require one-time key reimport.
- Retention: Completed and failed task records are retained for up to 30 days and paused task records for up to 7 days. Transfer chunks are removed immediately after a successful commit or abort. Abandoned website-transfer sessions become eligible for pruning after 24 hours and are removed on the next extension activation.
- Network behavior: The extension has no separate backend. It accepts nonce-bound packages only from
https://appscreenshots.net. Through the official APIs, credentials are used locally to generate short-lived Apple JWTs or Google OAuth tokens; Apple listing data and screenshots are sent directly to Apple APIs and Apple-provided time-limited signed upload URLs, while Google API access supports preflight and confirmed listing writes. Confirmed Apple API uploads run in a static, bundled Chrome offscreen document so they are not interrupted by the Manifest V3 service-worker lifetime; the task-only in-memory credential copy is discarded when that worker closes.
- Credentials and analytics: The extension never transmits store credentials to AppScreenshots, sells extension data, runs extension analytics, or loads remote executable code. Necessary data is disclosed to Apple or Google only when you select that store and start preflight or confirm a draft save, and is governed by that service's terms and privacy policy.
- Store safety: The extension verifies app identity, editable state, differences, screenshot counts, and local assets; replacing existing screenshots requires explicit confirmation. Google listing writes require confirmation because commit may trigger review or publishing; existing reviews are protected with ERROR_IF_IN_REVIEW. Apple saves drafts without review submission. Google commit may trigger review or publishing.
- Limited use: Extension data is used only to import, compare, and save the store-listing drafts you request. It is not used for advertising, profiling, credit decisions, or unrelated purposes. Its use complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
When the 0.3.0 update is released, it adds the following behavior. A local candidate build is not evidence that the update is available in the store.
- AppScreenshots checks account entitlements and authorizes sync tasks. The service stores account/task identifiers, profile reference, platform, target/material digests, operation scope, plan at authorization, status and timestamps. These reports do not contain store private keys, screenshot files or full listing text.
- A separate local billing/recovery ledger preserves authorizations and pending results across restarts. A periodic alarm retries first-party result reports even if the authorization page is closed. Reporting tokens are restricted to one task and revision, expire after seven days and require the original account to renew. They cannot log in or start another task.
- The billing/recovery ledger is distinct from the 30-day/7-day local task-history limits above. Local ledger records remain until extension/browser data is cleared; server trial and task records remain with the account and are removed on account deletion. Disconnecting or deleting a package does not reset the trial allowance.
- Fixed connection, preflight and upgrade events can be forwarded to the connected website's configured analytics. The extension event payload contains an event name, source and optional platform, not credentials, screenshots, listing text or raw errors. Website analytics may associate events with its existing identifiers.
- Huawei support uses developer-level Service Account or API-client credentials locally for native HarmonyOS listing operations. Necessary listing materials are sent directly to Huawei Connect API and authorized upload hosts. Android AppGallery publishing is not included.
- Store credentials continue to remain local and are not sent to AppScreenshots. No remote executable code is loaded. These data flows support the requested workflow, entitlements, recovery and limited usage measurement, not advertising, credit decisions or unrelated profiling.
We implement appropriate security measures to protect your personal information from unauthorized access, alteration, disclosure, or destruction.
We may employ third-party companies and individuals to facilitate our services (e.g. Analytics, Payment Processing, Cloud Storage), provide services on our behalf, or assist us in analyzing how our services are used.
The Store Sync sections above distinguish the published 0.1.1 behavior from the 0.3.0 update's first-party task service and connected-website analytics. Store credentials are not transmitted to AppScreenshots in either version. Necessary listing materials are sent to the selected supported store for the requested operation.
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
If you have any questions about this Privacy Policy, please contact us.