Prepared for Ultimate Lemmix 2.4.2, build 108. Updated 19 November 2026.
Your game and your data
Erik Veland develops Ultimate Lemmix. The app stores local players, progress, settings and imported game data on your device. Local play needs no separate hosted account.
Cloud saves, optional play counts and community rankings use services at glasscode.academy. Apple provides iCloud and Game Center.
The candidate has no advertising SDK or advertising identifier use. Its privacy manifests declare no advertising tracking. Network and service providers still process information needed to deliver requests.
Automatic cloud saves
The app synchronises progress when a connection and usable provider are available. This includes profiles, completion records, shared participants, turn ownership and saved journey information.
The cloud library excludes imported game media and mid-level engine checkpoints.
The app encrypts library contents before sending them to the hosted save service. The service receives encrypted contents, library and device identifiers, and update information.
It also receives an authentication credential, which it stores as a hash. It does not receive your library encryption key or sync password in plaintext.
Credentials remain in the device Keychain and can also use private iCloud storage. Private iCloud stores library recovery identities and encrypted saves.
A device-link code or shared sync password can connect different Apple accounts. Anyone with a working link or password can access the linked library.
Cloud saves are separate from sharing consent. Turning off count sharing does not turn off cloud saves. Removing the app does not remove existing cloud copies.
Optional play counts
Counts are sent after you choose Share counts and records. Fixed events describe installation opt-in, active days, level starts, outcomes, rescued characters and soundtrack choices.
They exclude player names, email addresses, Apple accounts, device identifiers, replay identifiers and imported file paths.
The counter service combines events into totals. The shared rescue count is public. Network providers receive connection information, including your network address.
Public records and action replays
Sharing counts and records also enables public record sharing for players without a separate choice. An explicit record-sharing choice for each player remains separate.
Shared records include player initials, scores, run identifiers and gameplay action replays. The service uses a separate random credential for each player.
Other players can see shared initials and scores. Eligible leaderboard entries also make action replays available.
Action replays contain timed commands and verification information. The current sharing flow excludes imported assets, calendar events and recorded video.
Turning sharing off stops future automatic submissions. It does not remove existing records. Use Remove shared records to request removal of that player’s hosted records and replays.
If the connection fails, removal remains pending and the app retries it. Removing hosted records keeps local records.
Apple services
Game Center processes the sign-in and leaderboard data needed for its features. The app can display your Game Center name and scores.
Mac and iOS also use Game Center saved games for compatible solo progress. Apple TV uses the cloud library for saved progress.
Game Center and community rankings are separate services. The community service does not need your Apple account credentials.
Calendar, widgets and transfers
With permission, Desk Clock reads the next relevant calendar event and displays its title and time. It does not add calendar events to telemetry or cloud archives.
The app and its extensions share local files for widget artwork and Apple TV Top Shelf scenery.
Apple TV receives selected files through a temporary local-network transfer page. This does not send files to the hosted save or ranking services.
Diagnostics and crash reports
This candidate does not include a dedicated third-party crash-reporting SDK. Optional play counts are separate from a crash report you choose to send to support.
Review diagnostic files before sending them. They can contain device details, file paths or other personal information.
Support correspondence
If you email support, you provide your email address, message and any attachments. We use them to reply and investigate your request.
You can ask about access to or deletion of that correspondence. Do not send passwords, recovery keys or device-link codes.
Children and shared devices
If a child uses the app, a parent or guardian should review optional sharing and each player’s record-sharing choice.
Shared initials, scores and eligible action replays can be public. Review those choices before enabling sharing on a shared device.
Retention
The counter service removes daily aggregate rows older than 90 days when it receives an event or serves a summary. Lifetime rescue and installation totals have no automatic expiry.
Aggregate totals have no separate contribution that can be removed for an individual player. Clearing local counts does not reset public totals. Earlier counts can remain in a local recovery backup.
The reviewed ranking service has no automatic age-based expiry for records or action replays. A replay can remain stored outside public leaderboard positions.
Service-maintenance backups can retain earlier records and replay files after removal from the live service. These protected copies are limited to the server operator and have no automatic deletion deadline.
Hosted cloud saves remain available for recovery and sync. Device-link codes expire after ten minutes and can be used once.
Cloud backups retain the three newest successful snapshots. Retention depends on successful backups rather than a fixed number of days. Older encrypted data can remain in those snapshots.
Apple controls retention for its services and device backups.
This website
This site has no analytics, tracking cookies or submission forms. Routine web access logging is disabled for this site.
Server error logs can include your network address and request details when an error occurs. The server uses daily rotation and retains 14 rotated archives, with older files compressed.
This is an archive-count limit, not an exact 14-day deletion deadline. Operating-system logs follow system storage limits rather than a fixed retention period.
The app’s sharing controls do not control server logs. Contact us about website data or retention.
Choices and contact
Read Your privacy choices for the available controls.
For privacy requests, email Erik Veland at erik@veland.au. Do not include passwords, recovery keys or device-link codes.
Changes to this notice
This notice is dated 19 November 2026 and describes the 2.4.2 candidate. We will update this page and its date when the policy changes.