Cubaster

Privacy Policy

Updated: October 2, 2026 · Current Google Play release: Cubaster 1.1.25

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

1. Who we are and what this notice covers

Cubaster is provided under the developer name Капуста ("we", "us"). Contact us about privacy or deletion at cubaster@proton.me. This notice covers the Cubaster Android app (com.cubaster), including the current release 1.1.25 available in Google Play, the earlier versions described below, and 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.

Crash reporting is optional and off by default in v51 (1.1.21) and subsequent releases, including v55 (1.1.25). To enable it, choose Settings → Crash Diagnostics from the game’s main menu. On the Data and diagnostics screen that opens, turn on Send minimal crash reports and confirm the explanation. You can play without enabling it. Until you enable it, the app does not save reports in its numeric report queue or upload diagnostic reports to us.

Only subsequent failures are eligible. Enabling reporting clears the previous queue and excludes earlier Android exit records. Turning it off clears pending reports and cancels further uploads. Data already received by the server cannot be recalled by the switch. The v50 build has no upload capability and its switch cannot enable uploading.

3. Crash reports and local diagnostics

When reporting is enabled, a crash, an app-not-responding event (ANR), or an abnormal exit caused by low memory or excessive resource use can generate a small report. Android's record of that exit may be read on the next launch. Reports are queued and uploaded asynchronously when a connection is available; a reporting failure does not block the game. We use them to diagnose failures and improve reliability.

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 queue holds at most 32 reports. Reports older than seven days are discarded at the next app/queue operation and are not uploaded. Turning reporting off or using Delete local diagnostics clears the pending queue and prevents earlier Android exits from recreating it. Received reports, decoded data and related analysis are retained for up to 30 days from receipt, with scheduled expiry cleanup. Matching reports are grouped for reliability analysis; summary groups and alerts require at least three reports.

For deletion requests, the device keeps up to 128 recent confirmed report references. To copy them, choose Settings → Crash Diagnostics from the game’s main menu. Scroll down in Data and diagnostics and select Copy sent report references, then email cubaster@proton.me. These references identify individual reports, not your installation. References expire after 30 days and are removed on the next launch or use. Clearing the pending queue keeps these references available. Clearing all app storage or uninstalling removes them along with other local data, including worlds and settings.

v50 difference: it can write local numeric crash/exit reports without enabling upload, up to 32 records with no fixed age limit. They remain until displaced, deleted in diagnostics, or app data is removed. It never uploads them. Upgrading from v50 to v51 or later discards that old queue and leaves reporting off. Android and the game runtime may keep separate local error records; the app's queue controls do not erase operating-system records.

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.

Where a legal basis is required, optional diagnostic processing relies on your consent, which you can withdraw in the app without affecting earlier lawful processing. We process information necessary to provide features you request to perform that service; hosting security and handling support enquiries rely on our legitimate interests in operating and supporting the service, subject to your rights. You can contact the data-protection authority in your jurisdiction if you believe your rights have been infringed.

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