TamerCorePRIVACY
Back to TamerCore
PRIVACY

Minimal data by default.

TamerCore is designed around a TamerCore account, optional cloud save, and owner-authorized Palworld server connections. It does not include advertising or third-party analytics in the current release.

What TamerCore stores on your device

  • Your TamerCore map access token is kept in session storage so it can authorize the current browsing/app session.
  • Your personal completion tracker โ€” seen/caught Pals, obtained/crafted items, unlocked technology and defeated bosses โ€” is cached locally and can sync to your TamerCore Cloud account when signed in.
  • Map-layer and interface preferences may be stored locally so the app remembers your choices.
  • Your Breeding Box, passive-trait notes, saved breeding goals and hatch log are cached locally and can sync to your TamerCore Cloud account when signed in.
  • If you unlock TamerCore Server Unlock controls, the separate owner control code is stored only in session storage for the current app/browser session.

Guest access & notifications

Server owners can provide a separate read-only guest access code for live player locations and shared map pins. Guest sessions cannot edit shared pins or unlock server administration. TamerCore can show in-app alerts for player joins, player leaves and live-server availability. Browser/device notifications are opt-in and can be disabled in the notification center.

Live server information

When connected to an authorized Palworld server, TamerCore can receive and display server-provided player information such as display names, character levels, network latency and in-game map coordinates. This live snapshot is used to render the map and is not saved as personal progress by the TamerCore web client.

TamerCore Server Unlock

The Server Unlock is a one-time, non-consumable purchase rather than a recurring subscription. Google Play purchase receipts are verified by TamerCore Cloud before a permanent entitlement is granted. When the server owner unlocks server controls, the app can request server health metrics, edit an allowlisted set of Palworld settings, create server-side save backups, send announcements, moderate online players, and start, stop or restart the configured Palworld server. Palworld administrator credentials remain on the server backend and are not sent to the mobile/web client.

Shared pins

If you create a shared map pin, its name, icon, coordinates and generated identifier are stored on the TamerCore server so other authorized users of that server can see it. Shared pins remain until an authorized user removes them or the server operator clears them.

Advertising & analytics

The current TamerCore release does not embed ad networks or third-party analytics SDKs. If that changes, this policy and the relevant store privacy disclosures must be updated before release.

Device permissions

The current TamerCore experience does not request camera, microphone or device geolocation access. Its live coordinates are Palworld in-game coordinates supplied by the connected game server, not your phone's physical location.

Deleting your data

You can reset personal completion data from TamerCore's Progress screen. You can also clear TamerCore site/app storage to remove locally stored settings and access-session data. Shared pins can be removed from their map popup by an authorized user.

Accounts, linked platforms & children

TamerCore accounts support cloud save, server membership, invitations, device notifications and permanent purchase entitlements. Google/Google Play, Steam, Xbox, PlayStation and Discord identities may be linked to a TamerCore account when the user chooses. TamerCore is not presented as a children's app and does not knowingly collect child-directed profile information.

Payments & policy changes

Android purchases of the digital Server Unlock use Google Play Billing. TamerCore Cloud stores the normalized entitlement and a hashed purchase-token record for fraud prevention and purchase restoration. Store privacy disclosures will be kept aligned with the submitted build whenever data practices or device permissions change.

Last updated: August 29, 2026Legal & attribution ยท App