Your trail, and the records it leaves.
How Orestride handles the records needed to run your expedition.
Paul has reviewed this version. Provider, support delivery, and backup status below describe the recorded operating setup.
Who is responsible
Paul Harman, operating in Sweden, is responsible for the personal data processed for Orestride at orestride.com. Service address: support@orestride.com. The contact page provides the support address for help and privacy requests. The service is intended for adults 18+.
Data and purposes
We store your chosen alias, an internal player identifier, game inventory and progress, records that prevent duplicate actions, expedition objectives and results, standings, recovery-code hashes, and session records. These run and save the game, prevent conflicting actions, and restore access. Choose an alias that does not identify you.
A wallet is optional. If you link one, we store its public address, short-lived login challenges and evidence needed to confirm the signed login. We do not request or hold your seed phrase or private signing key. A message signature authenticates your account; it is not a token transfer.
If a payment or reward feature is enabled in a separately validated configuration, we store immutable order references, exact token quantities, public transaction signatures, delivery and ledger records, eligibility decisions, and claims. Review requests store the text you submit and the related account, purchase, or daily reward reference. They support delivery, dispute handling, accounting, and abuse investigation. Do not include sensitive personal details.
The native game keeps a bounded operational audit and temporary abuse-control counters. An incoming connection exposes an IP address and ordinary HTTP information to the server and any active network provider. The native application limits aggregate account creation and API use, with additional per-player limits. The application does not use an IP address as proof of account ownership. Native operator audit records identify relevant account operations; they are private. No advertising trackers, third-party analytics SDKs, or nonessential tracking cookies are included.
Lawful bases
Running the game you request, maintaining its save, and handling account recovery rely on providing that service under the terms. Service integrity, proportionate anti-abuse checks, diagnostics, and resolving disputes rely on legitimate interests in protecting players and the service. Where a specific law requires financial records, the applicable records would be retained to meet that obligation. No optional marketing processing is planned.
Cookies and browser storage
An opaque HttpOnly session cookie is necessary to reconnect this browser to its server save. Hosted cookies use Secure and SameSite=Strict. Access renews at most daily while playing and expires after about 30 days of inactivity. Logout deletes the current server session and clears its cookie. Expiring or clearing the cookie does not delete the save. Native maintenance removes expired sessions and wallet challenges. Its hosted schedule still requires verification; an outage can delay cleanup.
| Storage | Purpose | Duration |
|---|---|---|
Session cookiecrypto_game_session locally; separate hosted session names | Opaque authenticated session, never exposed to page JavaScript | About 30 days of inactivity, or logout/recovery rotation |
| Wallet recovery context cookie | Short-lived HttpOnly context for a requested wallet recovery; it is not permission to access a save | Expires with the login challenge or is cleared after verification |
orestride-phantom-login IndexedDB | Pending Phantom connection: temporary encryption key, intended save and login message, kept in this browser to verify an encrypted return | Accepted for at most five minutes. Consumed callbacks remove the record; unused expired records are removed on a later connection or when you clear site storage |
orestride-phantom-purchases IndexedDB | Requested mobile purchase handoff: temporary encryption key, intended wallet/save, immutable order and prepared transaction, used to authenticate a signed return | Accepted for at most five minutes or the original order expiry, whichever is sooner. Consumed or cancelled callbacks remove the record; unused expired records are removed on a later purchase connection or when site storage is cleared |
crypto-game:settings | Chosen sound, reduced motion, and frame-rate preferences | Until you clear browser site storage |
crypto-game:checkout:*crypto-game:order:*crypto-game:order-attempt:* | Public order references, submission status and signatures used to resume the same payment | Completion clears active checkout markers; public receipt references may remain until site storage is cleared |
The game never stores your wallet seed phrase or wallet signing key. Phantom handoff temporarily stores a separate browser-generated encryption key in IndexedDB; it cannot spend wallet funds. The opaque game session stays in an HttpOnly cookie. Payment reference storage is used only when a separately enabled payment flow is requested. You can clear these records using your browser’s site-data controls; keep a recovery method first. These storage operations support the service or preference you request.
Providers, regions, and public networks
Cloudflare is the confirmed domain registrar for orestride.com. The prepared native game uses Cloudflare Workers and SQLite-backed Durable Objects for authoritative player records. Cloudflare operates a global network; this configuration does not guarantee that processing or storage stays in Sweden or another specific country. Recorded hosting: Cloudflare, Cloudflare global network; a single native SQLite Durable Object stores the game. Cloudflare forwards support@orestride.com to the operator’s private inbox. A populated private hosted restore passed with disposable accounts on 6 September 2026. It is historical recovery evidence, not proof that production backup schedules or the new financial format are running.
GitHub hosts the private source repository and verification and release automation. Player records, database exports, wallet files and credentials are excluded from source control and public review archives. The deletion workflow retains signed, encrypted deletion intents in a separate private GitHub draft release before removing a save. Financial allocation recovery uses separately encrypted leaf lists, proofs, original accounting and funding intent, retained independently before irreversible commitments. This recovery storage is outside source control and public review archives. The private hosted recovery rehearsal also verified independent deletion readback and suppression of a later-deleted account. Production schedules and the new financial format require their own verification. Wallet providers receive the requests you initiate under their own privacy practices. If an enabled blockchain transaction is submitted, its wallet addresses and transaction details become public on that network and cannot be deleted by Orestride. Opening the official X profile or a verified external token page sends a request to that external service; neither is embedded as a tracker.
Retention and backups
Saves remain on the server after a session expires, so a valid recovery method can restore them. The initial implementation preserves saves while the service is used and until a verified deletion request is processed; inactivity alone does not trigger deletion. Native action replies are compacted to a bounded recent set, while a consumed-action counter is retained with the save so older actions cannot execute again. At most ten recent practice records are kept per player. Maintenance removes resolved review requests after 90 days; pending reviews remain until resolved or the account is deleted. The operational audit keeps its latest 1,000 entries. Deletion requires Paul to verify control of the account and run the authenticated deletion operation. It removes the ordinary save and associated session, practice, review and recent action records; it is not an automatic button. Finalized purchases, unpaid allocations, disputes and the evidence needed to settle them are retained separately, so deleting a save does not cancel an obligation. Requests can be sent to support@orestride.com. A separate deletion ledger permanently retains the internal player identifier, deletion operation identifier and time to prevent an older backup from restoring a deleted account. This limited security retention and the request procedure require owner review. Records needed for an unresolved dispute, undelivered finalized purchase, security investigation, or a specific legal duty may require limited retention; the reason and relevant scope should be explained when handling the request.
Cloudflare offers provider recovery for SQLite Durable Objects. A disposable populated hosted rehearsal passed mining, recovery, an encrypted separate-store restore and suppression of a later deletion; both test stores were removed. This is not a live production backup schedule. The current export format streams authenticated encrypted chunks from one consistent frozen snapshot, including financial state. The intended production jobs make a private encrypted backup daily at 03:17 UTC with seven-day artifact retention, monitor backup age daily at 04:47 UTC with a 36-hour alert threshold, and verify a separate populated restore on Sundays at 05:17 UTC. Actual enabled schedules, deliveries and retention must be verified in the operating report; an outage may delay a job. Seven-day operational rotation never applies to independent deletion or unpaid-allocation evidence. Restores apply the newest independently retained deletion ledger and reconcile permanent chain receipts before money operations resume. Account deletion does not instantly remove older provider recovery points.
Financial records and unsettled obligations
Orders, finalized payment evidence, funding lots, daily rules and eligibility snapshots, allocations, disputes and delivery checkpoints are retained separately from ordinary saves. Unpaid or disputed entitlements and the encrypted leaf/proof records needed to recover them remain available until resolved; no timer or minimum delivery threshold forfeits them. Pausing payments or deleting a save does not release their reserved funding. Permanent public chain receipts cannot be erased by the game.
For settled records that constitute Swedish bookkeeping information, the retention period is through the end of the seventh year after the calendar year in which the relevant financial year ended. The declared financial year ends on 2028-01-01. Necessary evidence for an unresolved obligation is kept beyond that date until resolution. Afterwards, detailed personal records should be deleted or minimized unless a documented purpose still requires them. The current conservative financial store does not run an automatic seven-year purge; retention requires operator handling. Minimal consumed-payment and permanent receipt references remain necessary to prevent duplicate settlement.
Bokföringsnämnden explains the bookkeeping period and overseas storage conditions. The independent allocation archive is encrypted and kept beyond routine seven-day backups for the lifetime of unpaid obligations.
Support correspondence
Mail to support@orestride.com reaches the operator’s private inbox. The game does not automatically delete that mailbox or verify the operator’s outgoing reply identity. The proposed support policy is to remove ordinary resolved correspondence after 90 days, retaining only necessary material for an unresolved request, dispute, security investigation or applicable financial-record obligation. Paul must confirm and carry out that mailbox policy; no mailbox-deletion automation is claimed.
Your choices and rights
You may request information and access, correction, deletion, restriction, or portability where applicable, and object to processing based on legitimate interests. A request needs proportionate proof that you control the affected account, such as an authenticated session or a linked-wallet login; never send its secret recovery code. Send a request to support@orestride.com or use the authenticated in-game review route described on the contact page. There is no instant delete-account button, and logout is not erasure.
You may also contact or complain to Sweden’s privacy regulator, Integritetsskyddsmyndigheten (IMY). No solely automated decision with legal or similarly significant effect is intended; competition eligibility and disputed records include an operator review path.
Recovery and security
A guest recovery code grants one-time access to its save. Only its hash is stored. Keep it outside shared chats; restoring consumes it, rotates sessions, and prompts you to generate a replacement. A linked wallet provides another supported recovery method. Without either method, losing the browser session may make it impossible to establish ownership. Server protections reduce risk but cannot guarantee uninterrupted access or absolute security.
Changes
The dated notice will be revised when actual providers, retention, contact verification, or processing changes. Material changes should be made available before they take effect; owner review does not imply independent professional legal advice.