Bad Duck Studio logo

Bad Duck Studio

Official legal documents for WordWildWest

JogosWord Wild WestDocumentos
Inicio->Word Wild West->Privacy Choices and Consent Controls

Privacy Choices and Consent Controls

Effective date: 22 May 2026
Application: WordWildWest
Service Provider: BAD DUCK STUDIO, LDA
Contact: contact@badduckstudio.com

Open PDF Download PDF

This document explains the privacy choices that should be available in or through WordWildWest. Availability may vary by region, platform, age status, device settings and final app configuration.

1. First-start legal links

On first start, the Application should provide clear links to the Terms and Conditions, Privacy Policy, Cookie and Similar Technologies Policy, Regional Privacy Addendum and this Privacy Choices document. Where consent is required by law, legal links alone are not enough; consent must be requested before non-essential SDKs or tracking technologies run.

2. EU, EEA, UK and Switzerland consent controls

For users in the EU, EEA, UK and Switzerland, the Application should show a consent interface before using non-essential SDKs or Technologies that require consent. The interface should include:

  • Accept all;
  • Reject non-essential;
  • Manage choices;
  • clear categories and partner information;
  • a way to withdraw or change choices later in Settings.

Suggested categories:

  • Strictly necessary: always active;
  • Preferences;
  • Analytics and diagnostics;
  • Advertising and ad measurement;
  • Personalised advertising.

Because the Application may be offered to both children and adults, a neutral age screen or safe-by-default child-appropriate mode may be needed so that advertising, analytics and tracking choices match the user's age status.

3. United States privacy choices

Where applicable state privacy laws require it, the Application or website should provide a "Your Privacy Choices" or "Do Not Sell or Share My Personal Information" mechanism. This may include:

  • Opt out of targeted advertising;
  • Do not sell or share my personal information;
  • Limit use of sensitive personal information, if applicable;
  • Request access, deletion or correction;
  • Appeal a privacy request decision where required.

4. Brazil privacy choices

Brazilian users should be able to contact us to exercise LGPD rights, including confirmation of processing, access, correction, deletion, anonymisation/blocking, portability where regulated, information about sharing and withdrawal of consent. For children and adolescents, the Application should apply special care consistent with the LGPD, ECA and ECA Digital.

5. Australia and New Zealand choices

Australian and New Zealand users should be able to request access and correction, ask privacy questions, complain about privacy handling and manage personalised advertising choices where available. They may also use device privacy settings and advertising ID controls.

6. Account deletion

If the Application allows account creation, app-store releases should provide an in-app Delete Account option where required by platform rules. Users may also request deletion by emailing contact@badduckstudio.com. A web request path is available at Account Deletion Request. Account deletion may remove cloud saves, leaderboard entries, inventory, virtual currency and account-based entitlements, subject to legal and app-store exceptions.

7. Device controls

Users can also manage privacy through device and platform controls, including:

  • iOS App Tracking Transparency settings;
  • Android advertising ID and ads privacy settings;
  • Google account privacy settings;
  • Apple account and Game Center settings;
  • app permissions and notification settings;
  • app-store purchase and refund tools.

8. Support forms and notifications

Users may contact us through the Support Request page. The form sends the request to a Cloudflare Worker, which uses Resend to deliver the email to Bad Duck Studio. If an in-app support form or another external form provider is later enabled, users should be told what information is sent and which provider receives it. Local notifications should be controllable through device settings and, where practical, in-app settings.

9. Consent records

Where consent is collected, the Application should keep a compliance record that includes the consent version, date/time, region, interface shown and choices selected. These records should be retained as necessary to demonstrate compliance, prevent repeated prompts and respect user choices.

10. Contact

To exercise privacy rights or ask about privacy choices, contact contact@badduckstudio.com. Please include your country or region and enough information to locate your account or data.

Back to indexBack to topVer em português
© 2026 BAD DUCK STUDIO, LDA. All rights reserved.