Privacy Policy

1. Controller and draft status

SaVeGe is the supplied public operator name. The legal person or business name, service address, registration/tax details where required, and support/privacy contact have not yet been supplied. These details must be completed and reviewed before commercial launch.

This draft describes the implemented data categories and the intended public ecosystem. It must be completed with the actual controller, processor arrangements, hosting locations, lawful bases and contact procedures before commercial launch.

2. Data we process

Authentication uses the identity provider’s verified account identifier, display name and permitted profile information. The service stores account records, whitelist/access decisions, license redemptions, session verifiers, expiry/revocation records and security/audit records. A session label and creation/last-seen times help you manage access; they are not an assertion that a particular physical device has been identified.

The extension stores local script source, drafts, editor selections, settings and installed-script metadata. Those local files are not automatically uploaded as part of license verification. License checks send the extension identifier and authenticated session credential over HTTPS. Community scripts cannot read extension session storage through Scorpion’s public interfaces.

Existing opt-in gameplay features may send client-observed game coordinates, room membership or cosmetic selections to the service. These are game coordinates, not geographic location. Realtime messages can reach other users in the relevant game room. Review the relevant feature settings before enabling sharing.

3. Purposes and legal bases

Account authentication, license validation and requested features are intended to support the relevant contract or requested pre-contractual steps. Security, fraud prevention and proportionate service diagnostics require a documented lawful basis and balancing assessment where applicable. Legal accounting obligations may apply when real payments begin. Optional processing requiring consent must use a real choice and permit withdrawal; no optional analytics or advertising is enabled by this website.

4. Providers and recipients

Railway is the intended infrastructure provider, Discord supplies the existing sign-in identity and Spaceship manages the domain. PayPal is an intended future payment provider and is not active. Required processor terms, subprocessors, data locations and any international transfer safeguards must be reviewed and published for the actual deployment. Merely listing a provider does not establish that every legal safeguard has been completed.

5. Security and logging

Session credentials are protected through server-side verification and restricted storage or secure HttpOnly cookies as appropriate. Logs are designed to exclude tokens, license keys, request bodies and query strings. No system is guaranteed immune from compromise. Do not post secrets in script source, console output, screenshots or a support request.

6. Retention

Local extension scripts and drafts remain until you delete them or remove extension storage; keep your own exported backups. The existing service removes expired OAuth flows and transient tickets, retains expired session records for a bounded recovery period, and uses bounded audit/security retention. Current operational cleanup uses seven days for expired sessions and 90 days for audit/security evidence. These periods and their lawful basis must be reviewed before launch; legally required records or a documented dispute hold may need different retention.

Payment/accounting retention is not configured because checkout is inactive. There is no claim that deleting local extension data automatically deletes server account records.

7. Your rights and requests

Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to relevant processing, and withdraw consent without affecting its earlier lawfulness. You may complain to the competent supervisory authority, including the Polish data-protection authority where applicable. Identity verification must be proportionate. The privacy contact and request procedure must be supplied before launch; no non-working request form is presented here.

8. Age, changes and contact

The operator must finalize eligibility and any age-related requirements before sales begin. Do not assume that a third-party game’s audience establishes the lawful age or consent requirements for this service. Material privacy changes will need a dated notice and any required further consent. The current support/privacy contact is not configured.