YOUR PLAY. YOUR PRIVACY.

1. Who is responsible

Bane Digital LLC operates Frontline: Castle Siege under the Bane Digital Studio name. For privacy questions or requests, contact support@banedigital.com. Our studio website has a separate website privacy notice.

2. Information we handle

• Account information: an account identifier, sign-in provider identifiers, email and verification status where provided, profile information supplied by your chosen sign-in provider, and authentication/session information. A guest account has an assigned identifier even when no email is supplied.
• Age information: the birthday declaration and minimum eligibility records described below. We do not send your birthday to advertisers.
• Game progress: campaign progress, army, equipment, talents, resources, settings and saved game state.
• Gameplay and technical information: account-linked battle reports, game version, lineup, stage, outcome, duration, device/platform information, identifiers, IP addresses, timestamps, errors and service diagnostics used to operate, improve and protect the game.
• Purchase and reward information: product identifiers, account/customer identifiers, store transaction references, purchase history and status, receipts and reward-verification events. These verify delivery, recovery, refunds and duplicate prevention. We do not receive your full payment card details from an app store.
• Support information: messages and attachments you choose to send us.

The app stores session information, cached progress, settings and pending synchronization or transaction records on your device. Some settings remain only on that device. Information sent to our services is encrypted in transit.

3. Why we use it

We use information to sign you in, check age eligibility, save and synchronize progress, provide the features you request, deliver and recover verified purchases and rewards, handle support and privacy requests, understand game balance and reliability, and prevent fraud or abuse. Gameplay reports are not used to personalize advertising.

Where data protection law requires a legal basis, we rely on providing the service you request, our legitimate interests in improving and securing the game, compliance with legal obligations, or your consent where required. Contact us about the basis relevant to your situation.

4. Service providers and sharing

We use Supabase for authentication and cloud data, hosting and email providers, and RevenueCat for purchase verification and management. Apple and Google provide sign-in and handle their own store accounts and payments when you use those services. Google AdMob provides rewarded advertising, and Google Analytics for Firebase provides optional analytics and advertising measurement, as described below.

Information is shared as needed to provide these services, carry out your requests, protect the service, comply with law, or manage a business reorganization with appropriate protections. Providers may process information outside your country. Contact us for details about your data and applicable safeguards.

5. Optional advertising and choices

Supported native builds offer optional Google AdMob rewarded ads. You choose whether to request an ad; availability and rewards depend on a successfully completed, verified ad. An unavailable ad does not require a purchase.

Ads remain non-personalized for all ages. Non-personalized does not mean no data is processed: Google’s SDK may collect or share IP addresses and approximate location derived from them, device and account or advertising identifiers, ad/product interactions, and diagnostics or performance information for advertising, analytics and fraud prevention. Age and consent settings further limit processing where applicable. Your birthday is not included in ad requests.

Use Ad Privacy Choices in the Shop or privacy controls when that option is available. Your device also provides advertising privacy controls. Becoming an adult does not reset your existing choices or authorize personalized ads. Read how Google uses information from apps that use its services and Google’s privacy policy.

5a. Optional game analytics and advertising measurement

In supported Android versions, you can choose to share information with Google Analytics for Firebase to help Bane Digital LLC understand how Frontline: Castle Siege is used, improve the game and measure advertising results. This feature is off until you choose it. You can play and receive available rewards without enabling it.

If you opt in, Google receives an app-installation identifier, app and device information, approximate location derived from your IP address, and events about app use and game progress. These can include screens visited, sessions, tutorial and battle progress, results and duration, level changes, chest and reward activity, purchase details and checkout outcomes, ad activity and revenue, loading times and technical problems. Where advertising measurement is enabled, Google may also receive advertising identifiers and use permitted events to measure advertising results.

We do not send your email address, birthday, Bane account ID, saved-game file, full battle reports, messages or screen recordings through this analytics feature. Installation and device identifiers can still distinguish an app installation or device; this information is not necessarily anonymous.

Advertising measurement through this feature stays off for accounts aged 13–17, even if they choose game analytics. Their game analytics may still include in-game ad interactions. Personalized ads remain off for everyone. Optional rewarded ads have separate privacy controls and data processing, described in the advertising section above.

You can review or withdraw these choices in Profile → Account & Privacy → Your Privacy Choices → Game Analytics & Measurement. Choices apply to the account on that installation; review them on each device you use. Turning analytics off stops new collection through this feature. It does not by itself erase information already received by Google or stop the account, purchase, security or rewarded-ad processing described elsewhere in this policy.

To request access to or deletion of analytics information, contact support@banedigital.com or use Account & Data. We may need an analytics reference from the relevant installation to locate your records. We explain what we can identify and any remaining provider steps; we do not treat a local analytics reset as confirmation that Google has deleted previously received information.

To handle privacy requests, we keep a limited reference connecting your Bane account with its analytics installation identifiers in our restricted privacy systems. We do not send that account reference to Google through analytics or use it for advertising. We normally remove the lookup during routine cleanup once 16 months have passed since that installation's last recorded use. When a privacy request requires the reference, a restricted copy may be kept while the request and provider steps are handled and normally for up to 90 days after verified case closure. A completed deletion request can remove the active lookup sooner. These records do not preserve your saved game or full analytics history.

