Privacy policy

1. About this policy

SDEditor is a community tool for translating Path of Exile StatDescriptions files. This policy covers the editor at sdeditor.pages.dev and its cloud service at sdeditor-api.poemaid.com. The SDEditor project maintainer operates the service and can be contacted at lpeachl@gmail.com.

2. Data stored in your browser

The editor uses browser storage, including IndexedDB, to save preferences, dictionaries, imported archives, translated workspaces, clipboard content, and revision history. Imported archives, translated workspaces, clipboard content, and revision history are not uploaded by the cloud backup feature.

Local storage also holds synchronization state, pending changes, conflicts, recovery copies, and your SDEditor session when signed in. Temporary browser session storage helps complete Google sign-in. You can use local editing without a Google account.

3. Google sign-in and account information

When you choose Backup using Google account, Google authenticates you and supplies your Google account identifier, verified email address, and display name. SDEditor stores these details to recognize your account, display your identity, and let an administrator manage your language assignment. We also store your role, assigned language, and account creation and sign-in times.

We request only the openid, email, and profile permissions. SDEditor does not receive your Google password or request access to your Gmail messages, Google Drive files, contacts, or calendar. Google tokens are used to complete sign-in and are not retained in the SDEditor database; the editor uses its own session afterward.

SDEditor uses Google user data only to provide and secure these account features. We do not sell Google user data, use it for advertising, or use it to train AI models. Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

4. Cloud backups and shared dictionaries

Cloud synchronization starts after an administrator assigns your account a language. It backs up your editor preferences and personal regex rules to the SDEditor API. These settings are associated with your account and are not shared with other translators.

Dictionary entries for your assigned language, including Find/Replace text, alternates, and complete TL notes, are shared with other translators assigned that language. They can read, edit, and export that dictionary. The same language dictionary is used for PoE1 and PoE2. Dictionaries for other selected languages remain local.

Synchronization records include revisions, deletion markers, and change identifiers to merge edits and handle retries. Avoid putting private or sensitive information in dictionary entries or notes: other translators can retain their own copies.

5. Who can access data

The service operator can access server-stored data to run, maintain, secure, and support SDEditor. Administrators can view account identities and language assignments. Other translators receive the shared dictionary for their assigned language; they do not receive your Google account details or personal settings through dictionary synchronization.

Google handles sign-in. Cloudflare delivers the public website and the API connection. The editor loads libraries and fonts from providers including cdnjs, jsDelivr, and Google Fonts. These providers receive normal connection information, such as an IP address and browser request headers, when your browser connects to them. Their processing is governed by their own policies, including Google's Privacy Policy and Cloudflare's Privacy Policy.

The SDEditor application does not include advertising or analytics trackers. Hosting and network services may process operational logs for delivery, reliability, and security. We do not sell your personal data. Data may also be disclosed when required by applicable law.

6. Storage, security, and retention

Cloud data is stored on the SDEditor API server and may be included in operational backups. Public connections use HTTPS. Session credentials are stored in your browser, with only a hash retained on the server. The server also keeps administrative language-assignment audit records and synchronization metadata.

Your SDEditor session expires after 30 days without authenticated activity. Visits and active use renew it; background read polling alone does not. Session expiry does not delete your account, cloud settings, shared dictionary, or local work.

Local data remains until you remove it, clear site data, or your browser removes it. Account records, cloud settings, shared dictionaries, audit records, and backups do not currently have an automatic age-based deletion schedule. Backups may retain earlier copies until the operator removes them. No storage or transmission system can guarantee absolute security.

7. Your choices and deletion requests

• Stop cloud synchronization: sign out in Settings. Signing out keeps saved local profiles and does not delete existing cloud data.
• Remove the Google connection: manage SDEditor in your Google Account connections. Also sign out of SDEditor to end its separate session; removing the Google connection does not itself delete SDEditor data.
• Keep a copy: export settings and dictionaries from Settings, and export your translated files separately.
• Remove browser data: use your browser's site-data controls. Export anything you need first. Clearing browser data does not delete cloud backups or copies held by other translators.
• Request access, correction, or deletion: email lpeachl@gmail.com. Tell us which account and data your request concerns. We may need to verify account ownership; never send passwords or session tokens.

Account and cloud-data deletion requests are handled manually by the maintainer; there is no automatic account-deletion button. Shared dictionary contributions and copies already exported by other translators are separate from your personal account. If a request concerns personal information in a dictionary, identify the affected entry so it can be reviewed. We will explain any limits involving shared copies, backups, or records that must be retained by law.

8. Changes and contact

We may update this policy when SDEditor's features or data practices change. The current policy and its update date will remain available on this page.

For privacy questions or requests, contact the SDEditor maintainer at lpeachl@gmail.com.