Tamerra privacy notice

Who is responsible

Publisher in Google Play: VISION GAME STUDIOS
Privacy contact: [email protected]
Contact address: Herzog street, Kiryat Ata, Israel
Telephone: +972536555557

VISION GAME STUDIOS (Vision) is the publisher name used for Tamerra. The contact address, phone and email on this page are the service contact for the app and its three connected editions. Identify the edition concerned so support can locate the correct account records.

The services this notice covers

Tamerra connects to the existing game edition you select: Israel / Hebrew (pokemon-battle.net), America / English (pokemonworld.net), or Japan / Japanese (pokemon-arena.net). This notice covers the Android app and the game pages it opens.

Accounts and saved progress belong to the selected edition. Choosing an edition does not identify your physical location or move your account between services. The app does not automatically use one edition’s account information to sign in to another edition.

Current releases and age checks

This notice covers the current Google Play internal-test build 1.0.8 (code 9) and the separate direct-download Android beta 1.0.9 (code 10). Both builds include age checks. An intended future audience of 6 and over does not mean that access for children under 13 is available.

Both covered builds include an age-band screen. Each stores a coarse band on the device, without asking for a full birth date. For bands 6–8 and 9–12, an anonymous assessment request can create a server record with the band, a hashed access token and timestamps; the access token expires after 30 days and an assessment lease after five minutes. This record has no account or parental contact. A temporary rate-limit record uses a hashed IP-derived key and request counts; ordinary hosting access logs can also receive IP and request information. Token expiry prevents its use and does not prove that the row or logs have been deleted. A cleanup schedule has not yet been enabled.

Neither covered build sends a family-assessment request for the under-6 band. Both block under-13 gameplay and do not open the gameplay WebView or payment SDK for those bands. When an eligible signed-in user is bound to the age check, the selected service can record the account ID, coarse band, guardian-status field, policy version and timestamps. These safeguards are not a completed parental-consent service.

Account and game information

When you sign in, your username or email and password are sent to the selected service. An authenticator code is also used when your account requires it. The service maintains account identifiers, usernames, email where supplied, password hashes, authentication records and game progress. In direct beta 1.0.9, registration and guest play are available inside the app. Registration sends a username, email, password, chosen starter and an arithmetic verification answer to the selected game service. Starting as a guest creates a server account with a generated identifier and saved game progress without requiring an email. Saving a guest account sends a username, email and password and attaches them to the same account and progress. These requests use session credentials. Starting a guest also sends an onboarding identifier to prevent duplicate guest creation.

Game information includes your collection, inventory, currencies, quests and battle outcomes. The app remembers your selected edition and protects session credentials using secure storage on your device. Coordinates on the LIVE map describe the fictional game world, rather than your GPS position.

Support and privacy requests

Support and privacy requests can include your name or account identifier, contact email and message. A deletion request includes the account identifier, reply email, optional details and acknowledgement. A signed-in request is linked to the account shown on the form.

Submitting a deletion request creates a reference for review. It does not immediately delete an account or confirm that an anonymous requester has identified an existing account. Signing out or uninstalling Tamerra does not delete the account or its saved data.

Connection, security and usage information

The connected services receive IP addresses, browser or device request information, timestamps and session activity. They maintain security and game-action records and can estimate a country from network information.

Account and game information is used to authenticate players, operate the game and save progress. Social content enables communication. Support requests, safety reports and security records help handle requests and investigate misuse.

The app connects to its selected game service over HTTPS. Passwords are stored as hashes by the account service. Access to private request and moderation records is restricted to authorized administrators.

Analytics and your choices

Connected game pages include account-linked analytics and gameplay or interaction metrics. These are not treated as anonymous merely because the app has no advertising-ID permission.

Game metrics measure visits, game activity and feature use; advertising supports some guide pages. Optional profile content and social messages are supplied when those features are used. AI NPC chat processes what you write and recent history to answer you. Manual or enabled automatic translation can send message text to translation providers, and GIF searches send your query to GIPHY. Do not put sensitive personal information in chats, AI messages or search terms. The app has no single switch that disables every collection mechanism on connected pages. Both covered builds suppress the shared analytics/ad loaders for their family/native mode; local security or game records can still be kept. Browser/device settings may limit storage and can affect sign-in.

