Skip to content
AboutMusicGamesProjectsSay hello ↗
Home/Games/Tikal: Jade Guardians/Privacy Policy

Tikal: Jade Guardians · Player information

Privacy Policy

Play the campaign, create a battlefield, or join the Waykeepers. Here is how your information is handled along the way.

Effective October 29, 2026Updated October 29, 2026
Privacy Policy ↗Terms and Conditions ↗

On this page

  1. Developer and scope
  2. Saves and settings on your device
  3. Community account information
  4. Creations, gameplay, and community activity
  5. Connection and support information
  6. Why we use information
  7. Service providers and sharing
  8. Advertising, analytics, and permissions
  9. Purchases, restoration, and video rewards
  10. How long information is kept
  11. Delete your account or data
  12. Your choices and privacy rights
  13. Children and young players
  14. Security
  15. Policy updates and contact

At a glance

Campaign saves and settings are stored on your device. Community features use account information, shared creations, and gameplay records. Android and iOS builds may include store purchases, optional rewarded ads, ads between completed missions, and usage analytics. Availability and privacy choices depend on your build and region.

Delete your account or data ↗

1. Developer and scope

Tikal: Jade Guardians (Tower Defense) is developed and provided by Gilberto Avalos Osuna, based in Guadalajara, Mexico. In this policy, “we” and “us” refer to the developer. Contact us at avalos@indiefy.net for privacy questions or requests.

This policy covers the game’s browser, iOS, and Android builds when made available, its connected community service, its pages on gilbertoavalos.com, and related support correspondence. The game is in development. Features described here depend on the build and whether a community service is available. Jade Guardians accounts are separate from accounts for Tikal Online and other Tikal games.

2. Saves and settings on your device

The game stores campaign progress, earned stars, guardian and tower selections, saved battles, language, sound and accessibility preferences, Forge drafts, bookmarks, and cached community maps or campaigns on your device. It may use the device or browser language to select the initial interface language. A sign-in session is also stored locally when you use an account.

The campaign and local Forge can be used without a community account. Browser builds may cache game files for offline use. When signed in to a connected service, campaign progress and bookmarks can be synchronized with your account. Local Forge drafts are sent to the service when you choose to save them online or publish them.

A connected build may request community availability and public maps when it opens, even before you sign in. Consequently, playing without an account does not mean a connected build never makes network requests. Offline play does not send new gameplay records until a connection is available and an online feature submits them.

3. Community account information

If you create an email-and-password account, the service handles your email address, chosen display name, account identifier, account creation time, and authentication information. The current built-in sign-in system stores a salted password hash rather than a readable password. Your email address and password hash are not included in public creator profiles or rankings.

Some builds may use Firebase Authentication instead of built-in sign-in. When enabled, Firebase processes sign-in information and the game uses the resulting account identifier and authentication token. The sign-in options shown in that build determine which provider you use. The present game does not offer advertising-based sign-in or combine Jade Guardians accounts with the Tikal Online account system.

4. Creations, gameplay, and community activity

Connected features handle maps and campaigns you save online, including titles, descriptions, terrain, routes, waves, events, publication versions, timestamps, creator attribution, and remix source references. To verify a creation or a ranked result, the game sends the selected guardian, battle commands, scenario or campaign version, and simulation timing. The service computes results such as lives preserved, completion time, and remaining gold.

The service also handles synchronized progress and bookmarks, followed creators, ratings, blocked creators, and reports you submit. Reports include the relevant map, your account identifier, your stated reason, and the submission time. These records support the feature you choose to use, score verification, discovery, and moderation.

Your display name, creator identifier, published creations, remix attribution, and eligible ranking results can be visible to other players. Public listings may include aggregate ratings, play counts, clear rates, and follower counts. Account credentials, individual block lists, and report text are not displayed as public profile information. Do not put private contact details or someone else’s personal information in a display name, map title, description, or story.

5. Connection and support information

Game-service and website infrastructure processes technical information needed to deliver requests, including IP addresses, requested routes, request times, browser or device request headers, response status, and operational errors. The current community server logs requests for operation and troubleshooting and uses request limits to reduce abuse. These logs are separate from advertising analytics.

