Privacy policy

Local game data

Veilborn does not require a studio player account. Companions, progress, settings, local nicknames and purchase-delivery records are saved on your device. The game does not currently upload your saved game or provide studio cloud saves. Operating-system backups may independently retain app data.

There is no visual session replay. The app does not request contacts, camera, microphone or precise GPS location. Analytics, advertising and platform approval records are distinct from your local saved game.

Platform age and approval information

Where supported, Veilborn requests an age range/category and access or parental-approval status from Apple’s Declared Age Range or Google Play Age Signals services. It does not ask you to enter an exact date of birth. The game uses these signals to determine access, purchase eligibility and whether advertising and telemetry can be enabled. A platform decision may restrict access or purchases.

Age signals are kept in memory rather than included in saved games, analytics events or offers. When a significant-update approval flow is configured on Apple devices, the app may store update-approval questions/status in Apple’s iCloud key-value storage to remember platform approval across devices. This is not a cloud backup of gameplay. Apple processes platform and iCloud information under its privacy policy.

In the current configuration, advertising and Firebase Analytics/Crashlytics remain disabled for minors or when an adult age range cannot be confirmed. Enabling these services requires an age range whose lower bound is at least 18, and, on iOS, the required tracking authorization. This feature rule does not mean the whole game has an adults-only intended audience. Platform capabilities and decisions vary by OS version and region.

Tracking permission and advertising choices

On iOS, the current app can request Apple’s App Tracking Transparency permission before enabling the adult advertising/telemetry path. If authorization is denied or unavailable, that path remains disabled. If authorization is granted, advertising SDKs may access identifiers permitted by Apple, including the IDFA where available. Google consent messaging and available ad privacy choices are separate controls.

Android builds currently remove advertising-ID permissions and disable analytics ad personalization signals. This does not prevent all identifiers, IP-address processing or advertising-related data collection. Where presented, Google’s consent message lets you accept, decline or manage available ad choices before ad requests. You can revisit available choices using Settings → Ad privacy choices.

Analytics and diagnostics

When permitted by the controls above, Firebase Analytics records app opens and sessions and gameplay events such as starter selection, hatching, battles, progression, shop visits and completed purchases. Purchase events include product and displayed price rather than payment-card details or full receipts. Google may process app-instance identifiers, app/device details, usage events and approximate location inferred from network information.

Firebase Crashlytics records crashes and selected errors, including purchase-processing or save failures. Reports may contain stack traces, app state, device/OS information, app version, installation identifiers and recent analytics breadcrumbs. We do not deliberately attach your nickname, full saved game, email address or purchase receipt.

We use these records to understand play and improve reliability. Records use installation identifiers and are not necessarily anonymous. Google processes them under its privacy policy and Firebase privacy information. Collection follows the feature and permission controls described above.

Optional rewarded ads

Eligible players can choose AdMob rewarded ads for displayed benefits, including extra offline XP, a daily shop egg or quest-related rewards. Original offline XP is credited independently of the optional bonus. You can continue ordinary gameplay without choosing a rewarded ad. A reward is granted only when the advertising service confirms completion.

Google and its advertising partners may process IP addresses, approximate location, permitted device/ad identifiers, app/ad interactions and diagnostics to provide and measure ads and prevent fraud. This can be advertising-related tracking when enabled and permitted. Veilborn does not send your saved game, nickname or purchase receipts to AdMob. Availability depends on eligibility, choices, region and connectivity.

Purchases and verification

Optional purchases are processed by Apple’s App Store or Google Play. The platform handles payment details; Electron Game Studios does not receive payment-card information. The app receives product and transaction information to deliver content, restore eligible permanent purchases and prevent duplicate delivery. Purchase attempts can trigger a renewed platform age/approval check.

Apple purchases are checked through StoreKit on your device. Google Play transactions use native billing. The default configuration does not send Google purchase receipts to a studio verification server. If an Android release is configured with our HTTPS verification service, the app sends the product identifier, Google Play purchase token and app package name to that service to validate and deliver the purchase. Apple verification remains on the native StoreKit path. Verification records are used for delivery, fraud prevention and support rather than advertising profiles.

Store transaction records are retained independently by Apple or Google under their policies. The 30-day Double XP Pass is a one-time purchase that adds time, not an automatically renewing subscription.

Support, retention and international processing

If you email electron.cyber.secure@gmail.com, we receive your address and the information you send, such as device details, screenshots or order references. We use it to respond and investigate. Do not send passwords, payment-card details or full receipts.

Local progress and transaction records remain until removed or overwritten, subject to device backups. We retain support correspondence and any verification records while needed to handle requests, deliver purchases, prevent fraud and meet legal obligations. Google documents diagnostic retention in its Firebase privacy information; Analytics retention follows the property settings. Platform approval and store records follow their respective service settings and obligations.

Providers may process information outside your country. The studio policy explains purposes, applicable legal bases, sharing, international safeguards and security.

Your choices and younger players

You can decline optional ads, purchases, support contact and iOS tracking permission. Revisit available ad privacy choices and platform controls. Uninstalling stops future app collection from that installation but does not automatically delete historical provider records or support correspondence. Clearing app data may remove local progress; we cannot restore it from a studio cloud save.

Contact electron.cyber.secure@gmail.com to request access, correction or deletion, or ask about other applicable privacy rights. We may need limited verification and may be unable to link Firebase installation records to an email address. Apple and Google may retain independent records.

Veilborn is not directed to children under 13. Store content ratings and platform age/approval restrictions may differ by region. Purchases are subject to platform approval and parental controls; the current adult-only ad/telemetry rule is described above. If a child has sent information to support, contact us so we can address it.

Changes

We will update this page when Veilborn’s data handling changes and provide notice or obtain consent where required. See Veilborn support for help with gameplay or purchases.