Alien Bloom - Privacy Policy - Terms & Conditions

Privacy Policy for Bestwood Studios LLC

Version: 1.1

Effective Date: May 7, 2026

Last Updated: July 7, 2026

Bestwood Studios LLC ("Bestwood", "we", "us", or "our") provides Alien Bloom, an online multiplayer freemium game (the "Game"). This Privacy Policy explains how we collect, use, disclose, retain, export, and delete information when you use:

- Alien Bloom

- https://www.alienbloom.com

- Official Alien Bloom community/social channels, including Discord, YouTube, X, Facebook, and TikTok

Controller: Bestwood Studios LLC

Contact: alienpokerhelp@gmail.com

Policy URL: https://sites.google.com/view/alienbloom/home

1. Introduction

Alien Bloom requires online backend services to operate account, entitlement, purchase, privacy, and gameplay state. We process information to run multiplayer features, account services, platform login, account linking, support operations, fraud/security controls, purchases/entitlements, account deletion/export workflows, and platform compliance.

Production online play requires a PlayFab-backed account/session. Alien Bloom does not provide a separate non-PlayFab online account mode.

2. Age Requirement and No Gambling

Alien Bloom is intended for players age 13 and older, or the minimum age required by applicable law, region, or platform rules. If you are under the age of legal majority in your country or region, you may use Alien Bloom only with permission from a parent or legal guardian. Alien Bloom is not intended for children under 13.

Alien Bloom does not offer real-money gambling, wagering, cash prizes, or monetary-value prizes. Monetization is limited to in-app purchases.

We do not independently verify every player’s age unless required by applicable law, region, or platform. If we learn that a child under 13 provided personal information in connection with Alien Bloom, we will review the account and take appropriate action, including restriction, deletion, or anonymization where appropriate.

3. Information We Collect

We collect the following categories of information, depending on how you use Alien Bloom and related services.

A. Account, login, and linking identifiers

- PlayFab account identifiers, including the PlayFabId used for the current login and, after approved account linking, an effective/original PlayFabId used for gameplay, entitlement, export, and deletion workflows

- Alien ID, which is a user-facing label for the PlayFab-backed account

- Commander ID or account display name associated with the effective account, where available

- PlayerId/gameplay ID used for multiplayer/game-session state

- PlayFab session and entity authentication artifacts processed transiently to authenticate the account and authorize online services

- Gameplay-token claims and related authentication validation results used to authorize direct gameplay endpoints

- Native platform sign-in context used to create or access a PlayFab-backed account, including Steam on Steam builds, Google Play Games on Android, and Apple Game Center on iOS

- Platform account/context data from Apple, Google, Steam, or other platform identity providers when used through those platforms

- Hashed platform identity records and account-alias records used to associate a native/current PlayFab account with an effective/original PlayFab account

- CustomId/ServerCustomId or device-derived guest login identifiers used in development, Unity Editor, expressly permitted fallback flows, or legacy/account-continuity flows where applicable

- Temporary account-link code hashes and link-code lifecycle metadata, including issuance, expiry, use, replacement, invalidation, attempts, and rate-limit status. Link codes currently expire after 10 minutes, and generation is limited to three fresh codes per UTC day.

- Linked-device and linked-account records used to associate approved devices/accounts

- Active-session records used to limit the same Alien ID from being active in more than one match/session at a time

- Device-link attempt records and related security/rate-limit metadata

- Effective-account relationship metadata, including provider, active/replaced status, timestamps, and safe relationship status used to determine whether linked-account export or deletion can be handled automatically

Alien Bloom’s production platform builds use the platform’s native sign-in service and then use Microsoft PlayFab for the game account and online session. Online play and account-backed features require a valid PlayFab-backed session.

Account linking switches which verified Alien Bloom account is treated as the effective account for gameplay, entitlements, export, and deletion workflows. It does not necessarily merge every historical record from two unrelated accounts. Under the current implementation, only verified active one-to-one linked account relationships are handled automatically. Ambiguous, stale, inactive, replaced, missing, self-referential, or inconsistent account-link relationships may require support review before linked data is exported or deleted.

B. Gameplay and multiplayer state

- Matchmaking queue, seat, participant, and active-session state

- World map state

- Battle state and space battle state, including card/action state needed for server-authoritative play

- Bot takeover state where applicable

- Victory/defeat outcomes, faction victory progression, spaceship unlock progression, and victory-award idempotency/retry records

- Abandoned/disconnected session state and other state needed to resume, resolve, recover, or secure online play

- Account gameplay status and progression/state needed to run online play

- Required tutorial status and completion records, including the required tutorial version, completed tutorial version, completion timestamp, and related account-routing status used to determine whether the account must complete the tutorial before accessing the normal Main Menu or online account-backed features

C. Consent and account-lifecycle records

- Privacy policy/terms consent records, including consent status, versions, timestamps, and withdrawal status

- Account deletion request records, including pending status, grace-period metadata, cancel/fulfillment metadata, duplicate-request status, and deletion-scope metadata

- Data-export request records, including request status, request/completion timestamps, duplicate-request status, and applicable rate-limit metadata

- Privacy-account index records used to locate and clean account records across supported account, gameplay, entitlement, and privacy systems

D. Purchases, entitlements, restores, and refunds

- Purchase and entitlement records needed to validate and provide in-app purchases

- Economy v2 and/or PlayFab inventory records used to provide inventory, entitlements, faction access, and unlocks, including FACTION_ALIENS / "The Aliens" entitlement

- Transaction-related metadata provided by platform/payment ecosystems, such as Apple transaction IDs/original transaction IDs/environment/status metadata, Google order/package/product metadata and purchase-token hashes, and Steam order/transaction/status/refund metadata where applicable

- Entitlement restore, reattachment, transfer, source-status, previous/current account-owner, revocation, and audit records used to validate platform/store ownership, prevent duplicate entitlement abuse, support account recovery, and maintain accurate entitlement state

- Restore Unlocks status, duplicate-request, cooldown, and daily-limit records used to protect restore workflows

- Refund, chargeback, restore, reconciliation, unresolved-refund, and audit records needed for platform, accounting, fraud-prevention, entitlement, support, and dispute workflows

E. Local device storage

- Local settings and preferences stored on your device, such as language, audio, consent/account-status information, and other local settings

- Local account/login cache values, including a durable device or guest identifier and last-login account hints, where used for guest login, account continuity, or privacy/account flows

- Local gameplay/session cache values, such as current world-map match/player/suit context, battle return/session context, and temporary selection state used to resume or present gameplay

- Local tutorial completion cache values, such as the latest tutorial version completed on the device, used to avoid unnecessary tutorial redirects and support offline or temporary backend-failure recovery on that device

- Local pending-purchase state held by Unity IAP or in-memory app state during purchase processing; platform SDKs may also maintain their own purchase caches

- Exported data files created by you using in-game Export Data, saved to a user-selected destination on Android/iOS or to a visible Documents fallback folder on Steam/PC. On Steam/PC, the current fallback location is Documents/Alien Bloom/Privacy Exports/.

