Privacy

Signing in with Google

When you choose Google sign-in, Google confirms your identity. Pendekar stores your Google account identifier, your name and your verified email address when provided. We use these details to recognise your account when you return and show which account you are using.

Pendekar does not receive your Google password and does not store Google access or refresh tokens. Sign-in requests basic identity information; it does not request access to your Gmail, Drive or other Google content.

What other players can see

Completing your character setup automatically adds your chosen character name and joined date to the public Players directory. Your character identifier, appearance, overall level and total skill levels are also available through the public player service. Your Google name and email address are not included in that listing.

Where the player passport editor is available, you can optionally publish a bio, country and up to five social or website links. These details are public, are not copied from Google, and can be edited or cleared at any time. External links take you to other websites. Profile details are stored separately from adventure saves; protected backups may retain earlier copies.

In a shared multiplayer world, other players can see your player name, character appearance, equipment and movement. Chat messages you send are delivered to players in that world. Treat your character name and multiplayer chat as public information.

The map shows current online player positions throughout the selected World, including the mainland and Perhentian. Its public map feed contains only temporary connection identifiers, World, game area and tile position. It does not include account details, character identifiers, names, saves or movement history. Map updates pause when you close the map or hide the game tab.

Your character and cloud saves

Account play stores your character details and progress, including skills, inventory, equipment, quests and save timestamps. Saves are linked to your account so you can continue your journey after signing in.

Previous save revisions are kept as recovery history. The current game does not automatically prune that history. Your complete save, inventory and Google identity are not returned by the public player service.

On your browser

Guest adventures, your guest name and game preferences are saved in browser storage. Account play also keeps setup drafts, pending saves and recovery copies on your device. Bringing a guest adventure into an account is an explicit choice; the original guest save and a separate local backup are kept.

Links from the old game address or the www address can carry your guest save, name and settings to pendekar.io in a temporary URL fragment. Existing data on pendekar.io takes precedence. The transfer does not include account sessions or account drafts.

Sign-in uses cookies to connect the Google login to your browser and keep you signed in. The server stores a hashed session token and expiry details. Browser session storage also distinguishes pending saves in different game tabs.

Services the game uses

Cloudflare hosts the website, account database and multiplayer rooms. Google provides sign-in and the fonts used by the website. Game and character views load the Three.js library from Cloudflare’s cdnjs service.

When you first interact with the loaded game, we record first and latest play times to estimate how many players have played. A random browser cookie lasts up to one year; the database stores a hash of that identifier. When you sign in, we link prior guest play on that browser to your account to reduce double-counting. These records are retained for cumulative player counts and contain no IP addresses or browser fingerprints. Clearing cookies or changing devices can affect the guest count.

While the game is open, periodic activity reports record session times, recent activity or idle status, the game area and cloud-save status. Signed-in sessions are linked to your account and character; guests use the random browser identifier above. These records help the project owner monitor the game and investigate save problems through a private dashboard. The dashboard shows 90 days of detailed sessions and events. Older monitoring records are removed in hourly batches; cumulative player counts remain. The shared game servers also record connections and disconnections, including older game clients. Save-service confirmations and failures, startup and device-storage problems, and logout save outcomes include limited diagnostic codes and revision references. A bounded browser queue retries recent diagnostic events; room queues retry delivery independently. The owner can see recording health and alerts. Activity reports do not include chat text, full saves, IP addresses or browser fingerprints. Recording failures do not prevent play.

Cloudflare Web Analytics collects website usage and performance measurements.

The game also reports structured gameplay actions, such as fishing attempts and catches, cooking, crafting, combat, trading, travel and quest steps. Reports include the action, outcome, game area, item or step identifier, quantity and reported action duration, linked to the session and character. They help the owner understand which activities players use and investigate possible problems. Detailed action records are kept for 90 days and removed in hourly batches. Daily totals and pseudonymous participant records are retained for longer-term trends. Reports are observations from the browser and can be incomplete; reporting failures do not prevent play or saving.

From 11 October 2026, newly loaded game tabs also report game clicks, including mouse, touch and keyboard button activations, and the time between consecutive recorded clicks and game action phases. Reports contain the game area, a general world/interface category, input type, browser-reported occurrence time and elapsed gap. They restart when a tab resumes or its account, character or session changes. We do not collect typed text, chat, form values, click coordinates or page text. These observations are linked to the existing session and account for the owner’s private activity dashboard. Detailed input records are kept for 90 days; compact daily click totals and timing aggregates are retained for longer-term trends. Earlier activity is not backfilled. Reports can be incomplete or lost, and they do not determine player progress or prevent play and saving.

The owner can request an AI summary using Cloudflare Workers AI. Only aggregate activity counts, dates and known activity or area labels are sent to the model, without player names, account or character identifiers, email addresses, chat text or complete saves. Summaries are saved in the private dashboard as suggestions for the owner; they do not change your character or progress.

These providers receive the connection and request information needed to provide their services, such as your IP address and browser details. Account and save data are processed by the hosting service; Google handles the sign-in process.

Your choices and contact

You can browse the website without signing in. Playing starts with Google sign-in; existing adventures saved on your device can be brought into your account during character setup. Account and in-game backup controls let you download your saved character or a device copy. Signing out ends this browser’s login without deleting your character or local saves.

Clearing the site’s browser data removes local saves, preferences and recovery copies. It does not delete your cloud account or its history. There is currently no account-deletion button in the game.

For privacy questions or requests about your data, contact the project owner:

Optional public playtime

We count observed active play for each signed-in character from the start of playtime tracking. Overlapping tabs are counted once; hidden and idle periods are excluded. Durable totals remain after the 90-day activity history expires. In your ID book, you can choose whether to show whole minutes and the tracking start date publicly. This is off by default; switching it off removes these values from public responses. Your public passport shows character identity, levels and earned town stamps, never your inventory, stored possessions, account details or current location.