ORVASKPlay the game →

Privacy notice

Effective version: 1.2 · 18 October 2026. Operator: Stanislav Dian, Ireland. Contact: stanmastr@gmail.com.

What we collect and why

Guest play uses a random guest identity and a device save. When you choose Google sign-in, we receive your Google account's stable identifier, verified email and an identity token. We use the identifier to recognize your account and the email for account administration. We do not request your contacts, files, Google password or access to other Google services. Login tokens are not retained as Google API credentials. For new registrations, your verified Google identifier and email are held in a temporary, session-bound registration record. It expires after 15 minutes and is removed by routine cleanup, or removed immediately when registration is completed or cancelled. No account or guest-progress claim is created before a valid username is confirmed.

We store your username, campaign progress, unfinished puzzle, accepted level completions, completion dates, streaks, session records and account preferences. This delivers the game and account service you request. Security rate limits, short-lived country estimates, moderation records and service logs protect the service and help operate it.

Your connection sends an IP address to the server. We use it transiently for abuse protection and approximate country lookup on the server. Country lookup does not ask for GPS access. Country estimates may be wrong, especially with VPNs. Online presence and country are visible only to the operator, not other players. Online means a visible page with recent input and a heartbeat within 90 seconds; it is not an exact count of human beings.

What is public

If you sign in, choose a username and appear in the player table, other people can see that username, participation count and position, current Living Worlds level and verified daily streak. Your email, country and Google identifier are not public. You can hide your entry in Menu → Account. Imported personal history is excluded from participation totals.

Device storage and cookies

StoragePurposeDuration
__Host-orvask cookieEssential secure login or guest session. HttpOnly, Secure, SameSite=Lax.Up to 30 days for accounts or 180 days for guests; renewed when you reconnect
orvask.data.*, orvask.owner; original wayfarer-campaign-* savesPuzzle state, pending completions, account separation and migrationUntil you clear browser storage; account copies can remain after sign-out
orvask.guest-recovery.*Private bearer key that reconnects the same unclaimed guest after cookie loss; never included in device exports. Invalidated when claimed by an account.Up to 180 days without renewal on the server; local copy until claimed, cleared or replaced
orvask-audio-v2, orvask-motion, orvask-welcome, orvask.migrated and campaign preference keysSound, accessibility, tutorial and progress preferencesUntil you clear browser storage
orvask-offline-* service worker cacheReconnect screen and its stylesheet for the installed app; no account responses or gameplay savesUntil replaced by an updated worker or browser data is cleared
orvask.reload session storagePrevent repeated automatic reloadsUntil the tab session ends

This release uses essential storage and player-requested preferences. It does not install advertising trackers or optional analytics. There is no optional analytics consent banner because those technologies are not included. Google processes your visit to its sign-in page under its own privacy policy when you choose to sign in.

Recipients and hosting

The game is hosted on the operator's Hetzner server. Google provides authentication. Network providers and certificate infrastructure help deliver HTTPS. Backups and support correspondence remain under the operator's control; contact us for details of any separately configured backup provider. We do not sell player data.

Retention

Account progress remains until you delete the account or request deletion. Guest records with no activity are removed after 180 days. Account sessions expire after 30 days and guest sessions after 180 days, OAuth state after 10 minutes, unfinished registration authorization after 15 minutes (expired records removed at routine cleanup), runs after their validation window and routine cleanup, presence after 90 seconds, and rate-limit records within their configured window (at most one hour). Web access logs retain seven days, application logs up to 14 days, and moderation audit records 90 days. Daily backups have a 30-day retention target. A separate daily job expires backups older than 29 days and prunes remote data, even if creating a new backup fails. Operational failures can delay deletion; failed expiration is monitored and must be resolved. The operator must align backup-provider versioning and retention settings with this schedule.

Minimal random guest claim identifiers and deletion IDs/timestamps used to prevent restored backups from undoing known deletions are retained after account deletion to prevent the same guest entitlement being claimed again. They contain no Google email or Google identifier; guest claim records no longer link to the deleted account. Account deletion removes the live account and revokes its sessions and guest recovery authorization. Previously exported files and browser-local copies are separate; clear those if you no longer want them. Backup copies expire through the retention schedule.

Your choices and rights

Use Menu → Account to download your account data, hide your participation entry or delete your account. Deletion requires a recent Google sign-in. Use Settings to export a device save. You can also contact stanmastr@gmail.com to request access, correction, deletion or other applicable privacy rights. If data-protection law applies in your location, you may have rights to object, restrict processing, receive portable data and complain to the relevant supervisory authority. We may need to verify account ownership before acting on a request.

Young players

Account registration in this release is for people aged 16 or older. We do not ask for dates of birth or intentionally market account features to younger children. Contact us if a child has supplied personal information so we can address it.

Changes

Material privacy changes will be published here with a new effective version. Adding optional analytics, advertising or new data uses requires a separate review and any legally required consent before those uses begin.