- Temporary/cache files used during export/save and for game operation, reliability, diagnostics, and platform integration, including debug-log files only where debug diagnostics are enabled for a debug/development environment

F. Technical, diagnostic, rate-limit, and security data

- Service diagnostics, operational telemetry, and error/crash information

- Session-time and operational analytics events, including PlayFab Events where enabled

- Device/app/runtime context needed for troubleshooting, reliability, abuse prevention, and security, such as device model, OS/app/runtime version, locale/language, platform, and similar technical context depending on platform/provider defaults

- Server/API request metadata used for service operation and protection. This may include IP address, user agent, timestamps, endpoint names, response status, and request identifiers through platform, PlayFab, Azure, Application Insights, store, or hosting defaults

- Authentication/session artifacts, such as session tickets, entity tokens, and gameplay tokens, processed transiently for authentication/security operations

- Rate-limit, cooldown, idempotency, and cost-guard records, such as hashed guard keys, request counters, time windows, blocked-until timestamps, and safe outcome codes used to protect login, linking, gameplay, purchase restore, export, deletion, and consent workflows

4. How We Use Information

We use information to:

- Provide, maintain, and improve Alien Bloom online services

- Authenticate accounts and process multiplayer/game actions

- Operate platform-native login through Steam, Google Play Games, and Apple Game Center where applicable

- Create and maintain PlayFab-backed online sessions

- Perform server-authoritative account login and account-linking flows, including native platform login, temporary link-code verification, and verified linked-account association

- Determine the effective/original account used for gameplay, entitlements, export, deletion, and account recovery where a verified account link exists

- Determine whether a player has completed the currently required tutorial version and route incomplete accounts to the tutorial before allowing access to the normal Main Menu or online account-backed features

- Mint, validate, and enforce gameplay tokens for direct gameplay endpoints

- Operate matchmaking, world map, battle, space-battle, victory progression, and related game systems

- Provide in-app purchases, entitlements, refunds/revocations, restore/reconciliation, and support workflows

- Restore unlocks while preventing duplicate entitlement abuse

- Store and enforce consent choices

- Process account deletion/export requests and related support workflows

- Detect, investigate, and prevent abuse, fraud, cheating, unauthorized concurrent sessions, excessive requests, and security incidents

- Support account recovery, restore unlocks, support requests, account linking, and fraud/security checks tied to Alien ID/PlayFabId

- Comply with legal, accounting, platform, dispute, and regulatory obligations

5. Service Providers and Third Parties

We use service providers/processors to operate Alien Bloom, including:

- Microsoft PlayFab, including core account/backend services, CloudScript, inventory/economy, server APIs, and operational events where enabled

- Microsoft Azure services used for backend hosting, data storage, service security, diagnostics, privacy workflows, and operational monitoring

- Unity, including the Unity game engine/runtime and Unity In-App Purchasing used to integrate supported storefront purchases. Other Unity Services packages may be present in the project; if a Unity dashboard service is initialized and used to process player data, we will describe that active use in this Policy and applicable store disclosures.

- Platform operators and storefront ecosystems such as Apple, Google, and Steam

- Community/social platforms we use for communication and community engagement: Discord, YouTube, X, Facebook, and TikTok. These are community/social/marketing links/channels, not embedded gameplay identity providers unless explicitly integrated.

These providers process information under their own terms/policies and/or agreements with us, depending on the service relationship.

6. Analytics, Advertising, and Tracking

Based on the current implementation and privacy audit:

- We do not sell personal data.

- We do not intentionally use personalized advertising or targeted advertising in Alien Bloom.

- We do not intentionally use advertising SDKs, marketing attribution SDKs, IDFA/ATT tracking prompts, or cross-app tracking in Alien Bloom.

- Alien Bloom may use operational analytics, telemetry, diagnostics, and crash/error reporting to operate, secure, troubleshoot, and improve the Game.

- These are not intended for personalized advertising or cross-context behavioral advertising.

If third-party platforms process data in their own services, such as app store or social platform interactions, that processing is governed by those platforms' policies.

7. In-App Purchases and Restore Unlocks

Alien Bloom uses in-app purchases only.

We process purchase/entitlement information needed to validate transactions, grant items/features, prevent fraud/abuse, process refunds/revocations/restores/reconciliation, and support accounting/compliance requirements.

Alien Bloom uses PlayFab Economy v2 and/or PlayFab inventory systems to manage purchases, entitlements, faction access, and unlocks.

Platform stores, such as Apple, Google, and Steam, process billing and payments under their own policies.

When a valid platform/store purchase is restored or revalidated for an Alien Bloom account different from the account where the entitlement was previously granted, backend systems may attach or reattach the entitlement to the currently effective account and remove, revoke, or mark inactive the matching entitlement source for a previous account where appropriate. This is used to support account recovery and restore workflows while preventing duplicate entitlement abuse. If another active valid entitlement source remains for a previous account, access may be preserved consistent with backend-authoritative records and applicable platform/provider requirements.

Restore Unlocks is protected by duplicate-request and rate-limit controls. Under the current configuration, restore attempts are limited by a 60-second cooldown and a maximum of 10 attempts per day for the effective account. These limits may be adjusted for security, reliability, fraud prevention, support, or platform requirements.

Raw Apple receipts/JWS payloads, raw Google purchase tokens, payment card data, and platform-private billing details are not intentionally stored directly by Alien Bloom. Raw purchase proofs may be processed transiently to validate a transaction with Apple, Google, Steam, Unity, PlayFab, or Azure-backed services, then reduced to transaction IDs, token hashes, entitlement records, refund/reconciliation metadata, entitlement reattachment/transfer status, revocation status, source-status fields, and audit records needed for the purposes described above.

Steam purchase/refund records may include Steam order IDs, Steam transaction IDs, Steam ID hashes/prefixes, item IDs, currency/price configuration, status, restore/reattachment status, and refund/reconciliation metadata where applicable.

8. Gameplay, Multiplayer, and Account State

Alien Bloom is an online multiplayer game. Backend services process and store account and gameplay state needed to run online play, including matchmaking queues, active-session records, world map and battle systems, space battles, bot takeover logic, outcome/status records, victory progression awards, idempotency/retry records, and recovery records.

Gameplay production services use Microsoft Azure, PlayFab, and applicable platform services to operate and store online gameplay and account state. We do not publicly describe security-sensitive infrastructure topology or configuration details.

9. Diagnostic Logs and Security

We use diagnostic and security logging for operations and incident response. The game/backend may process technical logs, error diagnostics, security events, authentication validation results, matchmaking/session events, entitlement checks, link-code events, restore events, rate-limit events, and export/deletion lifecycle events.

Logs are used to operate the service, troubleshoot issues, prevent abuse, and secure the game. Current production-log controls are designed to reduce sensitive-data exposure.

