Cubaster

Privacy Policy

Updated: November 10, 2026

Читать на русском

1. Who we are and what this notice covers

Cubaster is provided under the developer name Капуста ("we", "us"). For privacy or deletion requests contact cubaster@proton.me. This notice applies to the Cubaster Android app (com.cubaster), including earlier releases where crash-reporting defaults differed, and to this website.

2. The app and your choice

The app has no advertising or in-app purchases, does not sell personal data, and has no Cubaster account system or tracking SDKs. It does not contact a Cubaster startup-verification or content-key service to start the game. Network features contact the services in section 4.

Minimal crash reporting is enabled by default in builds with the updated diagnostics setting. In earlier versions v51–v55 (1.1.21–1.1.25), it was off by default and required the player's confirmation. Any explicit choice to disable reporting is preserved when updating. At any time you can turn it off in Settings → Crash Diagnostics → Data and diagnostics, without affecting your ability to play. The app does not monitor ordinary gameplay through the crash-reporting channel.

Only failures after reporting becomes active are eligible. On first activation, the app starts a new local reporting generation so earlier Android exit records are excluded. Disabling reporting cancels further uploads and removes unsent reports, but cannot recall reports already received. Version v50 has no upload capability.

3. Crash reports and local diagnostics

When reporting is active, a crash, app-not-responding event (ANR), or abnormal exit due to low memory or excessive resource use can generate a small report; normal gameplay does not generate reports. Android's record of an eligible exit may be read on the next launch. Uploads are asynchronous when a connection is available, and reporting failures do not block the game. We use these reports only to diagnose and fix software failures and improve reliability, not for advertising or player profiling.

A report contains the app build/release, Android version, event time, available uptime and memory measurements, numeric failure, signal and app-stage codes, and a new random reference for that report. For native crashes, it can include up to 16 relative code addresses from our library if Android makes them available. We resolve those addresses using private information for the exact app build. The app does not upload the Android tombstone itself, textual stacks, text logs, memory dumps, usernames, chat, worlds, screenshots, hardware identifiers, or a persistent device or installation ID.

Reports are encrypted before HTTPS upload to our diagnostics service hosted by OVHcloud. Only the isolated analysis service has access to decryption. Ordinary connection metadata, including the IP address, reaches the network infrastructure. The crash database does not store your IP address, and our current access-log format omits it. The network server uses IP addresses transiently to limit requests; rare critical-error logs may contain connection metadata. Current service logs rotate after seven days.

The app queues up to 32 reports, discarding records older than seven days at its next queue operation without uploading them. Turning reporting off or choosing Delete local diagnostics clears pending reports. Encrypted reports received by our service, decoded data, and derived diagnostic records expire seven days after receipt, with automated cleanup. A service outage or deletion failure can delay physical removal; we monitor cleanup failures. Matching reports are grouped only for reliability analysis, with summary groups and alerts requiring at least three reports; those derived records follow the same retention limit.

The device can keep up to 128 recent sent-report references for deletion requests. In builds with the updated diagnostics setting, references expire after seven days at the next launch or use; in earlier v51–v55 builds they expired after 30 days. To copy available references, select Settings → Crash Diagnostics → Copy sent report references and email them to cubaster@proton.me. Each reference identifies a single report, not an installation or device. Clearing the pending report queue preserves available references; clearing all app data or uninstalling also removes them and other local game data.

v50 difference: this older release can store up to 32 local numeric crash/exit records without a fixed age limit but never uploads them. Upgrading to a later release discards its old queue. The default-on reporting setting creates a fresh reporting generation, and any previous explicit opt-out is respected. Android and the game runtime can maintain their own error records, which are not controlled by the app's queue settings.

4. Network features and communications

Game servers. The app connects directly to servers you choose. Their operators receive connection data such as your IP address, player name and game-profile identifier, plus chat and gameplay traffic you send. When you open the Recommended tab, the app can ping the listed servers to display their status and latency before you join one. Those servers receive your IP address as part of the connection. These transmissions are not routed through a Cubaster diagnostics service.