Service providers and disclosures

Requests for externally hosted artwork, audio or GIFs disclose the network information needed to deliver those resources. The details below explain who receives information and for what purpose.

Connected game pages use Google Analytics for account-linked usage and interaction information, and some guide pages use Google advertising. Shared analytics and advertising loaders are suppressed for the family/native mode used by both covered builds; this does not guarantee that every other third-party request or local log is disabled. AI NPC conversations send the current message and recent conversation history to Anthropic to generate a reply; the game also stores conversation and usage/security logs linked to the account and IP. Text translation sends the selected text and language information to Google Translate, with MyMemory as a fallback, and caches results locally. GIF search sends search terms to GIPHY. External image, audio, GIF and font hosts receive the connection information needed to serve resources. Messages emailed to support pass through Google Gmail, including their body, attachments and email metadata. PayPal and Stripe process existing website payments; related transaction records remain with the game. Public messages and profile fields are also disclosed to other players.

Purchases and advertising

Purchase history can include the account, package or item, amount and currency, transaction identifier, status and time. The details below describe the purchase and advertising features included in the covered release.

Cash purchases are disabled in the Google Play internal-test 1.0.8 build (code 9) and the separate direct-download 1.0.9 beta (code 10). Neither build initializes Google Play checkout or offers website cash checkout inside the app. Existing balances, items and historical purchase records remain associated with the selected game account. Connected accounts can contain records of existing PayPal and Stripe payments made on the game websites. Google Play purchases remain under development and no successful purchase test is claimed here. If later enabled, Google would process payment and the selected edition would receive the purchase token, product, order/status and an identifier derived for that edition to verify delivery and prevent replay. Shared analytics and advertising loaders are suppressed in the family/native mode of both builds, but other external resources and local game/security logs can still be used. Absence of an Android advertising-ID permission does not prevent web resources from receiving connection information.

How long information is kept

This section explains when information is removed and any information retained after account deletion.

Accounts, saved progress and related data remain while the account is used to provide the service. After a verified account-deletion request is carried out, the approved policy is to remove the remaining account data, including associated profile, social and usage data. Only payment records required by law and the minimum records needed for a specific fraud investigation or dispute may be retained for those purposes. Those exceptions do not justify keeping the whole account or indefinite retention: the applicable legal obligation or documented investigation/dispute determines when the remaining records can be removed. Support handles deletion manually and confirms the outcome and any justified exceptions; submitting a request is not confirmation of erasure. The actual backup rotation and deletion schedule has not yet been confirmed, so no fixed backup-erasure deadline is promised. Ask support about the status of a specific request, including copies held by service providers and backups.

Access, correction and deletion

Use the account and data deletion page for the edition holding your account. If more than one edition holds your information, identify each affected edition. Do not send passwords, authenticator codes, card details or identity documents through ordinary support messages.

You can ask for access, correction, or deletion through [email protected] or the account-deletion request page for your game edition. State which edition and account your request concerns. We handle requests manually and may ask for information necessary to verify that the account belongs to you or that you are authorized to act for its owner. Sending the form creates a request; it does not immediately erase an account. Do not send your password. Parents can also contact this address about a child’s information.

Account and data deletion

Audience

Google Play’s current internal-test build is Tamerra 1.0.8 (version code 9); its closed-test submission is in Google review. The initial Play audience is configured as 18+ only, with availability restricted for users Google identifies as minors. This saved declaration awaits Google review; it is not a claim of public-release approval or complete age verification. The separate direct-download Android beta is 1.0.9 (version code 10). Both builds ask for a coarse age group and block under-13 login and gameplay; the native age check does not block ages 13–17 solely because of age. The ordinary browser games’ terms remain 13+ with parental permission for players under 18. A future audience of ages 6 and over is intended; the parental-authorization service and under-13 gameplay are not available yet. Selecting an older age or possessing an account is not parental consent. Contact support if a child has provided information. Parents may request review, deletion and an end to further collection.

Changes to this notice

The effective date and version at the top identify this notice. Changes to the covered services and their use of information will be reflected in an updated notice.