Diagnostic and SDK error messages may include technical context needed to troubleshoot service issues. Production controls are designed to avoid intentional logging of raw secrets, tokens, receipts, raw link codes, full account dumps, full gameplay-state dumps, or full export/deletion payloads.

In production, we do not intentionally log raw secrets/tokens or full sensitive payloads, and we use masking/redaction, hashes, fingerprints, lengths, or presence flags for identifiers and sensitive fields where practical. This includes controls intended to avoid intentional production logging of:

- Raw secrets, auth tokens, session tickets, entity tokens, gameplay tokens, or auth headers

- Raw platform user IDs

- Raw receipts, Apple signed payloads, or raw Google purchase tokens

- Full account payloads or raw account dumps

- Full deletion/export payloads

- Raw link codes

- Full gameplay state payloads or full gameplay-state dumps

Session tickets, entity tokens, and gameplay tokens are processed transiently for authentication/security and are not intentionally logged in production.

Development/debug environments may include more verbose diagnostics than production. Debug overlays and debug-log files are intended for editor/development builds or explicitly enabled diagnostic environments, not ordinary production gameplay.

10. Data Retention

We retain data only as long as reasonably necessary for the purposes described in this Policy, including:

- Operating the Game and maintaining account/gameplay continuity while your account is active

- Security, fraud prevention, abuse prevention, anti-cheat, idempotency/retry safety, rate-limit enforcement, and incident investigation

- Legal, tax/accounting, dispute, and platform compliance obligations

- Enforcing/recording consent and account lifecycle decisions

- Retaining required tutorial completion status while the account is active so the Game can determine whether the account has completed the currently required tutorial version

- Retaining limited purchase, entitlement, entitlement-source, restore/reattachment/transfer, refund, chargeback, accounting, fraud-prevention, restore/dispute, and platform-compliance records as needed to provide purchased or unlocked digital content, prevent duplicate entitlement abuse, support account recovery, and comply with platform/legal requirements

- Retaining deletion lifecycle records as needed for processing, auditing, and disputes

Some operational records have explicit cleanup or expiry behavior, such as stale active sessions, link codes, queue/session cleanup, cooldown/rate-limit windows, and scheduled deletion workflows where enabled. Other account, gameplay, purchase/refund, and diagnostics records may remain until account deletion/anonymization, operational cleanup, platform/provider retention, or another applicable retention criterion applies.

Exported JSON files created through Export Data are saved locally first and remain on your device and/or chosen destination until you delete them.

Local device settings and cache data remain on your device until changed, cleared, or removed.

Where exact retention durations are not fixed in this policy, retention is based on the criteria above and applicable legal/platform requirements.

11. Account Deletion and Data Export

Request Alien Bloom Account Deletion Outside the App

You can request deletion of your Alien Bloom account without opening the Game by emailing:

alienpokerhelp@gmail.com

Use the subject line:

Alien Bloom Account Deletion Request

Include your Alien ID if available. Do not send passwords, purchase tokens, receipts, authentication tokens, or payment-card information.

We may ask for additional information to verify that you control the account before processing the request.

After verification, the account will enter the applicable deletion workflow. Account and associated gameplay data will be deleted or anonymized as described in this Privacy Policy. Limited purchase, refund, fraud-prevention, security, accounting, dispute, platform-compliance, and shared multiplayer records may be retained where permitted or required.

You may also initiate deletion from inside Alien Bloom through the account/privacy controls in the G.E.N.I.E. menu.

A. Account deletion lifecycle

When you request deletion:

1. We record the request.

2. The account may enter a pending deletion grace period.

3. While deletion is pending, online play/account features may be blocked.

4. If you log in during the grace period, pending deletion may be canceled.

5. After the grace period, we complete deletion and/or anonymization according to our systems and workflows.

Duplicate or repeated delete requests may return an existing pending, completed, or blocked status rather than creating another deletion job. Self-service delete requests are currently guarded to prevent duplicate destructive requests.

B. Linked-account deletion behavior

If you have a verified active one-to-one linked Alien Bloom account relationship, deleting your Alien Bloom account is intended to delete the covered account records for both the current/native account and the effective/original account across linked devices and platforms, subject to the retained exceptions described below.

For example, if a verified active linked account connects a Steam, Google Play Games, or Apple Game Center login to the same Alien Bloom account, the deletion workflow is intended to remove the covered Alien Bloom account records for that verified linked account relationship, not just the device or platform from which the request was started.

If account-link records are inconsistent, ambiguous, stale, inactive, replaced, missing, self-referential, involve multiple incoming links, or cannot be safely verified, automated linked-account deletion may be blocked or marked for support review. In those cases, we may require additional verification before deleting linked records.

Deleting an Alien Bloom account does not delete your external Apple, Google, Steam, Microsoft, Unity, Discord, YouTube, X, Facebook, or TikTok account. Platform/store records controlled by those providers remain subject to their own policies and account controls.

C. Retained exceptions and implementation limits

Even after deletion/anonymization, we may retain limited information where permitted or required for legal obligations, security, fraud prevention, accounting, disputes, platform compliance, transaction records, or records involving other players.

Deletion workflows are intended to cover PlayFab account data and current Azure-backed account/gameplay systems where reasonably linked to the verified account or verified active linked-account relationship. Some mixed-user multiplayer records, diagnostic records, provider logs, platform store records, and records not reasonably linkable to the verified account may be retained, redacted, summarized, naturally expired, or handled through manual/legal review rather than immediately deleted.

D. Data export scope and limitations

To support privacy rights and data portability, players can use Export Data from the in-game G.E.N.I.E. menu.

Export creates a JSON file named like AlienBloom_DataExport_yyyyMMdd_HHmmss.json.

The self-service Export Data function is limited to one newly generated backend export per 24-hour period. A repeated request during that period may return the existing request status or re-save the latest available local export instead of generating a new backend export. A cached/local export may keep the generatedAt timestamp and contents from when it was originally created. If no cached export is available during the 24-hour period, you may need to try again later.

The export JSON is structured and machine-readable, and may include:

- Export metadata and explanatory limitations

- Account identifiers, such as Alien ID/display name, Commander ID/display name, PlayFabId/internal account identifiers, effective/original account identifiers where applicable, and gameplay PlayerId where available

- Native-account relationship metadata for verified linked accounts, such as provider, active/replaced status, timestamps, and safe relationship status

- Hashed identity metadata associated with account-link records

- Consent records, including privacy/terms status, accepted versions, timestamps, withdrawal/deletion status where applicable

- Export request records, including status and timestamps where applicable

- Deletion lifecycle records, including request/pending/cancel/finalized metadata where available

- Required tutorial completion status, such as required tutorial version, completed tutorial version, completion timestamp, and related account-routing/completion metadata where available

- Gameplay/account summaries and statistics available through the self-service export path

- Classic inventory data and Economy v2 inventory/entitlement data, such as item ID, display name, count, and available catalog/collection metadata, including purchase/entitlement summaries where available

- Explanatory metadata about export generation, processing summaries, recipients, retention, excluded categories, and support-required conditions

