General / 01
Controller and contact
The respective provider is the controller; provider information and answers to privacy questions about the apps, including KeyType, are available through the central contact channel below. The provider of dev.ozverse.de is responsible for the developer website described in this document.
Privacy enquiries can be submitted through the central contact channel. Please name the affected app. Do not include credentials, health data or other unnecessary personal information.
General / 02
Data subject rights
Where personal data is processed, and subject to the applicable legal requirements, rights include in particular access, rectification, erasure, restriction of processing, data portability and objection. Any consent granted may be withdrawn at any time with effect for the future. There is also a right to lodge a complaint with a data protection supervisory authority.
These rights relate to data the controller can actually access. App data stored exclusively and locally on the device cannot be viewed, rectified or erased remotely. The available deletion and control options are described in the relevant app section.
General / 03
Developer website and contact
- Website: dev.ozverse.de mainly serves static website content and does not use tracking or analytics services or externally embedded runtime content. To remember the language selection, the website uses the technically necessary
ozverse_languagecookie. It stores one of the valuesde,en,it, oresfor up to one year. The cookie is neither used for tracking nor shared with third parties. - Contact form: The contact form sends the selected app or enquiry topic, email address and message, together with optional app version and device details, through the web server to the configured support mailbox. The submitted content is used to process the enquiry; the reply address is also processed for the abuse prevention described below. No database, external form provider, analytics service or external CAPTCHA service is used for this purpose.
- Local CAPTCHA and session: The six-character support CAPTCHA is provided by this web server as an image and an audio alternative. Both represent the same challenge. The audio reads letters with a spelling word and digits in English and starts only through the audio controls; no microphone access is required. The technically necessary
ozverse_supportsession cookie associates the check with the browser session and lasts until the browser session ends. It is restricted to the/path and protected bySecure,HttpOnlyandSameSite=Strict. Private PHP sessions hold up to ten challenges at a time. Each challenge is valid for at most ten minutes and can be used only once; expired state is cleaned up on later requests. No external CAPTCHA provider is involved. - Abuse prevention: To limit requests and sending attempts, HMAC identifiers are derived from the web server’s connection IP address and the reply address using a secret server key; IPv6 addresses are grouped by their /64 network. These identifiers and timestamps are processed in private temporary protection files for windows of at most 24 hours. The protection files contain no unmodified IP addresses, email addresses or messages. Expired entries and files are cleaned up on later requests. This processing protects the support form and is not used for tracking.
- Tester application: The voluntary form transmits the selected app, email address and, optionally, a name, device details and a message through the web server to the configured support mailbox. The details are used solely to process the application and coordinate a suitable beta test. No database, external form provider, analytics service or CAPTCHA service is used for this purpose.
- Consent and retention: The form is sent only after explicit consent. Consent may be withdrawn at any time with future effect through the central contact channel. The associated message is erased as soon as it is no longer needed to process the enquiry or application and run the selected test, unless statutory retention obligations apply.
- Scope: No blanket statements apply to the apps. The relevant app section below is authoritative.
App / 001 · iOS, iPadOS and watchOS · Updated: 18 September 2026
OZLife
Locally stored data
OZLife stores settings, onboarding and usage states, program and task progress, rewards, favorites, game progress, habits, workout and activity progress, and other states required for app functions locally on the device. Some daily data is shared locally with the OZLife widget through an app group.
Journal entries are stored in a local database with their text, entry type, timestamps and, where applicable, program context. Voluntary attachments may include files, voice notes and transcripts. The journal can optionally be protected by device authentication; OZLife does not receive biometric characteristics.
Optional iCloud synchronization
Synchronization is disabled by default and can be enabled separately for the journal and favorites. Once enabled, OZLife synchronizes journal text, metadata and attachments, or the identifiers of selected favorites and favorite games, through the signed-in Apple account’s private CloudKit database. Technical synchronization state, modification dates and deletion markers are also processed.
Turning synchronization off stops further synchronization but does not automatically erase records already stored in iCloud. Apple’s settings and privacy policy additionally govern storage, device synchronization and deletion in iCloud.
Apple Health and Apple Watch
Apple Health is optional and is used only after system permission has been granted. OZLife can read workout data from Apple Health and save completed OZLife workouts, including activity type, start, end, duration and technical identifiers, to Apple Health. For breathing exercises, OZLife can read current heart rate on iPhone and Apple Watch, calculate local biofeedback during the session and save the session as a workout. Health data is not transferred through OZLife’s iCloud synchronization.
Health permissions can be withdrawn in System Settings. Workouts already saved in Apple Health are managed and deleted there.
Microphone and speech recognition
After explicit permission, OZLife uses the microphone for optional journal voice notes, voice-based ingredient search and spoken feedback. Recordings are initially created as temporary audio files. For journal entries, the user can choose whether to retain the audio, the transcript or both. Feedback and search recordings are not retained as app content after conversion to text.
Apple speech recognition is used for transcription. Depending on the device, language, system availability and Apple settings, processing may take place on the device or through Apple services.
Purchases, notifications and sharing
Subscriptions and one-time purchases are handled through Apple StoreKit. OZLife processes product identifiers, purchase status and entitlement state but does not receive payment details. Optional reminders are scheduled as local system notifications. Content is passed to a selected app through the iOS share sheet or clipboard only after an explicit action.
Feedback
The voluntary feedback channel opens a pre-filled draft in the email app. It contains the selected category and the entered or dictated text. The app version, build, iOS version, device model, voluntary screen and area details, and a timestamp may optionally be added. Sending, the sender address and further processing are handled by the user and their email provider.
Analytics, advertising and retention
No third-party advertising, analytics or tracking SDKs were found in the reviewed project state. The Privacy Manifest declares no tracking and no data categories collected by the provider.
Local data remains until it is deleted through available app functions or the app and its local data are removed from the device. Journal entries and their attachments can be deleted individually; the current version does not provide a single deletion function for all local state. Data passed through iCloud, Apple Health, StoreKit, email or the share sheet is additionally subject to the retention and deletion rules of the relevant service.
App / 002 · iOS and iPadOS · Updated: 18 October 2026
Pew Pew Clocked Out
Locally stored game data
Pew Pew Clocked Out stores campaign progress locally on the device. This includes unlocked and completed levels, the current continuation point, checkpoints, scores, selected game modes, unlocked and selected chairs, and in-game streak and event states.
The app also stores local high-score tables containing up to three characters entered by the user, the score, level, game mode, date and time, and whether a level was completed without taking a hit. Other local settings include sound, music and effects volume, completion of the controls introduction, and the display sequence of in-game messages.
Optional office personalization
At the user’s explicit request, one image each can be selected for the “Management” and “Team” areas through the system photo picker. The app receives only the selected image and does not obtain general access to the photo library. The chosen crop is stored as a protected PNG file in the local Application Support directory. These image files are excluded from device backups and can be removed or replaced individually within the app.
Full-game purchase through Apple StoreKit
Levels 1–6 are free to play. An optional one-time, non-consumable in-app purchase unlocks access to levels 7–100; it is not a subscription. Product information, purchases, restoration and full-game entitlement checks use Apple StoreKit with the Apple Account used for the App Store.
To unlock and restore access, the app processes the product and transaction identifiers supplied by StoreKit, purchase and entitlement status including verification, and any revocation information on the device. This data is not transmitted to the provider’s own servers. Apple handles payment processing; the app does not receive credit card or bank account details. Apple’s App Store privacy notice and privacy policy also apply to Apple’s processing.
Data transmission and external services
The app does not require a separate app account and does not use its own servers. It contains no advertising, analytics or tracking services, or external software packages. Game progress, high scores, settings and selected portrait images are not transmitted to the provider’s servers. StoreKit functions communicate with the App Store through Apple’s system services.
Except for portrait images, which are explicitly excluded from backups, local app data may form part of an Apple-provided device backup depending on the device and backup settings. Such backups are governed by the settings and privacy policy of the selected backup service.
Retention and deletion
Data remains stored locally until it is replaced or deleted through app functions, or until the app and its local data are removed from the device. Starting a new campaign resets campaign progress and the checkpoint; the best retro streak and unlocked and selected chairs are retained. Portrait images can be removed individually. The current version does not provide a single deletion function for high-score tables and all settings.
Deleting the app or its local data does not delete purchase records managed by Apple. Apple’s rules govern the retention and deletion of those records. An existing full-game purchase can be restored through StoreKit.
App / 003 · iOS and iPadOS · Updated 4 August 2026
Long Weekend
Locally stored data
Long Weekend stores settings and leave plans exclusively and locally on the device. These include in particular the country, region, regional public-holiday rules, planning year, leave days, onboarding status, and saved suggestions with their period and processing status.
This information is not transmitted to the provider’s servers and is not used for advertising, analytics or profiling.
Calendar access
Long Weekend requests write access to the system calendar only after an explicit selection. The chosen leave days are then created as calendar entries with a title, period and note.
If a linked leave entry is to be deleted from the app, full calendar access is requested. It is used solely to find and remove the entry previously created by the app using its stored identifier. Other calendar entries are neither evaluated nor changed.
Whether calendar entries are synchronised through an Apple or third-party account depends on the system settings and the selected calendar account.
Email drafts
At the user’s request, Long Weekend creates a pre-filled leave request in the system email interface. Sending, recipient selection and any further processing are carried out only by the user and their email provider. Long Weekend receives neither recipient addresses nor email content.
Data transmission and third parties
The app uses no servers of its own, analytics or advertising services, social-media SDKs or tracking technologies. Only system functions provided by iOS are used for calendar and email; the privacy terms of the configured account provider also apply.
Storage period and control
Saved leave plans can be deleted from the leave overview. A linked calendar entry created by Long Weekend is also removed if calendar access has been granted. App settings and other local data are removed no later than when the app is deleted.
Calendar access can be revoked at any time in iOS Settings under “Privacy & Security”. All other app functions remain available without calendar permission.
App / 004 · iOS and iPadOS
Monte OZ
- The versioned game state is stored locally in the device’s Application Support directory.
- The documented project state contains no backend, cloud or telemetry.
- The app project documents no external dependencies.
App / 005 · macOS · Updated: 18 September 2026
Own Your Beat
Locally stored data
Own Your Beat stores information entered in the app exclusively on the Mac. This includes project names and settings, working-time intervals and optional notes, active timers, planned leave days and periods off, the status of leave plans, and settings for working hours, working days, leave allowance, public-holiday region, notifications and optional NetBird automation.
The data is stored as a JSON file in the user account’s Application Support directory. For the optional working-time notification, macOS also stores the date of the most recently displayed reminder in the app’s local preferences.
Own Your Beat does not require an account and does not transmit this locally stored app data to the provider’s servers. The app contains no analytics or advertising services and no tracking technologies.
Calendar access
At the user’s explicit request, Own Your Beat can add a planned period off to the default calendar as an all-day event. The app requests write-only calendar access for this purpose. The event contains the period off, the required leave days, related public holidays and, where applicable, a note stored with the leave plan. Existing calendar events are neither read nor changed.
The event is stored in the selected calendar independently of the app data. Deleting a leave plan from Own Your Beat does not automatically remove the calendar event. Whether the calendar is synchronized through an Apple or third-party account depends on the default calendar configured on the Mac and its settings.
Draft emails
On request, Own Your Beat opens a pre-filled leave request in the default email app. The draft contains the selected leave days, the planned period off and the related public holidays. Own Your Beat does not choose a recipient or send the message. Sending and further processing take place only through the user and their email app and email provider.
Optional NetBird automation
When NetBird automation is enabled, Own Your Beat regularly checks the connection status of a locally installed NetBird application. It processes only whether NetBird is connected or disconnected and starts or stops time tracking for the selected project accordingly. Own Your Beat does not store network addresses, peer data or user identifiers from the NetBird output and does not itself connect to the NetBird service. NetBird’s independent data processing is governed by the information provided by the relevant NetBird provider or operating organization.
Imports, notifications and launch at login
CSV files and JSON backups are read locally only after manual selection and are not transmitted by Own Your Beat. The optional eight-hour reminder is displayed as a local macOS notification. At the user’s request, Own Your Beat can be launched automatically through macOS login items.
Retention and deletion
Locally stored data remains until it is deleted within the app, replaced by restoring a backup or removed manually from the Mac’s local app data. Working-time entries can be deleted individually or in full, and leave plans can be deleted individually. The current version does not provide a single deletion function for projects and all settings. Calendar events created by the app must be deleted separately in the relevant calendar.
Calendar, notification and login-item permissions can be changed or withdrawn at any time in macOS System Settings.
App / 006 · iOS, iPadOS and macOS
Allotment Mayhem
- The documented app state is implemented as an offline single-player game without network, session or backend code.
- Game mode, completed levels and high scores are stored locally.
- The available privacy information makes no statement about analytics, tracking or further permissions.
App / 007 · iOS · Last updated: 18 September 2026
Sizing Calculator
Calculation and local processing
The values entered for storage demand, growth, planning period, reserves, technical overhead and redundancy, together with the calculated results, are processed within the current app session. The reviewed project version contains no function that permanently stores these inputs or results in files, databases, user defaults or a cloud service. They are therefore no longer available after the app session ends.
Optional email export
Only after an explicit selection does the app generate a CSV or HTML report from the current inputs and results. The report is created in memory and passed as an attachment to the system email composer. The app supplies a subject and message text but does not set a recipient or sender and does not send the message itself.
The user decides in the email composer whether and to whom the message is sent. From that point, the message and attachment are processed by the email app, the configured email provider and the selected recipients; their respective privacy and retention rules apply to storage, transmission and deletion.
Permissions, network and third parties
The app does not request access to the camera, microphone, location, contacts, calendar, photos or other protected device data. No proprietary network requests, third-party SDKs, advertising, usage analytics or tracking functions were found in the reviewed project version.
App / 008 · macOS, iPadOS and iOS · Updated: 21 October 2026
Grundwerk
Project data and local storage
Grundwerk processes the property, building, room and garden plans you create, dimensions, objects and connections, inventory and custom object templates, and energy, consumption, PV, water and supply data. Project management includes tasks, dates, costs, invoice and delivery details, site diaries, defects, inspections, decisions, permits and maintenance. Other content includes notes, location coordinates, time zone, adopted geodata, images and original documents such as PDFs, plans and receipts, and saved project versions. These contents may include personal information such as addresses, participants’ names or information in photos and documents.
The data supports planning, calculations, documentation and project organisation. Complete .grundwerk files and the custom object library are stored locally in the app’s Application Support directory; settings and technical recovery and synchronization states are also stored locally. Embedded documents remain part of the project file. Local storage does not mean that every feature operates without data transfers.
iCloud: object library and complete projects
In the unlocked full version, the custom object library automatically synchronizes with Apple’s private CloudKit database when an iCloud account is available: periodically while the app is active and after changes. There is no separate switch for this in the app. Transfers include custom templates with their names, properties and any included notes, plus technical change, import and deletion states. For account binding, the app locally stores a hash of the account identifier supplied by CloudKit. The library remains usable locally without an available iCloud account.
Complete project synchronization is a separate, explicitly started operation. After enabling it and choosing “Sync now”, the entire project file, including photos, original documents and saved versions, as well as the project identifier and title, may be transferred to the private CloudKit database. A previous cloud project version may also be retained there. Loading the cloud project list is also explicitly started. Complete projects are not synchronized automatically when you open them.
Location search, device location and Apple Maps
An explicitly started place or address search sends the search text to Apple MapKit. When confirming a location, automatic time zone detection may resolve its coordinates through Apple’s geocoding service. You can also set the time zone manually. The current device location is obtained only on request and after system permission; continuous location tracking is not provided. Permission can be revoked in system settings.
When a map or satellite background is displayed, Apple MapKit loads the map data needed for the visible area. This may also happen when reopening a project with its map background enabled. The requested area and technical connection information are processed; the complete project file is not uploaded as a map request. Further information: Apple Maps and Privacy.
External elevation, cadastral and infrastructure data
Availability checks and data requests are started through their respective actions. Depending on the source, transfers include a search area derived from the project location, a polygon, raster tile or data block identifiers, and technical query parameters. Adopted data is stored in the project and can subsequently be used locally.
- Bayerische Vermessungsverwaltung: DGM1 via
geoservices.bayern.de, with an area polygon; elevation files are downloaded from the addresses supplied by the service underbayernwolke.de. - INGV, Italy: the TINITALY elevation model via
tinitaly.pi.ingv.it; service metadata and, for downloads, a spatial area. - MASE / PST, Italy: LiDAR elevation data for parts of Puglia via
sim.mase.gov.it. The availability check loads the service configuration; only the download sends a polygon and dataset selection and creates a server-side preparation order. Its identifiers are used for status checks and file downloads. - Amazon Web Services (AWS): Copernicus DEM GLO-30 or GLO-90 from the public S3 datasets
copernicus-dem-30mandcopernicus-dem-90munders3.amazonaws.com. Tile paths and requested file blocks reveal the required geographical area. - Agenzia delle Entrate, Italy: parcel references through the WFS service at
wfs.cartografia.agenziaentrate.gov.it, with a spatial search rectangle. This does not retrieve private ownership records. Personal cadastral documents are imported as files you select. - Esri / ArcGIS: explicitly opening the browser link to the power line map (
arcgis.com, line layer atservices-eu1.arcgis.com) passes location coordinates and the layer address. Opening the browser link does not automatically import power lines into your project.
With these network connections, the receiving service also technically receives the public IP address and connection or HTTP metadata. Coordinates and areas may relate to your property. The geodata requests do not transfer complete project records, inventories or original documents. Your building plans and manually aligned sewer plans are processed as project content. This does not automatically request official sewer or building records.
PV yield data
An explicitly started PVGIS request sends location coordinates, weather year and PV parameters such as tilt, orientation, mounting, technology, assumed losses and horizon selection to the European Commission’s Joint Research Centre at re.jrc.ec.europa.eu. The request uses a normalized capacity of 1 kWp; scaling to your system’s capacity happens locally. The provider also receives technical connection data. The response used is stored in the project; inventory and actual consumption series are not uploaded for this request. The PVGIS data protection notice refers to the European Commission and the JRC data protection register entry; no fixed retention period for these specific API queries is promised here.
Purchases, accounts and other services
Grundwerk requires no separate registration or OZverse account. Product information, purchases, restoration and full-version entitlement checks use Apple StoreKit. The app processes product and transaction identifiers, purchase entitlements and any revocation information; Apple processes payment data. Apple’s account terms and privacy policy also apply to StoreKit and iCloud. According to the App Store privacy notice, Apple retains purchase and download data for at least ten years for most customers, with regional differences. This period does not apply to Grundwerk project files.
Grundwerk does not send project data to its own OZverse servers or use advertising, tracking, telemetry, analytics or crash-reporting services. This does not cover Apple’s system-level processing or the external services you use. Other source and authority links open the respective website only when selected; that website’s privacy information applies there.
Provider information on roles, logs and transfers
For the processing of EEA-related data described in its own privacy policy, Apple names Apple Distribution International Limited in Ireland, worldwide transfers including the USA, and standard contractual clauses. For personal app content processed through CloudKit, the Apple developer terms, Attachment 4, section 3.6, contain separate provisions on processing on behalf of the developer and data protection. These roles must be distinguished; storage exclusively in Europe is not guaranteed.
The Landesamt für Digitalisierung, Breitband und Vermessung describes access logs including full IP addresses for its websites and services; it does not state a fixed general deletion period. The general web privacy notice of the Istituto Nazionale di Geofisica e Vulcanologia (INGV) generally states up to 365 days for web contact records, with exceptions for investigating computer-related offences. This general web retention period is not a separate deletion commitment for TINITALY elevation requests.
The SIM portal notice of the Ministero dell’Ambiente e della Sicurezza Energetica (MASE) states twelve months for browsing data used for security and diagnostics. This browsing-data period is not a deletion commitment for spatial PST preparation orders or their files.
The AWS data registry lists both Copernicus datasets as managed by Sinergise in the Frankfurt region (eu-central-1). This identifies the location of the public elevation rasters, not necessarily where access metadata is processed. Opening ArcGIS in the browser is subject to the Esri privacy statement, which describes international processing including the USA and transfer mechanisms such as the Data Privacy Framework and standard contractual clauses. The line layer’s EU address does not guarantee exclusively European processing.
Export, retention and control
When saving, exporting, printing or sharing, you choose the file, destination and recipients. Project files, PDF/SVG, CSV and calendar files may contain the selected project information. If you choose cloud storage or another app, that service handles further processing. You import calendar files into your calendar yourself; Grundwerk does not access the system calendar directly for this.
Local files and settings remain until deleted or replaced. Removed content may still exist in saved project versions, backups, exports or iCloud copies. Deleting a local project file or ending synchronization does not delete cloud projects already stored. Synchronizing again may upload content still present locally. According to Apple’s CloudKit data management guidance, Apple’s general data export does not include data from other apps’ CloudKit containers. You cannot delete complete cloud projects directly in Grundwerk. Use the central contact channel for access and deletion requests. Device backups are additionally managed through the available Apple functions. Stated provider retention periods apply to the specified data types; they are not a promise to delete all project content.
App / 009 · macOS 14+ · Updated: 23 October 2026
KeyType
Local entries and settings
KeyType stores passwords and single-line text snippets with names, categories, favourite status, target layouts and optional typing timing in the local macOS Keychain. Earlier values are retained in local history when entries change. Entries are not synced through iCloud. Language, global timing, shortcut and window layout are stored locally in app preferences.
Settings such as the shortcut, typing speed and start delay are stored locally on the Mac. This data is used to find stored entries and carry out explicitly authorized typing with the selected layout and speed.
Encrypted backup files
At your explicit request, KeyType exports all entries with current values, history and metadata, plus app settings, to an AES-256-GCM encrypted .keytypebackup file. The separate password is not stored. You choose the location; if you use a synced folder or network drive, further processing depends on that service. KeyType does not upload the file itself. Restoring applies the saved app settings; existing entries are kept and differing versions are added as copies.
Exported backup files remain after an entry is deleted and must be deleted separately from the chosen location.
System authentication and Accessibility
Typing a selected password requires explicit approval through native macOS authentication with Touch ID or the macOS login password. KeyType requires the macOS Accessibility permission to type. This permission can be managed and revoked in System Settings.
Deliberate input into the target field
After approval, KeyType sends the password locally to the target application as keyboard events, character by character. The user selects the target field beforehand. Pressing the shortcut again cancels typing in progress; KeyType does not send Enter automatically and does not use clipboard functionality.
A target application, such as a remote client, may further process this input or transmit it to a remote system. That processing depends on the selected target application, target system and their configuration.
No network or cloud functionality of its own
KeyType contains no network, cloud or telemetry functionality and does not transmit stored entries to the provider’s servers. Entries, history and settings are managed locally; this does not give website support remote access to the data.
Retention and deletion
The current password and earlier history values remain stored locally until the associated entry is deleted. Deleting an entry in KeyType removes its current value together with its associated history.
Website and voluntary contact
Local app storage is separate from contacting support voluntarily through the website. Anyone using the central contact channel sends their chosen message and sender details through the web server to the configured support mailbox. The Website and contact section applies to this process. Do not send real passwords, credentials or other sensitive content; use only synthetic test data to describe an issue. Further guidance is available on the KeyType support page.
App / 010 · iOS / iPadOS 16+ · Updated: 1 November 2026
Cuddle Chaos
Local game data and settings
Cuddle Chaos stores campaign progress, unlocked levels, the active round with its board, goals, remaining moves, the status of the one-time rescue paw and technical resume states, along with earned helpers, locally on your device. This includes room credits, levels already rewarded, unlocked cats, the cat room stage, fulfilled decorating wishes and visit or completion states for the extra attic room. The golden family paw is derived from fulfilled wishes and the saved win in level 300. These data support gameplay and resuming interrupted rounds.
Lasting supplies and the daily Cozy Wheel locally store quantities of yarn, feathers, Toy mice and Pillow swirls, the last claimed local calendar day, the reward pack, remaining packs and whether the reward has been acknowledged. This preserves rewards across interruptions and prevents a claimed daily spin from being awarded again. No server connection is needed.
The saved game and sound preference share a local file in the Application Support directory. The selected app language is stored separately in local app preferences. The provider has no remote access to these records.
Network, accounts and third parties
The app needs no user account and can be played offline. It contains no network communication of its own, cloud sync, advertising, analytics, tracking or crash-reporting services, or in-app purchases. Saved games and settings are not sent to the provider’s servers.
Depending on your device and backup settings, local app data may be included in an Apple-managed device backup. This is not a sync feature provided by Cuddle Chaos. Apple’s settings and privacy information also apply to device backups and restoration.
Permissions, retention and deletion
The app does not request access to location, contacts, camera, microphone, photos, calendars or health data. Music and game effects play from bundled audio files; no audio is recorded.
Saved games and settings stay on the device until replaced by further game actions or the app and its data are deleted from the device. The regular app offers no combined deletion or full reset function. Offloading the app does not delete its data. Manage existing device backups separately through the available Apple functions.
Website and voluntary support contact
When using the Cuddle Chaos support page and its contact form, you choose whether to send a message and what to include. Message content, sender details and optional technical information are sent through the web server to the configured support mailbox. The app does not send saved games or diagnostic reports automatically. The general website and contact information applies.
The Cast-Offs
Local game progress
The app stores confirmed solo victories and chapter completions, unlocked characters and equipment, your chosen squad of three, and shooting-range and racing personal bests in a local profile on your device. On Mac, this also includes window size, position and mode. These data support gameplay and are not automatically sent to the provider. A running battle or online session is not resumed after fully quitting the app.
Offline solo and optional online matches
Offline solo play needs neither a separate user account nor Game Center sign-in. When you deliberately use online features or accept an invitation, the iOS/iPadOS version uses Apple’s Game Center for sign-in, private invitations and connecting participants. Online modes are in development.
Data during an online session
The app processes Game Center player identifiers in memory to assign participants. Lobby, ownership, equipment, game commands and state data needed for a match are exchanged between participants through GameKit. These session data are not saved as an online profile; online results do not write to local solo progress. Apple’s Game Center privacy information and your Apple settings also apply to Apple’s processing.
Storage and deletion
The local profile remains until changed by gameplay or until app data are removed. On iPhone and iPad, deleting the app together with its data removes the local profile; offloading retains the data. On Mac, deleting the app alone does not necessarily remove its separate user-data folder. Contact support for help deleting local data. Manage device backups and data held by Apple separately through Apple.
Website and voluntary support contact
The app has no advertising, analytics or tracking services of its own and does not automatically send saved games or diagnostic reports to the provider. Information you enter in a voluntary support request is processed through the existing website form. The general Website and contact section applies. Do not send credentials or Game Center identifiers.