Our Google Analytics retention settings are two months for ordinary event data and 14 months for user-level data and key-event data. New analytics activity restarts the 14-month retention period for user-level data, so it can remain longer than 14 months from its original collection while you continue using analytics-enabled features. This reset does not extend the ordinary event-data period. Google removes expired data through its scheduled monthly process. Standard aggregated reports are not governed by these settings and may remain longer. Withdrawing consent stops new collection through this feature; requests to delete previously collected information are handled separately.

Read how Google uses information from apps that use its services and Google's privacy policy.

6. Age information and children

Frontline is offered to people aged 13 and older. We use the birthday you enter to check eligibility and apply age-appropriate privacy and advertising protections. Your birthday is not part of your public profile, gameplay reports or ad requests. We do not share it with advertisers.

If you are under 13 and no account has been created, we discard the birthday you entered. We may keep a short-lived eligibility-denial setting on your device until the next daily eligibility check to prevent immediate retries. It contains no birthday. An eligible birthday entered before sign-in is held temporarily on your device for up to one hour to finish sign-in and is cleared when that step ends or expires.

For players aged 13 to 17, we keep the birthday in a restricted account record to check eligibility and update age protections. We remove it when you turn 18, within 24 hours of that transition, and keep only a minimum adult eligibility record. If you are already 18 or older when you enter your birthday, we calculate that status without keeping the birthday in our account records. We also remove age records after 12 months without authenticated Frontline activity; you will need to provide a fresh declaration before continuing. Turning 18 does not give permission for personalized advertising. Our ads remain non-personalized for all players.

If we learn that an existing account belongs to a child under 13, we stop ordinary Frontline gameplay and advertising collection and begin removing the child's information promptly. We do not keep the account waiting for the child to turn 13. Our operating limit for removing active Frontline age and gameplay information is 24 hours, subject only to specific lawful, limited records described below. If the sign-in account serves other games, we restrict it and promptly review the appropriate scope of removal rather than silently deleting unrelated progress. We also contact relevant service providers for deletion. Privacy requests, reporting an age mistake and support remain available without continued gameplay.

7. Deletion and corrections

You can request deletion through Frontline's privacy controls or contact support@banedigital.com. You can also contact us to correct an age-entry mistake. In your first message, provide your request reference if you have one; please do not email a government ID or your full birthday. We may ask for the minimum information needed to verify and handle the request through an appropriate method.

Deleting Frontline data or the account includes its stored age information. Deleting gameplay reports alone does not delete age information or game saves. Once we accept a deletion request, we block new collection for that scope. We aim to remove the requested data from active systems within 24 hours and complete that first-party removal within seven days. Known under-13 accounts receive the faster handling described above. We aim to complete the remaining provider and backup steps within 30 days. If a step remains unfinished, we will explain the remaining work and next action; we do not report deletion as complete merely because we accepted the request.

Google's provider-side deletion process may take longer than our 30-day operating target. We will explain outstanding steps and any legally permitted extension. We do not report removal as complete solely because a request was submitted. We retain only the limited records needed for the purposes and periods described in this policy.

8. Recovery copies and limited records

Our database host provides a seven-day daily backup recovery window. Recovery copies are restricted to recovery purposes and are not used to resume normal processing of deleted information. Before a recovery copy is put back into service, we reapply deletions and age-information cleanup. Provider copies may remain subject to documented provider retention schedules. We verify backup disposition and applicable provider actions before issuing a final completion status.

We keep only limited records where needed to meet a legal obligation, handle a transaction dispute, protect the service or document a privacy request. These records are restricted to that purpose. Ordinary security records are kept for up to 30 days; relevant extracts for an active investigation may be kept for up to 90 days. Financial records follow the applicable accounting and tax period, generally three years after the relevant return was filed or due, with longer retention only where applicable. A specific legal hold may require longer retention. These exceptions do not justify keeping a birthday or gameplay history that is no longer needed. Privacy-case identifiers normally expire within 90 days after verified closure, and minimum deletion-suppression records remain only while needed to prevent restoration or delayed processing, plus up to 30 days. We review exceptions and delete the records when their specific purpose ends.

9. Your choices and rights

Use Profile → Account & Privacy for privacy controls and account deletion. Your Information also offers report-only and Frontline-data deletion, access and correction requests. You can request access, a copy, correction or deletion by contacting us through Account & data. Signing out or uninstalling does not delete cloud data.

Depending on your location, you may also have rights to portability, restriction, objection, withdrawal of consent, or a complaint to a data protection authority. We may need to verify your control of the account before acting. Never send a password or sign-in code.

10. Changes and contact

The date above identifies this policy version. We will provide additional notice or obtain consent when required for material changes. We use access restrictions and service-provider security controls; no method of storage or transmission is completely secure.

Contact Bane Digital LLC at support@banedigital.com and identify your request as relating to Frontline: Castle Siege.