Where a verified active one-to-one linked account relationship exists, Export Data is intended to include data reasonably available through the implemented export path for the current/native account and the effective/original account. If the account-link relationship is inconsistent, ambiguous, stale, inactive, replaced, missing, self-referential, involves multiple incoming links, or cannot be safely verified, the export may identify the linked portion as support-required rather than disclose data from an account whose control cannot be established.

Export does not include raw secrets/tokens, service credentials, raw receipts, raw Google purchase tokens, platform billing credentials/details, JWTs, auth headers, PlayFab session tickets/entity tokens, gameplay tokens, raw platform user IDs, raw link codes, internal abuse/security signals, or other players' data.

The in-game export is a user-facing self-service export of data reasonably available through the implemented export path. It is not necessarily identical to a full provider-level PlayFab GDPR export or every record held by every processor/provider. You may contact us for additional access requests, and we may use provider tools, manual review, or support workflows where appropriate.

Export scope may still be limited by:

- Security/integrity safeguards

- Data about other users

- Trade-secret or anti-abuse protections

- Legal, platform, or technical constraints

- Data not reasonably linked to your verified account

- Provider-controlled logs, billing records, or platform account records

E. Export file delivery and saving

- On Android, the game opens the system Save To picker where available so you can choose where to save the exported JSON.

- On iOS, the game opens Save to Files or a document picker where available so you can choose where to save the exported JSON.

- On Steam/PC, the game saves or re-saves the export to Documents/Alien Bloom/Privacy Exports/ and may reveal the file or show the saved path.

- If a system save picker is cancelled, unavailable, or fails, the game shows a success, cancellation, or failure message as appropriate and may use an appropriate platform fallback.

- You control the destination and onward storage after saving or sharing the exported file through a selected platform or app.

- The game does not intentionally copy exported JSON file contents to the clipboard.

12. Your Privacy Rights

Depending on your location, you may have rights to:

- Access personal information we hold about you

- Request correction of inaccurate information

- Request deletion of your information

- Withdraw consent where processing is based on consent

- Request export/portability of data we can provide in a structured format

- Opt out where applicable under local law

How to request: email alienpokerhelp@gmail.com

We may take reasonable steps to verify identity before fulfilling requests. Where an account is linked across platforms, we may use verified account-link information to process export and deletion requests for the covered linked Alien Bloom account records. Where account-link records are ambiguous or cannot be safely verified, we may require additional support review.

Withdrawing consent records the withdrawal, signs the player out, and disables online account and gameplay features until required consent is granted again. Duplicate or in-flight withdrawal requests may return the existing withdrawal status without creating another record.

If we deny a request, you may ask us to review/appeal that decision by replying to our decision email or contacting alienpokerhelp@gmail.com with "Privacy Appeal" in the subject line.

13. GDPR / EEA / UK / Switzerland Legal Bases

For users in the EEA, UK, Switzerland, or other regions with GDPR-style laws, our legal bases may include:

- Contract necessity: to provide account login, native platform sign-in, account linking, gameplay-token authentication, online multiplayer gameplay, matchmaking, world map state, battle and space battle systems, purchases, entitlements, unlocks, support features, deletion/export tools, and other requested game services.

- Consent: to record privacy/terms consent where required, process consent withdrawal, and support optional community or marketing interactions where applicable.

- Legitimate interests: to operate and secure the Game, prevent fraud, cheating, abuse, unauthorized concurrent sessions, excessive requests, and security incidents, diagnose service problems, improve reliability, provide support, maintain operational analytics, and preserve idempotency/retry/rate-limit records.

- Legal obligation: to comply with tax, accounting, platform, dispute, regulatory, and lawful request obligations.

- Vital/public interests are generally not expected to apply to Alien Bloom's ordinary processing.

14. U.S. State Privacy Rights

California-style disclosures (CPRA/CCPA context)

- In the preceding 12 months, we may have collected and disclosed to service providers/processors the categories described in this Policy, including identifiers, account and gameplay state, linked-account metadata, hashed platform identity metadata, purchase and entitlement records, refund/reconciliation records, consent/export/deletion records, local settings where applicable, diagnostics/security data, rate-limit/cost-guard records, and operational analytics.

- We disclose these categories to service providers/processors for service operation, security, support, compliance, purchases/entitlements, diagnostics, and product improvement.

- Sale/sharing for cross-context behavioral advertising: we do not sell personal information and do not intentionally share personal information for cross-context behavioral advertising.

- Sensitive information: we do not intentionally collect sensitive personal information such as precise geolocation, government identification numbers, biometric data, health information, or similar sensitive categories for the purpose of inferring characteristics. If any information is treated as sensitive under applicable law, we use it only as permitted for service operation, security, fraud prevention, compliance, support, or other allowed purposes. We do not sell or share sensitive personal information for cross-context behavioral advertising.

- You may request access, deletion, correction, and, where applicable, limit/use controls available under law.

- We will not discriminate or retaliate against you for exercising privacy rights, as required by applicable law.

- We will respond to privacy requests within the time required by applicable law. If additional time is needed, we may notify you as permitted by law.

Virginia-style appeal (VCDPA context)

If we deny your request, you may appeal by contacting alienpokerhelp@gmail.com with "VCDPA Appeal" in the subject line. We will review and respond within timelines required by applicable law.

15. International Users

Alien Bloom is operated from the United States, and our providers may process information in the United States and other countries. Where applicable law requires a transfer mechanism, we and/or our providers use the mechanism applicable to that service and transfer. Contact us for information about safeguards relevant to your request.

16. Children and Minors

Alien Bloom is intended for players age 13 and older, or the minimum age required by applicable law, region, or platform rules. If you are under the age of legal majority in your country or region, you may use Alien Bloom only with permission from a parent or legal guardian. Alien Bloom is not intended for children under 13.

We do not independently verify every player’s age unless required by applicable law, region, or platform. If we learn that a child under 13 provided personal information in connection with Alien Bloom, we will review the account and take appropriate action, including restriction, deletion, or anonymization where appropriate. If you believe a child under 13 provided personal information in connection with Alien Bloom, contact us at alienpokerhelp@gmail.com.

17. Security

We use technical and organizational measures designed to protect information, including access controls, monitoring, secure credential and secret-management practices, and other safeguards appropriate to the nature of the information we process. No system is perfectly secure, and we cannot guarantee absolute security.

18. Third-Party Links and Community Platforms

Our website, Game, or community presence may include links to third-party services. Their privacy practices are governed by their own policies.

Official platforms currently include Discord, YouTube, X, Facebook, and TikTok. These are external links/community channels unless a feature clearly says it is integrating with one of those services.

19. Changes to This Policy

We may update this Privacy Policy from time to time. We will post updates and revise the "Last Updated" date. If changes are material, we may provide additional notice in-game, on our website, or through platform update channels as appropriate.

20. Contact Us

Bestwood Studios LLC

Email: alienpokerhelp@gmail.com

---

Third-party privacy pages for convenience:

