Document version 0.2.0 · Updated: 4 November 2026
This notice covers the paid Steam edition of Captain Fuor for Windows and Linux (App ID 5559440), with the optional online leaderboard. Android editions and earlier editions remain covered by their assigned privacy notices.
Controller and contact
Captain Fuor is a game by JourneyBit, the games label of schukai. The controller is schukai, Eichenstraße 26, 82290 Landsberied, Germany. Privacy and support: hey@schukai.com. Full provider information: https://www.schukai.com/de/impressum. The game is intended for adults aged 18 and over.
Local play
Normal play needs neither a schukai account nor a leaderboard server. The app's private storage holds your local best score and contract, unlocked and selected ships, earned ship wallet, music, sound, autofire and graphics settings, and whether you have seen the intro. Automatic graphics adjustment measures the frame rate locally and stores the resulting quality level. The ship wallet is game currency, not money that can be withdrawn.
These save files and settings are not uploaded to the leaderboard. The desktop edition contains no schukai advertising, analytics or crash-reporting services. It does not bind a Steam ID to your leaderboard identifier or use Steam achievements or Steam leaderboards. Processing by the Steam client and platform remains separate. Your own backups and copies of the user-data folder may also contain the participation key; protect them accordingly. Transfer or recovery of the leaderboard key is not promised.
Optional online leaderboard
The service at https://api.captain-fuor.schukai.com provides daily and all-time lists for each rules version. Your best single accepted run counts, not a sum. Daily lists are available for the current and previous 34 UTC days. The leaderboard is public and can also be accessed outside the app.
Viewing a list. Opening the panel downloads nothing. You connect only when you select “Load list”. Without participation, no identity or attempt is created. If you participate, your public identifier may be sent to show your rank and neighbouring entries. Each connection processes your network address and technical connection information for transmission and security.
Joining. Only after your explicit selection does the app create its own device key. The private key stays in private app storage. The server receives the public key, protocol identifier and deletion code; it stores only a secure verifier of the code. Your public identifier and automatically generated callsign derive from your public key. The service also stores when you joined and when your last accepted run occurred. You cannot post your own name, messages or images. The server does not store a version of your participation information or a separate consent record.
Starting runs. While you participate, the app attempts to obtain a signed attempt before each round. It contains an identifier, random seed, rules version, issue time and seven-day validity. One attempt may be open per identity. If offline, the round starts locally and cannot become an online attempt retrospectively. The connection may fail after a successful online start.
Event log and submission. During an online round, the app stores the attempt and ordered event log encrypted in private app storage. Events include a sequence number and active play time: starting ship, weapons and relevant equipment; waves and uniquely identified rocks; shots, projectile identifiers and powered states; destruction, causes, fragments and ore creation; ore collection and expiry; contracts; station visits, departures and field clearing; weapon/equipment changes, relevant frame durations and the end of the run. This does not completely record or prove positions or human input.
You submit a completed run through a separate action; the app does not upload its log automatically. Submission sends your public identifier, attempt and chained log blocks with integrity values. Requests are signed with your key and include a timestamp and one-use request identifier. The server checks the event sequence, calculates points, contracts and active duration, and adds the UTC day of first acceptance. Repeating the same completion creates no second entry. Duration is logged play time, not independently proven real time. You may discard an attempt. Before another online start, interrupted attempts are abandoned without sending their log. Purchase receipts, payment data and the ship wallet are not sent to the leaderboard; equipment used in the run is part of the log.
Public data. Callsign, public player and run identifiers, points, contract count, duration and rank are public. Event logs, public keys, deletion codes, joining time and last activity time are not publicly displayed. Others may copy public entries; schukai has no direct control over their copies.
Checks and moderation. Automatic rules checks can reject a submission, leaving no entry. They prove neither actual hits, human input nor an unmodified app. Carefully fabricated logs or bots may pass. This is not full replay verification. Authorised operators may remove individual runs and block or unblock identities. This affects the online list, not local play or purchases. You may request human review at hey@schukai.com.
Purposes and legal bases
Where the GDPR applies, we process participation, attempt, event and public ranking data to perform the free leaderboard participation service you request, under Article 6(1)(b) GDPR. This covers only data necessary for that service. You can play without this additional agreement and end participation at any time. Joining is not blanket privacy consent.
Request limits, abuse prevention, proportionate rules checks and technical security rely on Article 6(1)(f) GDPR. Our legitimate interest is a secure, reliable and fair optional service. This basis also covers a list you explicitly request without a participation agreement. There is no advertising, behavioural analysis for marketing or combination with other user profiles.
Local storage and access strictly necessary for the game you explicitly request, your selected settings and online functions rely on section 25(2)(2) TDDDG. This includes the participation key and locally protected log for your requested submission. This does not permit unnecessary advertising or analytics access.
Points and ranking are calculated automatically. They and technical rejection do not determine game purchases, local usage rights or other legal or similarly significant matters. Blocks and manual removals are performed by people; people can review disputed decisions.
Recipients, hosting and operations
Hosting and encrypted external backups use DigitalOcean, LLC infrastructure; this service uses a Droplet and Spaces in Frankfurt am Main. DigitalOcean processes entrusted service data as a processor. Authorised schukai operators have access as needed for operations, support, security or moderation.
Access outside the EEA remains possible. The DigitalOcean agreement identifies the EU-US Data Privacy Framework and applicable standard contractual clauses as fallback. Subprocessors are referenced there. Ask our privacy contact about applicable safeguards.
The application limiter briefly processes a hashed network address in memory; the preceding proxy processes it to limit connections. Request/access logs are disabled for this service. Game logs, signatures, deletion codes and full player IP addresses are not stored as access logs. Separate technical operations and security messages concern hosts, services, administrative access and backup health; central operations logs are pruned after 14 days and aggregate metrics after 30 days. Metrics contain no individual player identifiers or event logs. The information below additionally applies to websites you open and emails you send.
Separate protected records of administrative personal-data access contain actor, time, access source, affected identifier or data scope, and operation for statutory accountability. They contain no complete game logs, signatures or deletion codes and are not player HTTP access logs. Retention is one year, or two where an applicable statutory two-year requirement applies, then deletion. They are distinct from 14-day technical logs and backups no older than seven days. Their purpose is security, oversight and legal evidence of data access; where the GDPR applies, Article 6(1)(f) covers the legitimate interests in security, accountability and legal defence. Applicable Korean statutory access-control duties additionally apply.
Retention and deletion
On your device. Saves, settings, participation data and stored attempts are kept in the game's user-data folder: %APPDATA%/CaptainFuor on Windows; $XDG_DATA_HOME/CaptainFuor on Linux, or $HOME/.local/share/CaptainFuor if XDG_DATA_HOME is unset. Uninstalling does not reliably remove them. To delete local data, close the game and delete the folder. First preserve your deletion code and saves if needed; delete your own backups separately. Deleting the folder also removes the participation key but does not delete online data. Use the online deletion function first or your saved deletion code later. Without a saved key or deletion code, later identification is harder.
Runs and identity. Accepted run data, including the event log, is pruned after 35 days; your best eligible run per rules version remains without its log. Blocks for discarded or expired attempts are removed at the next scheduled cleanup; remaining attempt data is removed 35 days after expiry. Request identifiers and cached responses remain valid for 60 seconds and are removed by cleanup. Scheduled cleanup runs every five minutes.
24 calendar months after your last valid accepted run, your identity, public key and remaining personal leaderboard data are deleted. If no run was accepted, this period starts when you joined. Viewing lists, rejected submissions and app use without an accepted online run do not extend it.
Deleting yourself. “Delete online data” ends participation and deletes your identity, open attempts, logs, runs and best scores from the live service. Only after confirmation does the app remove its participation key and local attempt data; you can retry a failed request. Local saves and local best scores remain.
You can view your deletion code when joining and later in the app. Keep it separately from your device. After losing the key, you can use it without an account at https://api.captain-fuor.schukai.com/delete. Enter it only in the form, not in a URL or public message. For security, the page gives the same response for wrong or previously used codes.
Without a key or code. Write to hey@schukai.com. We assess individually whether proportionate additional information can establish a reliable link. A public identifier or callsign alone does not establish entitlement; we do not routinely demand identity documents. If we still cannot identify you reliably, we explain this and possible next steps. This is neither a blanket denial of your rights nor an automatic requirement to wait 24 months.
Backups. Encrypted external backups are created at least hourly and retained for at most seven days. Deleted data may remain there until expiry. A separately protected recovery journal contains the type, affected identifier and time of deletion and moderation actions until all affected older backups have been removed. That journal and current retention rules are applied before a restored service is reopened. When the service ends, live ranking data is deleted; backups and the recovery journal follow these periods. Legally necessary records remain separate and limited to what is required.
Reports, support and purchase data
You may report errors, entries or moderation decisions to hey@schukai.com. Identify the entry or its precise location and explain your concern. For reports of potentially illegal content, also provide reachable contact details and a statement that, to the best of your knowledge, your information is accurate and complete. Your report and email address are not published on the leaderboard. We process them to handle and answer the report, conduct human review and keep necessary legal records. Legal bases are Article 6(1)(b) GDPR for contract-related requests, (c) for legal duties and otherwise (f) for appropriate resolution and legal defence. Correspondence is retained only while handling, necessary legal records or claims require it; data no longer needed is deleted. Support data is not collected automatically in the game. Support services and providers are described at https://www.schukai.com/de/datenschutz.
This edition has no in-app purchases; credits are earned in play. Acquisition and use through Steam are governed by the Steam Subscriber Agreement. Valve processes Steam account, payment, device and usage data under its privacy policy. schukai receives no card, bank or other payment-instrument data from the game. Steam supplies sales, refund and financial reports for accounting and business analysis, including quantities, amounts, currencies and regional summaries. We handle data you supply in purchase or support enquiries to answer them. Contract-related handling relies on Article 6(1)(b) GDPR; statutory accounting and retention duties on (c). Accounting vouchers subject to retention are generally kept for eight years from the end of their creation year; other statutory documents may have different periods and statutory extensions. Data no longer required is deleted when its purpose ends. The game does not link the leaderboard identifier to a Steam purchase or Steam ID.
When you use Steam discussions or reviews, your public Steam profile and posts may be visible there. schukai processes information you supply there to answer questions, investigate faults and moderate, under Article 6(1)(b) GDPR for contract-related requests and otherwise (f), with the legitimate interest in support and appropriate community management. Do not share private keys or deletion codes there. Valve's notices additionally cover platform processing and deletion options on Steam; we keep our own copies only while handling, statutory records or claims require them.
Rights and changes
Where the GDPR applies and its conditions are met, you have rights of access, rectification, erasure, restriction and portability, and may object to processing under Article 6(1)(f). If another processing activity relies on consent, you may withdraw it for the future. Contact hey@schukai.com; you may complain to a competent supervisory authority. We cannot remotely read or erase data stored only on your device.
Mandatory rights under your applicable local privacy law remain intact. They may also include confirmation, access, anonymisation and blocking. Where Brazil's LGPD applies, its rights remain, including confirmation and access, rectification, anonymisation, blocking or deletion of unlawful or unnecessary data, statutory portability, recipient information, information on the possibility and consequences of refusing consent, withdrawal and consent-related deletion. Use the stated contact; complaints to ANPD remain available. schukai does not sell personal data.
Opening websites and sending emails are separate actions outside local play. Websites are covered by https://www.schukai.com/de/datenschutz. We expressly inform affected users of material processing changes in good time before they start: prominently in the app for app functions and before any required consent. For service changes affecting older editions, we additionally use an appropriate existing, lawfully usable contact or service channel. A silently changed website is insufficient. New privacy notices do not constitute agreement to contract changes.