If you contact us, we receive your email address, message, and any details or attachments you choose to send. We use them to answer questions, investigate problems, and handle privacy or safety requests. Send only what is needed; never send your password or sign-in token.

6. Why we use information

We use information to provide and secure accounts, restore and synchronize progress, save and publish creations, attribute remixes, verify clears and rankings, provide community discovery and social features, investigate reports, operate the service, and respond to support or privacy requests. These are the purposes of the features described in this policy.

Where applicable law requires a legal basis, processing may be necessary to provide requested services, based on legitimate interests in service reliability and abuse prevention, required by a legal obligation, or based on your consent where consent is required. Accepting game terms does not replace a separate consent that the law requires. We do not use these records to build advertising profiles or automatically add support contacts to a marketing list.

7. Service providers and sharing

We do not sell community-account records or player-authored maps. Published content and public player information are shared with other players as described above. Hosting and email providers process information needed to operate the service. Amazon Web Services delivers the project website. Depending on the build, Google provides Firebase Authentication, Firebase Analytics, AdMob advertising, consent messaging, and Google Play billing. Google may process advertising data under its own policies and the privacy choices applicable in your region. Apple processes iOS payments and supplies signed purchase, app-download and refund information used by our service to verify and restore access.

App stores and device-platform providers may separately handle downloads, purchases if offered, backups, or diagnostics under their own policies and your device settings. Following an external link takes you to a service with its own privacy practices.

We may disclose relevant information where required by applicable law or a valid legal request, or where reasonably necessary to investigate abuse or protect people and legal rights. Hosting, authentication, and email providers may process information outside your country, subject to applicable requirements for international data transfers.

8. Advertising, analytics, and permissions

Android and iOS builds that enable monetization integrate Google AdMob and the Google User Messaging Platform. The advertising service may process IP addresses, device and app information, advertising identifiers where permitted, consent choices, ad interactions, and estimated impression revenue. Ads are offered voluntarily for a disclosed mission attempt or between completed missions. Full-game owners do not receive ads. Google handles its processing under its privacy policies and applicable regional choices. The current iOS integration requests non-personalized ads and does not collect IDFA or request permission to track you across other companies’ apps and websites.

When configured, Firebase Analytics measures events such as app use, tutorials, mission starts and outcomes, store offers, and purchase or advertising events. You can turn off future usage analytics in Game settings. Advertising privacy options appear in settings when the consent service requires that entry point. Required regional messages are handled before ad requests. Changing analytics preferences does not erase necessary purchase, refund, reward-verification, or security records.

The game does not request precise location, contacts, camera, or microphone access. Gameplay replays verify game results. Project website pages do not use advertising trackers or third-party analytics cookies. Browser storage and caching support saves, preferences, sign-in, and offline files. Importing or exporting a Forge file does not grant general access to your files.

9. Purchases, restoration, and video rewards

Google Play handles Android payments. The game service receives and verifies purchase tokens, product and order identifiers, purchase state, and restoration or refund information. An installation identifier connects these records to your app without requiring a community account. We do not receive your full payment-card details. Original paid-app buyers can request restoration using their Google Play order number; support verifies the original order before granting access.

Apple handles iOS payments. Our service receives and verifies Apple-signed transaction and app-download information, including product and transaction identifiers, purchase or refund state, and the original app version used to restore earlier paid downloads. An installation identifier connects purchase and reward records without requiring a community account. In iOS it is kept in the secure Keychain and can remain after an app is uninstalled; this supports restoration when the app is reinstalled. Use Restore purchases with the Apple Account that made the purchase. We do not receive your Apple Account password or full payment-card details.

For rewarded videos, the service records the requested mission, daily allowance, signed ad-delivery confirmation, transaction identifier, and trial attempt. This delivers the promised reward once and preserves a suspended battle. Estimated advertising revenue is recorded separately from finalized store or advertising payments.

10. How long information is kept

Local saves and cached files remain until you remove the relevant app or browser data. Online account information, cloud progress, saved creations, and associated community records remain while needed to provide those features and until the relevant content or account is deleted. The current service does not automatically erase an account merely because it has been inactive.