- Apple: https://www.apple.com/legal/privacy

- Google: https://policies.google.com/privacy

- Steam: https://store.steampowered.com/privacy_agreement/

- Unity: https://unity.com/legal/privacy-policy

- Microsoft: https://privacy.microsoft.com/

- Discord: https://discord.com/privacy

- YouTube / Google: https://policies.google.com/privacy

- X: https://x.com/en/privacy

- Facebook: https://www.facebook.com/privacy/policy

- TikTok: https://www.tiktok.com/legal/page/us/privacy-policy/en

Alien Bloom Terms and Conditions

Version: 1.1

Effective Date: May 7, 2026

Last Updated: July 7, 2026

These Terms and Conditions ("Terms") are a legal agreement between you and Bestwood Studios LLC ("Bestwood," "Company," "we," "us," or "our") for your access to and use of Alien Bloom and related services.

Alien Bloom is an online multiplayer freemium game that depends on online backend services.

By downloading, installing, accessing, or using Alien Bloom (the "Game"), our website at https://www.alienbloom.com, and/or our official community channels (including Discord, YouTube, X, Facebook, TikTok, and other official channels we operate), you agree to these Terms.

If you do not agree, do not use the Game or Services.

1) Company and Service Overview

Bestwood Studios LLC provides Alien Bloom and related online services.

Alien Bloom includes fictional game mechanics and online multiplayer systems, account systems, progression systems, social/community channels, and optional in-app purchases. The current paid in-app purchase unlock is "The Aliens" / FACTION_ALIENS. Platform or store product identifiers may vary by platform, environment, or store configuration and are maintained through the applicable storefront and support systems.

2) Eligibility (13+)

Alien Bloom is intended for players age 13 and older, or the minimum age required by applicable law, region, or platform rules. If you are under the age of legal majority in your country or region, you may use Alien Bloom only with permission from a parent or legal guardian. Alien Bloom is not intended for children under 13.

Alien Bloom may not independently verify your age unless required by applicable platform, regional, or legal requirements.

3) No Real-Money Gambling or Wagering

Alien Bloom does not provide real-money gambling, wagering, cash prizes, or monetary-value prizes.

Any terms in the Game such as "chips," "hexes," "bet," "raise," "all-in," "pot," or similar terminology describe fictional in-game mechanics only. They do not represent real currency, real wagering, or any right to money or monetary-value prizes.

Alien Bloom is not intended to provide personalized advertising, targeted advertising, or cross-context behavioral advertising. Operational analytics, diagnostics, and security logging may be used as described in these Terms and our Privacy Policy.

4) License to Use the Game

Subject to your compliance with these Terms, Bestwood grants you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use Alien Bloom for your personal, non-commercial entertainment use.

You may not copy, modify, distribute, sell, lease, sublicense, reverse engineer, decompile, disassemble, or otherwise exploit the Game or Services except:

(a) as expressly permitted by these Terms; or

(b) to the limited extent non-waivable applicable law expressly permits.

5) User Content and Content Creation Permission

We permit players and creators to make and share content featuring Alien Bloom gameplay, including videos, livestreams, screenshots, reviews, guides, social posts, and monetized creator content.

This permission is subject to these Terms and any published community/platform rules.

You keep ownership of your original commentary and creative expression, but Bestwood and its licensors retain all rights, title, and interest in Alien Bloom, including all game assets, characters, art, audio, code, trademarks, and related intellectual property.

You may not claim ownership of Bestwood assets or distribute standalone game assets outside normal gameplay capture/use.

6) Accounts and Identifiers

Alien Bloom may use one or more account/identity models, including:

- Native platform sign-in for production platform builds: Steam on Steam builds, Google Play Games on Android, and Apple Game Center on iOS

- Guest or device-derived sign-in flows, which may use CustomId, ServerCustomId, or similar backend/device login identifiers in development, expressly permitted fallback, legacy, or account-continuity flows

- PlayFab/account identifiers (including PlayFab IDs)

- Alien ID, which is a user-facing label for the account identifier

- Commander ID or other effective display identity associated with the effective Alien Bloom account, where available

- Gameplay-specific PlayerId identifiers used for online multiplayer state

Production online play and account-backed features require a valid PlayFab-backed account/session. Alien Bloom does not provide a separate non-PlayFab online account mode.

Linked devices may be associated with an Alien ID, and temporary link codes may be used to connect a current/native account or device to an effective/original Alien Bloom account. Link codes currently expire after 10 minutes, and generation is limited to three fresh codes per UTC day. These limits may change for security, abuse prevention, reliability, support, or platform requirements.

For a verified active one-to-one account link, the effective/original account may be used for gameplay, entitlements, Export Data, Delete Data, and account recovery workflows across linked devices or platforms. Account linking is not a general merge of unrelated accounts and does not guarantee that every historical record, purchase, entitlement, item, statistic, or progression record from separate accounts will be combined.

Ambiguous, stale, inactive, replaced, missing-target, self-referential, multiple-incoming, or otherwise inconsistent account-link relationships may be blocked, excluded from automated linked-account actions, or require support review and additional verification.

We may impose an operational limit on the number of linked devices per Alien ID. That limit may vary based on security, platform, service, or configuration requirements. We may reject or revoke links for security, abuse, fraud, or platform compliance reasons.

You are responsible for activity on your account or device access path, and for maintaining appropriate security of your device(s), credentials, linked platform accounts, and link codes.

You may not sell, share, trade, transfer, or grant unauthorized access to your account.

Depending on your location, you may have rights to request access, export, correction, deletion, or appeal related to account data. These requests are handled through our Privacy Policy process and support contact at alienpokerhelp@gmail.com.

7) Online Service Dependency and Required Updates

Alien Bloom is an online multiplayer game that depends on live services and compatible software.

Use of the Game may require, at minimum:

- Supported app/client version

- Compatible device/platform environment

- Internet connectivity

- Availability of backend and infrastructure services, including PlayFab, Azure, and relevant platform services

Production platform login uses Steam sign-in on Steam builds, Google Play Games sign-in on Android, and Apple Game Center sign-in on iOS, followed by creation or validation of the PlayFab-backed account/session required for online play.

Account login, account linking, Restore Unlocks, entitlement verification, Export Data, Delete Data, matchmaking, and active-session controls require live backend services.

Same Alien ID concurrent active session/match restrictions may prevent launching or joining another match until the current session is left, closed, or cleared by backend systems.

We may require updates, patches, or version changes to continue accessing some or all features.

Alien Bloom may require completion of the current required tutorial version before allowing access to the normal Main Menu, online play, matchmaking, or other account-backed features. Tutorial completion may be recorded server-side for the effective Alien Bloom account and may also be cached locally on the device. If the required tutorial version changes, or if completion cannot be verified, you may be required to complete or repeat the tutorial before accessing affected features.

8) Backend-Authoritative Gameplay and Finality

Alien Bloom gameplay is backend-authoritative. To the fullest extent permitted by applicable law, backend/server records are authoritative for online game state and outcomes, including but not limited to:

