Paint Sort! – Puzzle game

Privacy policy

How AlmostBrain handles information in Paint Sort! and on this website.

Last updated: 12 November 2026

Who this policy covers

AlmostBrain is an independent casual mobile game studio. This policy covers Paint Sort! – Puzzle game (Android application ID: com.almostbrain.paintsort) and this AlmostBrain website. For privacy questions or requests, email kiwisgames26@gmail.com.

Information we use, and why

Progress saved on your device

The game stores campaign progress, puzzle boards, moves, active playing time, undo and reveal state, personal results, audio preferences, country selection and score-sharing preferences. These let you resume play and keep your settings. Local analytics counters and milestones prevent repeated events. Your entire local save is not uploaded as a cloud backup.

Guest profile and online play

When online features connect, the game automatically creates or restores a Supabase guest identity. It uses a service-generated account identifier, a display name, Friend ID, optional manually selected country, sharing preferences and session credentials. Guest play does not ask for an account email or password. Device-protected session storage keeps you signed in. An avatar selection is stored locally.

Online puzzle validation uses puzzle and attempt identifiers, versions, moves, elapsed time, results and action records to check scores and prevent duplicate or invalid submissions. Where available, streak, earned-item balances and grant/spend records support those features. Country selection is not GPS or proof of residence.

Where competitive rankings are available, they use server-observed start and finish times and connection records. These include network delay and differ from your personal active-play time. Interrupted attempts can retain personal progress and Daily completion eligibility while becoming ineligible for competitive ranking. Practice does not replace the first official Daily result.

During closed testing, an invitation code grants Daily access to your existing guest profile. The server stores your enrollment, its access period and a reference to the invitation. It stores a one-way hash of the invitation code rather than the readable code. Codes are not added to game saves or Analytics. Enrollment does not grant access to another player’s private data. Google Play test eligibility is separate.

Friends and shared scores

The service stores friend requests, accepted relationships, blocks and reports to operate Friends and manage abuse. Shared leaderboards display your name, country flag, score and a public player reference. A Friend ID is sent to the service when you deliberately look up another player or connect with them; it is not a password. Invitations use your device’s sharing interface. The game does not read your contacts or collect invitation recipients.

Usage analytics

Firebase Analytics uses the separate consent controls described below. We send game events such as level starts and outcomes, moves, active time, scores, progression, Daily play, tool use and interactions with leaderboards and Friends. Properties include manually selected country, platform, level band, score-sharing preference and whether you have accepted friends. These help us understand play and improve the game.

When Analytics is enabled by your choice, Firebase also processes automatic app, device, installation and session information and identifiers. Its Analytics SDK can use an advertising identifier where available and derive approximate location from IP information. The game does not request precise GPS location. Our custom events do not include names, Friend IDs, Supabase IDs, email addresses, invitation contents or full move transcripts; we do not set a Firebase user ID. This does not mean that SDK data is identifier-free.

Crashes and diagnostics

Firebase Crashlytics helps diagnose failures. Optional crash reporting is OFF unless you enable it in Settings → Privacy details → Crash reports. It processes crash reports, stack traces, device and app information, installation identifiers and diagnostic context. Game-specific context includes the level, mode, attempt number, ranking eligibility and connection status. Handled errors use fixed failure categories rather than server responses or credentials. This optional reporting is separate from score sharing. Automatic Crashlytics uploads remain disabled; the game sends eligible stored reports after the independent opt-in. It does not enable separate Firebase session reporting through that upload.

Support messages

If you email us, we receive your email address, message and any attachments you choose to send. We use these to investigate and respond to your request. Please do not send passwords, session tokens or unrelated personal information.

Your choices

  • Share my scores: found in Settings and ON for new saves. Turning it OFF stops new publication and requests withdrawal of your public scores. If offline, removal completes after the server acknowledges it. It keeps local results and does not delete your guest identity, Friends or private service records. Turning it back ON does not republish earlier private attempts.
  • Country: you choose it manually. It controls country comparisons and is also used in Analytics.
  • Profile deletion: Settings → My profile → Delete profile → Confirm deletion. The alternative “Keep profile” cancels. See full deletion instructions.
  • Analytics and crashes: Google’s privacy form manages the relevant Analytics and advertising choices. Settings → Privacy options reopens the form when required. Optional Analytics collection remains disabled when its choice is unknown, denied or unavailable. Outside the configured consent region, an absent form does not enable Analytics by itself. Crash reports have an independent opt-in in Settings → Privacy details. Advertising consent does not turn crash reporting on. “Share my scores” does not control Analytics, crash reports or advertising data. Device-level advertising-ID choices do not disable every SDK operation.
  • Privacy requests: email kiwisgames26@gmail.com to request account/data deletion, access or correction without reinstalling the app. Available rights depend on applicable law. We may need information to identify your record and verify the request; do not send credentials.

Advertising and reward verification

Paint Sort! supports between-level interstitial ads and optional rewarded ads for one practice replay per completed Daily puzzle. Availability depends on the installed version, service configuration, connectivity and Google’s privacy requirements. Some closed-test releases or service configurations have advertising disabled. Practice never replaces your official first result.

Google sends signed reward callbacks to our server. Our server validates those callbacks before granting a practice reward. The callback includes an opaque reward-intent identifier and transaction information linked by our service to your guest account and dated puzzle. A delayed connection can delay availability; the game checks again automatically without requiring another ad.

