Editing files
The hosted browser builds execute on your device. Opening a local file in an editor does not upload it to this site's Go backend. Unsaved changes can disappear when a tab closes, so save or export a copy. Browser caches and application storage can retain app data locally; manage those through your browser.
An upstream app may offer optional sharing, network resources, or collaboration. If you enable those features, their behavior and destination are determined by that app and your choices. We do not operate a collaboration service.
Normal web requests
Serving a page requires the server and network infrastructure to receive connection information such as an IP address. This application does not store IP addresses, user agents, file names, or document content in SQLite. Hosting infrastructure may keep its own operational logs according to the server owner's configuration.
Optional usage counts
Anonymous first-party launch counting is disabled by default. When the server owner enables it, launching an editor sends only the app identifier and a launch_requested event. SQLite stores an aggregate count per app per UTC day, without cookies, user identifiers, or per-visitor histories. Counts older than 90 days are removed when new counts are written. A launch count does not prove a successful edit.
Optional Google sign-in
If you choose Sign in with Google, Google authenticates you and provides your stable Google account identifier, verified email address and display name. We store those details, account creation and update times, and a hashed website session token in SQLite on our Europe server to operate your account. We do not request Gmail, Google Drive, contacts or offline access, and do not store Google access or refresh tokens. Signing in does not create a cloud backup of your editing files.
An essential, host-only, secure HTTP-only session cookie keeps you signed in for up to 30 days. A separate essential sign-in cookie and server-side request record expire after 10 minutes. Expired records are removed when authentication is used or the service restarts. No sign-in cookie is set merely by reading public pages. These cookies are used for authentication, not advertising or tracking.
Your account profile remains until you delete it on the account page. Deletion immediately removes the live profile and its website sessions; you can sign out this device or all devices without deleting the account. Recovery backups can contain earlier records and are restricted to server administrators. Contact support for privacy or backup-related requests. You can also remove this app's connection in your Google account settings; that does not by itself remove the profile already stored here.
Support email
When you email support@opensourcephotoeditor.org, the message, sender details and any attachments are processed in our Microsoft 365 shared mailbox so the website operator can respond. Please send only information necessary for the request. We keep correspondence while it is needed to resolve and follow up on the request; contact the same address to request deletion, subject to applicable recordkeeping obligations.
External links and settings
Website images, fonts, styles, scripts and installed editor bundles are served locally. The site includes no Google Analytics, Clarity, advertising tags or third-party embeds. Following an external source link takes you to that site's privacy practices. Theme choice is kept only in this tab's memory; no tracking cookie is used.