- Action legality/validation

- Turn timing and timers

- World map state, territory ownership, matchmaking, match/battle actions, and sequencing

- Bot takeover and abandonment handling

- Victory/defeat determinations

- Match closure and result recording

- Account/gameplay state persistence and reconciliation

- Account login/session validation

- Account linking and linked-device status

- Required tutorial version, tutorial completion status, tutorial completion timestamp, and tutorial-gate eligibility

- Entitlement verification, restore checks, and reconciliation

- Active-session guard and duplicate-session prevention

- Leave-match, abandonment, bot takeover, and re-queue eligibility

Client-side displays may lag, desync, or differ temporarily from backend state. Backend records remain authoritative, subject to correction, reconciliation, security review, or support/administrative action where appropriate.

9) Virtual Goods, In-App Purchases, and Entitlements

Alien Bloom uses in-app purchases only. We do not currently offer subscriptions or external-payment purchases in the Game.

Alien Bloom may offer virtual goods, currencies, items, cosmetics, entitlements, faction unlocks, or other digital content ("Virtual Goods") via in-app purchases. The current paid unlock is "The Aliens" / FACTION_ALIENS.

All Virtual Goods are provided as limited-license digital content, not as personal property. Virtual Goods are:

- Non-transferable

- Non-redeemable for cash

- Not exchangeable for real money

- Without cash value or monetary-value prize rights

Virtual Goods and entitlements are generally account-bound to the Alien ID/account where granted, except where platform/provider records, Restore Unlocks, account recovery, fraud prevention, refund/revocation handling, backend reconciliation, or applicable platform/provider rules require or allow a different result.

Platform billing and payment processing are handled through the applicable platform/store where available, including Apple App Store in-app purchase, Google Play Billing, and Steam Wallet / Steam microtransaction APIs. Bestwood does not receive or store your payment card details or platform-private billing credentials.

Bestwood and service providers (including PlayFab and Azure) may process entitlement and inventory metadata (including Economy systems) to grant, verify, restore, reattach, transfer, revoke, secure, and protect purchased or unlocked content. For Steam, Alien Bloom backend services may store limited order, transaction, status, refund, restore, reattachment, transfer, revocation, and reconciliation metadata to validate, restore, revoke, prevent fraud/abuse, support accounting, resolve disputes, and meet legal/platform compliance needs.

Restore Unlocks checks the currently logged-in account/Alien ID and applicable platform/provider records. If Apple, Google, Steam, or another supported platform verifies that the current platform/store account owns a purchased entitlement, Bestwood backend systems may attach or reattach that entitlement to the currently logged-in Alien Bloom account. To prevent duplicate entitlement abuse, restoring a valid purchase to a different Alien Bloom account may cause the same entitlement to be removed, revoked, marked inactive, transferred, or otherwise no longer available on a previous Alien Bloom account, unless another active valid entitlement source remains for that previous account.

Restore Unlocks is not a general account-merge tool. It does not merge separate accounts, progress, match history, statistics, devices, or unrelated Virtual Goods. It only restores or reconciles eligible platform-backed entitlements according to backend-authoritative records and applicable platform/provider rules.

Restore Unlocks is protected by duplicate-request and rate-limit controls. Under the current configuration, restore attempts are limited by a 60-second cooldown and a maximum of 10 attempts per day for the effective account. These limits may change for security, abuse prevention, reliability, support, or platform requirements.

Account linking does not guarantee merging purchases, progress, Virtual Goods, or entitlements from multiple separate accounts. Entitlements may remain with, move to, or be restored to an Alien ID/account according to platform/provider ownership records, backend-authoritative entitlement records, Restore Unlocks, refund/revocation status, account recovery, fraud-prevention, and service-integrity requirements.

To the fullest extent permitted by applicable law, we may modify, rebalance, disable, remove, replace, transfer, revoke, or discontinue Virtual Goods or related features as needed for gameplay balance, exploit prevention, security, fraud prevention, refund/revocation handling, legal/platform compliance, or service operations.

10) Purchases, Billing, and Refunds

Purchases and payment processing are handled by the applicable platform/store and are subject to that platform's terms and policies, including where applicable Apple, Google, Steam, and other platforms where Alien Bloom is made available.

Refund eligibility, billing disputes, and payment reversals are generally determined by the platform/store that processed the purchase.

Purchases may require platform verification and backend entitlement checks.

Failed, canceled, refunded, charged back, revoked, voided, or otherwise reversed payments may result in entitlement removal, rollback, transfer, revocation, or restriction where allowed by applicable law and platform rules. If another active valid entitlement source remains, the backend may preserve access consistent with its authoritative records and platform/provider requirements.

If a purchase entitlement has been restored, reattached, or transferred between Alien Bloom accounts, later refund, chargeback, revocation, voiding, or reversal handling may apply to the account where that entitlement is currently active and/or to other accounts associated with the same platform/provider purchase record, subject to backend-authoritative records, applicable platform/provider rules, and any other active valid entitlement sources.

Bestwood does not control third-party platform refund determinations.

11) Data Export and Portability

Where available for an authenticated account, G.E.N.I.E. Export Data provides a machine-readable JSON account data export.

Export Data is currently limited to one newly generated backend export per 24-hour period. A repeated request during that period may return an existing request status or re-save the latest available local export instead of creating a new backend export. A cached/local export may keep the generatedAt timestamp and contents from when it was originally created. If no cached export is available during the 24-hour period, you may need to try again later.

For a verified active one-to-one linked-account relationship, Export Data is intended to include data reasonably and safely available through the implemented export path for both the authenticated current/native account and the effective/original Alien Bloom account. If the relationship is ambiguous, stale, inactive, replaced, missing-target, self-referential, multiple-incoming, inconsistent, or otherwise cannot be safely verified, linked portions may be blocked or marked for support review rather than disclosed.

Exports are designed to exclude raw secrets, credentials, JWTs, auth headers, PlayFab tickets/entity tokens, raw receipts, raw Google purchase tokens, platform-private billing details, internal abuse/security signals, and other players' personal data or private gameplay data. Purchase information may be represented through limited transaction, entitlement, inventory, or refund/reconciliation metadata where appropriate.

Export Data may include required tutorial completion status and related metadata, such as the required tutorial version, completed tutorial version, completion timestamp, and whether tutorial completion was available through the implemented export path.

Export files use the filename pattern AlienBloom_DataExport_yyyyMMdd_HHmmss.json.

On Android, the Game uses the system Save To picker where available.

On iOS, the Game uses Save to Files or a document picker where available.

On Steam/PC, the Game saves or re-saves the export to Documents/Alien Bloom/Privacy Exports/ and may show or reveal the saved location.

If a system save picker is cancelled, unavailable, or fails, the Game may show a success, cancellation, or failure message as appropriate and may use an appropriate platform fallback.

After you save or share an export, the destination, onward storage, and sharing controls are managed by you and/or your selected platform or app.