When advertising is enabled, Google Mobile Ads processes IP-derived approximate location, app/ad interactions, diagnostic and performance information, and device or account identifiers, including advertising/app-set identifiers when available, for advertising, measurement and fraud prevention. Advertising choices and device identifier controls may limit this processing; they do not disable every technical request. Automatic interstitial-related collection is not controlled by the voluntary rewarded-ad button. Analytics, Crash reports and Share my scores are separate settings.

The app includes Google Mobile Ads and its User Messaging Platform (UMP), Advertising ID permission, Firebase Analytics and Crashlytics. Disabling ad display does not remove these components or stop all collection. Google’s consent service receives technical requests with IP information, app and device details, language, screen information and consent information to provide the appropriate privacy flow.

Our Firebase/Google Analytics Android app is linked to AdMob. Analytics data collected under the applicable choices can be available to the linked AdMob service for measurement and product features. This link remains in place when ad display is disabled. Google signals is disabled; granular location and device data collection is enabled in the Analytics property. These settings do not override the app’s requirement for an explicit Analytics consent grant.

The app requests updated Google consent information at launch and offers Settings → Privacy options when Google requires it. Forms depend on the configured region and Google’s consent requirements. Consent or network errors do not block campaign gameplay. Essential online guest-profile and score services remain separate from optional Analytics and diagnostics choices.

Service providers and visibility

  • Supabase: guest authentication, profiles, Friends, score validation and related game records. Network requests also involve technical information such as IP addresses and service logs. See Supabase’s privacy information.
  • Google Firebase / Google Analytics: usage measurement and crash diagnostics. See Firebase privacy information and Google’s privacy policy.
  • Google Mobile Ads / UMP: consent management, advertising delivery, linked measurement, fraud prevention and signed reward callbacks, subject to the availability described above. Google documents potential SDK data processing in its Unity advertising disclosure.
  • Firebase Hosting: serves this website. Hosting processes technical requests, including IP addresses, to deliver pages and protect the service.
  • Email: messages sent to our support address are handled through Gmail.

Score sharing defaults ON for new saves: other players can see the public name, country flag, score and player reference published with eligible results. You can turn it OFF in Settings. Deliberate Friends actions reveal the information needed to connect players. Provider processing can occur outside your country. Online and Firebase data are not stored exclusively on your device. Contact us for information about service-provider processing relevant to your request.

Retention and deletion

Local progress and backups remain on the device until removed through device storage controls or another explicit local action. Deleting an online profile does not erase that progress, local analytics counters or already collected Firebase reports.

Online profile deletion removes the profile, linked scores and game records, including competitive and reward records, closed-test enrollment, Friends relationships and associated records through the service, then requests deletion of the guest authentication account. The service retains evidence so completion can be verified if a connection fails after deletion. The game clears its saved session after verified completion; a pending request is not confirmation. Deletion does not automatically create a replacement guest profile.

Deletion-completion receipts are retained without automatic expiry. Each contains a one-way hash of a random deletion confirmation and a creation time. During deletion it is linked to the authentication account; that link is removed when the authentication account is deleted. The completed receipt contains no account identifier, name, Friend ID, scores or login credentials. It allows a returning device to verify completion even after a long interruption. Separate deletion-protection records support unfinished deletion and safe retries. These operational records are not restored game profiles.

Online records are retained to operate your profile, verify results and maintain the integrity of game transactions, unless removed through deletion or service cleanup. We do not state an automatic deletion deadline for these records. Provider logs, backups and support correspondence are managed separately. Deleting live game records does not immediately erase copies in provider backups or logs. Their retention depends on the relevant service and configuration; we do not promise a project-specific removal period that has not been established. Support correspondence has no fixed automatic deletion period currently established. Contact us to request review or deletion of identifiable records; uninstalling the game alone does not erase server records.

Firebase information is not linked by the game to your Supabase guest ID for deletion. Deleting your guest profile is not a Firebase erasure request, and we cannot promise to identify every analytics or crash record from a Friend ID alone. Google publishes separate Firebase retention information. For Crashlytics crash traces and associated identifiers, Google states a 90-day retention period before starting removal from live and backup systems; that is not a promise that all copies are erased on day 90. The Google Analytics property is configured to retain event-level data for 2 months and user-level data for 14 months, with the user retention period reset on new activity. These controls apply to the relevant granular data, not every aggregate report or provider backup. They are not a promise that all provider data disappears after those periods. See data deletion for the available process and limitations.

This website

These pages use no website analytics, advertising, tracking cookies, external fonts or client-side scripts. Opening an email link opens your email application; it does not send a message automatically. Hosting and email providers still process the technical information needed to provide their services.

Audience and policy changes

Paint Sort! is intended for adults aged 18 and over. It is not designed or marketed for children. This intended audience is not an age-verification system, and access by minors is not technically blocked by the game. If you are a parent or guardian concerned that a child has provided personal information, contact kiwisgames26@gmail.com. We will update this page when data practices change and show the updated date.

Contact AlmostBrain

Privacy and support: kiwisgames26@gmail.com. For an account or data deletion request, use the subject “Paint Sort! — Account and Data Deletion Request” and include your Friend ID and display name if available. Ownership verification is required; a Friend ID alone is not proof. Never send passwords, authentication tokens or other credentials. See the deletion page for lost-access limitations and how to request review of other identifiable data.