Privacy
scattersparks privacy policy
Who is responsible
Pavuno LTD is responsible for the personal information it processes to operate scattersparks, its website and online services. This policy covers the full game and demo, including Android, desktop and browser versions. Features differ by edition and platform. Optional accounts are currently restricted to an invited test cohort; this policy does not announce public registration.
Local play and profiles
The game stores your chosen runner name, settings, progress, records, saved games and retained replays on your device or in browser storage. Local play does not require a scattersparks account. A local profile name is not proof of an online identity. Exporting a profile creates a file you control; it does not by itself upload that file to us. Exports can contain names and detailed gameplay, so share them carefully. Account session secrets are excluded from profile exports.
Online connections and multiplayer
Online features send requests to our servers. These connections expose your IP address and may provide client version, platform, request time, status and browser information. Live-room participation sends reservation and session identifiers, your room name or alias, readiness, game inputs and reconnect information. The server runs the match and records results and gameplay. Operational information is used to run rooms, investigate failures and prevent abuse. An alias hides your profile name from other players where supported; it does not make your network connection anonymous to us.
Accounts, sign-in and providers
If you enrol in the account test, we process your account identifier, public profile code, display name, linked provider identifiers, device labels, session metadata, security events and account choices. Passkeys use public-key credentials: we retain the public credential information needed to verify sign-in, not your passkey private key, fingerprint or face image. Your operating system or credential provider handles unlocking the passkey. Recovery codes and session credentials are sensitive; do not include them in support messages.
Where enabled, Google Play Games and Play Integrity support identity, app integrity and ownership checks. These flows can process a scoped player identifier, authorisation proof and app, device or licensing verdicts. Google handles its own account, store and payment data under Google's privacy policy. Buying through a store does not provide us with your card details. Linking a provider is distinct from associating local gameplay history. Planned Steam integration, rankings and public account registration are not described here as already available.
Replays, records and public visibility
Completed public-room games are archived on the server. Selected replays and results may appear in the website gallery or public room archive. A replay contains game actions and outcomes, not a camera or microphone recording. Public event replays currently use neutral human aliases until authenticated identity-publication controls are qualified. Your name can still be visible to participants in the live room. Local replays and profile exports may retain actual recorded names.
Local records are not automatically verified global records. Any enabled submission flow must explain what evidence is uploaded and what becomes public. Copies already downloaded by others cannot necessarily be recalled by removing our published copy. Contact us about a published replay that identifies you or contains information you want reviewed.
Storage, advertising and sharing
The current website does not use advertising or analytics trackers. Browser storage and authentication state support the game and sign-in rather than advertising. Our game services use OVHcloud hosting and operator-managed backup systems. Privacy and support email is handled through Hostinger. These service providers process the information needed to deliver their services; authorised operators may access data for support, security and maintenance. Publicly selected gameplay is shared with website visitors. External stores and sign-in providers process information under their own policies. We do not sell player information.
Why we process information
We process information necessary to provide the accounts and online play you request to deliver those services. We rely on legitimate interests in operating a secure, reliable game for operational security, abuse prevention and troubleshooting. Selected public-room gameplay is published with neutral human aliases to demonstrate the game and share match outcomes; we do not treat room participation as consent to publish an authenticated identity. Optional named publication requires the specific choice presented to you. Where the law requires records or disclosures, we process the necessary information to meet that obligation. Accepting a privacy notice is not blanket consent to unrelated processing.
Retention
Local data remains under your control, subject to the game's replay-retention limits and device or browser cleanup. The account implementation gives generated account exports a 24-hour download window or one successful download, and expires account security events after 90 days through maintenance. Account deletion has a seven-day cancellation period before finalisation. These limits do not describe all server logs, replay archives or backups.
The automated off-host account backup script retains a 35-day window when it runs. Disconnected offline recovery drives require a separate rotation and deletion process; they must not be represented as automatically erased after 35 days. Restores apply a deletion ledger to avoid reactivating deleted account data. Routine website access logs are configured for daily rotation with 14 rotated files; this is a rotation policy, not a guarantee that every entry is erased exactly 14 days after collection. Ordinary room replay files are pruned oldest-first when archive capacity limits are reached. Replays retained for an investigation or selected for the gallery are protected from ordinary pruning and require operator removal. Removing replay files does not necessarily remove room results or archive audit metadata. Offline backups persist until the operator rotates or erases the media. Minimal deletion records support deletion after a restore. Contact us to request review or erasure of data retained outside the self-service account workflow; incident evidence or legally required records may need to be retained separately.
Access, export and deletion
For local data, use the game's profile export and available deletion controls; clearing app or browser storage can remove local progress. Uninstalling the game does not delete a server account or copies of exported files. In the account centre, signed-in test users can request an account export or use Privacy to request deletion. Fresh authentication and security cooldowns can apply. The deletion workflow provides a seven-day cancellation period. For loss of account access, public replay removal or other data not covered by self-service, email privacy@pavuno.org. Include your public profile code or room/replay reference where available, never passwords, recovery codes or session secrets.
Depending on applicable law and the processing involved, you may request access, correction, erasure, restriction or portability, and withdraw consent where consent is the basis. You may object to processing based on legitimate interests. We may need proportionate verification of a request. You can complain to the UK Information Commissioner's Office or your local data-protection authority.
Younger players and changes
Local game suitability and eligibility for online accounts are separate matters. The persistent-service beta is currently limited to invited testers aged 16 or over while younger-player safeguards are reviewed. This is not a declaration that the whole game is intended only for adults. We will update this policy when data practices change and explain material changes before introducing the affected features.