12) Account Deletion and Effects

Account deletion and privacy lifecycle handling are described in our Privacy Policy Version 1.1.

When deletion is requested, an account may enter a pending-deletion/grace state. During this state, online features or login may be restricted. Logging in during the grace period may cancel deletion where supported by current workflows.

For a verified active one-to-one linked Alien Bloom account relationship, Delete Data is intended to delete or anonymize the covered Alien Bloom records for both the authenticated current/native account and the effective/original account across linked devices and platforms. This may include covered account, gameplay, progression, entitlement, purchase/refund, linked-device, account-link, privacy-index, and privacy-lifecycle records, subject to the retained exceptions described in the Privacy Policy.

If an account-link relationship is ambiguous, stale, inactive, replaced, missing-target, self-referential, multiple-incoming, inconsistent, or otherwise cannot be safely verified, automated linked-account deletion may be blocked or require support review and additional verification. We will not automatically delete another account merely because an unsafe or unverified relationship record references it.

Deleting Alien Bloom data does not delete your external Apple, Google, Steam, Microsoft, Unity, Discord, YouTube, X, Facebook, TikTok, or other third-party account. Records controlled by those providers remain subject to their own terms, policies, and account controls.

After final deletion/anonymization, you may permanently lose access to account-linked services, progression, Virtual Goods, entitlements, linked-device associations, account-linking records, match history, Alien ID, Commander ID/effective display identity, and online gameplay state, subject to limited retained exceptions described in the Privacy Policy (for example, legal, security, fraud, accounting, dispute, or platform compliance needs).

Linking another device does not avoid account deletion restrictions or outcomes.

As explained in the Privacy Policy, durable local device identifiers and user-created export files may remain on a device unless you or the device operating system clears them.

13) User Conduct Rules

You agree to use Alien Bloom, any in-game communication features that may be available, and related official community or social channels lawfully and respectfully.

You must not:

- Cheat, exploit bugs, bot, script, or use unauthorized automation

- Use or distribute modified clients or unauthorized third-party tools

- Manipulate packets, API calls, requests, receipts, purchase tokens, restore-unlocks flows, account identifiers, session tickets, or server communications

- Submit fake receipts, replay purchase tokens, reuse stale purchase proofs, or abuse refund/reversal or restore-unlocks workflows

- Perform replay attacks, stale request abuse, request forgery, or timing abuse

- Misuse account-link codes, share link codes publicly, use another person's link code without permission, or attempt unauthorized account/device linking

- Attempt to bypass linked-device limits

- Attempt to bypass active-session guard or same Alien ID concurrency controls

- Attempt to bypass, disable, or undermine PlayFab/Azure/backend validation, login flows, or security controls (including ServerCustomId/CustomId handling)

- Reverse engineer/decompile/disassemble except to the limited extent applicable law requires permission

- Sell, share, trade, hijack, or obtain unauthorized account access

- Harass, threaten, stalk, or abuse others

- Post unlawful content, spam, malicious links, or disruptive content

- Disrupt service integrity, matchmaking, community spaces, or other users' experience

14) Enforcement and Remedies

To the fullest extent permitted by applicable law, if we believe you violated these Terms or compromised game integrity, we may take action directly or through our service providers or platform operators, where available, including:

- Warnings

- Content removal/moderation

- Temporary or permanent suspension

- Account termination

- Matchmaking or feature restrictions

- Rollback/removal of illicit progress, entitlements, or Virtual Goods

- Revocation of linked devices, invalidation of link codes, or restriction of account linking

- Session clear/closure actions and re-queue restriction actions

- Technical blocking of access, devices, or accounts where available through our systems, service providers, or platform operators

- Referral or reporting to platform operators or law enforcement where appropriate

Enforcement and integrity reviews may rely on backend records, security/diagnostic logs, entitlement and inventory records, platform/store records, gameplay-integrity metadata, and rate-limit, cooldown, idempotency, and cost-guard records.

We may act with or without prior notice depending on severity, risk, and operational constraints.

15) Logging, Diagnostics, and Security Operations

We may use operational analytics, telemetry, diagnostic logs, crash/error reporting, and security logging for service operations, fraud/abuse prevention, support, troubleshooting, incident response, gameplay integrity, reliability, and product improvement.

We may create and use rate-limit, cooldown, duplicate-request, idempotency, and cost-guard records, including hashed guard keys, request counters, time windows, blocked-until timestamps, and safe outcome codes, to protect login, account linking, gameplay, purchases, Restore Unlocks, export, deletion, consent, and other service workflows.

Production controls are designed to avoid intentional logging of raw secrets, credentials, auth tokens, JWTs, auth headers, PlayFab tickets/entity tokens, session tickets, raw receipts, raw Google purchase tokens, raw link codes, full account dumps, full gameplay-state dumps, or full export/deletion payloads. Diagnostic and SDK error messages may include technical context needed to troubleshoot service issues. Development/debug environments may include more verbose diagnostics than production, but should still avoid logging secrets or raw purchase proofs.

16) Community and Social Platforms

Your participation in official community channels (including Discord, YouTube, X, Facebook, TikTok, alienbloom.com, and any other official channels) must comply with:

- These Terms

- Any channel-specific community guidelines we publish

- The applicable third-party platform rules/terms

We may moderate, limit, or remove content and/or access in our channels to protect community safety and service integrity.

17) Feedback and Suggestions

If you choose to share feedback, ideas, suggestions, or feature requests, you allow Bestwood to use them to improve, develop, market, and operate Alien Bloom without compensation or obligation to you. You understand that we may use similar ideas or features in the Game, even if they are based on or similar to feedback you provided.

18) Third-Party Services and Terms

Alien Bloom may rely on or interoperate with third-party services and platforms, depending on build/platform and where enabled, including Microsoft PlayFab, Microsoft Azure services, the Unity game engine/runtime, Unity In-App Purchasing used to integrate supported storefront purchases, Apple, Google, Steam, Discord, YouTube, X, Facebook, and TikTok. Other Unity Services packages may be present in the project; a Unity dashboard service is relevant to these Terms only if it is initialized and used to provide the Game or process player data.

Your use of third-party platforms may also be governed by their separate terms and policies. Bestwood is not responsible for third-party services beyond our control.

19) Privacy Policy

Our Privacy Policy Version 1.1 explains how we collect, use, disclose, retain, export, and delete information related to Alien Bloom.

Our Privacy Policy is available at https://sites.google.com/view/alienbloom/home and, where provided, in-game. This is the canonical public Privacy Policy and privacy-request page unless we publish a replacement URL.

The Privacy Policy also describes how we handle account identifiers, Alien ID, Commander ID/effective display identity, effective/original account relationships, hashed platform identity and alias metadata, linked-device records, link-code records, active-session records, authentication/session artifacts, rate-limit/cost-guard records, operational analytics, diagnostics, security logging, in-app purchases, entitlements, consent records, account lifecycle records, verified linked-account export and deletion, international transfers, and applicable privacy rights request workflows.

