LAST UPDATED · 11 OCTOBER 2026

Privacy Policy

This notice covers PirateCraft Build 155 and the PirateCraft2D project website. The project is maintained by PirateCraft2D. Contact for support and data-protection requests: Support & Privacy Contact — Open a support/privacy request.

Local play and saves

The game stores Journey saves, settings and backups on your computer. Saves include world progress, position, equipment, inventory and other gameplay state. In co-op, the host’s local save also includes the guest’s gameplay state so a returning guest can continue. The reviewed save projection does not add Epic account IDs or the friends list to Journey saves. There is no developer-operated cloud-save service in this build.

Epic sign-in and online play

If you choose Epic Login, the integration processes your Epic account identity, Product User ID, display name and authentication/session information. It requests Basic Profile, Friends List and Presence permissions to support identity, the social overlay and invitations. Epic credentials are entered in Epic’s own sign-in flow, not into a PirateCraft password form. Persistent sign-in may retain authentication information through the Epic SDK on the device.

Private lobbies contain participant identifiers, the host identifier, member count, build/protocol compatibility and generated connection/session information. Gameplay data — such as player actions, position, inventory, equipment and world changes — is exchanged with the other player using EOS P2P/relay. Connection handling involves network information such as IP addresses and routing data. The host runs the shared world and can retain guest gameplay state in its local save. Built-in lobby voice chat is disabled in this build.

Who processes information

Epic Games provides account authentication, social functions, lobbies and connectivity. Please read Epic Games’ Privacy Policy for Epic’s own processing and account controls. This notice does not make promises about Epic’s retention or use of information. The other co-op participant receives the gameplay information needed to play together.

No developer-operated player database, advertising tracker, analytics uploader or automatic crash-report upload was found in the reviewed PirateCraft runtime. Local engine logs can contain technical errors and connection diagnostics. If you choose to open a support/privacy issue, we receive the message and any information you attach. GitHub Issues are public: other visitors may read or copy them. Do not include personal information or attachments in an initial privacy request; ask to arrange private follow-up first.

This website

This is a static project-information site intended for GitHub Pages. It has no sign-in form, analytics scripts, advertising, embedded social widgets or tracking cookies added by us. Fonts and artwork are served with the site. Hosting a page still involves network requests; GitHub’s processing is explained in the GitHub Privacy Statement. Following an external link or opening an issue involves the respective service. Contact requests are hosted on GitHub and are subject to its account requirements and privacy practices.

Purpose and legal basis

Information is processed to run the game, provide the online features you request, maintain connection security and respond to support or privacy requests. Where data-protection law requires a legal basis, the applicable basis depends on the activity: providing requested services, legitimate interests in reliability and security, consent where required, or legal obligations. Epic’s permission/consent screen is managed by Epic and does not replace any separate legal obligations of the developer.

Retention and deletion

Local saves and backups remain until overwritten or deleted by the person controlling the computer. The host may keep guest progress after a guest disconnects; deleting the guest’s own installation does not erase the host’s copy. Runtime session references are cleared when the session ends; local EOS cache, persisted sign-in data and engine logs have their own device/SDK lifecycle. We do not promise a fixed expiry period for data controlled by Epic or a co-op host.

You can manage/delete Journeys in the game and remove remaining local backups, logs or cache from the game’s application-data folder while the game is closed. Ask the host to remove its saved copy when applicable. Manage connected-app access and account information through Epic’s account controls. For help locating local files, contact us; please do not post them publicly.

If you send us support data, we use it for the request and retain it only as needed to resolve it, meet applicable obligations or handle related disputes. You can ask us to remove support material when it is no longer needed, subject to the controls available to repository maintainers and GitHub. Public copies held by other people may persist; do not post sensitive material to begin with. We cannot delete files held solely on another player’s computer or independently control Epic’s records.

Your choices and rights

You can play solo without choosing Epic Login. Depending on applicable law, you may have rights to access, correct, delete, restrict, object to processing, obtain a portable copy, withdraw consent, or complain to a competent supervisory authority. Use Support & Privacy Contact — Open a support/privacy request for an initial request; it is a public GitHub Issues page, not a confidential form. Ask for private follow-up without posting personal details, passwords or tokens. We may need limited information to verify that a request relates to you. Requests about an Epic account should also be directed to Epic.

Changes

This notice will be updated if the game’s processing or website changes. The date above identifies this version.