Duck Outpost · Android

Privacy Policy

Effective date: September 18, 2026 · Last updated: September 18, 2026

This Privacy Policy explains how the independent mobile game Duck Outpost (“Duck Outpost,” “the game,” “we,” “us,” or “our”) handles information when you use its Android application.

The Android package is com.indieben.duckoutpost. The game currently has no user account system, no Facebook Login, and no in-app purchases. The presence of the Meta SDK does not mean that you log in to Facebook or that we receive access to your Facebook profile.

1. Information stored on your device

Duck Outpost stores game progress and preferences locally on your device, including progress, crew and weapon state, currencies, settings, and local playtest statistics. These local playtest records can include gameplay actions and timestamps. They are not automatically uploaded as part of the playtest export feature. They remain on the device until you reset the game, clear the app’s storage, or uninstall the app, subject to Android backup and restore behavior.

2. Analytics and technical information

The game uses Firebase Analytics and Meta App Events. Depending on your device, operating-system settings, SDK behavior, and permissions, these services may process:

We do not ask you to provide a name, postal address, phone number, or account profile inside the game. Analytics identifiers are not a Duck Outpost account and may not allow us to identify you by name.

3. Firebase Analytics (Google)

Firebase Analytics is used to understand game usage, sessions, active users, retention, tutorial completion, and gameplay progression. The current integration sends Firebase automatic analytics events and these game events: tutorial_start, tutorial_complete, game_start, run_start, run_end, and level_end. It also sets a highest-stage analytics property.

Google may process the related information as described in its Firebase privacy information and Google Privacy Policy.

4. Meta App Events

Duck Outpost uses the Meta/Facebook SDK and Meta App Events (Meta App ID 1293160969492429) to measure app installations, activations, and the effectiveness of user-acquisition or advertising campaigns. Automatic App Events and advertiser-ID collection are enabled in release builds when the Meta client configuration is present.

To avoid unnecessary duplication, only four custom gameplay events are currently also sent to Meta: game_start, run_start, level_end, and run_end. Meta may use event and device information to provide attribution, measurement, reporting, fraud prevention, and related services under the Meta Privacy Policy. Duck Outpost does not currently use Facebook Login.

5. Why information is processed

We use this information to:

Depending on the applicable law and the specific processing, the legal basis may be our legitimate interests in operating and improving the game, or consent where consent is required for analytics, advertising identifiers, or advertising measurement.

6. Service providers and disclosures

Information may be processed by Google/Firebase and Meta as described above. It may also be disclosed when required by law, to protect legal rights or safety, or in connection with a merger, acquisition, financing, or transfer of the game, subject to appropriate safeguards. We do not use the game to sell items through in-app purchases at this time.

7. Retention

Local game data remains on your device as described in Section 1. Analytics and App Events are retained according to our applicable service settings, the purposes described in this Policy, legal requirements, and the retention practices of Google/Firebase and Meta. Retention periods can vary by data type. Aggregated or de-identified information may be retained longer when it no longer reasonably identifies an individual.

8. Your choices and rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or portability of personal data, and to withdraw consent where processing relies on consent. You may also have the right to complain to your local data-protection authority.

Because Duck Outpost has no account or login, we may not be able to connect an email address to a particular pseudonymous analytics record. We will explain what can be identified and deleted after reviewing a request.

9. International processing and security

Google/Firebase and Meta may process information in countries other than your own. Their policies describe their international-transfer safeguards. We use reasonable measures intended to protect information, but no storage or transmission method is completely secure.

10. Children’s privacy

We do not knowingly ask children to provide direct personal details or create an account. If you are a parent or guardian and believe that a child’s information has been processed through Duck Outpost, contact us so that we can review the request.

11. Changes to this Policy

We may update this Policy when the game, its SDKs, or legal requirements change. The current version and effective date will be posted on this page.

12. Contact

For privacy questions or requests, email benjamin.dehant@gmail.com.