Server catalog and website. The app downloads a static list of server addresses from cubaster.com. The request contains ordinary connection and HTTP metadata, including an IP address, and may include a cache validator. It does not contain your player name, chat, worlds, or a persistent app installation ID. The catalog is not personalised. GitHub Pages hosts the catalog and website and logs visitor IP addresses for security. We do not operate a catalog-request database or add advertising, analytics, tracking cookies, or tracking pixels to this site. See GitHub Pages data collection and GitHub's privacy statement.

Skins and server content. Multiplayer can cause the app to download uncached skin textures and server resource packs. The download host receives your IP address and request metadata. Resource-pack requests can also include your player name, game-profile identifier, and game version information. Pack downloads depend on the server's offer and your pack settings or confirmation. The relevant server and content-host policies apply; the download host may be different from the game server.

Google Play and other links. Google processes information needed to run its store. Installing the app, submitting store feedback, or following a social-media link involves that service's own data handling. See Google's Privacy Policy. We may receive feedback that you choose to submit through those services.

Support. If you email us or send feedback, we receive the address or profile information supplied with your message, its contents, and any attachments you choose to provide. We use them to answer you and investigate your request. Our contact mailbox is hosted by Proton; see Proton's Privacy Policy. Please send only the information needed to explain the issue.

5. Earlier testing

The old Cubaster backend and its on-server records, keys and dedicated backups were removed on September 7, 2026. Earlier versions no longer have an active reporting or startup service. The previous notice is retained as a historical document.

6. Retention, your choices and your rights

Current diagnostic retention and deletion are explained in section 3; earlier server records are covered in section 5. We keep support correspondence and feedback only as long as needed to resolve the issue, follow up, and meet applicable legal obligations. Hosting providers apply their own retention policies to their connection and security records.

You may ask us for access, correction, deletion or restriction of personal data that we control, object to processing based on legitimate interests, and request portability where applicable. Email cubaster@proton.me and describe your request. You do not need to create an account or send an identity document to start a request. We ask for additional verification only when necessary and proportionate.

We cannot retrieve local reports from your device. Supply the available report references when requesting deletion of received reports. We do not maintain a name-to-report or installation-to-report directory, so without a reference we may be unable to identify a report; it remains subject to normal expiry. We will explain any identification limitation and consider additional information you choose to provide. We respond within the time required by applicable law; where GDPR applies, normally within one month. If a lawful extension or retention exception is needed, we will explain it.

For the limited default-on crash diagnostics, where permitted by applicable law, we rely on our legitimate interests in finding software defects and maintaining app reliability. You can object to further diagnostic processing by switching reporting off or contacting us. In earlier versions where reporting required active permission, its legal basis was consent and that permission could be withdrawn in the app. Data needed for features you request is processed to provide those features; hosting security and support requests are handled on applicable legitimate-interest grounds. You may contact the relevant data-protection authority about a complaint.

7. Security and service providers

We use access restrictions and encrypted connections for our website, catalog and operator-controlled diagnostic services. Crash-upload packages are also encrypted before upload, with decryption restricted to the analysis service. These protections do not describe every independent game server's connection or guarantee that all internet traffic is encrypted.

Our infrastructure providers include GitHub Pages for the site and catalog, OVHcloud for our diagnostic service, and Proton for email. Google and independent game/content services also process information for their own services. Providers may process information in countries other than yours under their applicable terms and privacy notices. Contact us for details about the location and safeguards for personal data we control.

8. Children and changes to this notice

Cubaster is a general-audience game and is not specifically directed to children under 13. If you believe a child has provided us with personal data, contact us so we can review the information and handle it as required by applicable law. Having no in-app account system does not remove children's privacy rights.

We will update this notice when our actual data practices change and show the revision date here. Where a change requires a notice or consent before processing, we will provide it. Previous notice.

← Back to Home