20) Service Changes, Maintenance, Outages, and Discontinuation

To the fullest extent permitted by applicable law, we may update, change, suspend, limit, or discontinue any part of Alien Bloom or related services at any time, including for maintenance, security, technical migration, legal/platform requirements, or business reasons.

We do not guarantee continuous availability, uninterrupted uptime, or error-free operation.

21) Disclaimer of Warranties

To the fullest extent permitted by applicable law, Alien Bloom and related services are provided "as is" and "as available," without warranties of any kind, express or implied, including implied warranties of merchantability, fitness for a particular purpose, non-infringement, and availability.

Some jurisdictions do not allow exclusion of certain warranties, so some exclusions may not apply to you.

22) Limitation of Liability

To the fullest extent permitted by applicable law, Bestwood and its affiliates, licensors, service providers, and partners will not be liable for indirect, incidental, consequential, special, exemplary, or punitive damages, or for loss of data, progress, goodwill, or virtual content, arising from or related to your use of Alien Bloom.

To the fullest extent permitted by applicable law, total aggregate liability for claims arising out of or relating to these Terms or Alien Bloom will be limited to the greater of: (a) amounts you paid to Bestwood for Alien Bloom in the 12 months before the claim; or (b) US $50.

Nothing in these Terms excludes liability that cannot be excluded or limited under applicable law.

23) Mandatory Rights Savings Clause

Nothing in these Terms limits or excludes consumer rights or remedies that cannot be waived, restricted, or excluded under applicable law.

24) Intellectual Property

Alien Bloom, associated names/logos, and all related game content and technology are owned by Bestwood Studios LLC and/or its licensors and are protected by applicable intellectual property laws.

"Alien Bloom" is a trademark of Bestwood Studios LLC.

Certain game technology associated with Alien Bloom is protected by U.S. Patent No. 11,623,132.

Except for the limited license granted in these Terms, no rights are granted by implication, estoppel, or otherwise.

25) Governing Law

These Terms are governed by the laws of the State of Florida, United States, without regard to conflict-of-law principles, except where mandatory law in your jurisdiction requires otherwise.

26) Dispute Resolution

If you have a dispute with Bestwood related to Alien Bloom or these Terms, you agree to first contact us at alienpokerhelp@gmail.com and attempt to resolve the dispute informally.

If the dispute cannot be resolved informally, either party may pursue available remedies in a court or other forum with jurisdiction, subject to applicable law.

Nothing in these Terms limits rights or remedies that cannot be waived under applicable law.

27) Severability

If any provision of these Terms is held invalid or unenforceable, that provision will be interpreted to reflect the parties' intent to the maximum extent permitted, and the remaining provisions will remain in full force and effect.

28) Changes to These Terms

We may revise these Terms from time to time.

When we do, we will update the Effective Date and/or Version and publish the updated Terms through appropriate channels (for example, in-game notice, website update, store listing update, or similar methods).

Your continued use of Alien Bloom after updated Terms become effective constitutes acceptance of the updated Terms, to the fullest extent permitted by applicable law.

29) Contact

Bestwood Studios LLC

Email: alienpokerhelp@gmail.com

30) Acceptance of Terms

By accessing or using Alien Bloom or related services, you acknowledge that you have read, understood, and agree to these Terms.

Acknowledgments & Third-Party Licenses 

Music

Alien Bloom uses music made available by independent artists through OpenGameArt.org. We are grateful to these artists for sharing their work with the game development community.

"Action synth track" / "Notathing2"

Artist: PetterTheSturgeon

Source: OpenGameArt.org

URL: https://opengameart.org/content/action-synth-track

License used: CC-BY 4.0

Attribution notice: "Feel free to use and share anywhere, but note me, if you using it :D"

"Cyberpunk Moonlight Sonata"

Artist: Joth

Source: OpenGameArt.org

URL: https://opengameart.org/content/cyberpunk-moonlight-sonata

License: CC0

Attribution notice: Attribution appreciated, but not required

"A Flawless Getaway"

Artist: vitalezzz

Source: OpenGameArt.org

URL: https://opengameart.org/content/a-flawless-getaway

License: CC0

Attribution notice: Vitalezzz - A Flawless Getaway

"Downfall"

Artist: vitalezzz

Source: OpenGameArt.org

URL: https://opengameart.org/content/downfall

License: CC0

Attribution notice: Vitalezzz - Downfall

"Neural Malfunction"

Artist: vitalezzz

Source: OpenGameArt.org

URL: https://opengameart.org/content/neural-malfunction

License: CC0

Attribution notice: Vitalezzz - Neural Malfunction

"Persevere"

Artist: vitalezzz

Source: OpenGameArt.org

URL: https://opengameart.org/content/persevere

License: CC0

Attribution notice: Vitalezzz - Persevere

"Alert! Outsider!"

Artist: Alexandr Zhelanov

Source: OpenGameArt.org

URL: https://opengameart.org/content/alert-outsider

License: CC-BY 3.0

Attribution notice: Alexandr Zhelanov https://soundcloud.com/alexandr-zhelanov

Thank you to the artists above for making their work available to developers!

Exo 2

Font designed by Natanael Gama

License

Copyright 2013 The Exo 2 Project Authors (https://github.com/googlefonts/Exo-2.0)

This Font Software is licensed under the SIL Open Font License, Version 1.1 . This license is copied below, and is also available with a FAQ at: https://openfontlicense.org

SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007

PREAMBLE

The goals of the Open Font License (OFL) are to stimulate worldwide development of collaborative font projects, to support the font creation efforts of academic and linguistic communities, and to provide a free and open framework in which fonts may be shared and improved in partnership with others.

The OFL allows the licensed fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. The fonts, including any derivative works, can be bundled, embedded, redistributed and/or sold with any software provided that any reserved names are not used by derivative works. The fonts and derivatives, however, cannot be released under any other type of license. The requirement for fonts to remain under this license does not apply to any document created using the fonts or their derivatives.

DEFINITIONS

"Font Software" refers to the set of files released by the Copyright Holder(s) under this license and clearly marked as such. This may include source files, build scripts and documentation.

"Reserved Font Name" refers to any names specified as such after the copyright statement(s).

"Original Version" refers to the collection of Font Software components as distributed by the Copyright Holder(s).

"Modified Version" refers to any derivative made by adding to, deleting, or substituting -- in part or in whole -- any of the components of the Original Version, by changing formats or by porting the Font Software to a new environment.

"Author" refers to any designer, engineer, programmer, technical writer or other person who contributed to the Font Software.

PERMISSION & CONDITIONS

Permission is hereby granted, free of charge, to any person obtaining a copy of the Font Software, to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software, subject to the following conditions:

Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.

Original or Modified Versions of the Font Software may be bundled, redistributed and/or sold with any software, provided that each copy contains the above copyright notice and this license. These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user.

No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users.

The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission.

The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.

TERMINATION

This license becomes null and void if any of the above conditions are not met.

DISCLAIMER

THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.