Privacy policy

Last updated on October 14, 2026

The editor saves projects on your device and renders exports locally. You can use the core editor without an account. Optional features send data off your device: cloud storage, saving to your own Google Drive or GitHub, community posts, live collaboration, store uploads, translation, and cloud AI. Cloud auto save is on by default when you are signed in and cloud storage is available.

Who we are

Open Screenshot Generator is a free project with its source code public on GitHub. This policy covers openscrgen.app, editor.openscrgen.app, the desktop app, and the project's cloud and community services. For privacy questions, email pak437337@live.com.

What the editor stores, and where

• Projects, imported screenshots, recordings, sounds, and fonts are saved in the editor's local database on your device.
• PNG and MP4 exports are rendered on your device and saved to your disk.
• Preferences and connected account sessions are kept in local browser or app storage. Account access and refresh tokens can remain there across restarts.
• AI API keys are kept in memory unless you choose to remember them. Remembered API keys and store upload credentials are saved locally without encryption.
• Clearing the editor's local data removes local projects and settings. Cloud copies, public posts, and files saved to your own accounts must be removed separately.

Accounts and cloud storage

Connecting Google or GitHub is optional. When the cloud or community service is available, the editor can use that connection to sign you in to our service. Your provider access token is sent to our backend for verification. The backend stores an account identifier, email address, display name, handle, and, when available, profile picture. We use this information to authenticate your account, associate saved content with you, and show your community profile.

When you are signed in, cloud auto save is on by default. It uploads the open project's content and referenced media and fonts to our service, including screenshots, recordings, sound files, and text. You can turn cloud auto save off in Settings. Turning the setting off or signing out stops future automatic saves; existing cloud copies remain until you delete them.

Cloud projects are private unless you enable link sharing. A shared link lets anyone who has the link access the project and its assets. Turning sharing off stops access through that link, but does not remove copies that someone has already saved.

Saving to your own accounts and app stores

You can save projects to your own Google Drive or GitHub gists. Those saves send project content, media, and fonts directly to the provider. Automatic sync to your own storage is off by default and only updates projects that you previously saved there or opened from that account. Provider permissions and privacy policies apply.

Desktop store upload features send the screenshots or preview videos you select directly to App Store Connect or Google Play using your store credentials. Our cloud service does not receive those credentials or handle those store uploads.

Community posts and live collaboration

Publishing to Discover uploads the exported images, title, caption, tags, and related project information you choose to share. Posts and comments are public and associated with your profile. The service also stores likes, saved posts, and follows associated with your account. Discover searches send your search text to the service.

Live collaboration shares project changes and participant information with the people in your session. Referenced media comes from the shared cloud project. A signalling service introduces participants, and WebRTC connections carry live changes between them, using a relay when needed. These connections expose network information such as IP addresses to the services involved and, during direct connections, to other participants. Keep collaboration invitations private.

AI and translation

AI features run when you ask them to. Cloud AI requests send your instructions, attached screenshots, and relevant editor or chat context directly to the provider you choose. Providers can retain this information according to their policies and your account settings.

• API requests go to the provider or endpoint you select, such as Anthropic, OpenAI, Google, OpenRouter, or a compatible service.
• AI modes that use a provider's website use your session with that provider. Its cookies, account settings, and privacy policy apply inside the provider window. These sites can collect account and device identifiers, approximate location, page visits, interactions, advertising activity, and technical diagnostics.
• Desktop Claude Code and Codex agents use your installed agent and its provider login. Claude Code can read source files in code folders you explicitly attach, and that source can become part of the context sent to Anthropic.
• Local AI endpoints, such as Ollama or LM Studio on this device, process requests locally. A remote endpoint you configure sends requests to that remote service.
• If you connect an external AI client through MCP, that client can receive project content through the tools you use. The client's own data handling applies.

When server translation is available and you use it, artboard text is sent to the configured translation service. AI translation sends text to the AI provider you select.

Some AI provider sites use data for advertising and can combine activity with data from other services. OpenAI describes advertising partner use of identifiers, hashed email, and interaction or browsing information. Microsoft describes Copilot advertising that can use conversation history, shared files, and location. Provider settings can affect advertising, personalization, and model training. Review the OpenAI marketing practices and Microsoft privacy statement before choosing these services.

Website analytics, advertising, and network services

The marketing website and web editor load Google Analytics. Analytics records page views and interaction events, such as opening the editor, choosing a template, importing screenshots, and exporting. The editor's custom events describe the action, format, or count rather than sending project content or imported file names. Google Analytics can use cookies and browser identifiers and receives technical information about the connection.

The web editor also loads Google AdSense. Google's advertising services can use cookies, identifiers, and technical information. Google's policies and advertising settings govern that processing. These Analytics and AdSense scripts are disabled in the desktop editor.

• The marketing website is hosted by Vercel and the web editor by GitHub Pages. Hosting services can keep request logs, including IP addresses. See the Vercel privacy policy and GitHub privacy statement.
• Our cloud, community, and relay infrastructure keeps technical request logs for operation and troubleshooting. Logs can include IP addresses, requested URLs, search query parameters, status codes, and request times.
• Loading Google Fonts sends font requests to Google. Google also provides public STUN servers used to establish collaboration connections. See the Google privacy policy.
• Some website libraries load from jsDelivr. See the jsDelivr privacy policy.

The desktop app

The desktop app stores projects locally and does not load the editor's Google Analytics or AdSense scripts. Optional cloud, community, collaboration, AI, translation, and store features still use the network as described above. Font loading and checks for configured services can also make network requests. Provider websites opened inside AI windows can run their own scripts and use cookies.

Retention and deletion

Local data remains on your device until you remove it or clear the editor's data. Our service stores cloud account data and content to provide the features described here. You can delete individual cloud projects and your own community posts in the app. To request deletion of your cloud or community account and associated content, email pak437337@live.com with the provider and account you used. We may need information to verify that the account is yours.

Signing out does not delete cloud content. Removing local data does not remove files from Google Drive, GitHub, an AI provider, or an app store. Manage those copies with the relevant provider. Technical logs and backups can have separate retention periods; contact us for details about retention and deletion requests.

Children

If you believe a child has provided personal data through our cloud, community, or support services, email pak437337@live.com so we can investigate and handle a deletion request.

Changes to this policy

When this policy changes, we update the date at the top of this page.

Contact

For privacy questions, access or deletion requests, and support, email pak437337@live.com or visit the support page. Avoid posting private account or project information in public GitHub issues.