Support correspondence and operational logs are retained only as needed to handle the issue, maintain service security, and meet applicable legal obligations. They are handled separately from the game-account deletion action. If specific information must be retained for a legal obligation or an ongoing dispute, we will limit it to that purpose and explain the applicable exception when responding to your request. Copies downloaded or remixed by other players and backups controlled by your device or platform may need to be managed separately.

Purchase and entitlement records are retained as needed to restore access, process refunds, prevent duplicate rewards or fraudulent claims, and meet legal obligations. These records are separate from community-account deletion. Contact us to exercise applicable rights over installation or purchase records; Apple and Google may independently retain their billing or advertising records under their own policies.

11. Delete your account or data

In a connected game build, sign in, open your player profile, choose “Delete account and published content,” and confirm “Delete account permanently.” An internet connection is needed to complete this action. This removes the account and associated cloud progress, owned community maps and campaigns, submitted results, ratings, follows, and reports from that service. If Firebase Authentication is enabled, the game also requests deletion of that authentication account.

You can also request account or data deletion without opening the game: email avalos@indiefy.net with the subject “Tikal: Jade Guardians — account deletion.” Include your display name and the email address used for the account, preferably writing from that address. If you used a different sign-in method, describe it. We may ask for information reasonably necessary to verify ownership; do not send a password. We will respond within the period required by applicable law.

Deletion is permanent and removes your published originals from the service. Campaigns that rely on removed originals may also become unavailable. It cannot recall files already downloaded by other people or automatically erase independently saved remixes. Contact us if a retained copy contains personal information you want addressed.

Deleting the online account does not erase local campaign progress or Forge drafts. To remove those, clear the game’s site data in your browser or its app storage through your device settings. Deleting an iOS app removes its local app data; offloading can preserve it. Manage device or cloud backups separately. Clearing local storage or uninstalling the game alone does not delete an online account.

12. Your choices and privacy rights

You can use the offline campaign and local Forge without an online account, choose what to publish, change your display name in your profile, manage local data, and request deletion. Export a Forge creation before removing data if you want to keep your own copy.

Depending on applicable law, you may request access, correction, cancellation or deletion, or object to processing of personal information. These include the access, rectification, cancellation, and opposition rights known as ARCO in Mexico. Other applicable laws may provide rights to restrict processing, receive a portable copy, withdraw consent, or complain to a competent data-protection authority.

Send requests to avalos@indiefy.net with the subject “Tikal: Jade Guardians — privacy request,” explain what you want to exercise, and identify the relevant account or information. You or an authorized representative may submit a request. We may seek proportionate proof of identity or authorization and will explain any lawful restriction on the request. Withdrawing consent does not affect processing that was lawful before withdrawal.

13. Children and young players

The connected account and publishing features are intended for players aged 13 or older, or the higher minimum age required to use those features in their country. Players who cannot agree independently must have a parent or legal guardian’s permission. The game’s distributor age rating and local rules also apply; a content rating does not by itself authorize a child to create an account.

We do not knowingly collect community-account information from children below the applicable minimum age. If you believe a child has provided such information, contact avalos@indiefy.net so we can investigate and remove it where required. A parent or guardian may use the privacy-request process on behalf of a child.

14. Security

The current service uses authenticated account actions, password hashing for built-in sign-in, restricted moderator access, and request limits. Keep your device, sign-in details, and exported files secure. No method of storage or transmission can guarantee absolute security. Community services should be accessed through the secure connection supplied by the game build.

15. Policy updates and contact

We will update the effective and updated dates on this page when this policy changes. Material changes will be communicated through the game or another appropriate channel when required. New practices, including new authentication providers, purchases, analytics, or advertising, will be described before they are introduced and any required consent will be requested.

For questions about this policy or the handling of your information, contact Gilberto Avalos Osuna, Guadalajara, Mexico, at avalos@indiefy.net.

Back to Tikal: Jade Guardians ↗
Privacy Policy ↗Terms and Conditions ↗

Have something in mind?

Let’s make
something happen.

↗
© 2026 Gilberto Avalos
LinkedIn ↗GitHub ↗Instagram ↗
Back to top ↑